The 204 is freight's opening move. Where retail starts with a purchase order, the shipper–carrier world starts with a load tender: a shipper (or its broker or 3PL) electronically offers a specific load to a specific carrier, with everything the carrier needs to say yes — stops, windows, equipment, weight, and the rate reference. The X12 4010 version of that offer is the 204, and it anchors a four-document loop that runs most contract truckload and LTL freight in North America.
What's inside a 204
Strip the syntax and the 204 is a dispatch sheet:
- Shipment ID and purpose. The B2 segment carries the shipper's shipment reference and whether this is an original tender, an update, or a cancellation. Carriers key everything to this ID.
- References. BOL number, PO numbers for the freight being moved, rate or contract references. These must round-trip onto the status messages and the invoice, or settlement matching breaks.
- Stops. S5 loops define each stop in sequence — pick, drop, or both — with addresses, appointment windows, and per-stop weights and piece counts. Multi-stop tenders live or die on stop sequencing being explicit.
- Equipment and service. Trailer type and length, temperature requirements for reefer loads, hazmat flags, driver assist or liftgate needs.
- Totals. Weight, cases or pallets, and linear feet where it matters. Carriers price and plan against these; chronic understatement is how a shipper earns rejected tenders.
An update tender (same shipment ID, purpose code for change) replaces the original; a cancellation kills it. Carrier systems apply them in sequence, which is why out-of-order transmission — an update arriving before its original — is a classic integration bug worth testing for.
The response loop: 990, 214, 210
The 204 never travels alone. Three companions complete the lifecycle:
- 990 Response to Load Tender. Accept or decline, against a response window the shipper defines — commonly measured in minutes to a few hours for contract freight. No answer inside the window reads as a decline, and the shipper's routing guide cascades the load to the next carrier on the lane. Fast, automated 990s are how carriers protect tender acceptance scores, which in turn protect their position in the routing guide.
- 214 Transportation Carrier Shipment Status. The heartbeat while the load moves: dispatched, arrived at shipper, loaded, in transit with position, arrived at consignee, delivered. Shippers grade carriers on 214 timeliness and completeness because their own customers' promise dates depend on it.
- 210 Motor Carrier Freight Details and Invoice. The carrier's bill, matched against the tender's rate references and the delivered status. Accessorials — detention, layover, lumper fees — appear as separate charge lines, and disputed 210s almost always trace to accessorials that were never captured as events during the move.
The discipline that makes the loop work is reference integrity: the shipment ID and references from the 204 appear verbatim on the 990, every 214, and the 210. When they do, settlement is a machine's job. When they don't, it's a phone call.
Who has to care
Carriers meet the 204 as a requirement from any sizable shipper: trade it electronically or don't get the freight. Shippers and brokers meet it from the other side — moving from emailed rate cons to tendering via EDI is usually driven by TMS adoption and the need for auditable tender-acceptance data. Both sides trade on X12 4010, over the same AS2 or SFTP transports as retail EDI (the AS2 primer applies unchanged), with 997 functional acknowledgments confirming receipt of every document within minutes — a tender that was never acknowledged is a load nobody is covering.
For a supplier who already trades retail documents like the 850, the freight set is a second dialect of a familiar language: same envelopes, same transports, different segments.
Running the loop with EDISQ
EDISQ carries freight documents on the same meter as everything else: per document, first 25 each month free, then from 50¢ tapering with volume, with AS2/SFTP/VAN connectivity operated as part of the service and acknowledgments automatic in both directions. A carrier standing up its first shipper connection, or a shipper tendering to a stable of carriers, prices the whole program from document counts alone — details on how the platform works.
FAQ
What is an EDI 204?
The Motor Carrier Load Tender — a shipper's electronic offer of a load to a carrier. It carries the stops, dates, equipment requirement, weight and piece counts, and the reference numbers the carrier must echo on status updates and the invoice.
How does a carrier respond to a 204?
With a 990 Response to Load Tender — accept or decline, usually inside a response window the shipper sets. Silence past the window is treated as a decline by most TMS routing engines, and the load cascades to the next carrier.
What's the difference between the 204 and the 214?
The 204 tenders the load before it moves; the 214 reports status while it moves — dispatched, arrived at pickup, loaded, in transit, delivered. Same load, two phases of its life.
What X12 version is used for freight documents?
Version 4010 remains the norm across the shipper-carrier world. Most freight EDI programs run the 204/990/214/210 set on 4010, typically over AS2 or SFTP.