FTL booking software should prove the carrier accepted the load

Key Takeaways

In FTL, proof of carrier acceptance is a written record that matches the tender: the same load, rate, equipment, pickup window and stops.
FTL acceptance needs evidence that other modes rarely do: trailer type and length, reefer settings, exclusive use of the trailer, power-only trailer details, and solo or team service when the delivery date depends on it.
The costliest acceptance problem is the silent change, where the carrier's paperwork quietly differs from the tender on date, equipment, rate structure or accessorials.
Booking software should show every difference and keep the load out of "booked" until someone resolves it.
Wilson, by Cartage, tenders FTL loads to the company's approved carriers, records the written acceptance, sends the rate confirmation, confirms the pickup window and escalates what falls outside the company's rules.

What proof should FTL booking software produce when a carrier accepts?

FTL booking software should produce one record that ties the carrier's written acceptance to the exact tender: load reference, agreed rate, equipment, pickup window and stops, backed by a rate confirmation that says the same thing. If any field differs, the software should show the difference instead of marking the load booked.

On a full truckload, one carrier commits one truck and driver to one shipper's freight, so the acceptance is a promise about a particular trailer, day and price. Acceptances arrive as a one-line email, a phone call, an EDI response where the carrier supports it, or the carrier's own confirmation document. Consider an illustrative load: 42,000 lb of packaged goods, a 53-foot dry van, pickup Tuesday between 7:00 and 9:00 a.m., tendered at an all-in rate of $2,450. The dispatcher replies "Covered, rate con to follow." The carrier's document then lists pickup on Wednesday and $2,450 linehaul plus fuel. Neither change appears in the "covered" email; one surfaces at the dock, the other on the invoice.

This is a narrower question than whether an accepted load is fully booked, which the five booking checks cover. The point here is whether the acceptance itself can be trusted.

Four layers of FTL acceptance evidence

A complete FTL acceptance answers four questions: who accepted, on what commercial terms, with what equipment and service, and for which times and places. Software that records only the first one gives the team a name and a timestamp but no proof.

Identity. The accepting carrier is on the company's approved list, the person who accepted can be reached, and the acceptance references the load number, PO or order, and the current tender version if the load was re-tendered.
Commercial terms. The rate matches the tender in amount and in structure: all-in, or linehaul plus fuel. Included accessorials, such as a stop-off charge or driver assist, are named.
Equipment and service. Trailer type and length, reefer setpoint and mode, flatbed securement or tarps, and whether the move is solo, team or power-only. Exclusive use of the trailer is assumed in FTL, so nothing in the acceptance should contradict it.
Time and place. The pickup window, the delivery appointment or window, every stop in sequence, and the facility addresses, matching the tender rather than a carrier's default.

Equipment and timing often live in the ERP order, so software connected to that order data can check them without anyone retyping the load.

Where FTL acceptances go wrong in practice

Most FTL acceptance failures are not refusals. They are acceptances that commit to something slightly different from what the shipper tendered.

Equipment and service details

If neither tender nor acceptance states trailer length, a 48-foot trailer can show up for a 53-foot load. On reefer loads, a confirmed temperature without the mode, continuous or cycle, leaves room for a product claim.

Power-only loads

In power-only, the carrier brings a tractor and the shipper provides the trailer. The acceptance must name the trailer number, where it is staged, whether it is preloaded and sealed for a drop-and-hook, and who returns the empty. Without those details, the driver arrives at the wrong yard or hooks the wrong trailer.

Team versus solo

When a delivery date depends on team service, an illustrative 1,900-mile run due in under two days, a solo acceptance silently moves the delivery. A solo driver's hours-of-service limits make the original date impossible, and nobody finds out until the consignee asks.

Stops and later changes

FTL rates assume the trailer serves one shipper. An added stop, or any order change after acceptance, changes transit and rate, so the earlier acceptance no longer proves anything about the new load. A phone acceptance has the same weakness until it is confirmed back in writing.

How should software handle an acceptance that doesn't match?

Software should treat a mismatched acceptance as its own status, not as booked, and route it by what changed.

Material differences hold the load. Pickup date, equipment, rate amount or structure, team versus solo, power-only trailer details and added stops all change what the shipper bought. The load stays "accepted with discrepancy" until the carrier corrects its paperwork or an authorized person approves the change.
Nothing is overwritten. The tender and the carrier's version stay side by side; replacing one with the other erases the evidence.
Rate differences follow approval limits. A small accessorial inside the configured limit can be accepted under the rules; anything outside goes to the person who owns that decision.
No fix, next carrier. If the carrier won't conform, the workflow moves to the next approved carrier where the rules allow and escalates when no acceptable approved option remains.

To evaluate a product, feed it a carrier confirmation with a changed pickup date and rate structure, then ask where the difference appears and who decides. Once the acceptance holds up, the next risk is the gap between booking and truck arrival, covered in booked is not picked up.

An FTL acceptance-proof checklist

Run this on any FTL load your current process marks as booked. A field the acceptance doesn't state is a field the carrier hasn't committed to.

Field	What the acceptance should show	Discrepancy to flag
Carrier	A carrier on the approved list, named as on the tender	Different carrier name on the paperwork
Load reference	Load number, PO and tender version	Earlier version or no reference
Rate amount	The tendered or negotiated amount	Any different total
Rate structure	All-in or linehaul plus fuel, as tendered	All-in changed to linehaul plus fuel
Accessorials	Each included charge named	Detention or stop-off terms not discussed
Trailer	Type and length	48-foot for a 53-foot tender
Reefer	Setpoint and continuous or cycle mode	Temperature only, or a different setpoint
Driver service	Solo or team, as tendered	Solo on a team tender
Power-only	Trailer number, staging location, empty return	Any of the three missing
Exclusive use	No added stops or co-loading	Extra stop on the carrier's plan
Pickup	Date and window	Different day or open-ended time
Delivery	Appointment or window	Later date than tendered

A load passes when every applicable row matches. One flagged row means the load is accepted, not proven.

How Wilson, by Cartage, proves the FTL acceptance

Wilson tenders FTL loads to the company's approved carriers, records the written acceptance on the shipment and carries the load through rate confirmation and a confirmed pickup window. Wilson replaces the TMS for freight execution and starts the tender from the company's ERP order data.

Tender. Wilson tenders to approved carriers first, by email, API, EDI where the carrier supports it, or phone where configured. It negotiates against the company's rate targets under configured rules and approval limits.
Acceptance. Wilson records the carrier's written acceptance on the shipment, then generates and sends the rate confirmation.
Pickup. Wilson schedules and confirms the pickup window and reconfirms before the truck is due.
Exceptions. If a carrier declines or doesn't respond, Wilson moves to the next approved carrier where the rules allow. When a carrier can't confirm, or no approved carrier accepts, Wilson escalates to the team with the context attached.
Record. Messages, confirmations and changes are recorded in the shipment history.

Wilson starts with assisted execution, and the company decides which differences need a person. Which acceptance fields are compared, and how, depends on the workflow configured for the company's lanes. For the full FTL sequence from tender to POD, see how AI coordinates FTL shipments.

Bring an FTL load whose carrier confirmation didn't match your tender, and see Wilson record the acceptance and how your rules handle the difference in a demo.