Real-time shipment visibility from carrier to shipper - automated pickup confirmation, in-transit milestones, exception alerts, and proof of delivery without manual tracking calls or portal logins.
The EDI 214 is the carrier's event-based status feed for a shipment in motion. After a load tender is accepted (204/990 exchange), the carrier sends a series of 214 messages as the shipment moves through its lifecycle - from driver dispatch to pickup confirmation, through terminal scans and linehaul moves, to final delivery with proof of delivery details.
Each 214 transaction carries one or more AT7 (Shipment Status Details) segments that contain a standardized status code, the timestamp of the event, and where applicable, a reason code explaining delays or exceptions. Status codes cover the full journey: X3 = dispatched, X1 = picked up, AF = out for delivery, D1 = delivered, X6 = delayed - with many carriers supplementing standard codes with their own extensions mapped in the AT7 loop.
For order management and customer service teams, 214 is the backbone of proactive exception management. Instead of waiting for complaints, systems consuming 214s can automatically flag late pickups, missed appointment windows, weather delays, or refused deliveries - triggering customer notifications or escalation workflows within minutes of the carrier reporting the event.
LTL carriers like FedEx Freight, Estes, and Old Dominion generate 214s from terminal scan events in their network operations systems. TL carriers generate fewer events (pickup + delivery + exceptions) but must send 214s within contractual windows. Carrier compliance with 214 requirements is increasingly monitored and scored by major shippers.
Retailers use 214 status feeds to manage inbound DC scheduling. When a 214 confirms a supplier's shipment was picked up, the DC can pre-schedule a receiving door appointment. Late-pickup alerts from 214 exceptions let retailers proactively shift receiving labor before the shipment arrives. Major retailers mandate 214 from all carriers in their routing guide.
eCommerce brands use 214 to power customer-facing order tracking. The 214's AT7 status codes and timestamps are transformed into consumer-friendly messages - "Your order has shipped," "Out for delivery today," "Delivered at 2:14 PM." Without 214, brands must either screen-scrape carrier tracking pages or call carriers for updates - neither scales.
3PLs relay 214 status data to their clients' order management systems, providing end-to-end visibility across dozens of carrier relationships through a single integration. Manufacturers use 214 for inbound freight management - production schedules can be adjusted when 214 exceptions signal inbound material delays before they cause line stoppages.
Opens the 214. B1001 = reference identification (often the shipper's reference or BOL number), B1002 = shipment identification number (carrier's PRO number), B1003 = SCAC code of the reporting carrier. The PRO number in B1002 is the primary key linking this 214 back to the original 204 load tender and any associated 210 invoices.
The core status segment - one per event. AT701 = shipment status code (e.g., X1 = pickup, D1 = delivered, X6 = delayed in transit, NS = not yet picked up), AT702 = shipment status or appointment reason code, AT703 = date (CCYYMMDD), AT704 = time (HHMM), AT705 = time zone. Multiple AT7s in one 214 represent multiple events for the same shipment reported together.
MS1 identifies the location of the shipment at the time of the status event - city, state, country code, ZIP. MS2 adds equipment details: MS201 = standard carrier alpha code, MS202 = equipment initial (trailer prefix), MS203 = equipment number. For TL shipments, these segments let shippers track not just status but where the trailer physically is at each milestone.
Carries actual-as-delivered quantity data: AT801 = weight qualifier, AT802 = weight unit code (L = lbs, K = kg), AT803 = weight, AT804 = lading quantity (pieces), AT805 = packaging form code. When delivered quantity differs from tendered quantity (short shipment, refused pieces), the AT8 data supports claims and discrepancy resolution against the original 204.
Reference segment for cross-referencing other documents: L1101 = reference ID (PO number, BOL number, ship notice number), L1102 = reference qualifier (PO = purchase order, BM = BOL, CN = carrier's reference). Multiple L11 segments link the status back to all relevant documents. Critical for automated matching in TMS and OMS systems that need to update order records when a 214 is received.
Identifies the parties relevant to the status event: shipper (SH), consignee (CN), notify party (NF). For deliveries, NM1 for the consignee may include the name of the person who signed for the delivery (POD signer) in NM103. This data flows directly into proof-of-delivery records and is legally significant for freight claims and retailer chargeback disputes.
The load tender that originated the shipment. The 214's PRO number and BOL reference trace back to the 204's shipment ID, enabling systems to automatically close out open load records when a 214 with a delivery status is received.
Sent by the shipper for the same goods being tracked. Retailers match 214 status events against open 856 ASNs to update inbound shipment records. When 214 confirms delivery, the retailer's system can trigger receipt posting against the ASN.
Follows the 214 delivery confirmation. Freight audit systems use the 214 POD timestamp to validate that the 210 invoice was issued after confirmed delivery, and to cross-check claimed detention or accessorial hours against 214 arrival/departure timestamps.
Better EDI normalizes 214 status feeds from any carrier into your TMS, OMS, or customer-facing tracking system - with exception alerting and status code mapping included.
Talk to an EDI Expert