The carrier marked it delivered. Where is the confirmation?
Key Takeaways
When a carrier marks a load delivered, the confirmation is the signed proof of delivery, and the team should request it, check it against the order, and only then close the load. An AI logistics coordinator should treat "delivered" as a claim that needs evidence, because billing, payment, and customer disputes all depend on the signed record.
- A proof of delivery, or POD, is the signed record that the receiver took the freight, often the bill of lading signed at delivery.
- A carrier's "delivered" status is a scan or a system update. It is useful, but it is not the receiver's signature.
- The POD shows who signed, when, and whether the receiver noted shortages or damage.
- Many teams invoice customers and pay carriers based on the POD, so a missing POD delays cash in both directions.
- The POD should be checked for the right load, a signature, a date, and any exceptions noted by the receiver.
- Wilson, by Cartage, is an AI logistics coordinator that collects shipping documents such as bills of lading and PODs as part of each load, and audits carrier invoices against what was booked before payment.
Why is a "delivered" status not enough?
A "delivered" status is not enough because it records the carrier's claim, not the receiver's acceptance of the freight. An AI logistics coordinator should keep the load open until the signed POD arrives and matches the order.
A carrier's system may mark a load delivered when the driver taps a button, when a terminal scans the freight, or when a dispatcher closes the trip. None of these is the receiver's signature. In most cases the freight did arrive. But when it did not, or when part of it was damaged or short, the status alone gives the shipper nothing to work with.
The table below compares a delivery status with a proof of delivery.
| Question | "Delivered" status | Signed POD |
|---|---|---|
| Who created it? | Carrier system or driver | Receiver signs, carrier provides |
| What does it prove? | Carrier says the trip ended | Receiver took the freight |
| Does it show the count? | Usually not | Often shows pieces or pallets received |
| Does it show damage? | No | Receiver can note damage or shortage |
| Can it support a claim? | Weakly | Yes, it is the key document |
| Is it enough to bill the customer? | Often not | Usually yes |
Who should own POD collection
The logistics team usually owns POD collection, because it holds the carrier relationship. Billing needs the POD to invoice. Customer service needs it for disputes. Finance needs it to release carrier payment. When nobody owns collection, each group assumes another one has it. An AI logistics coordinator can own the collection step for the logistics team and share the POD with each group that needs it.
Delivery scan versus confirmed receipt
A delivery scan says the carrier believes it delivered. Confirmed receipt says the receiver signed for the freight. The difference matters when something goes wrong. A receiver who says "we never got it" will be answered by the POD, not by the scan. An AI logistics employee should label which one the team has for each load.
Most delivered loads are fine
Most loads marked delivered did arrive in good order. The point of checking is not distrust. It is to have proof ready for the few that go wrong, and to bill and pay on time for the rest. An AI logistics coordinator can do the routine checks quickly so people only look at exceptions.
What can go wrong after "delivered"
Several problems hide behind a delivered status. The freight went to the wrong address. The receiver refused part of it. Pallets arrived damaged and the receiver noted it. The count was short. The driver marked delivered before unloading. Each of these shows up on the POD, not on the status.
Delivered notifications sent too early
Some systems send customers a "delivered" message the moment the carrier's status changes. If the POD later shows a shortage or a refusal, the customer has already been told everything is fine. An AI logistics coordinator can hold external delivered messages until the POD confirms a clean delivery, or send a softer message such as "The carrier reports delivery; we are confirming receipt." The choice depends on the customer and the team's rules.
Why the POD affects cash
Many shippers invoice their customers when they have a POD. Many also release carrier payment only after the POD arrives. A missing POD can delay both. The shipper waits to bill, and the carrier waits to be paid. An AI logistics coordinator that collects PODs quickly helps cash move on both sides.
Where does the confirmation come from, and how do you get it?
The confirmation usually comes from the carrier, who collects the receiver's signature on the bill of lading or an electronic device and then shares it. An AI logistics coordinator should know where each carrier keeps PODs and request them as soon as the delivery status appears.
A bill of lading, or BOL, is the shipping document that lists the freight and serves as a receipt between shipper and carrier. At delivery, the receiver signs it, and that signed copy becomes the POD. Some carriers capture the signature on a handheld device and produce an electronic POD.
Ask the receiver when the carrier is slow
When the carrier is slow, the receiver may be faster. Many receivers keep a signed copy of the delivery paperwork or a receiving record in their own system. A short request to the receiver's dock, with the PO number and delivery date, can produce a copy within hours. An AI logistics coordinator can ask the receiver as a second step, where the customer relationship allows it.
Common POD sources
| Source | How it works | What to watch for |
|---|---|---|
| Carrier website or portal | POD image posted by PRO or load number | May take hours or days to appear |
| Carrier email | Dispatch sends the POD on request | Needs a clear request |
| Carrier API or EDI | Document or image sent electronically | Not every carrier offers it |
| Driver photo | Driver sends a photo of the signed BOL | Quality and legibility vary |
| Receiver | Receiver shares its signed copy | Useful when the carrier is slow |
A PRO number is the tracking number an LTL carrier assigns. An application programming interface (API) is a direct system connection. Electronic data interchange (EDI) is an older standard for exchanging business documents.
Multi-stop loads need a POD for each stop
A load with several deliveries needs a signed POD from each receiver. A carrier may mark the whole load delivered after the last stop, while the PODs from earlier stops are missing. An AI logistics employee should track each stop's POD separately and keep the load open until all of them arrive. Otherwise, a shortage at the second stop may never be seen.
When to request the POD
Request the POD as soon as the carrier marks the load delivered. Many carriers post PODs within a day, but some only send them when asked. A rule might say: check the carrier portal four hours after delivery; if no POD, email dispatch; if still none after one business day, follow up again and escalate after two. An AI logistics employee can apply this rule on every load.
Electronic PODs and paper PODs
Electronic PODs arrive faster and are easier to read. The receiver signs on the driver's device, and the carrier posts the image or sends it through a feed. Paper PODs depend on the driver returning the signed BOL to the terminal, where it is scanned. Paper can take days. An AI logistics employee should know which carriers use which method and set request times to match, so it does not chase a paper POD on the same schedule as an electronic one.
A good POD request
A short, specific request works best. For example: "Please send the signed POD for load 6614 / PRO 8823451, delivered to Harbor Supply on Tuesday." The carrier can find the document quickly. A vague request such as "please send paperwork" often gets the wrong document.
Hypothetical example: delivered without a POD
This example is hypothetical and does not describe a real customer. A distributor's LTL shipment shows "delivered" on Monday. By Wednesday, no POD appears on the carrier's site. The AI logistics coordinator emails the carrier's POD team with the PRO number. The carrier replies that the driver's handheld failed and the paper BOL is at the terminal.
The terminal scans the signed BOL on Thursday. The POD shows the receiver signed for 11 pallets, not 12, with a note: "1 pallet short." The coordinator flags the shortage to the logistics team the same day. Without the POD, the distributor would have billed the customer for 12 pallets and found the shortage only when the customer disputed the invoice.
What should you check on the POD?
You should check that the POD belongs to the right load, has a legible signature and date, shows the expected count, and lists any exceptions the receiver noted. An AI logistics coordinator should run these checks on every POD before the load is closed.
A POD checklist
- Right load. The PRO, BOL, or load number matches the shipment.
- Right receiver. The consignee name and address match the order. A consignee is the party receiving the freight.
- Signature. A signature or a printed name is present and legible.
- Date and time. The delivery date matches the carrier's status and the delivery window.
- Count. The pieces or pallets received match the pieces or pallets shipped.
- Exceptions. Notes such as "damaged," "short," "refused," or "subject to inspection" are captured.
- Legibility. The image is readable enough to use in a dispute.
Hypothetical example: a POD for the wrong load
This example is hypothetical and does not describe a real customer. A chemicals distributor receives a POD from a carrier for load 3381. The AI logistics coordinator checks it and finds the consignee name is a different customer and the pallet count does not match. The carrier sent the POD for another shipper's freight. The coordinator asks the carrier for the correct document, which arrives the next day. Without the check, the wrong POD would have been filed and found only during a dispute months later.
Clean POD versus exception POD
A clean POD has no exceptions. The load can close, and billing and payment can proceed. An exception POD has a note about damage, shortage, or refusal. That load needs follow-up before it closes. An AI logistics employee should route exception PODs to the person who handles claims or customer issues.
Concealed damage
Concealed damage is damage the receiver cannot see at delivery, such as a crushed product inside an intact carton. It is found later, when the receiver opens the freight. A clean POD does not rule it out. The receiver should report concealed damage quickly, and the team should record the report with the load. An AI logistics employee can attach the report to the POD so a claim, if needed, has the full record.
What "subject to inspection" means
Some receivers sign with "subject to inspection" or similar wording. This means they accepted the freight but kept the right to report hidden damage later. The load can usually close, but the team should know that a claim may still come. Recording the note helps if the customer reports damage days later.
Read the handwriting
Many PODs are paper forms with handwritten notes. A receiver may write "2 cartons crushed" in a corner. A quick glance can miss it. An AI logistics coordinator should read the whole image, including margins and stamps, and flag any handwritten note for a person to confirm when the writing is unclear. A missed note can cost the team its strongest evidence in a claim.
Common POD mistakes
- Accepting a "delivered" scan as the POD. The team has no signature to show.
- Not reading the POD. Exceptions written on the POD go unnoticed.
- Filing the POD with the wrong load. The document cannot be found when needed.
- Waiting weeks to request it. Carriers take longer to find old paperwork.
How does the POD connect to billing, payment, and disputes?
The POD connects to billing because it proves the customer received the goods, to payment because it proves the carrier finished the job, and to disputes because it records what the receiver accepted. An AI logistics coordinator should link the POD to the shipment, the customer invoice, and the carrier invoice.
Hypothetical example: billing waits on the POD
This example is hypothetical and does not describe a real customer. A building products distributor invoices customers only with a POD. Its average time from delivery to POD was five days, so cash came in late. The AI logistics coordinator begins requesting PODs four hours after each delivery scan and following up the next morning. The average time to POD drops to about one day. The billing team now invoices most loads the day after delivery.
Customer billing
Many shippers invoice the customer only after delivery is confirmed. A POD protects the shipper if the customer later says it did not receive the goods. If the POD shows a shortage, the invoice may need to change. An AI logistics employee can tell the billing team when a clean POD arrives, or when an exception POD needs a credit decision.
Close the load only when everything matches
A load should close when the POD is in hand, the count matches, exceptions are handled, and the carrier invoice matches the booking. Closing earlier leaves loose ends that surface during audits. An AI logistics employee can show which of these steps is still open for each load, so the team knows exactly what is left.
Carrier payment
Carriers want to be paid quickly. Many shippers require a POD before payment, because it proves the service was completed. Wilson audits and reconciles each carrier invoice against what was booked before payment. Customers use the Wilson Wallet to pay their carriers, and payments above approval limits or outside the rules wait for a person.
Refused freight
Sometimes the receiver refuses all or part of the shipment. The POD should show the refusal and the reason, such as damage or a wrong product. Refused freight usually goes back to the carrier's terminal, where storage charges can start. The team must decide quickly whether to return the freight, re-deliver it, or send it elsewhere. An AI logistics coordinator should flag refusals the same day and ask the person who owns returns for a decision.
Freight claims
A freight claim is a request to the carrier for payment for lost or damaged freight. The POD is usually the first document a claim needs. If the receiver noted damage on the POD, the claim is stronger. If the POD is clean, a later damage claim is harder. The person who owns claims should see exception PODs as soon as they arrive.
Keep PODs easy to find
A POD is only useful if someone can find it quickly. Store it with the shipment, named by load number, PRO number, and delivery date. Link it to the customer order and the carrier invoice. When a dispute comes months later, the team should find the POD in seconds. An AI logistics coordinator can file each POD to the right shipment as it arrives.
Accessorial disputes
Some carrier invoices include extra charges for things that happened at delivery, such as waiting time or a liftgate. The POD and the delivery record can show whether the extra service happened. An accessorial charge is a fee for extra service beyond the base rate. An AI logistics coordinator should check those charges against the delivery evidence.
Hypothetical example: a POD settles a dispute
This example is hypothetical and does not describe a real customer. A customer tells a manufacturer that a shipment never arrived and refuses to pay. The manufacturer's AI logistics coordinator pulls the POD, which shows a signature from the customer's receiving clerk, a date, and a full count. The manufacturer shares the POD with the customer, who finds the pallets in a different part of its warehouse. The invoice is paid that week.
How should you evaluate proof of delivery software?
Evaluate proof of delivery software by giving it a load marked delivered with no POD and a POD with a shortage note, and watching what it does with each. An AI logistics coordinator should chase the missing POD and flag the exception.
Demo tests for POD work
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Separates status from POD | Mark a load delivered with no document | Load stays open, POD requested |
| Requests by rule | Wait past the first check time | Portal checked, then dispatch emailed |
| Escalates | Keep the POD missing two days | Escalation with history |
| Checks the POD | Upload a POD with the wrong load number | Mismatch flagged |
| Captures exceptions | Upload a POD noting one pallet short | Exception routed to the right person |
| Links to billing and payment | Close a clean POD | Billing and payment steps can proceed |
| Record | Open the load | POD, source, time, and checks saved |
Demo questions about POD work
- Where does the AI logistics coordinator look for PODs for each carrier?
- How soon after delivery does it request the POD?
- How does it read the POD for count and exceptions?
- Who receives exception PODs?
- How is the POD linked to the customer invoice and the carrier invoice?
- Can the team see PODs still missing by carrier?
Ask about older loads
Ask the vendor how its AI logistics coordinator handles loads delivered weeks ago with no POD on file. Most teams have a backlog. A good answer explains how the backlog is requested, tracked, and closed without overwhelming carriers with requests on the same day.
How to measure POD work
Measure the time from delivery to POD in hand. Count the loads closed without a POD. Track how many exception PODs were flagged within one business day. These measures show whether the AI logistics employee closes loads with evidence.
Test a slow paper POD
Ask the vendor to include a carrier that sends paper PODs days after delivery. Watch whether the AI logistics coordinator adjusts its follow-up timing and keeps the load open without flooding the carrier with requests. Paper PODs are where most delays happen.
Scoring the POD demo
Score each test as pass, partial, or fail. A pass means the POD was requested, checked, and linked, and exceptions were flagged. A partial means the POD was collected but not checked. A fail means the load closed on a status alone.
Warning signs in a POD demo
- "Delivered" closes the load with no document.
- PODs are stored as attachments nobody reads.
- There is no follow-up rule for missing PODs.
- Exception notes are not captured.
- PODs are not linked to invoices.
Where does Wilson fit when a load is marked delivered without confirmation?
Wilson, by Cartage, is an AI logistics coordinator that collects shipping documents, such as bills of lading and proofs of delivery, as part of executing each load. It replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment.
Wilson tracks each load using the best source available, including carrier APIs, the carrier's website by PRO number, and email or direct outreach, including calls where configured. This AI logistics employee requests the documents it needs from the carrier and informs the people who need to know.
What Wilson records
Wilson keeps searchable shipment records with change history. A team can open a load and see the delivery status, the POD, when it arrived, and from which source. When the carrier invoice arrives, Wilson audits and reconciles it against what was booked.
What Cartage asks about PODs in discovery
Cartage asks how the team collects PODs today, which carriers are slow to send them, and who handles exception PODs and claims. Typical questions also cover whether billing waits for the POD. These answers shape the POD rules an AI logistics coordinator applies.
What Wilson does not do for PODs
Wilson does not file or settle freight claims for the customer; a person should own claims. Specific POD reading and exception routing should be confirmed in a demo for the customer's carriers. Not every carrier provides electronic PODs. Exact ERP connection details depend on the customer's systems, and not every connection writes data back to the ERP.
Where teams start with PODs
Most teams start their AI logistics coordinator on a few lanes and expand from there. Timing depends on scope. Cartage helps identify the first workflow during discovery. Teams with slow billing often start with the carriers that are slowest to send PODs.
Teams that want to stop early "delivered" messages can read how to stop a delivered notification before the POD arrives. Teams setting follow-up rules can see when to chase a missing POD. Both topics shape what an AI logistics coordinator does after delivery. Teams sorting out ownership can review who owns a missing POD.
FAQs
The carrier marked it delivered. Where is the confirmation?
The confirmation is the signed proof of delivery, usually from the carrier's portal, email, or electronic feed. An AI logistics coordinator should request it right away and check it against the order.
Is a delivery scan the same as a proof of delivery?
No. A scan is the carrier's record. A POD carries the receiver's signature and any exceptions. An AI logistics employee should keep the load open until the POD arrives.
What should you do if the POD shows a shortage?
Flag it to the person who handles claims and customer issues the same day. An AI logistics coordinator should hold related billing or payment steps until the team decides.
How long should a carrier take to send a POD?
Many carriers post PODs within a day. Set a rule, such as a request after a few hours and escalation after two business days. An AI logistics employee should apply the rule on every load.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator keeps a "delivered" load open until the signed POD arrives, reads it for shortages, and links it to your invoice: talk to the Cartage team.