Transportation Carrier Shipment Status Message
The X12 214 provides in-transit status updates (pickup, in-transit, delivered, exception) for a freight shipment.
In this guide
214 Shipment Status moves from Motor / LTL / Freight Carrier to Shipper / Broker / Consignee (Carrier → Shipper) via AS2, SFTP, API. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How 214 Shipment Status Works
Sender
Motor / LTL / Freight Carrier
Receiver
Shipper / Broker / Consignee
Direction
Carrier → Shipper
Standard
ANSI ASC X12
Version
005010
Transport
AS2 / SFTP / API
Business Purpose
Logistics & Fulfillment
Sender — Motor / LTL / Freight Carrier
EDI Transmission
214
Transportation Carrier Shipment Status Message
ANSI ASC X12 004010 / 005010
Receiver — Shipper / Broker / Consignee
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →214 Shipment Status workflow. Steps: Status Event Occurs, Generate 214, Send to Shipper, TMS Ingests Update, Refresh Visibility, Exception Alerting. Transmitted from Motor / LTL / Freight Carrier to Shipper / Broker / Consignee via AS2, SFTP, API, following ANSI ASC X12 004010 / 005010.
Overview
Gives shippers and consignees real-time visibility into freight movement without needing to call the carrier.
Sender
Motor / LTL / Freight Carrier
Receiver
Shipper / Broker / Consignee
Direction
Carrier → Shipper
Standard / Version
ANSI ASC X12 004010 / 005010
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| B10 | Beginning Segment for Transportation Carrier Shipment Status Message | Shipment identification and reference numbers. |
| LX | Assigned Number | Loop counter for multiple shipment status reports. |
| AT7 | Shipment Status Details | Status code, reason code, and date/time of the event. |
| MS1/MS2 | Equipment/Location Information | Current city/state and equipment identification. |
Interactive example
Click any segment below to see its business meaning.
ST
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
ST*214*0001~
B10*SHIP-99201*PRO-784512399*FEDEX~
LX*1~
AT7*AF*NS***20230921*1015~
MS1*Columbus*OH*US~
SE*6*0001~Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| Carrier Tracking Event | event.status_code | AT701 (Shipment Status Code) |
| Carrier Tracking Event | event.timestamp | AT705/AT706 (Date/Time) |
| Carrier Tracking Event | event.city | MS101 (City Name) |
Validation rules
- B10 reference numbers must match a shipment known to the receiving TMS (via PRO or shipment ID).
- AT701 status codes must come from the agreed carrier status code list.
- Status events should be sent in chronological order per shipment to avoid out-of-sequence updates overwriting newer status.
Common errors & troubleshooting
Shipment shows stale status in shipper's TMS
Cause: An older 214 arrived out of order after a newer one due to queuing/retry delays.
Fix: Sequence status updates using AT705/AT706 timestamps rather than message arrival order.
Exception status not triggering alerts
Cause: Carrier used a non-standard status/reason code combination not mapped in the shipper's rules engine.
Fix: Maintain an up-to-date crosswalk of carrier-specific status codes to standardized exception categories.
Frequently asked questions
Typically several — one for each major milestone such as pickup, in-transit scans, out for delivery, and final delivery, plus any for exceptions like delays or damage.
Still have questions about 214?
Ask EDI AI →