Skip to content

Systems

EDI 214 status messages: four reasons ETAs go wrong

Four failures between a carrier's system and your screen, and what to show beside every ETA.

Computing America. Applications, integrations, data analysis and AI/ML engineering.

Send the messages
5 min readComputing America
A sealed semi trailer backed against a closed loading dock door at dawn.

In short

  • A 214 reports a status somebody entered, at most with a location attached to that status. Treating it as a position feed is a root cause of ETA defects.
  • X12 standardizes the code list, not the carrier state behind each code. Each trading partner maps its internal statuses onto the list differently, so the mapping belongs in data you can edit, not in code you have to redeploy.
  • Status messages arrive late, out of order and duplicated. A shipment view built on last-write-wins will show an arrived load as in transit.
  • Every ETA a customer sees needs an age and a source attached.
  • The fix is an append-only event log per shipment with both the observed time and the received time recorded, and a derived view on top. Correcting history stops being a data-repair ticket.

ETAs built on an X12 214 (opens in a new tab) go wrong because a 214 reports a status a carrier’s system recorded, not a live position. It can carry a location, but only as city and state or longitude and latitude in an MS1 segment (opens in a new tab) attached to a status event. Four failures follow from reading it as more: a timestamp without its zone, a status code whose meaning varies by partner, messages that arrive late, twice and out of order, and an ETA with no computation behind it.

The symptoms are familiar. A portal says the load is two hours out and it arrives the next morning, or one screen shows a shipment delivered while another shows it in transit. The integration is usually doing exactly what it was told: it carries a status at a time the carrier believes, for a stop the carrier names in its own vocabulary.

Fig. 1
  1. Group: Set by the carrier

    Carrier's system

    Failure 2: same code, different meaning

    • To 214 message
  2. Group: Set by the carrier

    214 message

    Failure 1: a time without its zone

    • To Delivery to you
  3. Group: Shared: queues, intake

    Delivery to you

    Failure 3: late, duplicated, out of order

    • To Your screen
  4. Group: Yours alone

    Your screen

    Failure 4: an ETA with no computation behind it

Failures 1 and 2 start at the carrier, failure 3 in the queues between carrier and your intake, and only failure 4, the ETA on your screen, is entirely yours.

SourceData path as described in this article; the numbered failures match its sections.

Before the four: match the shipment

One thing has to work before any of the four can matter, and it fails silently. A status message identifies its shipment by whatever reference the carrier holds: a pro number, a bill of lading or your order number, often a different one per partner. When the reference doesn't match, the event attaches to nothing, and an integration may discard it. No one notices, because a shipment with no updates looks like one with nothing to report. Match on more than one reference, route failures to a queue a person can see, and watch its size. A jump in it can be the first sign a partner changed something.

Failure one: the timestamp does not mean what the column says

Check first for a local time stored as if it were absolute. A status event carries a time and, separately, a time code for its zone. In Stedi’s AT7 reference (opens in a new tab), that code is optional, and when it is absent the time is local to where the status occurred. Derive the zone from the stop’s location and mark the UTC value as inferred. A pipeline that treats a local time as absolute produces errors as wide as the zone offset.

Daylight saving sharpens it. Twice a year an hour repeats and an hour doesn't exist, so a system sorting by timestamp can render a delivery before its pickup. Store UTC alongside the reported local time and its zone.

Every event also has a second time: when you learned about it. Freshness and disputes are settled with the received time, and a table with one timestamp column has thrown away half the record.

Failure two: the code list is standard, the meaning is not

X12 publishes the transaction set and its status and reason codes. It can't publish which internal state of a carrier each code represents. One partner sends arrived when the driver crosses the facility's geofence. Another sends it when the truck is checked in at the dock. A third sends it when a clerk works through the paperwork at the end of the shift, which shows up as timestamps clustering at the same time every evening.

None of them is wrong. The meanings clash only when you show them as the same event on one screen. Keep the mapping from partner code to your internal state as configuration a person can inspect and change, keep the raw code on the event, and plan to correct the mapping in a new partner's first weeks.

Failure three: messages arrive late, twice and out of order

Carrier systems queue, retry and resend batches after an outage. You'll receive a departure after the arrival that followed it, and the same event twice. The shipment can't be a row you update in place.

Keep an append-only event log keyed by shipment and stop, and give each event a deterministic identity so a resend is recognized as the same event. Derive the current view from the log, ordered by when each event happened, whatever order it arrived in. Late data then corrects history automatically. Last-write-wins can't express that a message received now describes an earlier moment, so it overwrites good state with stale state.

Build the key from shipment, stop, status code and reported time. Deduplicating on the interchange control number works only until a partner resets its counters.

Failure four: no one computed the ETA you are displaying

A carrier-reported ETA is a commercial statement: it reflects a plan. An ETA computed from a position feed is a physical estimate. Showing both in the same field erases that distinction.

Physical estimates have a constraint route calculators often ignore: the driver's available hours. A motor carrier must require each driver to record duty status (opens in a new tab). Under 49 CFR 395.3 (opens in a new tab), a driver may not drive after 14 consecutive hours on duty, counted from the end of 10 consecutive hours off duty. Within that window the driver may drive 11 hours in total, and may not drive after 8 hours of driving without a 30-minute interruption. On-duty time is capped at 60 hours in 7 days, or 70 hours in 8 days for a carrier that operates every day. An ETA that lands in a mandatory rest period is one the truck can't meet.

The carrier keeps those records, and the rule doesn't address a shipper's access to them. Your ETA reflects the limit only if the carrier or its ELD provider shares hours data with you, so ask for it in the contract.

What none of this fixes

If a partner sends statuses in one batch at the end of the day, no architecture recovers the intraday truth. That's a commercial conversation, and the log supplies the evidence. A position feed (telematics, an ELD provider, a carrier API) then becomes another source writing into the same log, ranked above the 214 when both describe the same moment.

What to display instead

  • An age and a source on every ETA: computed from position at 14:20, or reported by carrier at 09:05. The customer needs to know whether they're reading an hour-old fact or a yesterday-old promise.
  • Stale as a state. After a threshold, show when the last status arrived in place of an ETA.
  • Silence as an exception. A shipment that has sent nothing for six hours needs attention as much as one that reported a delay, and only received time finds it.

Sources

  1. 1.X12 Transaction Sets (opens in a new tab), X12
  2. 2.49 CFR 395.8: Driver’s record of duty status (opens in a new tab), Electronic Code of Federal Regulations

Next step

Send us a day of 214s.

One day of raw EDI 214 messages with the identifiers changed. We will tell you which of these failures your messages show, from the messages themselves rather than from the dashboard.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing