Customers keep asking for the BOL and POD after delivery. How do we send them without being asked?

Bills of lading guideNov 17, 202617 min read

Short answer

Set up a document pack for each customer. Send it as soon as the signed POD is filed. List the documents each customer needs and who should get them. Check that each file matches the order before you send it. This is the work Wilson, by Cartage, takes off your team. The AI logistics agent requests and files each POD and keeps the BOL on the shipment.

Book 15 minutes with the team →

How do you send customers their BOL and POD without being asked?

On Monday morning, a customer service rep opens her inbox and finds six emails from customers. Three ask for a POD. Two ask for the signed BOL. One asks for both, plus the packing list, because the customer's accounts payable team won't release payment without them. Each request takes ten to twenty minutes: find the load, find the carrier, check whether the POD came in, look for it in a shared inbox, download it, rename it, send it. Two of the PODs are not on file, so she emails the carriers and waits.

None of these customers had a problem with the freight. They needed paper, and nobody sent it.

To send customers their BOL and POD without being asked, set up a document pack for each customer that lists the documents they need, who receives them and in what format, then send the pack automatically when the signed POD is filed and checked against the order. For documents needed earlier, like the signed BOL at pickup, set a separate trigger. File every document on the shipment so any later request takes one search.

The work is not hard. It is just repeated across hundreds of loads, by different people, with different rules for each customer. When the rules live in people's heads, documents go out late, go to the wrong person or don't go out at all.

Why customers need the documents

Customers ask for documents for practical reasons:

  • Payment. Many accounts payable teams release payment only with a signed POD.
  • Receiving and inventory. The BOL and packing list show what was shipped, to match what was received.
  • Claims. If freight arrived short or damaged, the POD notes are the first evidence.
  • Their own customers. A distributor may need to pass the POD to the end customer.
  • Records. Some industries keep shipping documents for audits or traceability.

When the shipper sends the documents first, all of these move faster. The guide on what to do when the customer won't pay without the POD shows how much the payment side depends on it.

What each request really costs

A single document request looks small. Count the whole chain, though, and it adds up. Someone on the customer's side notices a missing POD, writes an email and waits. Someone on the shipper's side reads it, finds the load, looks for the document, maybe asks the carrier, and replies. The customer's AP team then matches the document to the invoice. If the POD was not on file, the chain runs again a day later.

Consider a hypothetical shipper that gets 40 document requests a week, at about 15 minutes each on its side. That is around 10 hours a week of searching and forwarding, before counting the customer's time or the payments that wait. The exact numbers will differ for every company. The point is that a request is a sign of work done twice: once to file the document, and again to find and send it.

What "without being asked" means

Sending documents proactively does not mean sending everything to everyone. It means each customer gets the documents they actually use, at the moment they need them, without a request. A customer that needs only the POD should not get five attachments. A customer whose payables team needs three documents should get all three in one message.

Where to start

Let's review which documents your customers ask for after delivery. You don't need to prepare anything: Cartage maps the workflow with you on the call.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

What should go in each customer's document pack?

A document pack is a short rule per customer: which documents, which trigger, which recipient, which format and which references. Write it once, and every load for that customer follows it.

The common documents

Document What it is When it exists Who usually wants it
Bill of lading (BOL) The shipping contract and receipt for the freight Created before pickup; signed at pickup Customer receiving, customer AP
Signed BOL The BOL with the driver's signature and any exceptions At pickup Customer receiving, claims
Proof of delivery (POD) The delivery receipt signed by the receiver, often the BOL signed at delivery At delivery Customer AP, customer service
Packing list The list of items, quantities and lots in the shipment Before pickup Customer receiving, inventory
Commercial invoice The invoice for goods, needed on cross-border loads Before pickup Customs broker, customer
Certificate of analysis (COA) Test results for a product lot Before or at shipment Quality teams in food, chemicals and materials
Weight ticket A scale ticket for the loaded truck At pickup Customers who pay by weight

