A shipment can be sitting at a carrier's terminal for six hours longer than expected and nobody in dispatch finds out until a customer calls asking where their delivery is, because the milestone event that should have triggered an alert never made it across the EDI connection cleanly. Carrier integration is usually treated as a one-time setup task, but the real work is in what happens when an event gets dropped, arrives out of order, or never gets sent at all. A system that only works when every message arrives perfectly is not actually integrated, it is just hopeful. See carrier milestone integration running against your own shipment data.
Know Where Every Shipment Is, Even When a Message Drops
iFactory AI maps carrier EDI and API events to pickup and delivery milestones, with missing-event alerts and automatic retry so a dropped message never means a blind spot.
Two Protocols, One Milestone Map
Different carriers send shipment status through different formats, some over traditional EDI transaction sets and others through a modern REST API, and the integration challenge is not connecting to either one, it is mapping both of them to the same consistent set of milestones so a dispatcher never has to know which protocol a particular carrier happens to use.
| Source | Typical Format | Mapped Milestone |
|---|---|---|
| EDI 214 | Fixed-format transaction set | Shipment status update |
| EDI 990 | Fixed-format transaction set | Load tender response |
| Carrier REST API | JSON webhook or polling response | Pickup, in-transit, or delivery event |
| Manual status update | Dispatcher-entered fallback | Any milestone, when no automated event arrives |
The Milestones That Matter
Regardless of source protocol, every shipment is tracked against the same core sequence of events.
Map Your Own Carrier Events
Book a 30-minute session and see your carrier EDI and API feeds mapped to a consistent milestone view.
When a Message Drops
The real test of carrier integration is not the happy path, it is what happens when an expected event never arrives.
Rolling Out Across Your Carrier Base
iFactory AI connects to each carrier's existing EDI or API feed, building the milestone map incrementally as carriers are added.
Reconciling Against the Carrier's Own Record
Automated retry closes most gaps on its own, but a small number of events need a final reconciliation step against the carrier's own system of record before a shipment's milestone history can be considered complete.
Retry Succeeds
The dropped event is recovered automatically on a later attempt, no manual step needed.
Retry Exhausted
After repeated attempts fail, the gap is flagged for manual reconciliation.
Carrier Portal Check
A dispatcher confirms the actual status directly against the carrier's own tracking portal.
Record Closed
The milestone is entered manually and the shipment's timeline is marked complete.
Integration Coverage Across a Carrier Base
A composite view across carrier groups, scored by how reliably events are arriving without needing manual reconciliation.
Expert Review
The carriers worth integrating first are usually not the ones with the cleanest EDI feed, they are the ones currently generating the most manual status-check calls into dispatch, since that is where a missing-event alert replaces the most repetitive work immediately.
Frequently Asked Questions
Does this support both EDI and API carriers at once?
Yes, both protocols map to the same milestone structure, so dispatch sees one consistent view regardless of which format a given carrier uses. Support can confirm compatibility with your specific carriers.
What happens when a carrier's event arrives out of order?
Events are reconciled against the shipment's own timeline rather than assumed to be sequential, so a late-arriving but earlier-timestamped event is placed correctly rather than treated as the newest status.
How is a missing-event alert threshold set?
Thresholds are tuned per carrier based on that carrier's typical reporting cadence, so a carrier with naturally sparser updates does not generate constant false alerts. See threshold tuning on a call.
What happens if a carrier connection fails entirely?
Failed connections are retried automatically, and if a gap persists, dispatch is alerted so a manual status check can be initiated rather than the shipment going untracked.
Can this integrate with our existing TMS or dispatch system?
Yes, mapped milestones are available to your existing transportation management or dispatch system rather than requiring a separate tracking interface. Ask support about your specific TMS integration.
Never Lose a Shipment to a Dropped Message
iFactory AI maps every carrier's EDI and API events to one consistent milestone view, with alerts and retry built in. Book a demo on your own carrier feeds.
