How do you stop freight software from booking an unapproved carrier?
Key Takeaways
You stop freight software from booking an unapproved carrier by making the approved list a hard rule, not a preference. The list should be set by the company, kept per lane and mode, checked before every quote request and every tender, and changed only by a named person. An AI logistics agent such as Wilson, by Cartage, books only carriers the company allows. When no allowed carrier is available, the load goes to a person instead of to whoever answers first.
- The approved list is a company decision. Software should apply it, never extend it on its own.
- Check the list twice: before quote requests go out and again before the tender.
- Keep approvals specific: a carrier approved for LTL in the Midwest is not approved for cross-border truckload.
- When no approved carrier can take the load, route it to a named approver with the options.
- Watch for side doors: replies from unknown senders, carriers that broker the load to someone else and rebookings under time pressure.
- Record every booking against the list, so any exception is visible and explained.
Where do unapproved carriers get booked?
Unapproved carriers usually get booked through a few predictable gaps, not through one big failure. An AI logistics agent closes these gaps by checking the list at every step where a carrier could enter. The table shows the common gaps and the control for each.
| Gap | How it happens | Control |
|---|---|---|
| Open quote requests | A request goes to a load board or a wide list | Send requests only to carriers approved for the lane |
| Unknown reply | A carrier the team does not know answers a forwarded request | Accept quotes only from approved carriers; route others to a person |
| Urgent rebooking | A cancellation the day before pickup leads to "anyone who can take it" | Approved backups per lane; approver for anything else |
| Wrong scope | A carrier approved for one mode or region is used for another | Approvals per lane, mode and region |
| Re-brokering | The approved carrier hands the load to another carrier | Ask who is hauling; check the carrier on the BOL and at pickup |
| Lapsed approval | Insurance or authority expired since approval | Review dates on the list; block expired carriers |
| Personal shortcuts | A coordinator books a favorite carrier outside the system | Bookings only through the system that checks the list |
What does a typical slip look like?
A hypothetical example shows how an unapproved booking happens. A distributor's coordinator sends a spot quote request for a truckload to five approved carriers. One of them forwards it to a partner. The partner replies directly with a quote $150 below the others. The coordinator, busy with three other loads, books it. The truck arrives with a name nobody recognizes. The load delivers fine, but a month later the team learns the carrier's insurance had lapsed. Nothing went wrong this time, but the company carried a risk it never agreed to. The same thing would not happen if quotes were accepted only from carriers on the list.
Why does it matter?
It matters because an unapproved carrier has not passed the checks the company relies on: insurance, operating authority, safety record and service history. If something goes wrong, such as damage, theft or a missed delivery, the company may find its coverage or its contract terms do not apply the way it expected. Even when nothing goes wrong, a booking outside the list weakens the company's position with its approved carriers, who give better rates and capacity in exchange for steady volume.
Is this only a problem for large shippers?
No. Unapproved bookings happen at companies of every size. A busy desk with two coordinators can book an unknown carrier under pressure just as easily as a large team. The risk is the same: the carrier has not passed the company's checks. What changes with size is how often it happens and how hard it is to see. A system that checks the list on every load works the same way whether the company moves ten loads a week or a thousand.
What does "approved" mean?
"Approved" means the company has checked the carrier and decided to use it for certain freight. The checks usually include insurance certificates, operating authority, safety information and sometimes a contract or carrier agreement. The decision usually comes from logistics, procurement or risk. The approved list is the result. Freight software should treat the list as the company's decision, not as a suggestion that it can extend when it is convenient.
How should the approved list be set up?
The approved list should be set up per lane and mode, with the reason for each approval and a review date. An AI logistics agent like Wilson works from this list on every load. The more specific the list, the fewer judgment calls the agent or the team has to make under pressure.
| Field | Example | Why it matters |
|---|---|---|
| Carrier | Carrier name and identifiers | Matches the carrier on quotes, BOLs and invoices |
| Modes | LTL, FTL, drayage, parcel, ocean, cross-border | A carrier may be approved for one mode only |
| Lanes or regions | Midwest to Southeast; Laredo crossings | Limits the carrier to where it was checked |
| Role | Primary, backup, spot | Decides the order of offers |
| Equipment | Dry van, reefer, flatbed, liftgate | Avoids sending a load the carrier cannot handle |
| Review date | Insurance or agreement renewal | Blocks lapsed approvals |
| Approved by | Name and date | Shows who owns the decision |
How should the list handle different modes?
The list should handle modes separately, because each mode has its own carriers and its own checks. An LTL carrier is approved for less-than-truckload shipments through its terminal network. A truckload carrier is approved for full loads with specific equipment. A drayage carrier works at specific ports and rail ramps. A cross-border carrier needs the right authority and customs arrangements. A parcel carrier works through the company's account. A carrier approved in one mode is not automatically approved in another, even if it offers that service.
Should the list be per lane or company-wide?
The list should be per lane when the company has different needs on different lanes, which most do. A company-wide list is simpler but forces every lane to accept every approved carrier, even where the carrier has no coverage or a weak record. A per-lane list can start small: the main lanes get their own primary and backup carriers, and everything else uses a general approved list until it needs its own.
How often should the list be reviewed?
The list should be reviewed on a schedule and whenever an event calls for it. A schedule might be quarterly for the full list and monthly for the main lanes. Events that call for a review include an expired insurance certificate, a serious service failure, a claim, a change in the carrier's ownership or a new lane. The review dates on the list let the agent block a carrier automatically once its approval has lapsed, until someone renews it.
Who should own changes to the list?
A named person or small group should own changes, usually the logistics lead with procurement or risk. Changes should be recorded with the date, the person and the reason. The agent should never add a carrier on its own. It can suggest that a lane needs more carriers, for example when quote requests often get no answers, but the decision belongs to the team.
What about Wilson's network?
Wilson's network is an option the company can choose. When the company turns it on for certain lanes, Wilson can use carriers from its network on those lanes, and the freight rate is the price the shipper pays with nothing on top. When it is off, Wilson works only with the company's own approved carriers. The company decides which lanes, if any, use the network. Either way, Wilson books only carriers the company allows.
How should the software enforce the list?
The software should enforce the list at every step where a carrier enters the load: the quote request, the reply, the tender, the rebooking and the pickup. An AI logistics agent checks the list at each step automatically, so enforcement does not depend on someone remembering.
- Before the quote request. Only carriers approved for the lane, mode and equipment receive the request.
- When replies arrive. Quotes are accepted only from carriers on the list. A reply from anyone else goes to a person.
- Before the tender. The chosen carrier is checked again against the list and its review date.
- On rebooking. Backups come from the approved list for the lane. Anything else needs approval.
- At pickup. The carrier on the BOL and the arriving truck are checked against the booked carrier where the site shares that information.
What about carriers the team contacts by phone?
Carriers contacted by phone go through the same check. If a coordinator calls a carrier to cover a load, the carrier must be on the approved list for that lane, or the booking needs approval. Wilson can call carriers where configured and records the call on the load. A rate agreed by phone becomes a booking only when the carrier accepts in writing and the rate confirmation is on file, and the agent checks the list again before that happens.
Why check twice before booking?
Checking twice protects against changes between the quote and the tender. A carrier's approval can expire. A carrier can be removed from a lane because of a recent problem. A quote can arrive from a sister company or a different operating entity with a similar name. The second check, right before the tender, catches these cases. It takes no time for software and avoids a booking that would be hard to undo.
What happens to a quote from an unknown sender?
A quote from an unknown sender is recorded but not used until a person decides. This happens more than teams expect: a quote request gets forwarded inside a carrier's network, or a broker hears about the load and offers capacity. The agent should not book from that quote. It can tell the team that an unapproved carrier offered a price, with the details, so the team can decide whether to approve the carrier for the future.
What about carriers with similar names?
Carriers with similar names should be matched on identifiers, not names. Many carriers share words like "Express", "Logistics" or "Transport", and some operate several companies under related names. A quote from "Northline Freight LLC" may not be the same company as the approved "Northline Freight Inc." The agent should match on the carrier's identifiers recorded on the approved list and the email domain or account it uses, and send anything uncertain to a person.
How should re-brokering be handled?
Re-brokering should be handled by asking who will haul the load and checking that the hauling carrier matches the booked carrier. Some carriers hand loads to partners without telling the shipper. The company may have approved the first carrier but not the second. The agent can ask the carrier to confirm the hauling carrier and driver details, and compare them with what appears on the BOL and at pickup. Wilson compares carrier, trailer and load number when the site shares check-in details, flags mismatches and corrects the records. Mismatches go to a person.
What should happen when no approved carrier is available?
When no approved carrier is available, the load should go to a named approver with the options, not to the first carrier that answers. An AI logistics agent can prepare the decision so the approver can act quickly. This is the moment when most unapproved bookings happen, because time pressure makes any truck look acceptable.
Should the agent ever book outside the list without approval?
No. If the company wants certain carriers to be used without approval in an emergency, those carriers should be added to the list as emergency options. Then they are approved, and the agent can use them under the emergency rule. Anything that is not on the list, in any role, needs a person. This keeps one simple rule that everyone can understand: the agent books only carriers the company allows.
What should the approver receive?
The approver should receive the load details, which approved carriers were asked and what they said, the time left before pickup, and any options outside the list with what is known about them. A hypothetical example: a reefer load needs to pick up tomorrow at 7 a.m. Both approved reefer carriers on the lane declined. The approver receives a message in Microsoft Teams with the two declines, the delivery commitment to the customer and two choices: approve a carrier from the general approved list that has reefer equipment but has not worked this lane, or move the pickup a day. The approver chooses, and the decision is recorded.
How fast should the approver answer?
The approver should answer fast enough to keep the options open. Trucks get booked by other shippers. Quotes expire. A request that waits until the next morning may lose the only available carrier. The rules should name a primary approver and a backup and say how long to wait before going to the backup. Wilson sends the approval request in the channel the approver uses, such as Slack, Microsoft Teams or email, and follows up if there is no answer.
Can the company pre-approve emergency options?
Yes. Many companies pre-approve a small set of emergency options per region, so urgent rebookings stay inside the rules. These carriers have passed the company's checks but are used only when the primary and backup carriers cannot take the load, often at a higher rate. Pre-approving them turns an emergency judgment call into a rule the agent can follow.
What if the customer requests a specific carrier?
If the customer requests a specific carrier, the request should be checked against the approved list like any other. Some customers have their own carrier agreements and want their freight moved by a named carrier, often on collect or third-party terms. If that carrier is already approved, the agent can use it. If not, the team decides whether to approve it for that customer's freight. The decision is recorded, so the next order for the same customer follows the same rule.
What about carriers that cancel at the last minute?
When a carrier cancels at the last minute, Wilson detects the cancellation, contacts the carrier, tells the team and starts rebooking from the approved carrier list. Whether the rebooking runs automatically within the rules or waits for approval depends on the company's settings. The rebooking still follows the list. Time pressure changes how fast the agent works, not which carriers it may use.
How do you show that the rule is being followed?
You show the rule is being followed by recording every booking against the list and reviewing the exceptions. An AI logistics agent like Wilson records, for every load, which carriers were asked, which answered, which was booked and whether it was on the approved list at the time. Exceptions carry the approver's name and the reason.
What should the team see on each load?
On each load, the team should see the booked carrier and a clear sign that it was on the approved list for that lane and mode at the time of booking. If the booking was an exception, the load should show the approver and the reason. This makes a quick scan of the week's loads enough to spot anything unusual, without opening each record.
What should a monthly review look at?
A monthly review should look at bookings outside the usual list, approvals given under time pressure, carriers that often decline or do not answer, and lanes with too few approved carriers. These patterns point to changes the team should make, such as approving another backup carrier on a lane or removing a carrier that keeps cancelling. Wilson can produce carrier-performance and lane-rate reports on request from the loads it has handled to support that review.
| Signal | What it suggests |
|---|---|
| Many approvals on one lane | The lane needs more approved carriers |
| One carrier often declines | Check its capacity or rate on that lane |
| Emergency options used often | Primary and backup carriers are not enough |
| Unknown senders quoting | Requests may be forwarded; check where they go |
| Mismatched carrier at pickup | Possible re-brokering; ask the booked carrier |
How does the rule interact with rate limits?
The approved list and the rate limits are separate rules, and both must be met. A carrier can be approved but quote above the limit; that booking needs rate approval. A carrier can quote within the limit but not be approved; that booking needs carrier approval. When both rules are written down, the agent knows which approval to ask for and who should give it. Wilson negotiates rates against the customer's rate targets under configured rules and approval limits, but only with carriers the company allows.
How does the record help with invoices?
The record helps with invoices because the carrier on the invoice should be the carrier that was booked. Wilson audits each carrier invoice against what was booked, the rate confirmation and the proof of delivery before paying from the Wilson Wallet. An invoice from a different carrier than the one booked is a sign of re-brokering or an error, and it waits for a person.
What should happen when a carrier is removed from the list?
When a carrier is removed from the list, open quotes and future loads with that carrier should stop, and loads already booked should be reviewed. The agent should stop sending quote requests to the carrier and refuse new tenders. For loads already booked, the team decides whether to keep the booking or move it. The removal date and reason are recorded, so later questions about why the carrier stopped getting loads have a clear answer.
How should exceptions be explained?
Exceptions should be explained in one or two plain sentences on the load. For example: "Approved by the logistics lead at 4:12 p.m.: both lane carriers declined, customer delivery fixed for Thursday, emergency carrier from the regional list." For more on what a full selection record should contain, see how freight software can record why a carrier was selected.
How does Wilson, by Cartage, keep bookings inside the approved list?
Wilson, by Cartage, is an AI logistics agent that requests quotes, tenders, books and rebooks only with carriers the company allows. It checks the approved list before each request and before each tender, routes anything outside the list to a named approver and records every booking with the reason. Wilson handles LTL, FTL, ocean, drayage, parcel and cross-border freight and works with carriers by email, API, EDI where supported and phone calls where configured.
Wilson replaces the TMS for freight execution and connects to the company's ERP. Teams use Wilson's dashboard and records the way they would use a TMS. For more on keeping approvals stable as automation grows, see approved carriers stay approved in automated booking.
How does Wilson handle a quote from an unapproved carrier?
When a carrier that is not on the list sends a quote, Wilson records it and tells the team, but does not use it. The team can decide to approve the carrier for future loads, approve it for this one load or ignore the quote. The decision and the reason are recorded on the load.
What stays with the team?
The team owns the approved list, the lane rules, the emergency options and the approval limits. Wilson starts with assisted execution, where more steps wait for approval, and routine bookings within the rules can run on their own as the team sees the results. Every action is recorded with a change history.
What does a typical week look like?
In a typical week, most loads are booked with primary or backup carriers on the approved list without anyone thinking about the rule. A few loads need approval because no approved carrier can take them. One or two quotes arrive from carriers that are not on the list and are reported to the team. The weekly view shows these exceptions in one place, so the team spends its time on the few decisions that matter.
How is Wilson priced?
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract.
How do teams start?
Most teams start Wilson on a few lanes and expand from there. Cartage helps map the highest-impact workflow during discovery. The approved list for those lanes is usually the first thing the team shares.
FAQs
How do you stop freight software from booking an unapproved carrier?
Make the approved list a hard rule per lane and mode, check it before quote requests and again before the tender, and send anything outside it to a named approver. An AI logistics agent like Wilson, by Cartage, books only carriers the company allows and records every booking against the list.
Can the software add a carrier to the list on its own?
No. An AI logistics agent should never extend the approved list. It can tell the team when a lane needs more carriers or when an unknown carrier offered a quote, but the approval is the company's decision.
What happens when every approved carrier declines?
An AI logistics agent sends the load to the named approver with the declines, the time left and the options. The approver decides, for example to use a pre-approved emergency carrier or to move the pickup.
How do you catch re-brokered loads?
An AI logistics agent asks the carrier who will haul the load and compares the carrier, trailer and load number at pickup when the site shares check-in details. Mismatches and invoices from a different carrier go to a person.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai
If your team still finds out at the dock which carrier showed up, book a demo to see how Wilson, the AI logistics agent by Cartage, keeps every booking inside your approved list.