Not every customer needs every document. The pack lists only the ones that customer uses.

The fields of a document pack rule

For each customer, or each customer location, write:

  • Documents: for example, signed POD and packing list.
  • Trigger: POD filed and checked; or signed BOL at pickup; or both.
  • Recipient: a named contact, a shared inbox, or both.
  • Format: one PDF per document, one combined PDF, or the format their system needs.
  • File naming: many customers want the PO number in the file name.
  • References in the message: PO number, order number, BOL number, PRO number.
  • Special notes: for example, "POD must show receiver's printed name" or "send to AP and receiving separately".

A hypothetical pack

Consider a hypothetical distributor customer:

"Send the signed POD and the packing list to the AP inbox when the POD is filed. File names start with the PO number. Message subject: PO number, ship date, delivery date. Send the signed BOL to the receiving lead the same day as pickup. COA for each lot goes with the BOL."

That is the whole rule. Anyone on the team, or an AI logistics agent, can follow it.

One rule per account or per location

Large customers often have different needs at different sites. The corporate AP team may want PODs for every delivery, while each distribution center's receiving lead wants only the signed BOL for its own loads. Write the rule at the level where the needs differ. If all sites behave the same, one account rule is enough. If they differ, set a rule per delivery location and let it override the account rule.

Per load or daily summary

Some customers want one email per load. Others, especially those receiving many loads a day, prefer one daily message with every POD attached and a short table of PO numbers and delivery dates. Ask which they prefer. A daily summary is easier for a busy AP team to process, but it delays each document by up to a day. A customer that pays on POD may want the faster option.

Where the rule lives

Keep the rule with the customer's record, not in an email folder or a note on one person's desk. When a new person handles the customer, the rule should be visible. When the customer changes the recipient, update the rule once.

How should the document workflow run after delivery?

The workflow is four steps: get the POD, check it, send the pack and file everything on the shipment. The order matters, because sending before checking creates new problems.

Step 1: Get the POD on delivery day

Ask the carrier for the signed POD the day the load delivers. Some carriers send it on their own. Some post it on their website. Some need a reminder. The longer the wait, the harder it is to get. The article on when to chase a missing POD covers timing and escalation.

Step 2: Check the POD against the order

Before the POD goes to the customer, check:

  • The PO or order number matches the load.
  • The delivery address matches.
  • The pallet or piece count matches the BOL.
  • The receiver signed and dated it.
  • Any exceptions written on it: shortage, damage, refused items.

If the POD has exceptions, do not just forward it. Tell the team first, because a claim may need to start and the customer will have questions. The receiver may already have noted the problem; the shipper should know before the customer calls.

If the POD belongs to another load, stop. Sending the wrong POD to a customer creates confusion and may show another customer's information. See what gets corrected when a POD is filed against the wrong load for the cleanup.

Step 3: Send the pack

Once the POD checks out, send the pack following the customer's rule: the right documents, to the right recipients, with the right file names and references. One message per load is usually best. Some customers prefer a daily summary with all of that day's deliveries.

What the message should say

Keep the message short and easy to file on the customer's side. A hypothetical example:

"Subject: PO 77120, delivered Nov 14, POD attached. Attached: signed POD and packing list for PO 77120, BOL 300518, shipped Nov 12 from the plant and delivered Nov 14 to your Columbus DC. No exceptions noted. Questions: logistics desk."

The receiver can match it to the order without opening the files. If there were exceptions on the POD, the message should say so plainly and name the person handling them.

Step 4: File everything on the shipment

Every document, and the message that sent it, should be saved on the shipment. When the customer asks again in three months, or when an auditor asks, the answer is one search. The guide on how to organize BOLs, PODs and freight documents covers filing in more detail.

Documents earlier in the load

