The EDI 204 · Motor Carrier Load Tender is the document a shipper or broker sends when freight needs a truck and a carrier has to decide — accept the load or refuse it, usually fast. Where the 850 · Purchase Order asks a supplier to sell goods, the 204 asks a carrier to commit capacity: a specific shipment, at specific pickup and delivery points, inside specific time windows. The carrier's answer comes back in the 990 · Response to a Load Tender, and once accepted, the tender becomes the contract the rest of the freight documents are measured against.
That decision window is what makes the 204 unforgiving. A tender that sits unread, or is read with a wrong weight, a wrong appointment time, or a wrong stop sequence, does not just create paperwork noise — it puts the wrong truck in the wrong place, or no truck at all, on the day the freight has to move.
What is the EDI 204 · Motor Carrier Load Tender?
The 204 is an X12 transaction set a shipper, broker, or 3PL uses to tender a shipment to a motor carrier. It carries the shipment identification, the parties, every stop in order — pickup, any intermediate stops, and final delivery — the dates and time windows for each stop, the equipment required, and the commodity detail: pieces, weight, dimensions, and handling notes.
Three ideas define it:
- It is an offer, not an assignment. Until the carrier accepts with a 990 · Response to a Load Tender, no truck is committed. Treating a sent tender as a booked load is the first and most expensive misunderstanding in freight EDI.
- The stop sequence is the shipment. A multi-stop load is not a pickup plus a delivery with extras; the order of stops, and the window attached to each one, is what the carrier actually plans a route and a driver around.
- The detail is operational, not decorative. Weight, cube, equipment type, and appointment windows decide whether the carrier can legally and physically run the load. A tender with placeholder weights tenders a fiction.
A 204 is usually generated from a transportation management system (TMS) at the moment a load is planned, and it supersedes phone calls and rate-confirmation emails as the machine-readable statement of what is being asked.
How is the 204 different from the 210, the 214, and the 990?
These four documents form one freight chain, and confusing any two of them breaks it:
- The 204 · Motor Carrier Load Tender opens the chain: the shipper or broker offers the load, with stops, windows, equipment, and commodity detail.
- The 990 · Response to a Load Tender is the carrier's answer — accept or decline. It is short, and it is the moment capacity is actually committed or released.
- The 214 · Transportation Carrier Shipment Status Message flows during the trip: the carrier reports pickup, departure, arrival, and delivery events against the accepted tender.
- The 210 · Motor Carrier Freight Details and Invoice closes the money side: after delivery, the carrier bills the shipment, and the invoice is audited against what the accepted 204 promised and what the 214 reported.
A useful shorthand: the 204 asks "will you take this load, on these terms?", the 990 answers, the 214 narrates, and the 210 bills. A freight audit that compares the 210 only to the rate, without the accepted 204 behind it, is checking an invoice against half a contract.
Why do shippers tender loads electronically instead of calling carriers?
Because tendering is a decision with a deadline, at volume. A shipper tendering dozens or hundreds of loads a day cannot work a phone tree for each one, and a carrier cannot staff one either. The 204 makes the offer machine-readable so a carrier's system can score it — lane, equipment, driver hours, network balance — and answer with a 990 in minutes.
The deeper reason is the audit trail. A phone tender leaves two memories of the terms; a 204 leaves one document. When the invoice arrives as a 210 and the accessorials do not match what anyone remembers agreeing to, the accepted tender is what settles the argument — which is why the version the carrier accepted, not the version the shipper first sent, is the one worth keeping.
Where do 204 flows usually break?
The first break is the tender treated as a booking. The shipper's team sees the 204 go out and plans as if the load is covered, while the carrier has not yet answered — or has already declined with a 990 nobody loaded. The fix is a state rule, enforced in the system: a load is covered when the acceptance is received and applied, never when the tender is sent.
The second break is the silent timeout. Many tender relationships run on response windows — accept within an hour or the load moves to the next carrier in the routing guide. If a 990 decline or a non-response is not monitored, the load sits in a dead tender while its pickup window closes. Monitoring tender ageing, not just tender transmission, is the control that catches this.
The third break is bad operational detail. Wrong weight, wrong equipment, a delivery window copied from the last load: the carrier accepts in good faith and discovers the truth at the dock, where it becomes a refused pickup, a re-tender at spot rates, or a service failure charged to the wrong party. The 204 is only as honest as the planning data behind it, and it is the worst place in the chain to discover that data was estimated.
The fourth break is the unrecorded change. Pickup times move and stops get added after acceptance, often by phone. If the change never becomes an updated 204, the carrier runs the original plan, the 214 statuses look wrong against the shipper's expectations, and the 210 audit inherits a dispute nobody can reconstruct.
What should you check in a 204 flow?
Four checks keep a load tender honest:
First, acceptance discipline: is every load's state driven by the 990 response actually received — accepted, declined, or timed out — rather than by the tender having been sent?
Second, tender-ageing alarms: is any tender approaching its response deadline without an answer flagged while there is still time to re-tender?
Third, detail fidelity: do weight, equipment, stops, and windows in the 204 match the physical load and the appointments, checked before the tender goes out rather than at the dock?
Fourth, change capture: does every post-acceptance change produce an updated tender in the system of record, so the 214 events and the 210 invoice can be audited against the terms the carrier actually agreed to?
A flow that runs those checks turns the 204 from an electronic phone call into what it is meant to be: a decision both sides can prove.
Frequently asked questions
Is an EDI 204 · Motor Carrier Load Tender a booking?
Not by itself. The 204 is the offer. The carrier's 990 · Response to a Load Tender accepting it is what commits capacity — a tender that was sent but never accepted covers nothing.
What is the difference between the EDI 204 and the EDI 210?
The 204 · Motor Carrier Load Tender offers the load before it moves, with stops, windows, and equipment. The 210 · Motor Carrier Freight Details and Invoice bills the shipment after delivery, and is audited against the accepted tender.
How fast must a carrier answer a 204?
It depends on the relationship's routing guide — response windows of minutes to a few hours are common, and an unanswered tender is usually re-tendered to the next carrier when the window closes. That is why monitoring ageing tenders matters as much as sending them.
What happens after a carrier accepts a 204?
The carrier executes the pickup and delivery and reports progress with 214 · Transportation Carrier Shipment Status Messages, then invoices with a 210 after delivery. Each later document is checked against the accepted tender.
Does a small shipper need the 204?
Only if it tenders freight to carriers at any real volume, or its broker or 3PL tenders on its behalf. A shipper booking an occasional load by phone or portal does not need EDI tendering; once tenders are daily and response windows matter, the 204 earns its keep quickly.
An order asks for goods; a tender asks for a decision, on a clock. The 204 works when both sides treat acceptance — not transmission — as the moment a load becomes real, and when the detail in the tender is the truth about the freight. At SignalEDI, we treat the 204 as the start of a provable chain — tender, answer, status, invoice — because freight disputes are won by the side that kept the documents in order.
— Chris, founder of SignalEDI
Top comments (0)