Transaction explainers · November 6, 2026

EDI 990 Response to a Load Tender: The Complete Guide

How the EDI 990 works: accepting or declining 204 load tenders, response-time expectations, tender waterfalls, and what acceptance rates cost carriers.

The EDI 990 is the shortest consequential document in freight. A shipper's TMS tenders a load with the 204; the carrier's answer — accept or decline — travels back as the 990. One decision, a reference number, and a timestamp. But strung together across thousands of tenders, those small answers become the metric that decides who gets tomorrow's freight: tender acceptance rate. In the shipper-carrier world, typically X12 4010, few documents carry more commercial weight per byte.

What's inside a 990

The document is deliberately minimal:

  • Shipment identification — the shipper's shipment/load ID from the 204, echoed exactly. This is non-negotiable plumbing: a 990 that can't be matched to its tender is a missed response, whatever it says.
  • The decision — an action code: accepted or declined. Some programs use a conditional accept-with-changes flow, but the routing guide governs whether that's honored; confirm rather than assume.
  • Reason detail — optionally, why a load was declined: no capacity, equipment mismatch, lane imbalance. Shippers that receive structured decline reasons plan better, and carriers that give them read as partners rather than black boxes.

That's essentially it. The engineering challenge isn't the document — it's answering fast, correctly, every time.

The clock and the waterfall

Truckload tendering runs on a waterfall: the TMS offers the load to the first carrier in the routing guide, waits a defined window, and on decline or expiry cascades to the next carrier, then to a broker, then to the spot market. Two numbers fall out of this mechanic and follow the carrier around:

  1. Response time. Tender windows are program-specific — confirm each shipper's in the routing guide — but they're short, and an expired tender counts against you exactly like a decline, with the added sting of having wasted the shipper's window.
  2. Acceptance rate. Routing guides get re-ranked on it. A carrier that accepts reliably on a lane earns primary position and steadier volume; a carrier that declines often drifts down the waterfall toward the freight nobody wanted. During tight markets, acceptance history is the difference between contracted volume and spot scraps.

The operational conclusion: the 990 must be generated from a live decision process — dispatch sees the tender immediately, capacity is checked, the answer transmits within the window. A tender that waits in a mailbox until morning is a decline you didn't choose.

The chain the 990 anchors

Accepting the tender is a commitment the rest of the document chain then documents: the 214 status feed narrates pickup through delivery, and the 210 freight invoice bills the move at the tendered terms. That linkage is why reference discipline starts here — the shipment ID accepted on the 990 is the thread the audit follows from tender to payment. Meanwhile the 997 rides along at the transport layer for every document, both directions, confirming receipt within minutes; programs expect it in addition to, never instead of, the business response.

For brokers, the 990 runs both directions: answering shippers' tenders upstream while tendering to carriers downstream. Latency compounds across that hop, which is why brokers are often the most demanding 990 counterparties of all.

Running tenders without leaks

The failure modes are consistent across fleets: tenders arriving into unmonitored channels, responses batched instead of event-driven, mismatched reference numbers breaking the tender-to-response match, and no reconciliation of what was accepted versus what was actually dispatched. Every one of them is an automation problem, not a people problem.

EDISQ treats the freight tender loop like every other flow on the platform: certified partner maps, validation against each partner's spec before transmission, automatic 997s, and AS2, SFTP, or VAN connectivity operated as part of the service. Pricing meters documents, not relationships — the first 25 each month free, then from $0.50 per document tapering with volume, published in full on the pricing page. A 990 is one small document; answering it fast, every time, is the whole game.

FAQ

What is an EDI 990?

The Response to a Load Tender — the document a carrier sends back to a shipper or broker to accept or decline a 204 load tender. It references the tender's shipment ID and states the decision, optionally with a reason.

How fast must a carrier respond to a tender?

The window is set by the shipper's routing guide — commonly measured in minutes to a few hours for truckload tenders. Miss the window and the load rolls to the next carrier in the waterfall, and the miss is recorded.

What is a tender waterfall?

The shipper's TMS offers the load to carriers in routing-guide order. Each declined or expired tender cascades to the next carrier. Acceptance rate and response speed determine where a carrier sits in that order over time.

Is a 997 the same as a 990?

No. The 997 says 'your document arrived and parsed.' The 990 is the business answer — take the load or not. Programs typically expect both: a 997 within minutes, a 990 within the tender window.