EDI guide: document 214

EDI 214 Shipment Status Message: the tracking update behind every milestone alert

The 214 is how a carrier tells a shipper where a shipment is. Picked up, in transit, delayed, delivered: each event is one 214, and the codes inside it are what your 3PL's tracking page and exception alerts are built from.

  • 214ANSI X12 transaction set
  • AT7the segment with the status code
  • D1the code that means delivered
  • Freeno signup
  • Sent byCarrier to shipper or 3PL
  • NextRepeats at each milestone until delivered; 210 carrier invoice follows
  • Before it211 Motor Carrier Bill of Lading
  • GlossaryDelivery confirmation

What it is

What an EDI 214 is and why it matters

An EDI 214 is the transportation carrier shipment status message. LTL and truckload carriers send one to the shipper (or the 3PL managing the freight) each time something happens to a shipment: the driver arrives for pickup, the freight departs, it passes through a terminal, it is out for delivery, it is delivered, or it is delayed. Each 214 identifies the shipment by PRO number, bill of lading and purchase order, and carries a status code, a reason code, a date, a time and a location.

Brands see the 214 indirectly. When a 3PL's portal shows a B2B order as 'in transit, ETA Thursday', or when an exception email says a retail delivery was refused at the dock, a 214 from the carrier is usually the source. Retailers also consume 214s from their inbound carriers to plan appointments, which is why a load that the carrier reports as delayed can shift a delivery window the brand is fined against.

For a 3PL that manages outbound freight, the 214 is the difference between answering 'where is my order' from a screen and answering it by phoning the carrier. The value depends on the carrier sending every milestone promptly with consistent codes, and on the 3PL's TMS or WMS mapping those codes to statuses a customer understands.

Sample layout

The EDI 214 segment by segment

Illustrative values. Each retailer or carrier publishes an implementation guide with the exact subset of segments and codes it accepts.

SegmentWhat it carriesExample
STStart of the transaction setST*214*0001
B10Beginning: carrier reference (PRO number), shipment ID from the shipper, carrier SCACB10*PRO88120*SHP0092811*RBTW
L11Reference numbers: BM bill of lading, PO purchase order, CN carrier PRO, others per partnerL11*BOL-55810*BM
N1 / N3 / N4Parties: SH shipper, CN consignee, with addressesN1*CN*DC 6021*92*6021
LXAssigned number that starts each status loopLX*1
AT7Shipment status: status code (X3 arrived at pickup, AF departed pickup, X6 en route, X1 arrived at delivery, D1 delivered, SD delayed, A3 returned, CA cancelled), reason code (NS normal, AH holiday, BC weather, A1 missed delivery, AM shipper related), date, time, time codeAT7*D1*NS***20260925*1032*ET
MS1Location of the event: city, state, countryMS1*Columbus*OH*US
MS2Equipment: SCAC and trailer numberMS2*RBTW*T48812
AT8Weight and piece count for the shipmentAT8*G*L*1820*4
SEEnd of the transaction setSE*11*0001

How it flows

How an EDI 214 moves from one system to the next

  1. A milestone happens on the roadThe driver scans at pickup, the terminal scans on arrival, the delivery is signed for. The carrier's system records the event with a time and place.
  2. The carrier sends a 214One message per event, referencing the PRO, BOL and PO so the shipper can match it. Delays and exceptions use SD or A-series codes with a reason.
  3. The 3PL updates the orderThe TMS or WMS maps AT7 codes to a customer-facing status, updates the tracking page, and fires an exception alert when a code like SD, A1 or A3 arrives.

Common rejection reasons

Why an EDI 214 gets rejected or fined

The failures that show up in 997s, exception queues and retailer chargebacks.

  • Missing PRO or BOL referenceB10 or L11 without the numbers the shipper uses to match. The status cannot be attached to an order and lands in an unmatched queue.
  • Status code outside the agreed listThe carrier sends codes the shipper's TMS was never mapped for. The event is stored as unknown and the customer sees no update.
  • Timestamp without a time zone codeAT7 date and time with no time code, so a 10:32 delivery is recorded in the wrong zone and the appointment metrics are off.
  • Out-of-order milestonesA D1 delivered arrives before the X1 arrival, or an AF departure after delivery, because the carrier batches uploads. Tracking pages jump around.
  • Duplicate 214sRepeated transmissions of the same event with a new control number. Without de-duplication the customer receives the same alert three times.

Before you sign

What a 3PL needs to run the 214 properly

Questions to settle with the warehouse
  • Ask which carriers send 214s to the 3PL by EDI and which are tracked by API or by manual carrier-site checks.
  • Confirm the 3PL maps AT7 codes to customer-facing statuses and which codes trigger an exception alert to you.
  • Agree how a delayed inbound load to a retailer (SD or A-series codes) is escalated, since the brand carries the on-time fine.
  • Check that 214 events feed carrier scorecards, so on-time pickup and delivery rates are measured rather than estimated.
3PLs that run this document3PL Directory

5,400+ providers; filter for freight management and B2B fulfillment to find 3PLs that manage carriers and consume 214 feeds.

Questions

EDI 214 FAQ

Is the 214 the same as parcel tracking?
It is the LTL and truckload equivalent. Parcel carriers (UPS, FedEx, USPS) expose tracking events through APIs rather than 214s, although UPS and FedEx also support EDI 214 for some enterprise shippers.
Who sends the 214, and who receives it?
The carrier sends it. The receiver is whoever tendered the load: the shipper, the 3PL or the freight broker. Retailers also receive 214s from their own inbound carriers.
What do the common AT7 status codes mean?
X3 arrived at pickup location, AF departed pickup, X6 en route to delivery, X1 arrived at delivery location, D1 completed delivery, SD shipment delayed, A3 shipment returned to shipper, CA shipment cancelled. Reason codes qualify them: NS normal status, BC weather, AH holiday, A1 missed delivery, AM shipper related.
How does the 214 relate to the 204 and 990?
The 204 is the load tender the shipper sends the carrier, the 990 is the carrier's accept or decline, the 211 or paper BOL covers the pickup, and the 214 reports progress once the freight is moving. The 210 invoice closes the sequence.

Retailer asking for EDI?

Get matched with a 3PL that already runs the 214

3PL Hub matches brands with warehouses already exchanging this document with the retailers and carriers you sell through. Free for brands, commission-free, from a directory of 5,400+ providers.

Ready to shortlist 3PLs?

Free for brands. No commissions. Your details go only to the 3PLs you match with.

Get matched to 3PLs
3PL Hub

The commission-free 3PL directory and matchmaking platform. 5,000+ 3PLs, 200+ verified members, and 3PLs never pay us to be recommended.

Taking Inventory

The 3PL newsletter, every two weeks

3PL, fulfillment, M&A, eCommerce and trade, written by a human. Read by 3,000+ operators and the logistics ecosystem.

Subscribe to Taking Inventory Free. Every two weeks. Unsubscribe any time.