EDI 214 – Transportation Carrier Shipment Status Message

What is an EDI 214?

EDI 214 (Transportation Carrier Shipment Status Message) is an X12 transaction carriers use to send time-stamped shipment updates to shippers, 3PLs, and consignees. It communicates where the load is, what just happened, and when key milestones occurred.

Primary purpose: near real-time visibility for in-transit shipments
Typical senders: Truckload, LTL, parcel, ocean, air carriers; brokers
Common triggers: Pickup, departure, arrival, delays, proof of delivery
Often paired with: EDI 204, EDI 990, EDI 210, EDI 997

Why EDI 214 Matters in 2025

Customer expectations: AI-powered trackers in TMS/WMS surface 214 events instantly.
Chargeback prevention: Accurate AT7 status + timestamps help defend OTIF metrics.
Exception handling: Standardized delay codes allow automated workflows and alerts.
Cost control: Fewer manual calls/emails; better planning for dock and labor.

EDI 214 Structure & Key Segments

Typical Segment Order

ST – Transaction Set Header
B10 – Reference numbers (PRO/BOL/PO)
LX – Assigned number (status loop start)
AT7 – Shipment status (code, reason, dates/times)
MS1 – Location (city, state, country)
MS2 – Equipment (SCAC, trailer/vehicle)
L11 – Additional references (optional)
SE – Transaction Set Trailer

Core Data Elements (Pointers)

Shipment Identifier: PRO/BOL/PO (from B10 and/or L11)
Status Code: AT7-01 (e.g., AF = Arrived at Pickup; X6 = En Route to Delivery)
Status Reason: AT7-05 (e.g., NS = No Show; WD = Weather Delay)
Date/Time: AT7-06/07 (event timestamp)
Geo: MS1 (lat/long optional; city/state/country recommended)
Equipment: MS2 (SCAC, trailer/vehicle ID)

Common AT7 Status Codes

Code	Meaning	When to Send
AF	Arrived at Pickup	Driver checks in at shipper
AG	Departed Pickup	Loaded and released
X6	En Route to Delivery	In transit
AB	Arrived at Delivery	At consignee gate/dock
D1	Completed Unloading	Unloaded / POD captured
D3	Delivery Appointment Scheduled	Appt confirmed
NS / WD	No Show / Weather Delay	Exception events

Note: Exact segments and qualifiers vary by trading partner implementation guide (IG).

214 in the Shipment Lifecycle

Tender & Acceptance: 204 → 990
In-Transit Visibility: Series of 214 events
Delivery & POD: Final 214 event(s) with timestamps
Billing: 210 (often validated against 214 timeline)
Acknowledgments: 997 for control

Implementation Checklist (Pointers)

Obtain partner IGs and status code matrices; align on AT7 usage and event cadence.
Map identifiers: PRO, BOL, PO, Shipment ID; decide which is system-of-record.
Normalize time zones to UTC and include local offset where required.
Provide precise locations (MS1) and equipment IDs (MS2).
Validate before send: control numbers, required loops, syntax.
Automate retries and 997 reconciliation; alert on negative 997s.
Pilot with one lane/shipper, then scale across customers.

Validation & Compliance

Syntax: Envelope (ISA/GS), ST/SE control, delimiters, terminators.
Semantic: Required elements present (e.g., AT7-01, timestamps, IDs).
Business rules: Event ordering (no delivery before pickup), duplicate suppression.
Security: AS2/AS4 with MDN; digital cert rotation policy; TLS minimums.