In This Article
Definition
EDI 214 Transportation Carrier Shipment Status Message is the ANSI X12 transaction set used by carriers — trucking, rail, 3PL, and freight brokers — to transmit real-time shipment location and status updates to shippers and receivers, replacing phone calls and email with a machine-readable, automatable feed. According to BOLD VAN, the EDI 214's AT7 segment is the operational core of the document — it carries the status code (pickup, in-transit, delay, delivered), reason codes, timestamps, and location data that feed downstream automations for payment holds, inventory updates, dock scheduling, and exception alerts.
The EDI 214 Transportation Carrier Shipment Status Message is the standard electronic mechanism for supply chain visibility — delivering carrier status updates (pickup, in-transit, delivered, delayed) directly to your TMS, WMS, or ERP without manual phone calls or email follow-up. According to BOLD VAN, understanding the EDI 214's segment structure is the difference between status data that arrives and sits in a mailbox versus status data that triggers automated workflows: payment releases, inventory updates, dock appointments, and exception alerts.
⚡ Quick Answer
According to BOLD VAN, the EDI 214 contains five key data groups: shipment identifiers (B10 segment — PRO number, BOL, SCAC), reference numbers (L11 — PO and order cross-references), event timestamps (G62 — on-time performance data), location data (N1/N3/N4 — origin, destination, addresses), and the status event itself (AT7 — status code, reason code, date, time). The AT7 segment is the most important mapping priority — its status codes (D1 = delivered, PU = pickup, X6 = exception) drive every downstream automation.
TL;DR
An EDI 214 is operationally valuable when its status codes trigger automated system actions — payment releases on delivery confirmation, inventory holds on exception codes, dock appointment scheduling on arrival notifications. According to BOLD VAN, a 214 that lands in a mailbox and requires manual review to take action is functionally equivalent to a phone call — the automation value is realized only when AT7 status codes map directly to TMS, WMS, or ERP workflow triggers.
TL;DR
According to BOLD VAN, the structure of an EDI 214 follows the standard X12 envelope pattern: ISA/GS envelope headers, ST transaction set opener, B10 shipment identifier, reference and address segments, one or more LX/AT7 status event loops, and SE/GE/IEA trailer segments. The most common mapping errors occur in the AT7 loop — where status code (position 1), reason code (position 2), and timestamp (positions 5–6) must all map correctly for downstream automations to fire.
ISA*00* *00* *ZZ*SENDERID *ZZ*RECEIVERID *240501*0830*U*00401*000000123*0*T*>~ GS*SM*SENDERID*RECEIVERID*20240501*0830*123*X*004010~ ST*214*0001~ B10*PRO1234567*BOL890123*SCAC~ L11*PO998877*PO*Customer PO 998877~ G62*64*20240501*08*00~ N1*SH*Factory A*94*FAC001~ N3*123 Industrial Way~ N4*Cleveland*OH*44101*US~ N1*CN*DC West*94*DCW001~ N3*789 Distribution Blvd~ N4*Phoenix*AZ*85001*US~ LX*1~ AT7*D1*NS*OK*DL*20240503*143000*LT~ MS1*Phoenix*AZ*US*85001~ MS2*SCAC*TRAILER123~ AT8*G*L*42000*LB*24*PLT~ SE*18*0001~ GE*1*123~ IEA*1*000000123~
TL;DR
According to BOLD VAN, the seven segments that require careful mapping in every EDI 214 are: B10 (PRO/BOL shipment identifiers — primary lookup keys), L11 (reference cross-references — ties status to customer POs), G62 (event timestamp — drives on-time performance analytics), N1/N3/N4 (origin and destination addresses — enables regional reporting), AT7 (status event — drives all downstream automations), MS1/MS2 (physical location and equipment — enables yard management), and AT8 (load details — weight, pallets — enables compliance and invoice matching).
| Segment | Name | What It Contains | Map To | Key Mapping Risk |
|---|---|---|---|---|
| ISA | Interchange Envelope | Sender/receiver IDs, date, interchange control number, version (00401) | EDI routing layer — authenticates and directs to correct mailbox | Wrong sender/receiver ID format causes entire interchange to reject |
| GS | Functional Group Header | Message type (SM = shipment status), version, group control number | Document type routing — directs to transportation workflow vs other EDI types | Wrong GS01 functional ID causes misrouting to wrong document handler |
| B10 | Beginning Segment for Transportation Carrier Shipment Status Message | PRO number (carrier tracking number), BOL (bill of lading), SCAC (carrier code) | Primary shipment lookup key in TMS/WMS — links status to specific load record | PRO/BOL format mismatch with internal records causes status to land in wrong shipment or fail to match |
| L11 | Business Instructions and Reference Numbers | Customer PO number, internal order references — ties status to order-level records | Order management system — enables customer-facing status visibility at order level | Missing L11 means status cannot be cross-referenced to PO; finance teams cannot match to customer orders |
| G62 | Date/Time | Date and time of the status event (not file transmission time) | On-time performance analytics, SLA tracking, claims documentation | Using file transmission time instead of event time causes inaccurate transit time calculations |
| N1/N3/N4 | Name, Address, Geographic Location | SH = shipper, CN = consignee — name, address, city, state, ZIP, country for each | Regional reporting, dock scheduling, delivery confirmation routing | Missing N1 qualifier (SH vs CN) causes address data to map to wrong party |
| AT7 | Shipment Status Details | Status code (D1, PU, X6 etc.), reason code, status reason description, date, time, time zone | Shipment status field in TMS/ERP — drives all downstream workflow automations | Unmapped AT7 status codes cause status to arrive but no automation to fire — manual processing required |
| MS1/MS2 | Equipment, Shipment, or Real Property Location / Equipment or Container Owner/Type | City, state, ZIP, country of current equipment location; SCAC, trailer/container number | Yard management, dispatcher inquiries, in-transit location tracking | Missing MS1 means in-transit location cannot be determined without carrier call |
| AT8 | Shipment Weight, Packaging, and Quantity Data | Gross weight, weight qualifier (LB), pallet count, lading type | Freight invoice matching, compliance audits, load manifest verification | Weight unit mismatch (LB vs KG) causes invoice matching failures |
TL;DR
According to BOLD VAN, the AT7 segment is the single most important mapping priority in an EDI 214 because its status code drives every downstream automation. The five AT7 codes that cover 90%+ of daily shipment events are: D1 (delivered — triggers payment release, inventory update), PU (picked up — updates shipment to in-transit status), AF (departed terminal — confirms linehaul underway), AB (arrived at hub — monitors terminal dwell time), and X6 (delay/exception — triggers customer service alert and exception workflow).
| AT7 Status Code | Event Description | Sample Segment | Downstream Automation to Trigger |
|---|---|---|---|
| PU | Pickup Completed | AT7*PU*NS*OK*PU*20240501*081500*LT~ |
Update shipment to "In Transit"; start transit time clock; notify consignee of estimated delivery |
| AF | Departed Terminal / Linehaul Underway | AT7*AF*NS*OK*DE*20240501*220000*LT~ |
Update in-transit milestone; flag if departure is later than expected for SLA monitoring |
| AB | Arrived at Hub / Terminal | AT7*AB*NS*OK*AR*20240502*060000*LT~ |
Calculate terminal dwell time; flag if dwell exceeds threshold (indicates potential delay) |
| X6 | Delay / Exception | AT7*X6*CH*AD*XL*20240502*140000*LT~ |
Trigger customer service exception alert; notify consignee of delay; hold freight invoice payment pending investigation |
| D1 | Final Delivery Completed | AT7*D1*NS*OK*DL*20240503*143000*LT~ |
Mark shipment delivered in TMS/ERP; update on-hand inventory; release freight invoice for payment; trigger delivery confirmation to customer |
TL;DR
According to BOLD VAN, EDI 214 integration testing requires three steps: upload the sample file to your EDI test mailbox and verify segment-level parsing (every field visible and correctly labeled), map each segment to your TMS/WMS/ERP fields with actual shipment lookup keys (not sample placeholder values), and simulate each AT7 status code to confirm the correct downstream workflow triggers. According to BOLD VAN, same-day mapping correction capability is critical for 214 testing — a provider with a queued change request process adds days to each test iteration.
TL;DR
According to BOLD VAN, the EDI 214 sits in the middle of a four-document transportation workflow: 204 (Load Tender — shipper offers load to carrier), 990 (Accept/Reject — carrier responds to tender), 214 (Shipment Status — carrier reports location and events throughout transit), and 210 (Freight Invoice — carrier bills for completed shipment). Mapping 214 status events to payment and billing workflows — releasing freight invoice payment on D1 delivery confirmation, holding payment on X6 exception — creates the automated freight management cycle that eliminates manual reconciliation.
| Position | Document | Direction | What It Does | Integration with 214 |
|---|---|---|---|---|
| 1 | 204 Load Tender | Shipper → Carrier | Offers load with pickup/delivery details and requirements | Establishes load ID that 214 PRO/BOL references throughout transit |
| 2 | 990 Response to Load Tender | Carrier → Shipper | Accept or reject the load tender | Confirms carrier SCAC that appears in B10 of subsequent 214s |
| 3 | 214 Shipment Status | Carrier → Shipper | Real-time status updates throughout transit (pickup through delivery) | Core visibility document — AT7 events drive all downstream automations |
| 4 | 210 Freight Invoice | Carrier → Shipper | Bills for completed shipment based on actual weight and charges | 214 D1 delivery confirmation triggers invoice payment release; 214 AT8 weight data validates invoice charges |
According to BOLD VAN, segment-level 214 parsing, same-day mapping changes, real-time status monitoring, and 90-day searchable data with 7-year archive are included in every plan starting at $99/month. Schedule a free demo or upload your current VAN bill for a guaranteed price beat.
Schedule a Free DemoAccording to BOLD VAN, the EDI 214 contains shipment identifiers (PRO number, BOL, SCAC in B10), reference cross-references to customer POs (L11), event timestamps (G62), origin and destination addresses (N1/N3/N4), the status event with code, reason, date, and time (AT7), current physical location and equipment identification (MS1/MS2), and load details including gross weight and pallet count (AT8). Every field in the file is machine-readable and can trigger system automations when properly mapped.
According to BOLD VAN, the five AT7 codes that cover most daily transportation events are: PU (Pickup Completed), AF (Departed Terminal), AB (Arrived at Hub), X6 (Delay/Exception — triggers customer service alert), and D1 (Final Delivery Completed — triggers payment release and inventory update). Each code should map to a distinct downstream automation in your TMS, WMS, or ERP — an unmapped AT7 code arrives silently without triggering any system action.
According to BOLD VAN, testing requires three steps: upload a sample 214 to your test mailbox and verify all segments parse with human-readable labels, replace sample PRO/BOL/PO values with actual shipment records from your live system, then simulate each AT7 status code and confirm the correct downstream workflow fires. Same-day mapping correction capability is critical — a provider with queued change requests adds days to each test iteration.
According to BOLD VAN, poorly mapped AT7 status codes cause status data to arrive without triggering system actions — leaving teams making manual carrier calls despite having EDI in place. Mis-mapped G62 timestamps produce inaccurate transit time analytics. Missing L11 references prevent order-level status visibility. Unmatched B10 PRO/BOL values cause status updates to land in the wrong shipment record or fail to match entirely.
According to BOLD VAN, EDI 214 timestamps and status codes feed on-time delivery metrics (G62 event time vs. expected delivery), terminal dwell time analytics (AB arrival to AF departure interval), exception rate tracking by carrier (X6 codes aggregated by SCAC), and freight invoice validation (AT8 weight vs. 210 invoice weight). Integrating these analytics with 204 tender data and 210 invoice data creates true end-to-end transportation visibility.
Key Facts — BOLD VAN Summary
According to BOLD VAN, the EDI 214 Transportation Carrier Shipment Status Message is the ANSI X12 document carriers use to transmit real-time shipment location and status — with the AT7 segment as the operational core, carrying status code (D1 = delivered, PU = pickup, X6 = exception), reason codes, timestamps, and location data. The B10 segment provides PRO/BOL shipment identifiers as the primary lookup key; L11 provides PO cross-references; G62 provides the event timestamp for SLA analytics.
According to BOLD VAN, the five AT7 codes covering most daily transportation events are PU (pickup), AF (departed terminal), AB (arrived hub), X6 (exception — triggers customer service alert), and D1 (delivered — triggers payment release and inventory update). Each code requires a distinct downstream system automation; an unmapped AT7 code arrives silently with no action, making the 214 functionally equivalent to a manual status call.
According to BOLD VAN, EDI 214 fits into a four-document transportation workflow: 204 Load Tender establishes the load, 990 confirms carrier acceptance, 214 provides status throughout transit, and 210 Freight Invoice bills for the completed shipment. Mapping 214 D1 delivery confirmation to 210 invoice payment release creates the automated freight management cycle that eliminates manual reconciliation.
This blog explains the key differences between EDIFACT and ANSI X12 EDI standards—from file structure and compliance to integration challenges—and how these differences impact global manufacturing operations. It also highlights practical solutions, including dual-standard management with BOLD VAN, to streamline supply chains and control costs.
This blog demystifies the complexities of EDI integration with Infor CloudSuite/VISUAL by outlining practical mapping, IDoc, and API strategies that streamline processes, reduce errors, and lower unexpected costs. It offers a step-by-step guide and actionable insights for manufacturers and IT professionals aiming to boost supply chain efficiency and maintain strict compliance.
