The EDI 214 is the Transportation Carrier Shipment Status Message — the document carriers send to report pickup confirmations, checkpoint arrivals, delays with reasons, exceptions and final delivery. Key points:
- Every update ties to a specific shipment ID, PO number, SCAC carrier code and timestamp
- Eight status codes cover most events: PU, DE, AR, DL, RT, HE, AD, XL
- The exception codes (XL, HE, RT) carry the most operational value — they let teams respond before the impact lands
- The DL code with proof-of-delivery details can trigger invoice approval automatically in an integrated ERP
Trying to make sense of a 214 that isn't posting to your ERP? Ask us — we love a good status code mystery. Start a conversation.
Without EDI 214 automation, shipment status visibility defaults to the most expensive possible method: phone calls to carriers, inbox monitoring and reactive scrambles over problems that were already hours old when someone noticed. The 214 replaces all of that with structured, timestamped checkpoints tied to specific orders — and teams that implement it well reduce manual shipment tracking dramatically.
The status updates themselves aren't the point, though. The point is converting a transportation event — a delay, a customs hold, a delivery — into an immediate operational response: adjusted warehouse labor, a proactive customer heads-up, an invoice approved the hour the truck unloads. This guide covers what's in a 214, what each status code means and when carriers should send them.
In this article
What EDI 214 Is and Why It Matters
The EDI 214 is the standardized X12 document carriers use to transmit shipment status to shippers, receivers and trading partners. Three things separate it from a generic "in transit" notification:
It's tied to specific orders. Every update carries the shipment ID and PO number, so whoever receives it knows immediately which order is affected and can pull the ERP record without a search — no "which shipment was that again?" step.
It's timestamped with enough precision to act on. Updates include actual times, revised ETAs and delay reasons, which is what lets a warehouse adjust receiving labor or a planner reshuffle production. A three-hour delay discovered from an XL update the moment it happens costs a fraction of the same delay discovered from an angry customer call.
It closes the billing loop. The DL (delivered) status arrives with proof-of-delivery timestamp and signature details — exactly what finance needs to approve the carrier's EDI 210 invoice without waiting for a signed BOL to surface. That's a direct cash flow benefit, not just a visibility one.
Key Components of an EDI 214 Message
| Data Element | What It Contains | Operational Use |
|---|---|---|
| Shipment ID and PO number | Unique identifiers tying the status event to a specific order in the ERP | Immediate record lookup, no manual order identification |
| Carrier info (SCAC), shipper, receiver | Carrier Standard Carrier Alpha Code, origin party, destination party | Carrier performance tracking; contact routing for escalation |
| Key dates and times | Actual pickup timestamp, estimated arrival, revised arrival, hold durations | Warehouse labor scheduling; inventory planning; customer communication |
| Location updates | Named terminal, port, cross-dock or inspection facility, with departed/arrived context | Route tracking; customs document prep; dock scheduling |
| Status codes | Structured event classification (PU, DE, AR, DL, RT, HE, AD, XL) | Automated ERP workflow triggers; exception routing; invoice approval |
| Exception and reason details | Specific reason for a delay, hold, return or reroute | Root cause documentation; carrier scorecards; customer updates |
Status Codes Decoded: The Eight Codes Every Team Needs to Know
| Code | Meaning | Example Update | Operational Response |
|---|---|---|---|
| PU | Pickup — cargo has left the origin facility | "PU at 08:00 from Factory X, SCAC:TRUK, ETA 12/13 2 PM" | Baseline ETA set in ERP; receiving dock scheduled; customer notified of ship date |
| DE | Departed — rolling out from a hub or checkpoint | "DE Terminal Y at 14:30, I-95 route confirmed" | ETA confirmation; route tracking updated |
| AR | Arrived — reached a terminal, port or checkpoint | "AR Warehouse Z at 16:45" | Receiving dock prep; inbound workflow initiated |
| DL | Delivered — proof of delivery logged | "DL 17:20, signed J.Smith, DC Receiving Door 4" | Invoice approval triggered; EDI 210 payment processing initiated |
| RT | Return — goods heading back, usually for damage or refusal | "RT PO#4567, refused — damaged packaging" | Immediate investigation; replacement shipment evaluated; customer notified |
| HE | Held — journey paused for customs or inspection | "HE at Airport — awaiting customs docs until 6 PM UTC" | Customs document prep; dock rescheduled; customer ETA updated |
| AD | Advance date — ETA improved over the original estimate | "AD — revised ETA 12/13 11 AM, 3 hours early" | Receiving moved up; labor scheduling adjusted |
| XL | Explain late — delay with a specific reason | "XL Traffic accident I-95, ETA revised to +4 hours" | Receiving labor rescheduled; production adjusted; customer proactively notified |
Notice which codes actually earn their keep. PU, DE, AR and DL confirm things you expected to happen. The exception codes — XL, HE and RT — are the ones that flag things you didn't, while there's still time to respond. A 214 program's value is roughly proportional to how fast those three codes trigger action.
Getting 214s from carriers but they're not flowing into your ERP the way they should? That's a puzzle we happily take on. Tell us what's happening — no pitch, just answers.
A Real-World EDI 214 Scenario, Pickup to Delivery
Consider a batch of HVAC parts shipping from a factory to a distributor's DC — a routine load whose status would otherwise take multiple phone calls to track through the day:
7 a.m. — PU (Pickup). The carrier sends "Picked up PO#4567 at Factory Site, SCAC:TRUK, ETA 12/13 2 PM." The ERP updates the sales order with the pickup confirmation and baseline ETA, the receiving dock gets scheduled and the customer gets a ship-date notification. Nobody made a call.
Noon — DE (Departed). "Departed terminal, I-95 route confirmed." The ERP notes the checkpoint; ETA holds. No action needed — the update's job is confirming the shipment is progressing.
2 p.m. — XL (Delay). "Traffic accident I-95, revised ETA +3 hours, expected 5 PM." The ERP updates the arrival, the dock supervisor gets a notification to shift labor, and the customer receives the revised ETA before they'd have thought to ask. Three hours of reactive scrambling becomes two minutes of automated notification.
5 p.m. — AR, then DL. "Arrived DC Receiving," and 10 minutes later, "Delivered 5:10 PM, signed J.Smith, Door 4." The delivery confirmation triggers the invoice approval workflow, EDI 210 payment processing starts and finance closes the receivable — again, without a call to the dock.
When to Send EDI 214: The Five Trigger Moments
Status updates should follow operational decision points, not a clock. Five moments matter:
- After pickup. The PU update establishes the baseline ETA that dock scheduling, labor planning and delivery commitments are all built on. A pickup confirmation that arrives hours late means every downstream decision is made on stale data.
- At major checkpoints. DE and AR updates at terminals, border crossings and ports turn ETA anxiety into ETA confidence — and for cross-border loads, an AR at the customs checkpoint starts document prep before a hold ever posts.
- The moment a delay (or improvement) is confirmed. An XL or AD sent immediately gives receiving teams and customers the maximum response window. The same delay reported an hour before the original ETA gives them none.
- For every exception. Returns, holds, damage and reroutes all require responses — investigations, replacement evaluation, customs paperwork — that can't start until the exception is communicated. Every hour between event and transmission is response window lost.
- At final delivery. The DL update with signature, timestamp and location details is what lets finance approve the carrier invoice automatically instead of after a phone call to the dock.
Whether you're setting up 214s with your first carrier or drowning in status updates that never reach the right people, we're glad to talk it through — no demo, no obligation. And because our pricing is flat per partner, high-frequency 214 traffic never costs you extra.
Let's talk shipment visibilityFrequently Asked Questions
What is the difference between EDI 214 and EDI 856 for shipment tracking?
The EDI 856 (Advance Ship Notice) is sent by the shipper before departure — what's being shipped, how it's packed and when it should arrive. The EDI 214 is sent by the carrier during transit — what's actually happening to the shipment, including delays, exceptions and final delivery. The 856 is the pre-shipment commitment; the 214 is the in-transit reality. Complete shipment visibility takes both.
Which EDI 214 status codes are most important for manufacturing operations?
The exception codes. XL (delay with reason) lets you adjust receiving labor and production scheduling before the impact lands, HE (held) lets you prepare customs documents before a hold extends, and RT (return) lets you start investigating before misdirected goods become a bigger problem. The routine codes — PU, DE, AR, DL — confirm expected events; the exception codes are where the operational value lives.
How does EDI 214 accelerate invoice approval?
The DL (delivered) status carries the proof-of-delivery timestamp and signature details finance needs to approve the carrier's EDI 210 invoice. When DL receipt is wired into the ERP accounts payable workflow, invoice approval triggers automatically — no waiting on a phone call to the receiving dock or a signed BOL in the mail.
Do EDI 214 messages incur per-message fees?
It depends on your provider's pricing model, and it matters more for the 214 than almost any other document — carriers can send four to six updates per shipment, and far more during peak seasons. Per-message pricing turns that volume into a bill. BOLD VAN includes unlimited 214 processing in flat per-partner pricing, so status update frequency never changes the cost.
