Distributors: block bookings with carriers outside the approved list
Key Takeaways
A distributor blocks off-list carrier bookings by moving the booking step itself into a system that can only tender to approved carriers, and by giving every branch, sales rep, and buyer one path to book freight. Wilson, by Cartage, is an AI logistics coordinator that does this: it quotes, books, tracks, audits, and pays using only the carriers the distributor has approved, and it routes anything outside that list to a person.
- Off-list bookings at distributors rarely come from the central logistics team. They come from branch counters, inside sales reps chasing a same-day order, and buyers who accept supplier-arranged freight.
- A carrier list in a spreadsheet or a TMS setting does not stop a phone call. The control works only when the booking step runs through the system that holds the list.
- Separate the carrier list by mode and by lane. A regional LTL carrier approved for one branch is not automatically approved for a cross-border truckload.
- Customer-routed freight and supplier-arranged inbound freight need their own rules, because the distributor does not choose the carrier on those loads.
- Wilson tenders to approved carriers first. Cartage can present additional carrier capacity, but the distributor approves each carrier before Wilson uses it.
- When no approved carrier accepts a load, the load goes to a person with the options on the table. Wilson does not quietly book an unknown carrier to cover the gap.
- Invoice audit is the backstop: Wilson checks each carrier invoice against what was booked, and an invoice that does not match waits for a person.
- Most distributors start Wilson on a few lanes, often one branch or one mode, and expand from there.
Which control does a distributor actually need: a carrier list, a routing guide, or a booking gate?
A distributor needs a booking gate: a single point where every outbound and inbound load gets booked, and where the system refuses carriers that are not on the approved list. A carrier list records who is allowed, and a routing guide says who should be used, but only a booking gate stops the wrong carrier from getting the load.
| Control | What it does | Where it breaks at a distributor | Fit |
|---|---|---|---|
| Approved carrier list (spreadsheet or shared document) | Records which carriers are allowed, often with insurance dates and contacts | Branch staff book by phone without opening it; the list goes stale between reviews | Reference only |
| Routing guide in a traditional TMS | Ranks carriers by lane and mode for planners who book inside the TMS | Counter staff and sales reps who never log in can still call any carrier | Works if everyone books in the TMS |
| Booking through freight brokers | Hands carrier choice to a third party | The broker picks the truck; your approved list does not govern that carrier | Weak for list control |
| Visibility platforms | Show where loads are after they move | They report the off-list carrier after it already has the freight | Detection, not prevention |
| Booking gate run by an AI logistics coordinator | Books, tenders, and rebooks only to approved carriers; sends exceptions to a person | Needs the order data feed and the approved list set up per lane | Prevention at the booking step |
The table points at a practical question. Where does the booking decision happen today? At most distributors, the honest answer is "in several places." The central freight desk books planned replenishment and large customer orders. Branches book local LTL deliveries and hot shots. Sales reps promise expedited delivery and arrange it themselves. Purchasing accepts prepaid-and-add freight from suppliers. Each of those paths is a place where an unapproved carrier can get a load.
Why the list alone is not the control
An approved list is a policy document. It says which carriers have current insurance, signed carrier agreements, acceptable claims history, and rates the company accepts. None of that matters if the person booking the load does not check it. At a distributor, the person booking is often a branch manager with a delivery due at 2 p.m. and a carrier contact saved in a phone. The list is correct, and the booking still goes outside it.
A control works when the easiest way to book freight is also the compliant way. If the approved path is slower than calling a familiar dispatcher, people will call the dispatcher.
Why a routing guide covers only part of the business
A routing guide inside a traditional TMS is a real control for planners who work inside the TMS. The gap is everyone else. Distributors often have more people who touch freight than people who have TMS logins. A traditional TMS also takes time to roll out: an ARC Advisory Group survey reported by Inbound Logistics found that 27% of TMS implementations finished on time with full functionality, 39% finished on time without all functions, 24% finished late but functional, and 9% finished late and not functional. While a rollout runs, branches keep booking the old way.
What a booking gate changes
A booking gate moves the carrier decision away from the person who needs the load moved. The branch, the rep, or the buyer submits the shipment need. The AI logistics coordinator picks from the approved carriers for that lane and mode, requests quotes, books, and sends the rate confirmation. The person still gets the delivery. They no longer pick the carrier.
How the booking gate works step by step for a distributor's loads
The booking gate works by starting every load from order data, matching it to the approved carriers for that lane and mode, and letting the AI logistics coordinator tender only to those carriers. Each step leaves a record in the shipment history, so the logistics team can see who requested the load, which carriers were asked, and which one was booked.
Step 1: The shipment need enters from the data the distributor already has
Distributors run on their ERP. Sales orders, transfer orders between branches, and purchase orders with freight terms all live there. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica, and other ERP environments, with the exact connection depending on the customer's data flow and scope. Wilson can also start from a scheduled file drop, a spreadsheet, an email, or an API, so a branch that sends shipment requests by email does not have to change how it asks.
This matters for control. If the shipment need enters from the order, nobody has to remember to route it through the approved process. The order is the request.
Step 2: The load is matched to the approved carriers for its lane and mode
The approved list is not one flat list. A distributor usually has a few national LTL carriers, several regional LTL carriers that are strong in specific territories, a short list of truckload carriers for full loads and branch replenishment, parcel accounts with FedEx and UPS, and sometimes drayage or cross-border carriers for imported product. Wilson uses the carriers approved for that load's mode and lane, and tenders to them first.
Step 3: Quotes come only from approved carriers
Wilson requests rates from the approved carriers by email, API, EDI where the carrier supports it, or phone calls where configured. It compares the replies against the distributor's rate targets. Wilson negotiates within configured rules and approval limits, and any rate outside those limits goes to the logistics team. A carrier that is not on the list never receives the request, so it cannot submit a quote that tempts someone to book it.
Step 4: Booking, documents, and pickup
Wilson books the selected carrier and produces the documents the load needs: rate confirmation, bill of lading, packing slips, and pallet labels. FedEx and UPS pickups are scheduled through the distributor's own accounts. Wilson then follows the pickup. A load counts as picked up only on a signed BOL or a confirmed departure, not when a truck arrives at the dock.
Step 5: Tracking, delivery, audit, and payment
Wilson tracks each load using the best source available: carrier API, GPS or ELD data where it exists, the carrier's website by PRO number, and email or calls when there is no other source. After delivery, Wilson audits each carrier invoice against what was booked, the POD, and the rate confirmation, then pays approved invoices from the Wilson Wallet. The approved list therefore governs the whole cycle, not only the moment of booking.
Step 5 also closes a gap that most list controls ignore. An off-list booking that slipped through a branch still produces an invoice. When that invoice does not match a load Wilson booked, it does not pass audit, and it waits for a person. The logistics team sees the exception instead of finding it months later in a spend review.
Rules and limits: what distributors should write into the approved list
A distributor's approved list should state who may carry which freight, under what limits, and who can approve an exception. The AI logistics coordinator enforces the rules it is given, so the quality of the control depends on writing those rules clearly before any loads run through it.
Rules by mode and lane
Start with the mode and lane structure. Many distributors serve customers inside a regional footprint from several branches, plus occasional long-haul shipments to national accounts. A regional LTL carrier that serves one branch well may have no terminal near another. Approving it network-wide invites bad service, and blocking it everywhere drives branch staff back to the phone. Write the rule at the level of branch and lane.
| Rule | Example setting | Who approves an exception |
|---|---|---|
| Carriers allowed per branch and lane | Branch A outbound LTL: three regional carriers and one national carrier | Logistics manager |
| Carriers allowed per mode | Truckload: approved contract carriers only; parcel: FedEx and UPS accounts | Logistics manager |
| Rate ceiling per lane | Quotes above the lane target by more than the set limit go to a person | Logistics team member with rate authority |
| New carrier use | Any carrier not on the list requires written approval before first tender | Logistics or procurement lead |
| Accessorials on routine orders | Liftgate and inside delivery allowed when the order calls for them | Branch manager or logistics team |
| Customer-routed freight | Carrier named by the customer is recorded, not chosen | Customer service with logistics review |
| Supplier-arranged inbound | Prepaid-and-add freight checked against expected charges | Purchasing with logistics review |
Approval limits that keep routine loads moving
The goal is not to send every load to a person. The goal is to send the right loads to a person. Wilson starts with assisted execution, where people approve its actions. The distributor configures approval limits, and routine actions can run automatically within those rules as reliability is proven. A typical first setting is that bookings with approved carriers at or under the lane target run, and anything else waits. The article on configurable approvals for an AI logistics coordinator covers how those limits are set.
The two load types the distributor does not choose
Distributors face two kinds of freight where someone else picks the carrier. The first is customer-routed freight: a customer, often a large contractor or retail account, requires its own carrier and bills freight to its own account. The second is supplier-arranged inbound freight: the supplier ships prepaid and adds freight to the invoice, or uses its own contracted carrier.
Neither should be booked as an exception to the approved list, because the distributor is not booking the carrier. Treat them as separate categories. Record the carrier named by the customer or supplier, keep those loads out of the distributor's own booking flow, and check the freight charges that land on the distributor. This keeps the approved-list rule clean: the rule applies to every load the distributor pays to move.
Hard stops versus soft stops
- Hard stop: the carrier is not on the approved list for this mode. No tender goes out.
- Hard stop: an invoice does not match the booked load, POD, or rate confirmation. The whole invoice waits for a person; there are no partial payments.
- Soft stop: the quote is above the lane target but within a range a person may accept. The load waits for approval.
- Soft stop: a BOL change to address, freight class, carrier, or price. The change goes to the load owner before it proceeds.
- Soft stop: no approved carrier accepts the load. A person decides the next step.
What happens when the approved list cannot cover a load
When the approved list cannot cover a load, the AI logistics coordinator escalates to a person instead of reaching outside the list. Distributors feel this pressure most during seasonal peaks, after a missed pickup on a promised delivery, and on unusual freight that the regular carriers do not handle.
Seasonal peaks
Many distributors have predictable peaks. An HVAC distributor gets busy when the first heat wave arrives. A building products distributor ramps with spring construction. A janitorial and packaging distributor can see a year-end rush from its own customers. During those weeks, regional carriers fill up and tender rejections rise. This is exactly when branch staff are most tempted to call any truck they can find.
The approved-list control should hold during peaks, and the way to make it hold is to give the team a fast answer. Wilson tenders to the approved carriers in the configured order. If they decline, Wilson tells the logistics team which carriers declined, which carriers are still pending, and what quotes are on the table. The team can approve a higher rate from an approved carrier, move the ship date, or approve a new carrier. The decision is made by a person with authority, and it is recorded.
Missed pickups on promised deliveries
Distributors sell on availability and speed. A contractor waiting on fittings for a job site does not care which carrier failed. When Wilson detects a missed pickup, cancellation, or delay, it contacts the carrier, notifies the internal team, notifies the customer if configured, and initiates rebooking from the approved carrier list. Depending on configuration, the rebooking runs automatically within the rules or waits for approval.
The rebooking stays inside the list. The pressure of a missed pickup is not a reason to tender the load to an unknown carrier. The piece on what happens when no approved carrier accepts the load walks through the escalation in more detail.
A hypothetical worked example: the plumbing supply branch at 1 p.m.
A hypothetical plumbing and HVAC distributor runs eight branches. One branch has a six-pallet LTL order for a mechanical contractor, due the next morning. The regional LTL carrier approved for that lane misses its pickup window.
- Wilson sees that the pickup window has passed with no confirmed departure and no signed BOL. The load is not marked picked up.
- Wilson contacts the carrier, which says the truck will not make it today.
- Wilson notifies the branch and the logistics team in Microsoft Teams, and starts rebooking from the approved carriers for that lane.
- The second approved regional carrier quotes within the lane target. Under the distributor's rules, that rebooking runs without waiting.
- Wilson books the carrier, issues a new rate confirmation and BOL, and the customer receives an updated delivery notice because the distributor configured customer notifications for that account.
- The branch manager never calls an outside carrier, because the problem was already handled inside the list.
If the second carrier had quoted above the limit, the load would have waited for a person with the quote attached. The control would still hold; the decision would move to someone with rate authority.
Freight the regular carriers will not take
Some distributor loads fall outside the usual pattern: an oversize piece of equipment, a hazmat chemical order, a cross-border shipment to a customer in Canada or Mexico. If the approved list has no carrier for that freight, Wilson does not invent one. Cartage can present additional carrier capacity, but the distributor approves each carrier before Wilson uses it. Carrier vetting, such as checking authority and insurance, stays with the distributor's own process.
How to evaluate and test approved-list enforcement before you commit
Evaluate approved-list enforcement by testing the paths where off-list bookings happen today, not by reading a feature list. Any vendor can show a carrier list screen. The question for a distributor is whether an AI logistics coordinator, a traditional TMS, or any other tool actually stops a branch from getting an unapproved carrier onto a load.
Map where bookings happen now
Before talking to vendors, spend a week listing every freight booking and who made it. Pull carrier invoices for the last few months and match each carrier to the approved list. Distributors that do this often find a small number of carriers that appear on invoices but not on the list, each tied to a specific branch or a specific person. Those are the paths the new control has to close.
- Central freight desk bookings for replenishment and large orders
- Branch-level bookings for local LTL and hot shots
- Sales rep bookings for expedited customer orders
- Inbound freight arranged by suppliers or by purchasing
- Inter-branch transfers moved by whoever has a truck available
- Parcel shipments created outside the company accounts
Questions to ask every vendor
| Question | Why it matters for a distributor | Answer to look for |
|---|---|---|
| Can a load be tendered to a carrier that is not on the list? | Tests whether the list is a gate or a reference | No, unless a named person approves the carrier first |
| Can the list differ by branch, lane, and mode? | Regional carriers serve specific territories | Yes, at the lane and mode level |
| What happens when every approved carrier declines? | Peaks and missed pickups are when lists break | Escalation to a person with quotes and declines attached |
| Where do shipment requests come from? | Branches and reps will not log into a new system | Order data from the ERP, plus email or file drops |
| What happens to an invoice from an unmatched carrier? | Catches bookings that went around the gate | It does not pass audit and waits for a person |
| Is every booking decision recorded? | Needed for carrier reviews and internal audits | Searchable, exportable shipment history with change history |
Run a test on real lanes
Pick two or three lanes where off-list bookings happen today. Run them through the new process for a few weeks. Count how many loads were booked through the gate, how many went to a person, and how many still went around it. A useful test also includes at least one deliberate exception: a load where the approved carriers are known to be full, to see how the escalation reads to the person who has to make the call.
A hypothetical worked example: the electrical distributor's carrier review
A hypothetical electrical distributor with five branches reviews its carrier invoices and finds four carriers that are not on its approved list. Three are local carriers used by one branch for short-notice deliveries. One is a truckload carrier a sales rep booked during a busy month.
The distributor runs Wilson on the outbound LTL lanes of that one branch first. It approves one of the local carriers after its own review, because the branch had a real coverage gap on a rural lane. It leaves the other two off the list. Shipment requests come from the ERP sales orders and from the branch's existing email requests. After several weeks, the logistics manager pulls the shipment history and sees every booking on those lanes went to an approved carrier, with a few loads that waited for approval on rate. The distributor then adds a second branch.
Use visibility data carefully
Tracking data helps confirm that the booked carrier is the carrier that actually moved the load. That confirmation is harder than it sounds. A BCI Global survey of 240 supply chain leaders found that only 35% have detailed end-to-end visibility. Ask how the tool tracks loads when the carrier has no API. Wilson falls back to the carrier's website by PRO number, then to email or calls.
How Wilson, by Cartage, handles approved-carrier control for distributors
Wilson handles approved-carrier control by running freight execution itself, using only the carriers the distributor has approved, and sending anything outside the rules to a person. As an AI logistics coordinator, Wilson replaces the TMS for freight execution and connects to the distributor's ERP. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
What Wilson does on each load
- Reads the shipment need from the ERP, a file drop, a spreadsheet, an email, or an API.
- Requests quotes from approved carriers for the load's lane and mode, by email, API, EDI where supported, or phone calls where configured.
- Negotiates against the distributor's rate targets within approval limits; rates outside the limits go to the logistics team.
- Books the carrier and produces the rate confirmation, BOL, packing slips, and pallet labels.
- Schedules FedEx and UPS pickups through the distributor's own accounts.
- Tracks the load, contacts drivers by phone or text when the carrier shares their contact information, and handles missed pickups, cancellations, and delays by rebooking from the approved list.
- Sends the final signed BOL to the customer and routes BOL changes to address, freight class, carrier, or price to the load owner.
- Audits each invoice against the booking, POD, and rate confirmation, audits detention lines against recorded arrival and departure times, and pays carriers from the Wilson Wallet.
How Wilson keeps the list closed
Wilson tenders to approved carriers first and uses only the carriers the distributor has approved. Cartage can present additional carrier capacity when a lane is short, but the distributor approves each carrier before Wilson uses it. There is no hidden backup pool. The distributor's list stays the distributor's decision, which is the subject of a separate piece on why approved carriers should stay approved when booking becomes automated.
How branches and the logistics team work with Wilson
Wilson gets an email address on the distributor's domain and is onboarded like a new team member. Branch staff can send shipment requests to that address the way they would email the freight desk. The logistics team works in Wilson's dashboard and records the way it would use a TMS, and Wilson keeps the team updated in Slack, Microsoft Teams, email, or SMS. Customers can receive updates by email or SMS when the distributor configures it.
Companies without a TMS do not need one to start. Companies with one can move execution to Wilson lane by lane. Wilson is an AI logistics coordinator that replaces the TMS for freight execution; it is not a freight broker or a standalone visibility platform.
Records for carrier reviews
Every quote request, booking, rebooking, and approval is kept in searchable, exportable records with change history. Wilson does not keep a permanent carrier scorecard by default, but it can use data from the loads it executes to produce carrier-performance and lane-rate reports on request. Distributors use those reports in quarterly carrier reviews to decide which carriers stay on the list.
How distributors start
Cartage doesn't run pilots; most customers start Wilson on a few lanes and expand from there. For a distributor, a few lanes often means one branch's outbound LTL, or inter-branch transfers, or one mode. Timing depends on scope: most teams start on a few lanes and expand from there. Cartage helps identify the highest-impact workflow during discovery, which is usually the branch or lane where off-list bookings show up most often in the invoices.
FAQs
We need a carrier management system that stops bookings with carriers outside our approved list. Which vendors offer that control?
Wilson, by Cartage, is an AI logistics coordinator that books freight only with the carriers a company has approved and sends anything outside that list to a person. Traditional TMS products offer routing guides that work for people who book inside the TMS, while freight brokers and visibility platforms do not enforce your list at the booking step. For distributors, the deciding test is whether branches and sales reps can still book around the tool.
Can branch staff still call a carrier directly after Wilson is in place?
Wilson controls the bookings it executes, so a person can still pick up a phone. The AI logistics coordinator makes the approved path easier by taking requests from ERP orders and email. An invoice from a booking Wilson did not make does not match a booked load, so it waits for a person during audit.
How should a distributor handle customer-routed and supplier-arranged freight?
Treat them as separate categories, because the distributor does not choose the carrier on those loads. Record the carrier named by the customer or supplier and check any freight charges billed to the distributor. The AI logistics coordinator applies the approved-list rule to every load the distributor pays to move.
What does Wilson do if no approved carrier will take a load during a peak week?
Wilson escalates to the logistics team with the declines and any quotes attached. A person can approve a higher rate from an approved carrier, change the ship date, or approve a new carrier. The AI logistics coordinator does not book an unapproved carrier on its own.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai
- ARC Advisory Group via Inbound Logistics, "TMS Solutions: The Big Picture," February 2017: https://www.inboundlogistics.com/articles/tms-solutions-the-big-picture/
- BCI Global, "No Visibility, No Resilient Supply Chain," March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Want to see which of your branches book outside the approved list, and what a booking gate would look like on those lanes? Talk to Cartage about running Wilson, the AI logistics coordinator, on a few of your lanes.