What is EDI 214 - Transportation Carrier Shipment Status Message?
The EDI 214, also known as the Transportation Carrier Shipment Status Message, is an EDI transaction, its primary purpose is to communicate precise updates regarding the shipment’s progress, 
such as its location, condition, or events (e.g., picked up, in transit, delivered, or delayed), enabling real-time tracking and coordination between trading partners in the supply chain.
Used to provide shippers, consignees, and other stakeholders with updates on the status of shipments, the EDI 214 - Transportation Carrier Shipment Status Message communicates key milestones (e.g., picked up), in-transit updates, and delivery status, enabling near real-time tracking and better coordination across supply chains.
Tracking Freight in ‘near real time’ is paramount, particularly with Omni-Channel deliveries. ‘Shipment Status Details’ updates reflected in the AT701 (Shipment Status Indicator Code) element can be sent in near real time back to the shipper. Statuses that indicate “Picked Up” and “Delivered” go a long way to ensure consumers are happy and that vendors and carriers are remunerated efficiently.
How does PartnerLinQ use the EDI 214 - Transportation Carrier Shipment Status Message? 
PartnerLinQ uses the 214 to proactively provide pickup, in-transit, and delivery status to shippers, consignees, and service providers. It leverages the AT701 Shipment Status Code segment to convey real-time updates, ensuring carriers share progress when events occur in their systems. PartnerLinQ also integrates reference numbers such as PRO numbers, shipment IDs, and purchase orders to align status with the shipper’s or consignee’s systems. For truckload and LTL shipments, the first 214 usually provides pickup date, PRO number, estimated delivery, and shipment identifiers.
What responses to the EDI 214 - Transportation Carrier Shipment Status Message are expected/sent?
The EDI 214 - Transportation Carrier Shipment Status Message works alongside related transactions such as the EDI 204 (Load Tender) and the EDI 990 (Response to Load Tender). While not a response transaction per-se, the 214 does provides continuous feedback in the shipment lifecycle.
What does the EDI 214 - Transportation Carrier Shipment Status message support?
The EDI 214 supports the movement of freight (logistics execution) by giving visibility into shipments as the progress. It underpins the shipment and invoicing (EDI 210) processes, exception management, and most importantly, it supports the customer experience through accurate, timely updates answering the key question, “Where’s my stuff?”
What are the Key Features of the EDI 214 - Transportation Carrier Shipment Status message?
- Real-time or near real-time shipment visibility
- Supports truckload and LTL carriers
- Uses AT701 for status indicators
- Communicates critical milestones: pickup, delivery, delays
- Links shipment updates with PRO, SID, PO, and other references
What is the Purpose of the EDI 214 - Transportation Carrier Shipment Status message?
The primary purpose of the Transportation Carrier Shipment Status or Message (214) is
to notify trading partners of shipment status updates in order to support operational efficiency, invoicing, and performance measurement of carriers; communicate precise updates regarding the shipment’s progress, such as its location, condition, or events (e.g., picked up, in transit, delivered, or delayed), enabling real-time tracking and coordination between trading partners in the supply chain.
Tracking Freight in ‘near real time’ is paramount, particularly in Omni-Channel shipments. ‘Shipment Status Details’ updates reflected in the AT701 (Shipment Status Indicator Code) element should be sent nearly immediately (in near real time) to the Shipper. Statuses which indicate “Picked Up” and “Delivered” are particularly important to consumers and in the invoicing and remittance process at most omnichannel retailers and also go a long way to ensure that carriers are remunerated in the most efficient way possible. Omni-Channel retailers are particularly sensitive to trading partners and acknowledge there are many acceptable substitute AT701 (Shipment Status Indicator Code) qualifiers in order to minimize any systemic impact to trading partners, EDI systems, and teams.
What Information is Included in the EDI 214 - Transportation Carrier Shipment Status message?
Shipment updates in the 214 typically include:
- Carrier’s PRO number
- Shipment Identification Number (SID)
- Pickup and delivery details
- Appointment times and changes (G62)
- AT701 status indicator codes
- AT702 reason codes for exceptions or appointments
What are the Essential Components of the EDI 214 - Transportation Carrier Shipment Status message?
These components provide a structured, event-driven snapshot of shipment movement—ensuring buyers, sellers, logistics providers, and visibility platforms maintain real-time awareness of pickup, transit, delay, and delivery milestones. They support proactive decision-making, exception resolution, and end-to-end supply chain visibility—key pillars of PartnerLinQ’s unified digital connectivity.
| Component | Description | Typical Segment(s) |
|---|---|---|
| Message Header & Control | Identifies the transaction and establishes control information. | ST, B10, LX |
| Shipment Identification | Provides shipment-level identifiers such as PRO number, BOL, PO, and customer references. | B10, REF |
| Status Events | Communicates shipment events—arrived, departed, delivered, delayed—including timestamps and event types. | AT7 |
| Event Location Details | Identifies the location associated with each status event. | MS1 |
| Equipment Identification | Provides equipment and trailer/container details linked to the shipment. | MS2 |
| Exception Details | Reports damage, overage, shortage, or delay exceptions. | Q7 |
| Location & Party Information | Identifies shipper, consignee, carrier, or facility addresses related to the event. | N1, N3, N4 |
| Additional Notes | Provides free-form remarks that expand on status or exception details. | K1 |
| Transaction Trailer | Indicates the end of the transaction and validates segment count. | SE |
What are the Common Segments Included in the EDI 214 - Transportation Carrier Shipment Status message?
| Segment | Segment Name | Purpose / Usage |
|---|---|---|
| ST | Transaction Set Header | Opens the 214 and assigns a control number. |
| B10 | Beginning Segment for Transportation Carrier Shipment Status Message | Provides primary shipment identifiers such as PRO number and reference numbers. |
| LX | Assigned/Line Control Number | Provides a counter for each status event. |
| N1/N3/N4 | Name / Address / Geographic Location | Identifies parties tied to the event—shipper, consignee, carrier, facility. |
| G62 | Dates/Times | Provides for key dates, like process, activity, and response dates. |
| L11 | Reference Identification | Communicates BOL, PO, shipment ID, SCAC, or other references. |
| AT7 | Shipment Status Details | Communicates shipment status code, reason code, dates, times, and appointment timestamps. |
| MS1 | Equipment, Shipment, or Real Property Location | Indicates the location (city, state, ZIP) of the status event. |
| MS2 | Equipment or Container Owner and Type | Identifies truck, trailer, or container. |
| Q7 | Lading Exception Code | Provides reason codes for exceptions: shortage, overage, damage, delay. |
| K1 | Remarks | Adds free-form textual information. |
| SE | Transaction Set Trailer | Closes the 214 and validates segment count. |
What Status Codes are used with the EDI 214 - Transportation Carrier Shipment Status message?
The 
AT701 element conveys status updates such as:
- AF: Carrier Departed Pick-up Location with Shipment (i.e., Picked Up)
- L1 Loading (i.e., Picked Up)
- P1 Departed Terminal Location (i.e., Picked Up)
- AJ: Tendered for Delivery (i.e., En Route)
- AV: Available for Delivery (i.e., En Route)
- CB: Completed Shipment (i.e. (i.e., Delivered)
- D1 Completed Unloading at Delivery Location (i.e., Delivered)
- (X1 Arrived at Delivery Locationi.e., Delivered)
Status codes ensure somewhat consistent reporting and are central to performance tracking. "Picked Up" and "Delivered" notifications for example are particularly important to the invoicing and remittance process to ensure that partners and carriers remuneration takes place in the most efficient way possible.
What Reason Codes are used with the EDI 214 - Transportation Carrier Shipment Status message?
Reason codes are central to performance tracking, the reason a shipment status or appointment reason was transmitted and are particularly helpful when complimented by alerting. The AT702 Appointment Reason Codes provide additional context, such as:
- A1 Missed Delivery
- A2 Incorrect Address
- AD Customer Requested Future Delivery-
- CU: Customer Unavailable
- NS Normal Status
What Use Cases does the EDI 214 - Transportation Carrier Shipment Status message support?
- Retailers tracking omnichannel deliveries
- Shippers monitoring performance of LTL and TL carriers
- Accrual, reversal, invoicing and remittance processing
- Consignees coordinating receiving operations
- Brokers providing visibility services
What are the Benefits of the EDI 214 - Transportation Carrier Shipment Status message? 
- Enhances visibility and transparency
- Supports invoice accuracy (210)
- Improves customer experience with timely updates
- Enables carrier performance measurement
How efficient is the EDI 214 - Transportation Carrier Shipment Status message?
The EDI 214 - Transportation Carrier Shipment Status message provides near real-time tracking and decision support for shippers and carriers, and it speeds up tracking and decision-making for carriers and shippers.
How Compliant is the EDI 214 - Transportation Carrier Shipment Status message?
The EDI 214 - Transportation Carrier Shipment Status message meets industry requirements for visibility and communication of shipment statuses and requirements for partners using intermodal or terminal-based logistics.
What is the Format of the EDI 214 - Transportation Carrier Shipment Status message?
The EDI 214 - Transportation Carrier Shipment Status message follows ASC X12 EDI 4010 standard with defined delimiters and segment structures.
How Accurate is the EDI 214 - Transportation Carrier Shipment Status message?
The EDI 214 - Transportation Carrier Shipment Status message standardizes data exchange and supports standardized reporting across carriers, minimizing disputes. However accuracy is dependent on user interpretation as there are multiple ways to signal that a package has been delivered in the AT7, interpretation of the AT7 is key to understanding shipment status.
What are the Limitations of the EDI 214 - Transportation Carrier Shipment Status message?
The EDI 214 has a tendency to generate high volumes of data when statuses are updated too frequently and such limitations may require alignment on acceptable substitute codes for 'Arrived' and 'Departed'.
Are Guidelines & Sample Files for the EDI 214 - Transportation Carrier Shipment Status message available?
Yes. PartnerLinQ provides sample EDI 214 - Transportation Carrier Shipment Status message Transaction and implementation guides through its Support and Guideline Management Team. Sample EDI 214 implementation guides illustrate both inbound and outbound flows, segment layouts, and valid data examples and support testing and partner onboarding. Customized specification documents for use in on boarding and technical development are available upon request. PartnerLinQ provides:
- EDI 214 - Transportation Carrier Shipment Status message implementation guide
- Sample payloads
- Qualification and testing maps
- Error handling and best-practice notes
What are the Basic Questions for EDI Integration of the EDI 214 - Transportation Carrier Shipment Status message ?
- Are samples and specifications available?
- What is the general direction of the transaction?
- Is the 214 inbound or outbound?
- Are multiple parties involved?
- What transactions might these interested parties be a party to?
- Is a Transportation Carrier Shipment Status or Message (214)a timed event?
- Are notifications involved/needed?
- How are the AT701 Shipment Status Codes handled?
- How are the AT702 Shipment Status or Appointment Reason Codes handled?
- Is customization required for specific customers? (e.g., acceptable substitute code list references for "Arrived" or "Departed")
- Is automation or human intervention required?
Are there SLAs for updates?
What Business Level Workflow does the EDI 214 - Transportation Carrier Shipment Status message support?
1. Carrier receives shipment (from EDI 204/990 process).
2. Carrier generates 214 updates for pickup, in-transit, and delivery.
3. Status messages (AT7) are transmitted with references and timestamps.
4. Shipper and consignee systems update dashboards and trigger workflows.
5. Final delivery status closes the loop for invoicing (EDI 210).
What are the Best Practices for using the EDI 214? - Transportation Carrier Shipment Status message.
- Send pickup and delivery statuses in near real-time.
- Ensure AT701 and AT702 codes are accurate.
- Align SCAC, PRO, and SID references between partners.
- Use functional acknowledgments (997) within 24 hours.
- Minimize systemic disruption by honoring substitute codes.
What Transactions are associated with the EDI 214 - Transportation Carrier Shipment Status message?
| Transaction | Name | Relationship to the 214 |
|---|---|---|
| EDI 204 | Motor Carrier Load Tender | The tender that initiates a shipment; the 214 provides movement updates throughout the shipment lifecycle. |
| EDI 210 | Motor Carrier Freight Details & Invoice | Final invoicing typically follows the delivered (D1) 214 status event. |
| EDI 211 | Motor Carrier Bill of Lading | Provides detailed shipment information that the 214 may reference in status updates. |
| EDI 753 / 754 | Routing Request / Routing Instructions | May precede or define the routing that later appears in 214 updates. |
| EDI 820 | Payment Order/Remittance Advice | Often triggered after the 210 invoice is issued following the delivery status update. |
| EDI 824 | Application Advice | Communicates corrections or issues with transmitted 214 data. |
| EDI 863 | Report of Test Results (used in some carrier testing scenarios) | Occasionally used during certification before production 214 transmissions begin. |
| EDI 990 | Response to a Load Tender | Carrier acceptance/rejection often precedes the first 214 event. |
| EDI 997 / 999 | Functional Acknowledgment / Implementation Acknowledgment | Acknowledge receipt of the 214 or other transportation messages. |
Explore Our Integration Solutions
PartnerLinQ Integration Solutions
Connect Everything. Integrate Intelligently.
Future-Proof Your Business with Composable, AI Powered Connectivity.