The pallet count changed. Does the BOL still match the load?
Key Takeaways
When the pallet count changes after the BOL is created, the BOL no longer matches the load until someone updates the count, checks the weight, reprints the pallet labels, and tells the carrier if the change affects the price or the trailer. An AI logistics coordinator can catch the change, compare it with the BOL and the booking, and route each fix to the right person before pickup.
- A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
- The pallet count on the BOL is what the driver signs for and what the receiver checks at delivery.
- A count that does not match the freight leads to shortage disputes, refused deliveries, and invoice problems.
- A count change often changes the weight, and on LTL loads it can change the price.
- Pallet labels, packing slips, and the BOL must all agree on the same count.
- The carrier should confirm the change in writing when it affects price, space, or equipment.
- Wilson, by Cartage, is an AI logistics coordinator that prepares bills of lading, packing slips, and pallet labels from the booked load and updates them when the freight changes.
Why does the pallet count on the BOL matter so much?
The pallet count on the BOL matters because it is the number the driver signs for at pickup and the number the receiver checks at delivery, so any difference becomes a dispute about missing or extra freight. An AI logistics coordinator should treat the count as one of the most important fields on the BOL and check it whenever the freight changes.
Federal rules require for-hire motor carriers to issue a receipt or bill of lading that shows the number of packages, along with the shipper, receiver, origin, destination, description, and weight or volume when it affects the rate. The count is part of the legal record of what the carrier received.
Where the count is used
| Who uses it | When | What happens if it is wrong |
|---|---|---|
| Driver | At pickup | Signs for the wrong number or notes an exception |
| Carrier terminal | At cross-dock | Freight may be split or left behind |
| Receiver | At delivery | Reports a shortage or overage |
| Carrier billing | At invoice | May bill a different weight or space |
| Claims team | After a loss | Cannot prove what was tendered |
Handling units versus pieces
The BOL usually lists handling units, such as pallets or crates, and sometimes the pieces inside them. A handling unit is anything the carrier moves as one item. If the warehouse combines two pallets into one, the piece count may stay the same while the handling unit count drops. Both numbers should be right, and the BOL should make clear which is which.
Driver exceptions at pickup
If the driver counts a different number of pallets than the BOL shows, the driver may write an exception on the BOL, such as "9 pallets loaded, BOL says 10." This note protects the carrier, but it also creates a record the shipper must explain. It is much better to fix the count before the driver arrives than to rely on the driver's note.
Why the receiver cares
The receiver counts pallets at the dock and signs the proof of delivery. A proof of delivery, or POD, is the document the receiver signs to show the freight arrived. If the BOL says 12 pallets and 11 arrive, the receiver writes "short 1" on the POD. That note starts a dispute, even if the 12th pallet was never shipped because the warehouse combined two. A correct BOL prevents the false shortage.
Why the carrier cares
On less-than-truckload loads, the carrier plans space and handling by the number of pallets. Less-than-truckload, or LTL, is freight that shares a trailer with other shippers' freight. More pallets than expected can mean the freight does not fit on the planned trailer. On truckload, a higher count may still fit, but the carrier may need to know for loading.
Claims depend on the count
If freight is lost or damaged, the shipper may file a freight claim with the carrier. The claim starts with the BOL: what was tendered, how many units, and in what condition. If the BOL count is wrong, the claim is harder to prove. A carrier may argue that the missing pallet was never loaded. An accurate count, confirmed by the driver's signature, is the strongest starting point for any claim.
Hypothetical example: a false shortage
This example is hypothetical and does not describe a real customer. A warehouse builds 10 pallets for an order and the BOL is printed for 10. Before pickup, the dock lead combines two light pallets into one to save space. Nine pallets ship. The BOL still says 10. The receiver signs the POD "short 1." The customer service team spends a week proving that nothing was lost. A recount and BOL update before pickup would have avoided the whole dispute.
Why does the pallet count change after the BOL is created?
The pallet count changes after the BOL is created because the order changes, the warehouse builds the pallets differently than planned, or part of the order ships on another load. An AI logistics coordinator should know which of these happened, because each cause leads to a different fix.
Common causes
| Cause | Example | What else may change |
|---|---|---|
| Order quantity changed | Customer adds or cancels a line | Weight, value, packing slip |
| Pallets rebuilt | Two pallets combined, or one split for height | Weight per pallet, labels |
| Partial shipment | Some lines back-ordered | Weight, packing slip, invoice to customer |
| Estimate replaced by actual | BOL used a planned count; final count differs | Weight |
| Damaged pallet rebuilt | Product moved to a new pallet | Labels |
| Load split | Order moved to two trucks | Separate BOLs needed |
Planned counts versus actual counts
Many BOLs are created before picking is finished, using a planned count from the order system. The warehouse then builds the pallets, and the real count may differ. This is normal. The important step is to replace the planned count with the actual count before pickup.
Pallet building rules
Warehouses build pallets to fit height, weight, and stacking limits. A carrier or receiver may have rules, such as a maximum pallet height. If a pallet is too tall, the warehouse may split it, which raises the count. If pallets are light, the warehouse may combine them, which lowers it. These choices are often made at the dock and not shared upstream.
Partial shipments
When some lines are back-ordered, the shipment may leave with fewer pallets than the order planned. The BOL, the packing slip, and the customer's advance notice should all show the partial quantity. An advance ship notice, or ASN, is an electronic message that tells the receiver what is coming. A mismatch between the ASN and the BOL can delay receiving.
Nobody tells upstream
The most common problem is not the change itself but the silence after it. The dock lead combines pallets to save space and moves on. Nobody tells the shipping clerk, so the BOL stays the same. Nobody tells the coordinator, so the carrier is not told. A simple rule helps: any change to the count at the dock must be entered in the warehouse system before the driver arrives. The AI logistics coordinator can then see it and act.
Late changes near pickup
Some changes happen in the last hour, when a pallet is damaged during loading or a product fails a final check. There may be no time to reprint everything. The team should have a quick rule for these cases: the dock lead corrects the count by hand on the BOL, both the dock lead and the driver initial the change, and the shipment record is updated right after. The handwritten change is better than a wrong printed number.
Hypothetical example: a split for height
This example is hypothetical and does not describe a real customer. A manufacturer's BOL shows 6 pallets. The receiver requires pallets no taller than 60 inches. Two pallets are 72 inches tall, so the warehouse splits them, and the load becomes 8 pallets. The AI logistics coordinator sees the new count in the warehouse data, flags that the BOL still says 6, and asks the shipping clerk to update the BOL and print new pallet labels.
What should be checked when the pallet count changes?
When the pallet count changes, the team should check the BOL count, the weight, the pallet labels, the packing slip, the booking, and the receiver's advance notice. An AI logistics coordinator should run these checks together, because a change in one usually means a change in the others.
The change checklist
| Item | What to check | Who fixes it |
|---|---|---|
| BOL handling unit count | Matches the actual pallets | Shipping clerk |
| BOL weight | Matches the scale or packing data | Warehouse |
| Pallet labels | One label per pallet, numbered correctly (for example, 1 of 8) | Warehouse |
| Packing slip | Matches the quantities on the pallets | Warehouse or customer service |
| Booking | Count and weight within what the carrier accepted | Load owner |
| Advance ship notice | Matches the new count | Customer service or EDI owner |
| Rate confirmation | Price still valid for the new count and weight | Load owner |
A rate confirmation is the document that states the agreed price and terms for one load.
The change workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Detect | Warehouse count differs from BOL | Flags the load and the size of the change | Never |
| 2. Check | Change flagged | Compares count and weight with the booking and quote | Never |
| 3. Update documents | Change confirmed by warehouse | Updates BOL, labels, and packing slip | When the warehouse cannot confirm the count |
| 4. Tell the carrier | Change affects price, space, or equipment | Asks for written confirmation | When the carrier changes the price above limits |
| 5. Tell the receiver | Change affects the delivery | Updates the advance notice | When the customer must approve a partial |
| 6. Record | All steps done | Saves the change, reason, and confirmations | Never |
Weight usually changes too
If pallets are added or removed because the quantity changed, the weight changes too. If pallets are combined or split with the same product, the weight may stay the same but the weight per pallet changes. On LTL loads, total weight drives the price, so the BOL weight should be updated whenever the quantity changes.
Labels must match the BOL
Pallet labels often show "1 of 10," "2 of 10," and so on. If the count changes to 9, all labels must be reprinted to show "of 9." Old labels on the dock can confuse the driver and the receiver and make a correct BOL look wrong.
Booking limits
The booking may limit pallets or weight. A truckload booked for 22 pallets may not fit 26. An LTL quote may be valid only up to a certain number of pallets or a certain weight. The AI logistics coordinator should compare the new count with the booking and flag any change that goes past the limit.
The customer may need to approve
If the count drops because some lines are back-ordered, the customer may need to agree to a partial shipment. Some customers prefer to wait for the full order. Others want what is ready. Customer service should confirm before the truck leaves, and the AI logistics coordinator should not release a partial shipment that the customer has not approved, if the rules require approval.
Hypothetical example: labels left on the dock
This example is hypothetical and does not describe a real customer. A distributor reduces a load from 10 to 9 pallets after a line is canceled. The BOL is updated, but the old labels marked "of 10" stay on the pallets. The receiver counts nine pallets with labels saying "of 10" and reports one missing. The AI logistics coordinator's checklist would have flagged the labels when the count changed.
When does a pallet count change need the carrier's approval?
A pallet count change needs the carrier's approval when it changes the price, the space needed, the equipment, or the handling, such as more pallets on an LTL load or a load that no longer fits the booked trailer. An AI logistics coordinator should ask the carrier to confirm in writing before pickup in those cases.
Approval rules by mode
| Mode | Change | Carrier approval needed? |
|---|---|---|
| Truckload | Count changes within trailer capacity | Usually no, but tell the carrier |
| Truckload | Count exceeds trailer capacity | Yes, new equipment or second truck |
| LTL | Count or weight goes up | Yes, the price may change |
| LTL | Count or weight goes down | Yes, to confirm the lower price |
| LTL volume quote | Count passes the volume threshold | Yes, may need a volume or truckload quote |
| Any | Pallets become non-stackable | Yes, space and handling change |
A volume quote is an LTL price for shipments that take up a large share of a trailer. Non-stackable means no freight can be placed on top of the pallet.
Why lower counts need confirmation too
When the count goes down, the price should go down on LTL loads. If the carrier does not confirm the lower price, the invoice may still use the original quote. The audit then needs to catch it. A written confirmation before pickup makes the audit simple.
Accessorials can follow a count change
A higher count can trigger extra charges beyond the base rate. A carrier may add a fee for extra handling, for pallets that cannot be stacked, or for freight that needs more trailer space than quoted. These are accessorials, which are fees for extra services beyond the base rate. The confirmation from the carrier should say whether any accessorial applies, so the invoice holds no surprises.
When the carrier says no
Sometimes the carrier cannot take more pallets on the planned truck. The load owner must decide: split the load, find a larger truck, or move it to another approved carrier. The decision should follow the company's approval limits, and the reason should be saved with the load.
Tell the carrier even when approval is not needed
Even on truckload, where a small count change rarely affects price, the carrier should know. The driver will count pallets at pickup. If the dispatcher's paperwork shows a different number, the driver may call the office or note an exception. A short message prevents the confusion. The note should be saved with the load.
Detention and delays
If the count change is found when the driver is already at the dock, the fix may take time. Detention is a fee a carrier bills when its truck waits too long at a dock. The September 2024 study by the American Transportation Research Institute (ATRI) found that detention affected 39.3% of truck stops in 2023. Catching count changes before the driver arrives is one way to stay out of that number.
Hypothetical example: a volume threshold
This example is hypothetical and does not describe a real customer. An LTL load is quoted for 5 pallets. The customer adds product, and the count rises to 9 pallets. The AI logistics coordinator sees that the new count passes the carrier's limit for a standard LTL quote and asks for a volume quote. The carrier offers a new rate. The new price is within the approval limit, so the coordinator accepts it, updates the rate confirmation, and reprints the BOL.
How should teams test whether software catches pallet count changes?
Teams should test software with loads where the count changes in different ways: a rebuilt pallet, an added line, a partial shipment, and a split load. An AI logistics coordinator should catch each change, update or flag the BOL, labels, and packing slip, and ask the carrier when the price or space changes.
The test
| Test case | Pass | Fail |
|---|---|---|
| Two pallets combined at the dock | Count and labels updated before pickup | BOL still shows the old count |
| Line added after BOL printed | Count, weight, and rate checked | Old weight ships |
| Partial shipment | BOL, packing slip, and ASN show the partial quantity | Receiver expects the full order |
| Count exceeds LTL quote | Carrier asked for a new quote | Price surprise on the invoice |
| Load split into two trucks | Two BOLs, each with its own count | One BOL for both |
| Record | Every count change saved with reason | Only the final number kept |
Include the warehouse system in the test
The test only works if the software receives real warehouse data. Ask the vendor how it gets the final pallet count: from the warehouse system, a scan at the dock, a spreadsheet, or a person typing it in. Then run one test load through that path, and change the count at the dock to see whether the software notices.
Questions to ask in a demo
- Where does the software get the actual pallet count from the warehouse?
- What happens when the count changes after the BOL is printed?
- Does it reprint labels and packing slips too?
- How does it know when a count change affects price?
- Who is told, and how?
Warning signs
- The BOL is printed from the order and never updated.
- Labels are printed separately with no link to the BOL.
- The carrier learns about the change at pickup.
- There is no record of why the count changed.
Warning signs at the dock
Ask the dock team how they report a rebuilt pallet today. If the answer is "we tell the driver" or "we write it on the BOL," the software is not getting the change. A good system makes the dock's report the trigger for every downstream update.
Measure the result
The team should track how many loads shipped with a BOL count that differed from the freight, how many deliveries had shortage or overage notes, and how many invoices showed a weight or count different from the BOL. Good software should push these numbers down.
Where does Wilson fit when the pallet count changes?
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. When the pallet count changes, Wilson checks every document against the new count and the booking.
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 from the connection or data flow the company already has, such as an ERP feed, a scheduled file drop, a spreadsheet, email, or API.
How Wilson handles a count change
Wilson updates the BOL, pallet labels, and packing slip from the new count, checks the weight, and compares the change with the booking. If the change affects price, space, or equipment, Wilson asks the carrier to confirm in writing. Wilson negotiates rates against the customer's rate targets within configured rules and approval limits, and sends rates outside those limits to the logistics team. 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.
At delivery and invoice
Wilson collects the POD at delivery and compares the receiver's count with the BOL. When the carrier invoice arrives, Wilson audits and reconciles it against what was booked, including any confirmed change. 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 the warehouse reports final counts, how often pallets are rebuilt at the dock, which receivers have pallet height or label rules, and how partial shipments are approved. These answers shape the checks an AI logistics coordinator runs when the count changes.
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 count change is saved in the shipment record with change history.
Teams dealing with price effects can read why a carrier may need to requote when the pallet count changes. Teams handling delivery disputes can see what to do about a partial delivery with missing pallets.
This article is part of our complete guide to bills of lading from booking to delivery.
FAQs
Does the BOL need to change when the pallet count changes?
Yes. The BOL count is what the driver signs for and the receiver checks. An AI logistics coordinator updates the BOL and labels before pickup.
Does a pallet count change affect the freight price?
Often on LTL loads, and sometimes on truckload if the freight no longer fits. An AI logistics coordinator asks the carrier to confirm in writing.
What else should change with the pallet count?
The weight, pallet labels, packing slip, advance ship notice, and sometimes the rate confirmation. An AI logistics coordinator checks them together.
How can false shortage claims be avoided?
By making sure the BOL count matches the pallets that actually ship. An AI logistics coordinator compares the warehouse count with the BOL before pickup.
What if the count changes while the driver is at the dock?
Correct the BOL by hand, have the dock lead and driver initial it, and update the record right after. An AI logistics coordinator then updates the labels, packing slip, and carrier record.
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
- American Transportation Research Institute, "New Research Documents Substantial Financial and Safety Impacts from Truck Driver Detention," September 2024: https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator keeps the bill of lading, labels, and booking in line when the pallet count changes: talk to the Cartage team.