When should a customer receive the final bill of lading?
Key Takeaways
A customer should receive the final bill of lading soon after pickup, once the driver has signed it and the carrier's tracking number is on it, usually together with the shipment notice. An AI logistics coordinator can collect the signed BOL, check it, and send it to the customer with the details the customer needs to receive the freight.
- A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
- The "final" BOL is the version the driver signed at pickup, with any exceptions noted.
- Customers use the BOL to plan receiving, match the delivery to their order, and support any claim.
- Sending a draft BOL before pickup can confuse the customer if the freight changes.
- The best time is shortly after pickup, with the carrier's name, tracking number, and expected delivery.
- After delivery, the customer may also need the proof of delivery, which is a different document.
- Wilson, by Cartage, is an AI logistics coordinator that prepares bills of lading, collects the signed copy after pickup, keeps customers informed by email, and sends the customer the final signed BOL after pickup.
What does "final bill of lading" mean?
The final bill of lading is the version the driver signed at pickup, showing what the carrier actually received, with any exceptions the driver noted and the carrier's tracking number. An AI logistics coordinator should send customers this version, not a draft printed before the freight was loaded.
Draft, active, and final
| Version | When it exists | What it shows |
|---|---|---|
| Draft | Before the order is fully packed | Planned freight, often estimated |
| Active | When the BOL is ready for pickup | The freight as staged |
| Final | After the driver signs | The freight the carrier received, with any exceptions |
What makes the final version different
The final BOL carries the driver's signature, the pickup date and time, and often the trailer and seal numbers. A seal is a numbered tag that shows the trailer was not opened in transit. If the driver noted anything, such as a short count or a damaged pallet, that note appears only on the signed copy. These details matter to the customer.
Corrections after pickup
Sometimes an error on the BOL is found after the truck leaves, such as a wrong reference number. The signed BOL cannot be changed, because it is the record of what was handed over. Instead, the team should send the customer the signed copy along with a short written correction. Both should be filed with the load.
Why the customer should not get the draft
A draft may show 12 pallets while the final shows 11. A customer who plans receiving around the draft may report a shortage that is not real. A draft may show an old carrier. The customer may then call the wrong carrier for tracking. Sending only the final version prevents these mix-ups.
The legal role of the BOL
Federal rules require for-hire motor carriers to issue a receipt or bill of lading showing 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. The signed BOL is the record of what was handed over. That is why the customer should get the signed copy.
Who holds the signed original
The driver usually keeps one signed copy, the shipper keeps another, and a third may travel with the freight to the receiver. The shipper's copy is the one that should be scanned and filed with the load. If the shipper's warehouse does not keep a signed copy, the team must request it from the carrier, which takes longer. A simple dock rule, "scan the signed BOL before the truck leaves the yard," avoids this.
Legibility matters
A signed BOL that cannot be read is not much use. Faint carbon copies, blurry phone photos, and cut-off pages are common. The AI logistics coordinator should check that the scan shows the signature, the count, and any exception notes clearly. If not, it should ask the warehouse for a better scan while the paper is still on site.
Hypothetical example: a draft that caused a false shortage
This example is hypothetical and does not describe a real customer. A distributor emails the customer a BOL on Monday for a Tuesday pickup, showing 12 pallets. On Tuesday, one pallet is held back for a quality check. The signed BOL shows 11. The customer receives 11 pallets and reports one missing. The customer service team spends two days explaining. Sending the signed BOL after pickup would have prevented the question.
When is the right time to send the final BOL to the customer?
The right time to send the final BOL is shortly after pickup, once the signed copy is scanned and the carrier's tracking number is known, and before the freight arrives. An AI logistics coordinator should send it with the shipment notice, so the customer gets everything needed to receive the freight in one message.
Timing options
| When | Pros | Cons |
|---|---|---|
| Before pickup | Customer can plan early | May not match what ships |
| Right after pickup | Matches what ships; customer can plan receiving | Needs the signed copy scanned quickly |
| With the delivery update | Customer has everything at once | Late for planning on short transits |
| With the invoice to the customer | Supports billing | Too late for receiving |
Why right after pickup works best
Right after pickup, the freight is fixed: the count, weight, carrier, and tracking number are known. The customer still has time to plan receiving. If the driver noted an exception, the customer learns about it before the truck arrives, not at the dock.
Batch sending at the end of the day
Some teams send all of the day's BOLs to customers in one batch each evening. This is simple, but it fails on short transits and makes exceptions arrive late. Sending each BOL soon after its pickup is better for the customer and spreads the work through the day.
Short transits need speed
On a same-day or next-day delivery, the window between pickup and delivery is short. The signed BOL must be scanned and sent within hours. If the warehouse scans documents only at the end of the day, the customer may receive the BOL after the freight. Teams with short transits should scan the signed BOL at the dock.
What if the signed copy is late?
If the signed BOL is not scanned within the expected time, the customer should still get the shipment notice with the carrier, tracking number, and count from the warehouse records. The notice can say the signed copy will follow. The AI logistics coordinator should then chase the scan and send it as soon as it arrives. The customer should not wait for a document to learn that the freight is on its way.
Delays after pickup
If the shipment is delayed after pickup, the customer needs an updated delivery time, not another copy of the BOL. The delay notice should repeat the PO number and tracking number, so the customer can match it to the earlier shipment notice. The AI logistics coordinator can send these updates where configured.
Customers with special requests
Some customers ask for the BOL before pickup to book a receiving appointment. In that case, the team can send the active version with a clear label: "Pre-pickup copy; final signed BOL will follow." The final copy should then be sent after pickup, with any differences highlighted.
The sending workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Collect | Truck leaves the dock | Asks the warehouse for the signed BOL scan | When no scan arrives in time |
| 2. Check | Scan received | Confirms it is legible and matches the order | When the count or items differ |
| 3. Read exceptions | Check complete | Looks for driver notes on count or condition | When an exception needs a decision |
| 4. Send | All clear or exception explained | Sends the shipment notice and BOL to the customer | Never for routine loads |
| 5. File | Message sent | Saves the BOL and the message with the load | Never |
Multi-stop and consolidated loads
When one truck carries orders for several customers, each customer should receive only its own part. If one BOL covers all stops, the team may need to send each customer a copy with only its lines, or a separate BOL per stop. Sending a customer the full BOL can share other customers' order details, which many companies want to avoid.
Hypothetical example: same-day delivery
This example is hypothetical and does not describe a real customer. A manufacturer ships a truckload at 7 a.m. for a 2 p.m. delivery 120 miles away. The dock scans the signed BOL at 7:10 a.m. The AI logistics coordinator checks it against the order and sends it to the customer's receiving team at 7:20 a.m. with the carrier name, the tracking number, and the expected arrival time. The customer's dock has the details five hours before the truck arrives.
What should be sent to the customer along with the BOL?
The final BOL should be sent with a short shipment notice that gives the carrier, the tracking number, the pickup time, the expected delivery, the count, and the customer's order references. An AI logistics coordinator should put the most useful details in the message itself, so the customer does not have to open the attachment to plan.
The shipment notice
| Item | Why the customer needs it |
|---|---|
| Customer PO number | To match the delivery to its order |
| Carrier name | To know who will arrive |
| PRO or tracking number | To track the shipment |
| Pickup date and time | To estimate arrival |
| Expected delivery date or window | To plan receiving |
| Pallet and piece count | To check the delivery |
| Exceptions noted at pickup | To know about any issue in advance |
| Signed BOL attached | For records and any claim |
A PRO number is a tracking number a carrier gives to a shipment.
The customer's carrier on collect loads
On collect loads, where the receiver pays the freight, the customer may have chosen the carrier. Collect means the receiver pays the freight charges. The customer then needs the BOL to match the carrier's invoice to its order. Sending the final BOL quickly helps the customer's finance team as much as its receiving team.
Packing slip and advance ship notice
Some customers also want the packing slip, which lists the products and quantities in the shipment. Others receive an advance ship notice, or ASN, which is an electronic message that tells the receiver what is coming. The BOL, the packing slip, and the ASN should all show the same count. If they differ, the customer will notice.
Use the customer's reference first
Customers organize their receiving by their own purchase order numbers, not by the shipper's order or load numbers. The shipment notice should lead with the customer's PO. If the customer has a receiving appointment number, it should appear too. The shipper's internal numbers can follow below.
Keep the message short
The customer's receiving team is busy. A message with the key details in the first lines and the BOL attached works better than a long email. A clear subject line helps too, such as "Shipped: PO 88214, 11 pallets, ABC Freight PRO 445-221, delivery Nov 6."
Protect sensitive details
A BOL may show details the shipper does not want every customer contact to see, such as a declared value, a third-party warehouse address, or freight charges on a prepaid load. Before sending, the team should decide which version the customer gets. Some companies send a customer copy with charges removed. The rule should be set per customer and applied every time.
Who should receive it
The BOL should go to the people who use it: the customer's receiving team, the buyer who placed the order, and anyone the customer has named for shipping documents. A general sales inbox is often the wrong place. The customer's contacts should be stored with the customer record.
Customers who use EDI
Some customers prefer to receive shipment data by EDI rather than email. EDI, or electronic data interchange, is a standard format that lets two companies' systems exchange business documents. For these customers, the ASN may carry the count and tracking number, and the signed BOL may be sent separately or only on request. The rule should be set per customer.
Hypothetical example: an exception noted
This example is hypothetical and does not describe a real customer. The driver notes "1 pallet shrink wrap torn" on the BOL at pickup. The AI logistics coordinator sees the note on the signed copy and includes it in the shipment notice: "Driver noted torn wrap on 1 pallet at pickup; contents checked and intact." The customer's receiving team knows to look at that pallet and is not surprised.
How is the final BOL different from the proof of delivery?
The final BOL shows what the carrier received at pickup; the proof of delivery shows what the customer received at delivery. An AI logistics coordinator should send the BOL after pickup and the POD after delivery, and compare the two to catch any difference.
BOL versus POD
| Document | Signed by | When | What it proves |
|---|---|---|---|
| Final BOL | Driver (and shipper) | At pickup | What the carrier received |
| Proof of delivery (POD) | Receiver | At delivery | What the customer received and in what condition |
A proof of delivery, or POD, is the document the receiver signs to show the freight arrived.
Why both matter
If the BOL shows 11 pallets and the POD shows 10, the freight was lost or misdelivered in transit. If both show 11 and the customer reports 10, the count may be wrong at receiving. Comparing the two documents tells the team where the problem happened.
Claims start with both documents
When freight is lost or damaged, a claim against the carrier usually needs both the signed BOL and the POD, along with photos and the invoice for the goods. Having both documents filed with the load, and sent to the customer when needed, makes the claim faster. Missing either one slows it down.
Who needs which document
The customer usually needs the BOL to plan receiving and the POD only if there is a dispute, since the customer signed it. The shipper's finance team needs the POD to support the invoice to the customer. The carrier's invoice review needs both. The AI logistics coordinator should send each document to the people who need it.
Collect the POD on time
The POD often comes from the carrier after delivery, sometimes days later. Following up on missing PODs is a separate routine. Teams that want the full process can read when to chase a missing POD.
Send the POD with the customer invoice
Some customers will not pay a freight-included invoice without a POD. Others ask for it only when there is a dispute. The finance team should know which customers need it, and the AI logistics coordinator should attach the POD to the customer's invoice when the rule says so. This shortens the time to get paid.
Hypothetical example: comparing the two
This example is hypothetical and does not describe a real customer. The final BOL shows 14 pallets. The POD shows the receiver signed for 13 with "short 1." The AI logistics coordinator compares the two, sees that the carrier received 14, and opens a claim inquiry with the carrier instead of asking the warehouse to recount. The carrier finds the 14th pallet at its terminal and delivers it the next day.
How should teams set up customer BOL delivery and test it?
Teams should set rules for which customers get the BOL, when, through which channel, and with what notice, and then test those rules with loads that change before pickup, have exceptions, or ship same day. An AI logistics coordinator should send the right version to the right people every time.
Setup checklist
| Setting | Example |
|---|---|
| Which customers want the BOL | All, or only those that ask |
| When to send | After pickup, within 1 hour of scan |
| Pre-pickup copy | Only for customers who book receiving appointments |
| Recipients | Receiving team and buyer |
| Message format | Shipment notice with BOL attached |
| POD | Sent on request or with the customer invoice |
The test
| Test case | Pass | Fail |
|---|---|---|
| Normal load | Signed BOL sent after pickup with notice | Draft sent or nothing sent |
| Count changed before pickup | Final count in the notice | Old count sent |
| Exception noted by driver | Exception in the notice | Customer surprised at the dock |
| Same-day delivery | BOL sent within an hour of pickup | BOL arrives after the freight |
| Customer wants a pre-pickup copy | Labeled pre-pickup copy, then final | Only one version sent |
| Record | What was sent, to whom, and when | No history |
Ask the customer what they want
The best setup comes from asking key customers how they want to receive shipping documents: when, in what format, and to whom. Some want every BOL. Others want only a daily summary. A short conversation saves months of documents going to the wrong place.
Measure the result
The team should track how often customers receive the final BOL before the freight arrives, how many customer questions about counts or carriers come in, and how many false shortage reports occur. These numbers show whether the setup works.
Questions to ask in a demo
- How does the software know when the signed BOL is available?
- Does it check the signed copy against the order before sending?
- Can it read exceptions noted by the driver?
- Can each customer have different recipients and timing?
- Does it compare the BOL with the POD after delivery?
Test with a real customer contact
If a friendly customer agrees, send test notices to its receiving team and ask for feedback. Was the subject line clear? Did they find the PO number fast? Did the attachment open? Real feedback is worth more than a vendor's sample email.
Warning signs
- The customer gets the BOL only if someone remembers to email it.
- Drafts are sent automatically before pickup.
- Exceptions on the signed copy are not read.
- There is no record of what was sent to the customer.
Where does Wilson fit in sending the final BOL to customers?
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. After pickup, Wilson collects the signed BOL, checks it against the order, and sends it to the customer.
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.
How Wilson keeps customers informed
Wilson keeps internal teams informed through Slack, Microsoft Teams, email, or SMS, and updates the shipper through email at each step, from booked to POD filed. Receivers can be updated by email or SMS on pickup, delays, delivery, and POD, where configured. Wilson asks the carrier for status and updates everyone else. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured.
After delivery
Wilson tracks each load using the best source available, collects the POD, and files it with the shipment. When the carrier invoice arrives, Wilson audits and reconciles it against what was booked. 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 Wilson does not do
Wilson does not change the contents of a signed BOL. If the signed copy shows an exception, Wilson reports it as written and brings any decision to the load owner. Wilson does not send documents to contacts the customer has not approved.
What Cartage asks in discovery
Cartage asks which customers want shipping documents, how the warehouse captures the signed BOL today, which customers use EDI, and who answers customer questions about shipments. These answers shape the customer update rules an AI logistics coordinator follows.
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 document and message is saved in the shipment record with change history.
Teams connecting shipping documents to delivery can read how a packing list connects to delivery confirmation.
This article is part of our complete guide to bills of lading from booking to delivery.
FAQs
When should a customer receive the final bill of lading?
Shortly after pickup, once the signed copy is scanned and the tracking number is known. An AI logistics coordinator sends it with the shipment notice.
What is the final bill of lading?
The version the driver signed at pickup, with any exceptions noted. An AI logistics coordinator sends this version, not a draft.
What should be sent with the BOL?
The PO number, carrier, tracking number, pickup time, expected delivery, count, and any exceptions. An AI logistics coordinator puts these in the message.
Is the BOL the same as the proof of delivery?
No. The BOL shows what the carrier received; the POD shows what the customer received. An AI logistics coordinator compares the two to catch differences.
Should the customer get a BOL before pickup?
Only if they need it to book receiving, and it should be labeled as a pre-pickup copy. An AI logistics coordinator sends the signed final version after pickup.
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 sends customers the final bill of lading at the right time, with the details they need to receive the freight: talk to the Cartage team.