Transportation EDI Beyond ASN: 204, 990, 214, 210 in Logistics Workflows
When most people hear “EDI” in a retail supply chain context, they think of the 856 Advance Ship Notice. But the ASN only tells a receiver what’s coming — it doesn’t cover how a shipment gets booked with a carrier, confirmed, tracked in transit, or paid for. That’s a separate set of transaction types built specifically for transportation, and understanding them is essential for any EDI practitioner working with carriers, brokers, or third-party logistics providers.
The core transportation transaction set
Four EDI documents form the backbone of a typical truckload move:
- EDI 204 – Motor Carrier Load Tender. This is how a shipper or broker offers a load to a carrier. It carries detailed scheduling, equipment requirements, commodities, and shipping instructions relevant to the load tender, and it’s meant strictly for full truckload moves rather than LTL bills of lading, pickup notices, or manifests.
- EDI 990 – Response to a Load Tender. This is where the carrier accepts, rejects, or counters the shipper’s offer — the transactional handshake that turns a tender into a committed load.
- EDI 214 – Transportation Carrier Shipment Status. Carriers use this transaction set to give shippers, consignees, and their agents visibility into shipment status — dates, times, locations, and route information as the freight moves toward delivery.
- EDI 210 – Motor Carrier Freight Details and Invoice. This closes the loop, with the carrier billing the shipper for completed service.
Together, these four documents map directly onto the physical lifecycle of a shipment: tender, acceptance, movement, and payment.
How a broker like C.H. Robinson structures the flow
C.H. Robinson’s carrier specs illustrate how this plays out operationally. An outbound 204 load tender includes shipment-level detail such as bill-to information, equipment needs, and stop sequencing, with reference qualifiers (L11 segments) used to pass load numbers, accessorial charges, and move types back and forth between systems. Carriers are expected to return status using the 214, with specific service-level expectations — for example, requesting “In Transit” status updates on a defined cadence throughout the move. On the acknowledgment side, C.H. Robinson defaults to sending 997 functional acknowledgments for received 214s unless a carrier requests otherwise, and it will not correct malformed data submitted by a trading partner — a reminder that syntax validation is the carrier’s responsibility, not the broker’s.
Critically, data has to be consistent across the set. Rate and term information agreed to in the 990 should flow through unchanged to the 210 invoice; discrepancies between what was committed and what was billed create disputes that slow down payment cycles and strain carrier relationships.
Where DHL’s model differs
DHL’s standard EDI offering frames the same lifecycle around three functions rather than four discrete document types: booking, status, and invoice, delivered through a single message service covering ordering, status reporting, and invoicing across shipments by road, ocean, air, or express. The underlying standard is EDIFACT D.01B, alongside XML for structured data transmission — a contrast to the ANSI X12 transaction sets used by domestic U.S. carriers like C.H. Robinson. Practitioners integrating with both networks need to map X12’s 204/990/214/210 logic to EDIFACT equivalents (IFTMIN, IFTSTA, IFTMCS) rather than assuming a single transaction-set vocabulary applies globally.
The practical takeaway
For EDI practitioners, transportation documents aren’t optional add-ons to the retail 850/855/810/856/997 cycle — they’re a parallel workflow with their own sequencing logic. Get the 204 tender fields wrong, and the 990 response can’t confirm rates cleanly. Skip 214 status cadence requirements, and visibility commitments to shippers break down. Let 210 invoice data drift from the 990 commitment, and freight payment disputes follow. Mapping these four documents correctly — and understanding where a partner’s EDIFACT equivalents diverge from X12 — is foundational work for anyone managing carrier-side integrations.
EDI Academy is a vendor-neutral EDI training and certification provider helping retail, supply chain, finance, and IT teams build practical skills for accurate transactions and smoother operations.