Overview
Truckload tender rejection occurs when a carrier declines an offer to transport a truckload shipment under specified terms. A tender generally identifies the lane, pickup and delivery requirements, equipment, and applicable rate. A rejection sends the shipment back to the shipper or its transportation provider for another capacity option.
Shippers monitor rejections to assess whether contracted capacity is available and whether freight can move as planned. Aggregated rejection indicators, such as those available through FreightWaves SONAR, can also help market participants interpret changing capacity conditions. Rejection is a transportation procurement measure; it differs from warehouse activities such as order fulfillment.
Etymology and Origins
In commercial usage, a tender is an offer made for acceptance. The logistics expression combines this meaning of tender with a carrier's decision to accept or reject a proposed load. A rejection is therefore a response to an offer, not necessarily a cancellation of an already accepted shipment.
The practice grew out of shipper–carrier arrangements for assigning individual loads. A first documented use of the full phrase and a single inventor have not been established. Its modern electronic form is associated with the growth of electronic data interchange, which enabled trading partners to exchange standardized business messages between computer systems.
Historical Development
Before computerized tendering became widespread, shippers and carriers arranged loads through telephone calls, paper records and other manual communications. The Motor Carrier Act of 1980 (Public Law 96-296) was a major milestone in U.S. trucking deregulation, contributing to a more competitive environment for arranging freight transportation. The statute was approved on July 1, 1980.
During the 1980s and 1990s, electronic data interchange became an increasingly important way for businesses to exchange standardized transaction information. In the X12 message family, the 204 Motor Carrier Load Tender communicates a load offer, while the 990 Response to a Load Tender communicates a response. These are distinct messages, so a successful transmission of a tender is not itself a carrier acceptance.
Transportation management systems subsequently helped automate carrier selection, tender delivery and response tracking. In the 2010s and 2020s, cloud-based platforms and market analytics expanded the use of aggregated tender data alongside other indicators. FreightWaves SONAR and DAT Trendlines illustrate the modern availability of freight-market data, although their measures and underlying populations differ. A published market index should not be treated as identical to a shipper's internal rejection scorecard.
Core Concepts and Process
A typical tendering sequence is:
- Prepare the shipment: Define origin, destination, dates, equipment, weight, service requirements and price.
- Offer the load: Send the tender to a selected carrier, often the primary carrier for a contracted lane.
- Capture the response: The carrier accepts, rejects or fails to respond within the applicable window. Treatment of nonresponse depends on the shipper's measurement rules and agreement.
- Recover capacity: If the offer is rejected or expires, tender to another carrier or seek a spot-market alternative.
- Record the outcome: Retain timestamps, reason codes and final transportation cost for analysis.
A routing guide sets the intended sequence of carriers and terms. When primary capacity is unavailable, the shipper may move to backup carriers or the spot market. DAT Trendlines provides context on spot-market conditions; a rejected contract tender does not itself establish the price of a replacement load.
Electronic tender messages can reduce manual rekeying, but partners still need consistent shipment identifiers, response deadlines and exception handling. Electronic data interchange is one way to exchange standardized transaction data; APIs and carrier portals are other common integration approaches. An electronic load tender and its response are separate transactions.
Measurement and Interpretation
A basic tender rejection rate is:
Rejected tenders ÷ eligible tenders × 100
For example, if a carrier rejects 20 of 100 eligible offers, the rejection rate is 20%. The complementary acceptance rate is 80% only if every eligible offer is classified as either accepted or rejected. Expired, withdrawn, duplicate and revised offers may require separate treatment.
The denominator matters. A shipment offered sequentially to three carriers can produce three tender attempts but remains one shipment. Shippers should distinguish the primary-carrier rejection rate from the rejection rate across all attempts, and document whether they count explicit declines, timeouts or both. A market index from FreightWaves SONAR should not be assumed to use the same population or methodology as an individual shipper's scorecard.
Illustrative example: A shipper offers 100 loads to primary carriers. Twenty are rejected and reoffered to backups; the other 80 are accepted. If backups accept 15 and reject five, the primary rejection rate is 20%, while the rejection rate across all 120 attempts is approximately 20.8% (25 rejections ÷ 120 attempts). Five shipments still need capacity. This example counts only explicit responses and excludes withdrawals and timeouts.
A rising rejection rate can signal tightening capacity or unattractive contract terms, but it is not a direct measure of truck availability or a guaranteed predictor of rates. Interpret it with lane volumes, lead times, service performance and market information such as DAT Trendlines.
Causes and Operational Effects
Carriers may reject tenders because of insufficient equipment or drivers, short notice, unfavorable rates, difficult pickup or delivery windows, or an imbalance between outbound and return freight. Driver availability also depends on operational constraints, including applicable hours-of-service rules.
Repeated rejection can delay carrier assignment, increase manual work and expose a shipment to a higher replacement rate. It may also disrupt warehouse schedules if the freight is ready but no truck is available. Coordination between transportation and warehouse fulfillment teams helps distinguish a capacity problem from a shipment-readiness or scheduling problem.
Not all rejections indicate poor carrier performance. A tender outside an agreed lane, volume commitment, lead time or equipment specification may fall outside the carrier's obligation. Contracts and scorecards should define the applicable terms before performance is evaluated.
Best Practices and Technology
- Set consistent rules. Define eligible offers, response windows, timeout treatment and reason codes before comparing carriers or periods.
- Segment results. Review rejection by carrier, lane, origin facility, equipment, day of week and tender lead time; an aggregate average can conceal a recurring local problem. Show offer counts alongside percentages so that small samples are not overinterpreted.
- Investigate exceptions. Compare rejected loads with agreed rates and operating requirements, and discuss recurring causes with carriers. Separately track an explicit rejection and an accepted load that is later cancelled; they occur at different stages of the process.
- Maintain a recovery plan. Specify backup carriers, escalation thresholds and who can authorize spot-market purchases.
- Measure the consequence. Track replacement cost and service outcomes as well as rejection rate; a low rejection rate alone does not establish reliable delivery. Compare like-for-like costs, including applicable accessorials, and retain both the original and replacement rates where available.
- Reconcile messages. Match each load tender to its response, and investigate missing, late or duplicate messages before assigning a performance outcome.
Transportation systems can automate tender sequences and maintain an audit trail. Integration with order management systems can help teams coordinate shipment readiness and transportation status, while electronic data interchange can support standardized exchanges with trading partners. The specific tendering functions available depend on the systems and integrations in use.