EDI 214 Status Codes Reference for Shipment Tracking and Exception Management
In this article
For CFOs, IT directors, and EDI coordinators overseeing manufacturing, shipping, or retail logistics, the EDI 214 Transportation Carrier Shipment Status Message is the foundation of shipment visibility and exception management. EDI 214 status codes provide automated, near real-time updates on shipments, driving everything from dock scheduling to exception alerts. When implemented and mapped correctly, these codes are critical for proactive shipment tracking, reducing risk, and enabling exception workflows in your ERP and TMS. BOLD VAN supports full integration of EDI 214 messaging, ensuring data is actionable and always accessible for audit and reporting.
This post offers a precise, practical reference for shipment lifecycle codes, exception triggers, and best practices for tracking and automation with the ANSI X12 EDI 214 standard. You will find detailed explanations of AT7 status and reason codes, tips for mapping to internal processes, and a provable checklist for onboarding any carrier or LSP. Our goal is to help your business achieve clear, actionable shipment visibility—whether you manage EDI internally or with a platform like BOLD VAN.
EDI 214 in the Shipment Lifecycle
The EDI 214 document allows carriers to communicate shipment status events electronically at key milestones. These status updates feed into shipper, customer, and 3PL portals, driving proactive management and historical visibility. Key segments include:
- ST: Transaction Set Header (identifies the transaction as a 214)
- B10 / B1: Shipment identification (shipment, SCAC, or reference numbers)
- LX: Shipment or stop sequence detail
- AT7: Shipment Status Details (main hub for status and reason codes)
- L11: Additional reference numbers (linking loads to PO/DO/shipment IDs)
The AT7 segment is the most critical, containing all the operational status and reason codes that drive automation and dashboards in your internal systems.
For actionable shipment monitoring, configure your system to always capture and map the AT7 status code, reason code, and date/time fields—these three elements power over 90 percent of exception management and on-time reporting.
| AT7 Field | Description | Primary Use |
|---|---|---|
| AT701 | Shipment event status code (e.g., X3, X6, X1, D1) | Drives lifecycle tracking in TMS/ERP and portals |
| AT702 | Reason/appt/exception code (e.g., A1, AB, K1) | Triggers exceptions, audits, and alerting |
| AT703 | Status date (CCYYMMDD format) | Timeline and on-time/delay calculations |
| AT704 | Status time (HHMM, local time) | Dock scheduling, window compliance checks |
| AT705 | Timezone code for the event | Aligns timestamps to system or customer timezone |
Understanding AT7 Status and Reason Codes
Core Movement Status Codes (AT701)
Most SMB supply chains encounter a familiar set of status codes used for every truckload, LTL, or intermodal move:
| Code | Description | Common Use |
|---|---|---|
| X3 | Arrived at pickup location | Trigger dock readiness, confirm load staging |
| AF | Departed pickup location with shipment | Set initial ETA, customer notification |
| X6 | En route/in transit | Marks shipment active; for ETA tracking |
| X1 | Arrived at delivery location (for unloading) | Alert dock; schedule unloading or appointment |
| D1 | Delivered and unloaded | Close shipment; trigger goods receipt in ERP |
| X4 | Arrived at terminal/intermediate stop | Dwell analysis; plan next transport leg |
| CP / CD | Released loaded/empty (rail/ intermodal) | Equipment management; shipping/ return process |
Appointment and ETA Codes
| Code | Description | How Used |
|---|---|---|
| AB | Appointment made | Dock scheduling; set delivery expectation |
| X9 | Appointment requested | Planner must review and respond |
| AG | Estimated delivery notified (ETA update) | Update expectation; alert if variance is large |
| AD | Advance date/earlier ETA | Adjust labor or receiving slot earlier |
Mapping for Simplicity
Many businesses also map these granular status codes to simplified business labels (such as PU, DE, AR, DL, RT, HE, AD, XL) so users in customer service or operations are not overwhelmed by X12 code detail.
Exception Management: Delay, Refusal, and Returns
Key Reason Codes (AT702) for Exception Handling
To reduce costs from delays, refusals, or misrouted freight, configure reason codes for immediate alerting and root cause analysis in ERP and TMS:
| Code | Description | Suggested Response |
|---|---|---|
| A1 | Missed delivery | Investigate cause; reschedule; review SLA impact |
| A2 | Incorrect address | Correct data; update master records; adjust ETA |
| A3 | Returned to shipper | Start return process; notify teams; document reason |
| A5 | Unable to locate address | Update with new directions; monitor for repeat events |
| AA | Mis sort | Investigate carrier; prevent recurrence |
| A7 | Refused by consignee | Flag sales/support; decide on next steps |
| CA | Shipment canceled/voided | Update order status and costs in ERP |
| K1 | Processing through customs | Escalate to compliance team, monitor ETA |
| RT | Return (mapped label) | Aggregate reasons for returns; adjust process |
Other Operational Exception Codes
- AR: Rail arrival — triggers next leg coordination
- J1: Delivered to connecting carrier — confirms hand-off in multi-leg
- AV: Shipment available for pickup (at destination ramp/terminal)
- HE: Held for inspection or customs — escalate internally
- SD: Bad order/equipment — initiate corrective maintenance
Using 214 Data in ERP and TMS
The value of status and reason codes emerges when mapped to your internal shipment lifecycle, with triggers for workflows and alerts that inform finance, operations, and customer service.
Mapping Standard Codes to Internal Stages
- Planned: Before receiving a 214
- Pickup Confirmed: X3, AF
- In Transit: X6, RL, P1
- At Facility: X4, X1
- Delivered: D1
- Exception: A1, A2, K1, SD, CA, etc.
Automating Alerts and Exception Workflows
- Delay Escalation: If X6 persists without AG (new ETA), flag for review
- Missed Delivery: A1 triggers customer service follow up
- Refusal: A7 routes to sales, creates case in CRM
- Customs Hold: K1 notifies compliance, adjusts service levels
- Return Cost Tracking: Aggregate all A3/A7 by product and carrier
Integrating With Major ERP and TMS
Platforms like NetSuite, Infor VISUAL, Microsoft Dynamics, and SAP can consume EDI 214 updates directly, automating goods receipt, three-way match, and production planning. BOLD VAN provides seamless mapping of 214 event codes to your order and shipment tables—no format changes required for your trading partners and no manual lookup needed for daily tasks. Audit-friendly access to 90 days of live EDI history with seven years of archival makes SLA review and compliance simple.
Onboarding and Monitoring 214s: Step-by-Step Checklist
Implementing 214-based visibility means more than just technical mapping—successful setups tie together carrier, EDI, and business teams:
| Step | Action | Result |
|---|---|---|
| 1. Gather Carrier Specs | Request full 214 implementation guide; review code tables | Understand what codes and formats to expect |
| 2. Map Internal Statuses | Create six to eight internal lifecycle stages (e.g., planned, picked up, delivered, exception) | Unified reporting language for all teams |
| 3. Set Up EDI Flow | Configure VAN/EDI platform for mailbox, partner IDs, protocols (AS2, FTP, HTTP) | Consistent, reliable 214 message flow |
| 4. Field Mapping | Attach AT7 values to ERP/TMS shipment records | Immediate status updates in key systems |
| 5. Run Test Scenarios | Test pickups, deliveries, delays, refusals, customs events | Verify each code fires the correct alert or workflow |
| 6. Monitor and Refine | Review 30 to 90 day performance; adjust unmapped or unused codes | Continually aligned exception management |
A practical benchmark for manufacturers is to see 95 percent of shipments progress logically from pickup through delivery codes, with exceptions flagged and escalated within 30 minutes after carrier transmission. If this is not realized, review code mappings or alerting rules and consider refining your business process.
Frequently asked questions
Which EDI 214 status codes are essential for my first integration?
Start with movement codes that cover the full lifecycle: X3 (pickup), AF (departed), X6 (in transit), X1 (arrival at delivery), D1 (delivered), and X4 (at terminal). Add small sets for exceptions such as A1 (missed delivery), A2 (incorrect address), A3 (returned), A7 (refused), CA (canceled), K1 (customs). This combination gives most organizations strong visibility without complexity overload.
Do all carriers use the same 214 status codes?
Carriers follow the X12 standard for EDI 214 and AT7 codes, but many add custom values or subsets, especially for intermodal or regional processes. Always request your carrier’s implementation guide and map their unique codes into your internal workflow before going live.
How frequently do 214 messages arrive for a shipment?
Most truckload or LTL shipments generate 5 to 10 AT7 events from pickup to delivery, including updates whenever a status changes substantially (arrival at facility, departure, delays, etc.). Exception events like delays or refusals add more messages. Frequency depends on carrier practices and modal requirements.
What’s the difference between an AT7 status code and a reason code?
The AT7 status code describes the event (pickup, delivery, transit), while the reason code explains specifics—usually appointment-related or exception-focused (such as missed delivery, incorrect address, customs hold, etc.). Both together give full context for operational action.
How can I keep EDI 214 history easily searchable for audits?
Choose a VAN or EDI platform that retains a minimum of 90 days of shipment data in a searchable portal and archives up to 7 years. BOLD VAN’s platform enables you to search, filter, and retrieve shipment records for audits, scorecards, and SLA analysis, without digging through raw EDI files.
