The bill of lading does not match the sales order. Who stops pickup?
Key Takeaways
When the bill of lading does not match the sales order, the load owner should decide whether the pickup stops, based on rules that say which mismatches are serious enough to hold the truck. An AI logistics coordinator can find the mismatch, classify it, and bring the decision to the right person before the driver leaves the dock.
- A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
- A sales order is the customer's order as recorded in the company's order system.
- Not every mismatch should stop a pickup. Some can be fixed after the truck leaves; others cannot.
- Address, product, and quantity mismatches usually justify a hold. Formatting and reference typos often do not.
- One named person should have the authority to stop the pickup. The warehouse should not have to guess.
- The fix and the decision should both be saved with the load.
- Wilson, by Cartage, is an AI logistics coordinator that builds bills of lading from the booked load, compares them with the order, and brings mismatches to the load owner before pickup.
Who has the authority to stop a pickup when the BOL and the order disagree?
The load owner should have the authority to stop a pickup when the BOL and the sales order disagree, with clear rules that tell the warehouse when to hold the freight on its own. An AI logistics coordinator can flag the mismatch, apply the rules, and ask the owner to decide when the rules do not cover the case.
The people involved
| Role | What they can see | What they can decide |
|---|---|---|
| Load owner | Order, booking, carrier, delivery promise | Hold, release, or reschedule |
| Warehouse lead | What is on the dock | Hold freight under set rules |
| Customer service | The customer's order and changes | Confirm the correct order details |
| Driver | The BOL and the freight in front of them | Sign, note exceptions, or refuse |
Why the warehouse should not decide alone
The warehouse sees the freight, but not the reasons behind the order. If the BOL shows 12 pallets and the order shows 14, the warehouse cannot know whether two pallets were back-ordered on purpose or forgotten. Asking the warehouse to decide puts the risk on the wrong person. The warehouse should hold under clear rules and call the owner when the rules are not enough.
Why the driver should not be the check
The driver signs for what is on the BOL and what is loaded. The driver does not see the sales order. A driver may notice that the count on the paper does not match the pallets, but will not notice that the product is wrong or the address is old. The check has to happen before the driver arrives.
Rules give the warehouse confidence
Clear rules let the warehouse act quickly. For example: "Hold any load where the ship-to address on the BOL differs from the order. Release loads where only the PO number format differs, and tell the owner." With rules like these, most decisions do not need a phone call.
Customer service confirms, the owner decides
Customer service often knows the right answer: the customer moved, the order was updated, or the customer asked for a partial shipment. But customer service may not know the carrier's terms or the cost of holding the truck. A good split is simple. Customer service confirms which order details are correct. The load owner decides what happens to the pickup. The AI logistics coordinator connects the two with one message each.
Back-up authority
The authority to stop a pickup should not depend on one person being at their desk. Each load owner should have a named back-up with the same authority. If neither can be reached within a set time, the rules should say what the warehouse does by default. For most teams, the safe default is to hold freight with a serious mismatch and release freight with a minor one.
Hypothetical example: who made the call
This example is hypothetical and does not describe a real customer. A BOL lists a delivery to a customer's old warehouse. The sales order shows a new address. The dock lead sees the AI logistics coordinator's flag and holds the freight, as the rules say. The load owner confirms the new address with customer service and reprints the BOL. The truck leaves 25 minutes late, to the right place.
Which BOL and sales order mismatches should stop a pickup?
Mismatches that would send the wrong freight, the wrong amount, or the right freight to the wrong place should stop a pickup. Mismatches in formatting or internal references usually should not. An AI logistics coordinator should sort each mismatch by its risk and apply the team's rules.
Mismatch types and the usual decision
| Mismatch | Example | Usual decision |
|---|---|---|
| Ship-to address | Old warehouse on BOL, new one on order | Stop |
| Consignee name | Different company name | Stop until confirmed |
| Product or description | Wrong SKU or product family | Stop |
| Quantity or pallet count | 12 pallets on BOL, 14 on order | Stop until the warehouse confirms what is loaded |
| Weight | Small difference within tolerance | Release, then update |
| Weight | Large difference on an LTL load | Stop and confirm the rate |
| Freight class | Different class on an LTL load | Stop and confirm |
| PO number | Missing or different | Release if the receiver does not require it; stop if it does |
| Special instructions | Liftgate on order, not on BOL | Fix before release |
| Freight terms | Prepaid versus collect | Stop until confirmed |
A SKU, or stock keeping unit, is a code that identifies one product. LTL, or less-than-truckload, is freight that shares a trailer with other shippers' freight. Freight class is a rating that affects LTL pricing. Prepaid means the shipper pays the freight charges; collect means the receiver pays.
Why quantity mismatches are tricky
A quantity mismatch can mean several things. The order may have changed and the BOL is old. The warehouse may have short-picked and the order is right. Part of the order may be shipping on another load. The owner needs to know which one before deciding. A good flag says which record changed last.
Address mismatches are the most expensive
A wrong address is often the costliest mismatch. The carrier may deliver to the wrong site, bill a reconsignment fee to redirect the freight, and add a day or more to the delivery. A reconsignment is a change to the delivery address after the freight is already moving. Catching the address before pickup avoids all of this, which is why most teams treat it as an automatic stop.
Why weight and class matter on LTL
On LTL loads, the carrier prices freight by weight and class. If the BOL shows a different weight or class from the order data, the carrier may reweigh or reclass the freight and bill more. A reweigh is when a carrier weighs the freight again and bills the new weight. A reclass is when a carrier changes the class and bills the new rate. Fixing the BOL before pickup prevents this.
Review the rules every quarter
Rules that made sense last year may not fit today. A new customer may require appointment numbers. A product may move to a new class. Reviewing the stop and release rules every few months keeps them useful.
Receiver requirements change the rules
Some receivers refuse freight without their PO number on the BOL. Others need an appointment number. For those receivers, a missing reference is as serious as a wrong address. The rules should list these receivers, so the AI logistics coordinator can treat their references as required.
Mismatches that look small but are not
Some mismatches look small and cause large problems. A suite number missing from a city address can send a driver to the wrong building. A product description that says "parts" instead of the real product can lead to a reclass or a refused claim. A missing "do not stack" note can lead to damage. The rules should treat these as serious, even though they are only a few characters on the page.
Federal BOL fields
Federal rules require for-hire motor carriers to issue a receipt or bill of lading that shows the consignor and consignee, origin and destination, number of packages, description of freight, and weight or volume when it affects the rate. The consignor is the shipper and the consignee is the receiver. Mismatches in these fields deserve the most care, because they define what the carrier received.
How should the mismatch be found before the driver arrives?
The mismatch should be found by comparing the BOL with the sales order automatically, when the BOL is created and again the day before pickup. An AI logistics coordinator should run the comparison field by field and flag any difference to the right owner with enough time to fix it.
The comparison workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Compare at creation | BOL created | Matches each field with the order | When a field does not match |
| 2. Watch for changes | Order or booking updated | Re-runs the comparison | When the change affects the BOL |
| 3. Day-before check | Pickup within 24 hours | Confirms the BOL and order still match | When anything differs |
| 4. Classify | Mismatch found | Applies the stop or release rules | When no rule covers it |
| 5. Route | Mismatch classified | Sends it to the person who can fix it | Owner decides on holds |
| 6. Confirm | Fix made | Checks the new BOL against the order | Never for routine fixes |
Why comparing once is not enough
Orders change after BOLs are created. A customer adds a line, cancels a line, or changes the delivery address. If the comparison runs only at creation, those later changes are missed. The comparison should run again whenever the order changes and once more before pickup.
Partial shipments
Not every order ships in one load. Sometimes part of an order ships today and the rest next week. The comparison should know which lines are on this load, so it does not flag the missing lines as an error. This needs the order system to show which lines were released to this shipment.
Multiple orders on one load
When several orders ship on one truck, the BOL may list each order separately or combine them. The comparison should check each order's lines, addresses, and references against its own part of the BOL. A combined total that matches can still hide a mistake, such as two pallets assigned to the wrong order. The receiver will notice when it counts the delivery against each purchase order, so the shipper should notice first.
Data quality issues
Many mismatches come from data, not from people. A customer master may have two addresses. A product may have an old weight in the system. A comparison will keep finding the same mismatch until the source data is fixed. The AI logistics coordinator should report repeat mismatches so the data owner can clean them up.
Unit of measure differences
Orders are often entered in units, such as cases or pieces, while BOLs list handling units, such as pallets or cartons. A comparison that looks only at numbers will flag every load. The software must convert the order quantity into the handling units on the BOL, using the packing data from the warehouse. When that data is missing, the AI logistics coordinator should ask the warehouse for the final handling unit count, not raise a false alarm.
Timing the comparison with the warehouse
The best moment for the final comparison is after the warehouse finishes picking and packing, but before the driver arrives. That is when the real counts and weights are known. If the warehouse works close to pickup, the comparison may need to run in the last hour. The AI logistics coordinator should know each site's packing schedule and time its check to match.
Hypothetical example: a canceled line
This example is hypothetical and does not describe a real customer. A distributor prints a BOL for 10 pallets on Monday. On Tuesday, the customer cancels two lines, and the order now needs 8 pallets. The day-before check finds the difference. The AI logistics coordinator tells the warehouse to stage 8 pallets and the shipping clerk to reprint the BOL. The truck leaves with 8 pallets and a matching BOL.
How should a BOL mismatch be fixed?
A BOL mismatch should be fixed at the source: correct the order if it is wrong, correct the BOL if it is out of date, and tell the carrier if the change affects the load. An AI logistics coordinator should route each fix to the right person and confirm the corrected BOL matches before release.
Who fixes what
| What is wrong | Who corrects it | Who needs to know |
|---|---|---|
| Order is wrong | Customer service | Warehouse, load owner |
| BOL is out of date | Shipping clerk or load owner | Warehouse |
| Product data is wrong | Product data owner | Load owner, carrier if class changes |
| Address data is wrong | Customer service or master data team | Carrier, receiver |
| Load changed and BOL needs carrier update | Load owner | Carrier |
Tell the carrier when it matters
If the fix changes the weight, class, count, or address, the carrier should know before pickup. A change in weight or class may change the price. A change in address may change the route. The carrier's confirmation should be in writing and saved with the load. A rate confirmation, which is the document that states the agreed price and terms for one load, may need to be updated too.
Fix the system record, not only the paper
When the order is right and the BOL is wrong, the fix is easy. When the order is wrong, the fix must happen in the order system too. Otherwise, the invoice to the customer, the packing slip, and the next BOL will repeat the error. The AI logistics coordinator should ask the order owner to correct the source record, not only to reprint the paper.
Keep the old version
The shipment record should show the original BOL, the corrected BOL, what changed, and who approved it. If the carrier's invoice uses the old weight, or the receiver says the count was wrong, the team can show exactly what was shipped.
Confirm the corrected BOL before release
After any correction, the new BOL should be compared with the order one more time before the freight is released. A rushed reprint can fix one field and break another. The AI logistics coordinator should run the same field-by-field check on the corrected version and tell the warehouse when it is clear.
When the fix cannot wait
If the driver is at the dock and the fix needs more than a few minutes, the owner must choose: hold the driver, reschedule, or let a partial load go. The choice depends on free time, delivery promises, and the cost of a second pickup. Free time is the time a carrier allows at a dock before detention charges begin.
Hypothetical example: a class difference
This example is hypothetical and does not describe a real customer. A manufacturer's BOL shows freight class 70 for an LTL shipment. The product master shows class 85 for that product after a packaging change. The AI logistics coordinator flags the mismatch the day before pickup. The product data owner confirms class 85 is correct. The coordinator updates the BOL and asks the carrier to confirm the rate at class 85 before pickup.
How should teams test whether software catches BOL and order mismatches?
Teams should test software with real mismatches: an old address, a changed quantity, a canceled line, a wrong class, and a missing PO number. An AI logistics coordinator should catch each one before pickup, apply the stop or release rules, and route the fix to the right person.
The test set
| Test case | Pass | Fail |
|---|---|---|
| Old ship-to address on BOL | Stopped and routed to customer service | Shipped to old address |
| Quantity changed after printing | Flagged and BOL updated | Old count shipped |
| Line canceled after printing | BOL corrected before pickup | Canceled freight shipped |
| Wrong class on LTL BOL | Flagged and carrier asked to confirm | Reclass on invoice |
| Missing required PO number | Added before release | Receiver refuses delivery |
| Partial shipment | Only released lines compared | False alarm on unreleased lines |
| Record | Both BOL versions and the decision saved | Only last version kept |
Score the alerts, not only the catches
A tool that flags every small difference will be ignored within a week. During the test, count how many alerts were useful and how many were noise. A good result is a short list of real mismatches, each with the right owner and a clear next step. Noise should be fixed by better rules or cleaner data, not accepted as normal.
Questions to ask in a demo
- How does the software know which order lines are on this load?
- What happens when the order changes after the BOL is printed?
- Who gets the alert, and who can stop the pickup?
- How does the software handle receivers with special reference rules?
- Does the carrier get told when a change affects price?
Warning signs
- The software prints BOLs from the order but never compares them later.
- Every mismatch is treated the same, so the warehouse ignores alerts.
- There is no way to set stop and release rules.
- Changes overwrite the old BOL with no history.
Include the warehouse in the test
The warehouse will live with the alerts every day. During the test, ask the dock leads whether the alerts were clear, whether they arrived in time, and whether they knew what to do. Their answers often matter more than the vendor's feature list.
Measure the result
After the software is in use, the team should track how many mismatches were found before pickup, how many reached the dock, and how many showed up later on invoices or claims. The goal is to move almost all of them to the first group.
Where does Wilson fit when the BOL does not match the order?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers and prepares the documents each load needs, such as bills of lading, rate confirmations, packing slips, and pallet labels. Wilson builds each BOL from the order and booking data and checks it again when either one changes.
Wilson replaces the TMS for freight execution and connects to the company's ERP. A TMS, or transportation management system, is software used to plan, book, and track freight. An ERP, or enterprise resource planning system, is the company's main business system for orders, inventory, and accounting. 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.
How Wilson handles a mismatch
When the BOL and the order disagree, Wilson flags the mismatch to the load owner, applies the customer's stop and release rules, and routes the fix to the person who owns it. If the change affects the carrier, Wilson tells the carrier and asks for written confirmation. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured, and it notifies internal teams through Slack, Microsoft Teams, email, or SMS.
After pickup
Wilson tracks the load using the best source available, collects the POD at delivery, and audits the carrier invoice against what was booked. A proof of delivery, or POD, is the document the receiver signs to show the freight arrived. Customers use the Wilson Wallet to pay their carriers. Payments above approval limits or outside the rules wait for a person. Wilson has no subscription or platform fee; its pricing is a percentage of the freight payments coordinated through the Wallet. Pricing scales down as volume grows, and Enterprise pricing is custom.
What Cartage asks in discovery
Cartage asks how orders flow from the ERP to shipping, how often orders change after release, which receivers have strict reference rules, and who has authority to stop a pickup today. These answers shape the stop and release rules an AI logistics coordinator applies.
Where teams start
Wilson starts with assisted execution. Approval limits are set by the customer, and routine actions can run automatically within those rules as reliability is proven. Timing depends on scope: most teams start on a few lanes and expand from there. Every flag, fix, and decision is saved in the shipment record with change history.
Teams dealing with count changes can read why a carrier may need to requote when the pallet count changes. Teams building a full pickup routine can start with the freight pickup guide.
This article is part of our complete guide to bills of lading from booking to delivery.
FAQs
Who should stop a pickup when the BOL does not match the order?
The load owner, with rules that let the warehouse hold freight in clear cases. An AI logistics coordinator flags the mismatch and brings the decision to the owner.
Which mismatches should stop a pickup?
Wrong address, wrong product, wrong quantity, wrong class on LTL, and missing references that the receiver requires. An AI logistics coordinator applies the team's rules to each one.
How can mismatches be found before the driver arrives?
By comparing the BOL with the order when it is created, when either changes, and the day before pickup. An AI logistics coordinator runs these checks on every load.
Should the carrier be told about a BOL correction?
Yes, when the change affects weight, class, count, or address. An AI logistics coordinator tells the carrier and saves the written confirmation.
What if the order is wrong, not the BOL?
The order should be corrected at the source, so the invoice and future documents are right. An AI logistics coordinator routes the fix to customer service and checks the new BOL against the corrected order.
Sources
- Electronic Code of Federal Regulations, 49 CFR 373.101, "For-hire, non-exempt motor carrier bills of lading": https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-373/subpart-A/section-373.101
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator compares every bill of lading with the sales order and brings mismatches to the right person before pickup: talk to the Cartage team.