Some documents are needed before delivery:

  • Signed BOL at pickup. Many customers want it the same day, to know what was shipped. The article on when a customer should receive the final bill of lading explains why the signed version, not the draft, is the one to send.
  • Packing list and COA. These often go with the BOL, or ahead of the truck, so receiving can plan.
  • Cross-border documents. The commercial invoice and packing list go to the customs broker before the border, under the customer's procedure.

Each of these can have its own trigger in the pack rule.

Who owns each step

Step Owner Common failure
Request the POD Load owner Requested only when the customer asks
Check the POD Load owner Forwarded without looking
Send the pack Load owner or customer service Sent to the wrong person or missing a document
File the documents Load owner Left in a personal inbox
Update the pack rule Customer service Old recipient still on file

What goes wrong when documents are sent only on request?

Waiting for requests costs time on both sides, slows customer payments and leaves documents scattered across inboxes. These are the usual mistakes.

Mistake 1: Treating document requests as customer service work

When documents go out only on request, customer service spends hours each week on a task that should be part of closing each load. The requests also arrive at random times, interrupting other work.

Mistake 2: No list of what each customer needs

Without a pack rule, each person guesses. One sends the POD only. Another sends the POD and BOL. The customer gets different packs from the same shipper and has to ask again.

Mistake 3: Forwarding a POD with exceptions

A POD that says "2 pallets damaged" is not just a document. It is the start of a possible claim. Forwarding it without telling the team leaves the customer to raise the problem.

Mistake 4: Sending the draft BOL

A BOL printed before pickup may not match what shipped. The driver may have changed the count, or a pallet may have been left behind. Send the signed version.

Mistake 5: Documents live in personal inboxes

If the POD arrived in one coordinator's inbox and was forwarded from there, the next person cannot find it. File every document on the shipment.

Mistake 6: Expecting the customer to use a portal

Some shippers tell customers to download documents from a portal. Many customers' AP teams will not log in, and will email instead. Ask each customer how they want to receive documents.

Mistake 7: Uploading to the customer's portal by hand, late

Some large customers require documents in their own supplier portal. That task is separate from emailing a pack, and someone has to own it. Put it in the pack rule with a clear owner and deadline.

Mistake 8: Sending another customer's documents

A POD filed against the wrong load, or a combined PDF built from the wrong files, can send one customer's prices, addresses or product details to another. Check the order number on every document before it leaves, and never reuse a document pack from a previous load as a template with the old files still attached.

A short decision guide

Situation What to do
POD filed, clean, matches the order Send the pack per the customer's rule
POD filed with shortage or damage noted Tell the team first; start the claims process; then send with a note
POD missing a day after delivery Chase the carrier; tell the customer only if they are waiting on it
POD belongs to another load Do not send; correct the filing and request the right POD
Customer asks for a document not in their pack Send it, then ask whether to add it to the pack
Customer requires a supplier portal upload Assign a person to do it; note it in the pack rule

What checklist should you use to set up document packs?

Set up the packs once, starting with the customers who ask most, and review them a few times a year. This checklist covers the setup.

Item Question to answer Owner
Request history Which customers asked for documents most in the last three months? Customer service
Documents Which documents does each customer need? Customer service
Trigger When does each document go out: pickup, POD filed, daily summary? Logistics
Recipients Who receives each document, by name or shared inbox? Customer service
Format Separate PDFs or one combined file? File naming rule? Customer service
References Which numbers go in the subject and file names? Customer service
POD check What is checked before the POD is sent? Logistics
Exceptions Who is told when a POD shows shortage or damage? Logistics
Filing Where is every document saved for each load? Logistics
Portals Which customers need a supplier portal upload, and who does it? Customer service
Cross-border Which documents go to the customs broker, and when? Logistics
Review How often is each pack rule reviewed? Customer service

How to roll it out

Pull the document requests from the last few months. Sort by customer. The top ten customers usually account for most requests. Write pack rules for them first. Run them for a month, then count the requests that still came in. Each one shows a gap: a missing document, a wrong recipient or a slow POD.

What to measure

  • Document requests from customers per week.
  • Time from delivery to POD filed.
  • Time from POD filed to pack sent.
  • Customer payments held for missing documents.

