How Load Tendering Works in Trucking
A plain-language guide to load tendering in US and Canadian trucking—EDI 204, rate cons, load boards, portals—and why accept, decline, and exception workflows differ by operation.
Load tendering is how freight gets offered, reviewed, and either booked or turned down in North American trucking. In plain terms: a shipper or broker sends a carrier a work offer with the details needed to move a load; the carrier accepts, declines, counters, or lets the offer expire—and the path that offer takes is rarely the same from one company to the next.
If you work dispatch, brokerage, or freight ops in the US or Canada, you already live this. What changes is the channel (EDI versus email versus a load board), the clock (minutes versus hours), who is allowed to say yes, and what happens when the equipment, rate, or timing does not match. Those differences are why tendering playbooks have to be flexible: every freight business runs unique rules around capacity, customers, and risk.
What load tendering is
Load tendering is the formal offer of a shipment to a motor carrier (or to a broker acting as the capacity manager), with enough detail to decide whether the move fits the network. A typical tender includes origin and destination, appointment or window times, equipment type, commodity and handling notes, weight and pieces, rate or rate method, reference numbers, and any special instructions (hazmat, temperature, team drivers, tarp, and so on).
Tendering is not the same as quoting. Quoting is often exploratory—what would this cost, can you cover it. A tender is closer to a booking request: take this load under these terms, or tell us you cannot. After acceptance, the operational loop usually continues with status updates and eventual settlement; in electronic trading partner setups, those later steps often use related message types such as shipment status and invoice documents.
In North America, the industry convention for electronic motor-carrier tenders is the ANSI X12 EDI 204 (Motor Carrier Load Tender). The carrier’s reply is commonly an EDI 990 (Response to a Load Tender). Once the load is moving, status is often shared with EDI 214 messages. Not every shop uses EDI for every customer—but those three transaction sets are the shared vocabulary when partners automate the offer–response–track loop.
Common tendering channels
Most fleets and brokerages do not live on a single channel. They mix methods by customer, lane, and urgency.
EDI 204 / 990
EDI tenders arrive as structured data into an ops system or EDI mailbox. The offer usually includes a must-respond-by window. A late or missing 990 can mean the shipper reassigns the load. Responses are typically accept, decline, and—depending on partner setup—conditional or pending states that need human review. EDI is fast and auditable when mapping and partner guides are solid; it is brittle when a customer’s implementation guide differs from what your team expects, or when conditional terms are auto-accepted without a dispatcher seeing the change.
Email rate confirmations
Many relationships still run on email: a rate confirmation (rate con) PDF or message with load details and terms. Acceptance may be a reply, a signed PDF, a portal click, or a verbal confirmation followed by paperwork. Email is flexible and familiar; it is also easy to miss, hard to standardize, and dependent on whoever is watching the inbox. Exception handling—wrong rate, wrong equipment, appointment change—often happens in long reply threads that are difficult to reconstruct later.
Load boards
Load boards surface available freight to a wider pool of carriers. “Tendering” here can mean posting, negotiating, then confirming. Speed and price discovery are the upside; the downside is more variability in data quality, more competition for the same freight, and less of the locked-in partner playbook you get with contracted EDI customers. Ops teams that treat board freight like contract freight without adjusting rules usually feel the friction in coverage and margin.
Shipper or broker portals
Portals let carriers view offers, accept or decline, upload documents, and update status in a customer-controlled UI. One company may have five different portal logins with five different button labels for the same action. Portal workflows are “electronic,” but they are not interchangeable with EDI—and they rarely share one status model across customers.
Phone and text
Phone and text still cover urgent covers, relationship freight, and last-minute changes. The risk is not the phone call; it is whether the accepted terms make it into the system of record before the driver is rolling. Good ops treat verbal acceptance as incomplete until the tender status, rate, and appointment are recorded where the rest of the team can see them.
Accept, decline, counter, and expire
The four outcomes that matter most:
Accept — The carrier (or broker covering with capacity) commits to the tender as presented, or under clearly agreed modifications that both sides record.
Decline — The offer is refused. Reasons may be capacity, equipment, timing, rate, lane preference, or customer risk. Some partners want structured decline codes; others just need a no before the clock runs out.
Counter — A conditional path: different pickup window, equipment swap, rate change, or layover terms. Counters are where many automated flows break, because a silent “yes” to modified terms creates a downstream appointment or settlement fight.
Expire / no response — If the response window passes, the tenderer may pull the offer and send it elsewhere. “We were going to take it” after expiry is not a booking.
Who is allowed to accept is a business rule, not a software preference. Some shops let any dispatcher take freight under a rate floor. Others require a manager for new shippers, hazmat, oversized, or anything outside preferred lanes. Brokerages often separate “cover” acceptance from carrier confirmation—meaning the internal status of “accepted with customer” is not the same as “truck assigned and confirmed.” Asset carriers may block acceptance when the proposed trip breaks hours-of-service planning or empty-mile thresholds.
Those differences are why a single binary Accept/Decline button rarely matches real life. Statuses, permissions, timers, and required fields have to follow the playbook the company actually uses.
How asset carriers, brokers, and hybrids differ
Asset carriers tender against trucks, drivers, trailers, and maintenance reality. Acceptance is capacity math: Can this tractor-trailer combination hit the appointment without blowing the next committed load? Do we have the right equipment in the right region? Is the rate worth the empty or the detention risk? Declines often come from network design, not from indifference.
Brokers tender against a network of carriers and against customer promises. Their tendering loop has two sides: receiving a customer tender (or creating one from a quote) and sending a tender or offer to a carrier. Status language gets messy—“covered,” “pending carrier,” “dispatched,” “confirmed”—and each shop defines those words differently. A broker’s decline to a shipper may happen because no truck could be secured in time, even if the desk wanted the freight.
Hybrids (asset plus brokerage, or private fleet with overflow) run both logics at once. An offer might be tried on owned trucks first, then spilled to the brokerage desk, with different rate floors and different acceptance authorities. The tender channel may be identical; the decision tree is not.
None of these models is “more correct.” They are different operating designs. Ops systems that force one tendering workflow onto all three create workarounds—shadow spreadsheets, side Slack channels, and status labels that mean different things to different teams.
Exception paths that show up every week
Tenders do not fail only on price. Common exception paths include:
Wrong or unavailable equipment — Reefer vs dry van, liftgate, teams, specific trailer length, or specialty gear. The clean path is a structured decline or counter before dispatch; the messy path is accepting and hoping.
Hours and appointment reality — A legal, safe plan may not fit the offered windows. Late tenders amplify this: an offer that arrives with a pickup in two hours is a different product than one with a two-day lead time.
Rate and accessorial disputes — Fuel, detention, layover, lumper, and stop-off terms may be incomplete on the tender. If acceptance implies the rate con as written, missing accessorial language becomes a settlement problem later.
Data mismatches — Wrong facility, missing reference numbers, commodity notes that conflict with equipment, or appointment times that do not match the facility’s actual hours.
Partner-specific rules — Some shippers require a 990 within a tight window; some want portal confirmation even after EDI; some forbid counters entirely.
Exception handling is where audit trails matter. When a load goes sideways, teams need to know who accepted what, under which terms, and whether a counter was acknowledged—not reconstruct it from memory and email.
What good tendering operations need
“Good” tendering ops are less about a perfect channel and more about control, visibility, and recovery:
Clear rules — Who can accept, on which customers, at which rate floors, with which equipment constraints, and within which response timers.
Status visibility — Offered, pending review, countered, accepted, declined, expired, and covered (for brokers) should mean the same thing to dispatch, customer service, and billing.
Channel fidelity without channel chaos — EDI, email, portal, board, and phone can all feed one operational picture, as long as the tender’s current state is not trapped in one inbox.
Exception workflows — Structured paths for late tenders, equipment mismatches, and conditional accepts—not only happy-path accept/decline.
Document and reference integrity — Rate cons, reference numbers, and special instructions attached to the load so drivers and settlements are not guessing.
Auditability — A record of offers and responses that survives staffing changes and customer disputes.
Because every carrier, broker, and hybrid builds a slightly different playbook, the supporting workflows—statuses, permissions, timers, required fields, and exception queues—usually need to be shaped to the business rather than the other way around. Customization here is not decoration; it is how tendering rules stay honest to how freight actually gets covered.
Practical checklist for operators
Use this as a self-audit, not a scorecard:
Map your channels — List where tenders actually arrive (EDI partners, email aliases, portals, boards, phone) and who owns each queue.
Define acceptance authority — Write down who can say yes, what needs a second look, and what is auto-decline territory.
Name your statuses — Agree on a short glossary for offered / pending / countered / accepted / declined / expired / covered, and use it in every channel handoff.
Time-box responses — Know each major customer’s respond-by expectation, and have an escalation when the clock is short.
Separate counter from accept — Never treat a modified tender as a clean accept unless both sides have recorded the change.
Capture verbal commitments — Phone/text accepts enter the system before the truck moves.
Review decline reasons — Spot patterns (equipment gaps, lane imbalance, rate floors) instead of only celebrating acceptance rate.
Trace exceptions — For the last few tender disputes, check whether you can reconstruct the offer, response, and terms without digging through personal inboxes.
Align brokerage and asset desks (if hybrid) — Spillover rules, rate floors, and status ownership should be explicit.
Revisit the playbook quarterly — Customer mix and capacity change; tendering rules should not be frozen to last year’s network.
Load tendering looks simple from the outside—offer, answer, move. Inside a North American trucking operation, it is a mix of electronic standards, human judgment, customer-specific clocks, and exception paths that differ by business model. The companies that stay calm under tender volume are usually the ones that made their accept/decline/exception workflows match how they actually sell and cover freight—not a generic template that assumes every desk works the same way.
FAQ
What is load tendering in trucking?
Load tendering is the offer of a specific shipment to a carrier (or brokerage desk) with the details needed to accept or refuse the move under stated terms.
What is an EDI 204?
An EDI 204 is the common ANSI X12 electronic Motor Carrier Load Tender used in North America to send structured load offers from a shipper or broker to a carrier.
What is an EDI 990 used for?
An EDI 990 is the carrier’s response to a load tender—typically accept, decline, or another agreed response code—within the tender’s respond-by window.
How is a rate confirmation different from an EDI tender?
A rate confirmation is often an email or PDF booking document with commercial terms, while an EDI 204/990 exchange is a structured electronic offer-and-response between trading partners; many operations use both depending on the customer.
Why do brokers and asset carriers handle tenders differently?
Asset carriers accept against owned capacity and network constraints, while brokers accept against customer commitments and third-party carrier cover—so statuses, authority, and risk checks follow different playbooks.
What should happen if a tender’s terms need to change?
Treat it as a counter or revised tender: record the modified equipment, time, or rate, get clear acknowledgment from both sides, and only then mark the load accepted under the new terms.