Bill of lading software: who checks the BOL before pickup?
Key Takeaways
The BOL should be checked before pickup by one named owner, and good bill of lading software makes that check routine: it compares the BOL with the sales order, the booking, and the pickup details, then flags any difference while there is still time to fix it. An AI logistics coordinator can run that check on every load and send only real problems to a person.
- A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
- The BOL usually comes from the shipper's side, but the carrier relies on it at pickup and at invoice time.
- Errors on the BOL often surface at the dock, on the invoice, or in a freight claim.
- The check should compare the BOL with three records: the sales order, the booking, and the pickup plan.
- Someone must own the check. When the warehouse, the coordinator, and the carrier each assume another party did it, nobody does.
- The best time to check is when the BOL is created and again the day before pickup.
- Wilson, by Cartage, is an AI logistics coordinator that prepares shipping documents such as bills of lading from the booked load and checks them before the truck arrives.
Who should check the bill of lading before pickup?
The person or system that owns the load should check the bill of lading before pickup, because that owner can see the order, the booking, and the pickup plan together. In many teams, an AI logistics coordinator can own the routine check and pass any mismatch to the coordinator, the warehouse, or customer service.
Three groups touch the BOL before the truck arrives. Each one sees only part of the picture.
| Group | What it knows | What it often misses |
|---|---|---|
| Warehouse | What is staged on the dock | The booked equipment and the carrier's terms |
| Logistics coordinator | The carrier, the rate, and the pickup time | The final piece count and weight |
| Customer service | The customer's order and delivery needs | The carrier and the pickup details |
| Carrier | What the driver sees at pickup | What was ordered and booked |
Why ownership is often unclear
In many companies, the BOL is printed by the warehouse from the order system, handed to the driver, and filed. Nobody compares it with the booking. The warehouse assumes logistics checked the carrier details. Logistics assumes the warehouse checked the freight. The driver signs for what is on the paper, not for what was ordered.
What the owner is responsible for
The owner of the BOL check does not need to fix every problem alone. The owner needs to make sure the check happens, that differences are seen before pickup, and that the right person decides how to fix each one. A wrong weight may go back to the warehouse. A wrong carrier name may go back to the coordinator. A wrong delivery address may go back to customer service.
Why the check matters to the carrier too
The carrier depends on the BOL. Under federal rules, for-hire motor carriers must 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. When the shipper's BOL is wrong, the carrier's records are wrong too.
What happens when nobody owns it
When nobody owns the check, the BOL errors show up later, in places that cost more to fix. The driver arrives and the count on the paper does not match the dock. The receiver refuses a delivery because the purchase order number is missing. The carrier bills a reclass two weeks after delivery. A freight claim stalls because the signed BOL shows no exception. Each problem lands on a different team, and each one starts with a document that nobody compared before pickup.
Ownership by load, not by department
The cleanest rule is to assign the check by load. Whoever owns the load owns the BOL check, even if other teams supply the data. This keeps one name on every document. It also makes handoffs easy: when a coordinator is out, the loads move to a back-up, and the BOL checks move with them.
A simple test of ownership
Ask one question about any load leaving tomorrow: who will compare the BOL with the booking before the truck arrives? If the answer is a person's name, or a system that does it every time, the check is owned. If the answer is "the warehouse probably does," it is not.
What should bill of lading software compare before pickup?
Bill of lading software should compare each field on the BOL with the record that should match it: the sales order for the freight, the booking for the carrier and service, and the pickup plan for the time and place. An AI logistics coordinator should flag any field that does not match and name the person who can fix it.
The fields to compare
| BOL field | Compare with | Common error |
|---|---|---|
| Shipper and pickup address | Pickup plan | Old address or wrong dock |
| Consignee and delivery address | Sales order | Bill-to address instead of ship-to |
| Carrier name and SCAC | Booking | Carrier changed after the BOL was printed |
| Piece and pallet count | Sales order and staged freight | Count changed after picking |
| Weight | Packing data or scale ticket | Estimate never updated |
| Description and freight class | Product master | Old class on an LTL load |
| Reference numbers | Sales order and booking | PO or load number missing |
| Special instructions | Booking and customer requirements | Liftgate or appointment not listed |
| Freight terms | Booking | Prepaid versus collect is wrong |
A SCAC, or Standard Carrier Alpha Code, is a short code that identifies a carrier. Freight class is a rating that affects less-than-truckload pricing. Less-than-truckload, or LTL, is freight that shares a trailer with other shippers' freight. Prepaid means the shipper pays the freight charges. Collect means the receiver pays.
Truckload and LTL need different checks
On a truckload, the most important BOL fields are often the addresses, the references, the seal number, and the piece count. The price usually does not change with weight, as long as the load stays within legal limits. On an LTL load, weight, class, and dimensions matter much more, because the carrier prices the freight by them. A good check knows the mode and puts the most effort on the fields that drive cost and service for that mode.
Weight and class deserve extra care
On LTL loads, weight and class drive the price. If the BOL shows a lighter weight or a lower class than the freight really has, the carrier may reweigh or reclass it 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 freight class and bills the new rate. If the BOL shows a heavier weight than the freight really has, the shipper may pay too much without anyone noticing. Either way, the BOL is the starting point.
Reference numbers connect the paperwork
The BOL should carry the numbers that let everyone find the load later: the purchase order, the shipper's load number, and the carrier's PRO number when one is assigned. A PRO number is a tracking number a carrier gives to a shipment. Without these references, the POD and the invoice are harder to match to the right load. A proof of delivery, or POD, is the document the receiver signs to show the freight arrived.
Hazardous materials and special handling
Some freight needs more than a standard BOL. Hazardous materials need specific shipping papers and emergency information. Temperature-controlled loads may need the required temperature on the paperwork. Freight that cannot be stacked or tipped needs that instruction where the driver will see it. The check should confirm that these details match the product and the booking, and that the carrier booked can handle them. When in doubt, the owner should ask the person responsible for compliance before the truck arrives.
Special instructions are often lost
A booking may include a liftgate, an appointment, or inside delivery. If the BOL does not list them, the driver may not know, and the carrier may bill for them later with no record that they were requested. Accessorials are fees for extra services, such as a liftgate. Listing them on the BOL protects both sides.
When should the BOL be checked, and by whom at each step?
The BOL should be checked at three points: when it is created, the day before pickup, and at the dock when the freight is loaded. An AI logistics coordinator can own the first two checks and alert the warehouse for the third, so problems are caught while they are still small.
The three checkpoints
| Checkpoint | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| Creation | Load booked and order released | Builds or reads the BOL and compares it with the order and booking | When a field cannot be matched |
| Day before pickup | Pickup is within 24 hours | Re-checks counts, weight, carrier, and instructions against the latest records | When something changed after creation |
| At the dock | Freight loaded | Asks the warehouse to confirm final counts and the driver signature | When the count differs from the BOL |
| After pickup | Signed BOL returned | Files the signed copy with the load | When the signed copy is missing or has exceptions |
Why the day-before check matters
Orders change. A customer adds two cartons. The warehouse splits a pallet. The carrier changes because the first one canceled. Each change can make a correct BOL wrong. A check the day before pickup catches most of these changes while there is still time to print a new BOL.
What the warehouse should confirm at the dock
At the dock, the warehouse should confirm the final piece count and that the driver signed the BOL. If the driver notes an exception, such as a damaged pallet or a short count, that note matters for any later claim. The warehouse should send that signed copy back to the shipment record the same day.
Multi-stop and consolidated loads
A truck with several stops needs a BOL for each stop, or one BOL with each stop listed clearly. The counts and weights for each stop should add up to the total on the booking. When a consolidated load combines several orders, the check should confirm that each order's references appear on the paperwork, so each receiver can match the delivery to its own purchase order.
When the BOL comes from the carrier
Some carriers issue their own BOL or accept a shipper BOL only on their own form. In that case, the check is the same, but the source is different. The coordinator should compare the carrier's BOL with the booking and the order, and ask the carrier to correct any field that does not match before pickup.
Seal numbers and trailer numbers
On full truckloads, the trailer number and the seal number are often written on the BOL at the dock. A seal is a numbered tag that shows the trailer was not opened in transit. The warehouse should record both on the signed copy. If the receiver later finds a broken seal or a different number, the BOL is the record that shows what left the dock.
Hypothetical example: a carrier change after printing
This example is hypothetical and does not describe a real customer. A distributor books an LTL load on Monday and prints the BOL with Carrier A. On Tuesday afternoon, Carrier A says it cannot pick up until Thursday. The coordinator books Carrier B for Wednesday. The day-before check finds that the printed BOL still names Carrier A and its quote number. The AI logistics coordinator flags it, the warehouse reprints the BOL with Carrier B, and the driver signs the correct document on Wednesday.
What happens when a BOL error is found before pickup?
When a BOL error is found before pickup, the owner should correct the document, confirm the change with the right party, and keep both versions in the shipment record. An AI logistics coordinator should route each type of error to the person who can fix it, and tell the carrier when the change affects the load.
Who fixes which error
| Error type | Who fixes it | Who needs to know |
|---|---|---|
| Wrong carrier or service | Logistics coordinator | Warehouse, carrier |
| Wrong count or weight | Warehouse | Carrier if the quote may change |
| Wrong delivery address | Customer service | Carrier, receiver |
| Missing reference numbers | Logistics coordinator or customer service | Receiver, billing |
| Wrong freight class | Logistics or product data owner | Carrier |
| Missing special instructions | Logistics coordinator | Carrier, receiver |
When the error changes the price
Some BOL errors change the cost of the load. A heavier weight, a higher class, or a new liftgate can raise the price. In those cases, the coordinator should ask the carrier to confirm the new price before pickup, not after. A pickup that goes ahead without that confirmation often leads to a dispute at invoice time. Teams that want the full picture of documents before pickup can review how to request missing bills of lading before pickup.
Tell the carrier in writing
When a correction affects the carrier, the carrier should hear about it in writing before pickup. A short message works: the load number, what changed, the new value, and whether the price is affected. The carrier's reply should be saved with the load. A phone call is fine for speed, but the written note is what settles questions later.
Keep both versions
If the BOL changes, the old version should not disappear. The shipment record should show what changed, who changed it, and when. This helps when a carrier invoice uses the old weight, or when a receiver says the delivery address was wrong.
When there is no time to fix it
Sometimes the truck is already at the dock. Then the team must decide: correct the BOL by hand, delay the pickup, or let the load go and fix the record afterward. The decision should belong to a named person, based on rules set in advance. For example, a wrong reference number might be fixed by hand, while a wrong delivery address should stop the pickup.
Track how often errors happen
A team that records each BOL correction learns where errors come from. If most corrections are weight changes, the packing data may arrive too late. If most are carrier changes, the BOL may be printed too early. If most are address errors, the order system may be using the bill-to address. Fixing the cause reduces the number of checks that find a problem.
Hypothetical example: a weight change caught early
This example is hypothetical and does not describe a real customer. A manufacturer creates a BOL for 4,200 pounds. The day before pickup, the packing data shows 5,100 pounds after a second product was added to the order. The AI logistics coordinator flags the difference and asks the warehouse to confirm the scale weight. The warehouse confirms 5,050 pounds. The coordinator updates the BOL and asks the LTL carrier to confirm the rate at the new weight before pickup.
How should teams evaluate bill of lading software?
Teams should evaluate bill of lading software by how it handles a BOL that is wrong, late, or changed, not by how it prints a clean BOL. An AI logistics coordinator should be scored on whether it catches each difference, routes it to the right person, and keeps the record straight.
Software categories
| Category | What it does well | What often stays manual |
|---|---|---|
| BOL template or form tool | Prints a standard BOL quickly | Comparing the BOL with the booking |
| Shipping software at the warehouse | Prints labels and BOLs from the order | Carrier changes after printing |
| Carrier portal | Creates a BOL on the carrier's form | Checking against the shipper's order |
| Transportation software suite | Builds the BOL from a load plan | Follow-up when data changes |
| AI logistics coordinator | Prepares the BOL from the booked load and checks it before pickup | Decisions about price changes above limits |
The evaluation test
| Test case | Pass | Fail |
|---|---|---|
| Carrier changed after BOL printed | Flagged and BOL updated before pickup | Old BOL used |
| Weight increased after picking | Flagged and carrier asked to confirm rate | Old weight shipped |
| Delivery address wrong | Stopped and sent to customer service | Shipped to wrong address |
| Liftgate booked but not on BOL | Added before pickup | Missing at delivery |
| Signed BOL not returned | Requested the same day | Not noticed |
| Record | Both versions saved with reasons | Only the last version kept |
Bring your own past loads
The best test uses loads the team already knows. Pick five past loads where the BOL was wrong, late, or changed. Give the vendor the order, the booking, and the original BOL for each one. Then watch what the software does. A useful tool should find the same problems the team found, and ideally find them earlier.
Questions to ask in a demo
- How does the software know a BOL is wrong if the order changed after printing?
- Where do weight and class come from?
- Who gets the alert when a field does not match?
- How does the carrier learn about a change?
- Where is the signed BOL stored after pickup?
Warning signs
- The demo shows only a clean BOL being printed.
- The software never compares the BOL with the booking.
- Alerts go to a shared inbox with no owner.
- The signed BOL lives only in the carrier's portal.
Teams comparing tools in more depth can review the best bill of lading software for manufacturers.
Where does Wilson fit in checking the BOL before pickup?
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. Because Wilson works from the booked load, it can compare the BOL with the order, the carrier, and the pickup plan before the truck arrives.
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 checks the BOL
Wilson builds the BOL from the order and booking data, re-checks it when the order or carrier changes, and flags differences to the person who owns each fix. It tells the carrier when a change affects the load. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured. It notifies internal teams through Slack, Microsoft Teams, email, or SMS.
What Wilson does not do with the BOL
Wilson does not decide whether a product is hazardous or what class it belongs to. Those rules come from the customer's product data and the people who own compliance. Wilson does not change a delivery address without the person who owns the customer order. When a field is uncertain, Wilson asks rather than guesses.
After pickup
Wilson files the signed BOL with the shipment record, tracks the load using the best source available, and collects the POD at delivery. When the carrier invoice arrives, Wilson audits and reconciles it against what was booked, including the weight and class on the BOL.
Carriers, approvals, and payment
Wilson tenders the customer's approved carriers first, and the customer approves each new carrier before Wilson uses it. 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 where BOLs are created today, which carriers require their own forms, how often orders change after printing, and who decides when a pickup should wait for a corrected BOL. These answers shape how an AI logistics coordinator sets the checks for each lane.
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 action is saved in the shipment record with change history.
This article is part of our complete guide to bills of lading from booking to delivery.
FAQs
Who should check the bill of lading before pickup?
The owner of the load should make sure it is checked, with the warehouse confirming final counts. An AI logistics coordinator can own the routine check and pass mismatches to the right person.
What should bill of lading software compare?
Addresses, carrier, counts, weight, class, references, special instructions, and freight terms, each against the order, booking, or pickup plan. An AI logistics coordinator flags any field that does not match.
When should the BOL be checked?
When it is created, the day before pickup, and at the dock. An AI logistics coordinator can run the first two checks and alert the warehouse for the third.
What happens if a BOL error changes the price?
The carrier should confirm the new price before pickup. An AI logistics coordinator asks for that confirmation and routes amounts above the limit to a person.
Does the carrier check the BOL?
The driver checks what is visible at pickup, such as the piece count, and signs for it. The carrier does not compare the BOL with the shipper's order. An AI logistics coordinator should do that comparison before the truck arrives.
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 checks every bill of lading against the order and the booking before the truck arrives: talk to the Cartage team.