As requests go down, customer service gets hours back and customers pay on time.

How does Wilson, by Cartage, send customers their shipping documents?

Wilson, by Cartage, is an AI logistics agent that generates the BOL, requests and files PODs, and can request, chase, file and attach any document configured in the workflow, so the documents a customer needs are on the shipment when they are needed. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

The labor

The labor is collecting and chasing the paper. Wilson generates and sends the BOL and attaches it to the shipment. It also generates documents such as rate confirmations, packing slips, packing lists, commercial invoices and pallet labels. It requests and files PODs, and follows up with carriers by phone and email until it gets an answer. It can request, chase, file and attach any other document configured in the workflow, such as a COA. For cross-border loads, Wilson helps run the customs paperwork under a customer-specific procedure and sends the information to the customer's customs broker; it is not a customs broker and does not clear customs.

Wilson reaches customers and consignees by email or SMS where configured. Which documents go to which customer, and when, is set up with the team during onboarding; confirm the exact pack for your customers in discovery. Wilson does not upload documents to customer portals.

When something goes wrong at delivery, such as damage, Wilson can handle the freight claim: it asks the receiver for photos and to set the product aside, opens the claim with the carrier and tells the team what it did. The claims process is defined during onboarding.

The data

The data is where every document lives. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. An activity log records who wrote what and when. Every message, confirmation and change stays in the shipment's change history, so a customer's request months later is answered with one search. Wilson replaces the TMS for freight execution and connects to the company's ERP.

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.

The network

The network gives the shipper better freight rates on every lane, because its volume counts with every other Wilson customer's. The network includes carriers and brokers, and the company still approves who hauls its freight.

The payments

The payments use the same documents. Wilson audits each carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person.

Control

Teams reach Wilson by email, Slack, Microsoft Teams, SMS, WhatsApp or phone. Control starts with assisted execution: the company sets approval limits, and routine actions run automatically within those rules as the workflow is proven. Timing depends on scope: most teams start on a few lanes and expand from there.

Pricing

Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

FAQs

Can Wilson send our customers their shipping documents?

Wilson, by Cartage, an AI logistics agent, generates and sends the BOL, requests and files PODs, and can request, chase, file and attach any document configured in the workflow. It reaches customers by email or SMS where configured. Which documents go to each customer, and when, is set up with the team.

When should a customer get the POD?

As soon as it is filed and checked against the order, ideally the day of delivery or the day after. Waiting for the customer to ask slows payment and adds work on both sides.

Should we send the BOL or the POD?

It depends on the customer. Many want the signed BOL at pickup and the POD after delivery. Often the POD is the BOL signed by the receiver. The pack rule should say which.

Does Wilson upload documents to customer portals?

No. Wilson does not upload documents to customer portals. If a customer requires a portal upload, assign a person to it and note it in the pack rule.

What if the POD shows damage or a shortage?

Tell the team before sending it, because a claim may need to start. Wilson can handle the freight claim under the process defined during onboarding: it asks the receiver for photos, opens the claim with the carrier and tells the team.

What if the carrier sends the wrong POD?

Do not forward it. Correct the filing and ask the carrier for the right one. Check the order number, address and count on every POD before it goes to a customer.

Can Wilson collect certificates of analysis or other documents?

Wilson can request, chase, file and attach any document configured in the workflow, which can include a COA.

How long should we keep shipping documents?

Follow your company's records policy and any customer or industry rules. Keeping them on the shipment record makes them easy to find for as long as you keep them.

Does a document pack replace the customer's invoice?

No. The pack carries shipping documents. Your sales invoice to the customer is separate, though many shippers attach the POD to it so the customer can pay without asking.

Will customers be annoyed by extra emails?

Not if each pack holds only what that customer uses and goes to the right person. One message per load, or one daily summary, is usually welcome.

Sources

Let's review which documents your customers ask for after delivery. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google