Transaction explainers · November 2, 2026

EDI 214 Transportation Carrier Shipment Status: The Complete Guide

How the EDI 214 works: status and reason code pairs, milestone events from pickup to delivery, and why shippers grade carriers on 214 discipline.

The EDI 214 is freight's answer to "where's my truck?" — asked and answered by machine, at every milestone, with timestamps. A carrier that runs the 214 well gives its shippers a live picture of every load without a single check call. A carrier that runs it badly generates phone calls, track-and-trace headcount, and eventually a lower spot on the routing guide. In the shipper-carrier world — typically X12 4010 — few documents map so directly to whether you keep the freight.

What's inside a 214

Strip the syntax and each 214 is a stack of status events against an identified shipment:

  • Shipment identification — the carrier's PRO number, the shipper's shipment or load ID, and the reference numbers (BOL, PO numbers) that let every party's system find the same shipment. Reference-number discipline is half the value of the document: a status update that can't be matched to a load is noise.
  • Status events — each one a code pair plus context. The status code says what happened: dispatched, picked up, arrived at terminal, departed terminal, out for delivery, delivered, refused. The reason code, when present, says why — weather, mechanical failure, shipper-related delay, consignee closed. Add a timestamp and a city/state, and one segment loop tells the whole story of the event.
  • Appointment and schedule data — estimated and scheduled delivery dates, appointment times, and revisions as they move.

The status/reason pairing deserves emphasis because it's where programs live or die. "Delivered" is easy. "Delayed — and here's the machine-readable why" is what lets a shipper's system distinguish a weather event from a chronically late carrier, automatically, across thousands of loads.

The milestone cadence

Most shipper and broker programs specify a minimum event set per load:

  1. Pickup confirmation — the load left the dock, timestamped.
  2. In-transit updates — at terminal arrivals/departures for LTL, or on a time cadence for truckload visibility programs.
  3. Out for delivery / arrival at consignee.
  4. Delivery confirmation — the event that stops the service-level clock and starts the billing one.
  5. Exception events — delays with reason codes, as they happen, not after delivery.

Timeliness requirements are contractual and vary by program; confirm the required events and windows in each shipper's routing guide or carrier packet. The consistent theme: visibility programs grade carriers on 214 completeness and latency, and those grades feed tender decisions on the 204 side of the relationship.

Where the 214 fits in the freight chain

The load tender (204) starts the story, the 990 response accepts it, the 214 narrates the execution, and the 210 freight invoice bills it. That chain is also the audit trail: shippers match the 210's charges against tendered terms and the 214's delivered event before paying. A carrier whose 214s are complete gets paid faster because the match clears itself; missing delivery events are a classic cause of invoices parked in exception queues.

For suppliers who ship into retail programs, the 214 also complements the 856 ASN: the ASN tells the retailer what's on the truck; the 214 tells you where the truck is. Feeding carrier status into your own ASN timing and appointment management is a quiet compliance advantage.

Running the 214 without drama

The failure modes are predictable: events batched hours after they happen, missing reason codes on delays, reference numbers that don't round-trip, and 997 acknowledgments nobody reconciles. The fixes are equally predictable — fire events from operational triggers rather than schedules, validate against the partner's spec before transmission, and treat an unacknowledged document as undelivered until proven otherwise.

EDISQ handles the 214 like every other document in the catalog: certified partner maps, validation before transmission, automatic 997s both directions, and connectivity — AS2, SFTP, or VAN, whichever the partner requires — operated as part of the service. Pricing is per document on the published ladder: first 25 monthly free, then from $0.50 tapering with volume, all on the pricing page. Status messages are high-frequency documents, which is precisely why they should ride a meter instead of a subscription.

FAQ

What is an EDI 214?

The Transportation Carrier Shipment Status Message — the document a carrier sends a shipper or broker to report where a shipment stands: picked up, in transit, out for delivery, delivered, or delayed, each with a timestamped status code.

What are 214 status and reason codes?

Each status update pairs a status code (what happened — e.g. picked up, arrived, delivered) with an optional reason code (why — e.g. weather, mechanical breakdown, consignee-related). The pair plus a timestamp and location is the whole story of the event.

Who sends the 214, and how often?

The carrier sends it to the shipper, broker, or 3PL. Frequency is contractual: typical programs require updates at defined milestones — pickup, arrival, delivery — and many add periodic in-transit updates for visibility.

How does the 214 relate to the 204 and 210?

The 204 tenders the load, the 214 reports its progress, and the 210 bills it. Auditing the 210 against tender terms and 214 events is how shippers verify freight bills before paying.