Every truckload move in North America runs on the same three-document conversation: the EDI 204 load tender, the EDI 990 response, and the EDI 214 status updates. When the loop runs cleanly, freight moves and nobody thinks about it. When it doesn’t, you get missed tenders, auto-revoked loads and a phone bank of check calls. Here is how the loop actually works, where it breaks, and what it takes to automate it end to end.
The load-tender loop, document by document
- EDI 204 (Motor Carrier Load Tender). The shipper or broker offers a load to a carrier: pickup and delivery stops, dates and appointment windows, equipment type, weight, commodity, rate references and special instructions. It can also cancel or update an existing tender, which is where a lot of the trouble starts.
- EDI 990 (Response to a Load Tender). The carrier accepts or declines. Most shippers run a response clock: no 990 inside the window (often 15 to 60 minutes) and the load is auto-revoked and tendered to the next carrier on the routing guide.
- EDI 214 (Shipment Status). The heartbeat of the move: arrived at pickup, loaded, in transit, arrived at delivery, delivered, plus exception codes for delays. Retailers and 3PLs increasingly score carriers on 214 timeliness and completeness.
Two more documents close the conversation: the EDI 210 freight invoice against the delivered load, and the EDI 997 functional acknowledgment confirming each document was received and parseable. The 997 is plumbing, not a business answer; a 997 on a 204 says “I can read your tender”, not “I accept your load”. Confusing the two is a classic onboarding bug.
Where the loop breaks in real operations
- Tender updates that don’t match. A 204 update or cancellation references the original shipment ID differently than the carrier’s TMS stored it, so the update lands as a new load or disappears. The carrier hauls a cancelled load or misses a changed appointment.
- 990s that arrive late or malformed. The carrier accepted in their TMS, but the 990 failed mapping on the way out. The shipper’s clock expires, the load auto-revokes, and both sides think the other dropped it.
- 214 gaps. Status codes that a partner requires but the map never sends, timezone errors on appointment times, or statuses batched hours late. Every gap becomes a check call, and repeated gaps become a scorecard problem.
- Partner-specific variations. Every shipper implements the “standard” 204 differently: different stop-off conventions, reference qualifiers and required segments. Each variation is a bespoke map, and each bespoke map is a developer ticket in most platforms.
What “automated” has to mean
Automating the loop is not just moving the documents. It means three things. First, the partner-specific mapping logic is captured in a spec your analysts own, so a new shipper’s 204 flavor is a spec-writing exercise, not a developer queue. Second, every document is validated against the partner’s requirements before it leaves, so 990s do not die on the wire while the response clock runs. Third, when something does fail, operations can see exactly which transaction failed, fix the map, and replay it in one click instead of reconstructing the move from logs.
That is the architecture behind DEXA: the mapping requirement spec is the source of truth, AI generates and tests the translator from it, and every run is observable and replayable. In a live logistics estate, that approach converted 110 EDI maps in five weeks with roughly 60% less effort, about 1,500 hours saved.
Frequently asked questions
What is an EDI 204?
The EDI 204 Motor Carrier Load Tender is the X12 transaction a shipper or broker sends to offer a load to a carrier. It carries stops, dates, equipment, weight and references, and it can also update or cancel a previously sent tender.
What is the difference between an EDI 990 and an EDI 997?
The 990 is the business answer: the carrier accepts or declines the tendered load. The 997 is a technical acknowledgment that a document was received and structurally valid. A 997 on a 204 does not mean the load was accepted; only the 990 does.
Why do shippers auto-revoke tenders?
Routing guides run on response clocks. If the carrier’s 990 acceptance does not arrive within the window, the shipper’s TMS revokes the tender and offers the load to the next carrier. Late or failed 990 mappings are one of the most expensive silent failures in carrier EDI.