What should freight software do when the carrier says “delivered” but the customer says it never arrived?
Key Takeaways
When the carrier says "delivered" but the customer says it never arrived, freight software should treat the load as an open exception, not as delivered. It should gather the carrier's proof of delivery and delivery details, the receiver's own records, and the delivery address and reference used, then compare them to find what happened: a wrong address, a delivery to the wrong dock or building, a signature by the wrong person, a status entered too early, or a real loss. Until it is resolved, the carrier's invoice should wait and the customer should get clear updates. An AI logistics agent such as Wilson, by Cartage, runs this sequence: it asks the carrier for the signed POD and delivery details, asks the receiver to check its records, records each answer with its source and sends the case to a person when a claim or a reshipment decision is needed.
- "Delivered" from the carrier is a claim. The signed POD and the receiver's records are the evidence.
- Most cases are not losses: wrong address, wrong dock, early status update or freight received but not logged.
- Ask the carrier for the signed POD, the time, the address and the name of the person who signed.
- Ask the receiver to check its receiving log, other docks and other buildings.
- Hold the carrier's invoice while the case is open.
- If the freight is lost or damaged, a person decides on the claim and any reshipment.
What could have happened?
Several things could have happened, and most of them are fixable. An AI logistics agent tests each possibility in order, starting with the most common. The table lists the usual causes, how to recognize them and what to do.
| Possible cause | Signs | Next step |
|---|---|---|
| Status entered before delivery | No signed POD; driver still en route | Ask carrier for current location and ETA |
| Delivered to the wrong address | POD address differs from the order | Ask carrier to recover and redeliver |
| Delivered to another dock or building at the same site | POD signed by someone at the site | Ask receiver to check other docks and buildings |
| Received but not logged | POD signed by a receiver employee | Ask receiver to check its receiving log and stock |
| Signed by someone without authority | Unknown name on POD | Ask receiver who signed; ask carrier for details |
| Partial delivery | POD shows fewer pieces | Ask carrier where the rest is |
| Real loss or theft | No valid POD; carrier cannot locate | Escalate to a person for a claim |
Does this differ for LTL and truckload?
It differs in where the freight can end up. An LTL shipment passes through terminals and may be delivered with other shipments on the same truck, so it can be left at the wrong stop, mixed with another shipper's freight or held at a terminal while marked delivered. A truckload goes directly from pickup to the receiver, so the usual causes are a wrong address, a wrong dock or a status set early. The questions to the carrier differ slightly: for LTL, ask about the terminal and the delivery manifest; for truckload, ask about the driver's stop and arrival time.
Why is "delivered" not enough?
"Delivered" is not enough because it is a status set by the carrier, sometimes by a driver tapping a button, sometimes by a terminal system. It can be set early, set on the wrong load or set after a delivery to the wrong place. The evidence that a delivery happened is the signed POD with a time, a location and a name, and ideally the receiver's own record. Wilson treats "delivered" as confirmed only with that evidence.
Why does speed matter?
Speed matters because evidence fades and options narrow. A receiver can check its docks and staging areas easily on the day after delivery; a week later, the freight may have been put away under the wrong PO or moved to another site. A carrier can recover freight delivered to the wrong address quickly while the driver remembers the stop. Claims also have time limits set by the carrier's terms. Starting the investigation the moment the customer reports the problem gives the best chance of a quick answer.
Who usually gets the call?
Customer service usually gets the call first, then asks logistics, who emails the carrier, who asks the driver or the terminal. Each handoff adds hours. When the agent receives the report and asks the carrier and the receiver at the same time, the loop shortens to the time it takes the two sides to check their records.
How common are these disputes?
These disputes are common enough that every logistics team has a process for them, even if it is informal. They are more common with LTL, multi-stop truckloads, large receiving sites with several docks, and deliveries to residential or small business addresses. Most are resolved within a day or two once both sides check their records.
What should the software do first?
The software should first stop treating the load as delivered and open an exception with an owner and a deadline. An AI logistics agent like Wilson does this as soon as the customer's report arrives. Then it gathers evidence from both sides at the same time, because waiting for one before asking the other wastes a day.
What should be asked of the carrier?
The carrier should be asked for the signed POD, the delivery date and time, the exact address and dock, the name of the person who signed, the piece count delivered, and any photos or notes. For LTL, the delivery terminal and the driver's delivery record. If the carrier cannot produce a signed POD, that is important information on its own. For more on getting PODs, see how to get proof of delivery when the carrier never sends it.
How fast should the carrier answer?
The carrier should answer within hours, not days, because it has the delivery record. Most carriers can pull a POD and the driver's delivery notes quickly. If the carrier does not answer by the deadline the rules set, the agent follows up by phone where configured and tells the team. A carrier that cannot produce a POD within a day is a signal that the delivery may not have happened as reported.
What should be asked of the receiver?
The receiver should be asked to check its receiving log for the delivery date, other docks and buildings on the site, its stock for the items, and whether the name on the POD belongs to an employee. Many cases end here: the freight was received at another dock and not yet logged, or put away under a different PO. Wilson emails the receiving contact on the ship-to record and records the answer.
What about parcel shipments?
Parcel shipments have the same problem with a different shape. A parcel carrier may show "delivered" with a GPS location or a photo instead of a signature. The agent should ask for the delivery photo or location, compare it with the address, and ask the recipient to check with neighbors, mailrooms or front desks. Parcel carriers have their own process for tracing and claims, which the team follows.
Should the agent call anyone?
Yes, when email is too slow. If the carrier has not answered within a couple of hours, Wilson can call the carrier's dispatch where calls are configured. It contacts drivers directly by phone or text when the carrier shares the driver's details; a driver often remembers a delivery the same day and can say exactly where the freight was left. Each call is recorded on the load.
What should be checked internally?
Internally, the software should check the order's ship-to address, the address on the BOL and the address in the tender. A wrong address in the order or the BOL is a common cause. It should also check whether the order shipped in more than one load, because the customer may be asking about a different shipment. Wilson keeps the order, the BOL and the tender on the same load record.
| Check | Where | What it can show |
|---|---|---|
| Ship-to on the order | ERP order | Whether the address was right at the source |
| Address on the BOL | BOL | Whether the address changed at pickup |
| Address in the tender | Tender and rate confirmation | What the carrier was told |
| Other loads on the same order | Load records | Whether the customer means another shipment |
| Pieces shipped | BOL | What should have arrived |
How should the evidence be compared?
The evidence should be compared point by point: address, time, signature and piece count. An AI logistics agent lines up the carrier's POD, the receiver's records and the order. Where they agree, the case moves quickly. Where they disagree, the difference shows where to look.
What if the time on the POD does not match the receiver's hours?
If the POD shows a delivery at a time the receiver was closed, something is wrong. The driver may have left the freight outside, delivered to a neighbor, or entered the time incorrectly. The agent should point out the mismatch to both sides and ask the carrier for the driver's account and any photos. This detail often unlocks the case quickly.
What if the POD shows a different address?
If the POD shows a different address, the freight was likely delivered to the wrong place. The carrier should be asked to recover it and redeliver to the correct address, at the carrier's cost if the tender and BOL had the right address. If the order or BOL had the wrong address, the shipper may bear the cost of redelivery.
What if the POD is signed at the right site by an unknown name?
If the POD is signed at the right site by an unknown name, the receiver should check whether that person works there, perhaps at another dock or on another shift. Often the freight is on site but not where the customer looked. If nobody at the site knows the name, the carrier should be asked for the driver's account and any photos.
What about GPS or photo evidence?
GPS data or delivery photos can help when the carrier has them. A GPS record showing the truck stopped at the right address at the right time supports the carrier's claim. A photo of the freight at a dock door can show where it was left. The agent asks for these when the signed POD is missing or unclear and records what it receives with its source.
What if there is no signed POD?
If there is no signed POD, the carrier has not shown that the delivery happened. The carrier should be asked to locate the freight. If it cannot, the load may be lost, and the case goes to a person to decide on a claim and a reshipment. The carrier's invoice stays on hold.
What if the receiver signed with an exception?
If the receiver signed the POD with an exception, such as "2 pallets short" or "damaged", the delivery happened but not as shipped. The case becomes a shortage or damage case, not a missing delivery. The agent records the exception, tells the team and the customer, and the claims process takes over. The invoice decision follows the company's policy for shortage and damage.
What if the piece count is short?
If the piece count is short, the delivery was partial. The POD may note the shortage, or it may not. The carrier should be asked where the missing pieces are; they may be at a terminal or on another truck. The customer should be told what arrived and what is being traced.
What should happen with the invoice and any claim?
The invoice should be held while the case is open, and any claim should follow the company's claims process with the evidence attached. An AI logistics agent like Wilson audits each carrier invoice against what was booked, the rate confirmation and the POD before paying from the Wilson Wallet. Customers can require a signed POD before payment releases.
What if the carrier insists on payment?
If the carrier insists on payment while the case is open, the agent shares what is known and what is missing, such as the signed POD, and explains that payment follows confirmation of delivery. Most carriers understand this when the request is clear and the case moves quickly. If the carrier produces the POD and the receiver confirms the freight, the invoice moves to audit and payment right away.
Why hold the invoice?
Holding the invoice keeps the payment tied to the outcome. If the freight was delivered correctly, the invoice is paid once that is confirmed. If it was delivered to the wrong place and the carrier must redeliver, the invoice is paid once the correct delivery is confirmed. If the freight was lost, the company's policy decides whether the freight charge is paid and how the claim is handled. Wilson does not pay part of an invoice; the whole invoice waits for a person when something does not match.
What happens if the freight turns up later?
If the freight turns up after a claim or a reshipment has started, the record should be updated and the claim withdrawn or adjusted. The customer may now have two shipments, and the team decides whether to return one, keep it as stock or credit the customer. The agent records the outcome so the invoice and the claim are closed correctly.
Who decides on a claim?
A person decides on a claim, following the company's process and the carrier's terms. The agent gathers the evidence: the BOL, the signed or missing POD, the receiver's statement, the carrier's account, the value of the goods and the timeline. Claims involve deadlines and documentation that depend on the carrier and the mode, so the team should know its own process.
What evidence should a claim include?
A claim usually needs the BOL showing what was shipped, the POD or the absence of one, the receiver's statement, the carrier's account, the commercial invoice or value of the goods, photos if there was damage, and the timeline of messages. The agent can collect these from the load record into one package for the person filing the claim. The exact requirements and deadlines depend on the carrier, the mode and the agreement.
Who decides on a reshipment?
A person decides whether to ship replacement goods before the case is resolved, usually customer service or sales with logistics. If the customer needs the goods urgently, waiting for a claim may not be an option. The agent can prepare the replacement load once the decision is made.
How should the customer be kept informed?
The customer should be kept informed with facts and a time for the next update, from one source. An AI logistics agent sends updates as the case moves, so the customer is not left wondering and customer service is not guessing.
What should the first message say?
The first message should say that the company is checking with the carrier and the receiver, what it has asked for, and when the customer will hear next. A hypothetical message: "We're checking PO 2291 with the carrier. Their system shows delivery yesterday at 2:40 p.m. We've asked for the signed proof of delivery and asked your receiving team to check other docks. We'll update you by noon."
What should later messages say?
Later messages should say what was found and what happens next: "The proof of delivery shows the pallets were signed for at Dock 7 by J. Smith. Your receiving team found them in the Dock 7 staging area." Or: "The carrier delivered to the wrong building and will redeliver tomorrow morning."
What should the customer not be told?
The customer should not be told a guess as a fact. "It was delivered, check your dock" can damage the relationship if the freight was actually delivered elsewhere. Until the evidence is in, the message should say what is being checked and when the next update comes. Once the cause is found, the message can be specific.
Should sales or customer service be included?
For key customers, the account manager or customer service contact should see the same updates. When the customer calls, they can give the current facts from the record rather than asking logistics.
| Stage | Message to customer |
|---|---|
| Report received | We're checking; next update by a set time |
| Evidence gathered | What the POD and records show |
| Cause found | What happened and the fix |
| Resolved | Freight located or redelivered; case closed |
| Claim needed | Replacement plan and claim status |
How does Wilson, by Cartage, handle "delivered but not received"?
Wilson, by Cartage, is an AI logistics agent that treats a disputed delivery as an open exception. It asks the carrier for the signed POD and delivery details, asks the receiver to check its records, checks the order and BOL addresses, compares the evidence, keeps the customer informed and holds the carrier's invoice until the case is resolved. Claims and reshipment decisions go to a person with the evidence attached. For how Wilson checks invoices, see how to check a freight invoice against the agreed carrier quote.
Wilson replaces the TMS for freight execution and connects to the company's ERP. It handles LTL, FTL, ocean, drayage, parcel and cross-border freight.
What does a case look like with Wilson?
A hypothetical case: at 9 a.m., a customer emails that PO 2291 never arrived, though the carrier's site shows delivered yesterday. Wilson marks the load as an open exception, asks the carrier for the signed POD and the delivery details, and asks the customer's receiving contact to check the log and other docks. At 10:30, the carrier sends a POD signed at 2:40 p.m. by "R. Lopez" at the right street address, Dock 7. Wilson forwards it to the receiver, who finds the pallets in the Dock 7 staging area; the regular receiving team works at Dock 2. Wilson updates the customer, closes the exception, releases the invoice for audit and adds a note to the ship-to record that deliveries should go to Dock 2.
How does the agent close the case?
The agent closes the case when the cause is found and the outcome is recorded: freight located, redelivered, or a claim and reshipment decided by a person. It updates the load status, releases or settles the invoice, tells the customer and the team, and adds any lesson to the ship-to record. The case history stays on the load.
What stays with the team?
The team decides on claims, reshipments and how to handle the customer relationship. Wilson gathers the facts, keeps everyone informed and applies the decisions.
How do teams start?
Most teams start Wilson on a few lanes and expand from there. Cartage helps map the highest-impact workflow during discovery, often the lanes with multi-building receivers or frequent POD gaps.
How is Wilson priced?
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.
How can these disputes be prevented?
These disputes can be prevented in part by getting the delivery details right before pickup and confirming the delivery at the time it happens. An AI logistics agent does both as part of normal work.
What helps with the ship-to record?
Keeping the ship-to record accurate helps more than anything else. The record should include the full address, the building and dock for multi-building sites, the receiving hours, the receiving contact and any special instructions. After each dispute, the agent can add what was learned, such as "deliver to Dock 2, not Dock 7". The next tender then carries the correct instructions.
What helps before pickup?
Before pickup, the order, the BOL and the tender should carry the full delivery address, the building or dock if the site has several, the receiving hours and the contact. Wilson checks that these details are on the tender and the BOL, and asks the order owner for anything missing.
What helps at delivery?
At delivery, asking the receiver to confirm check-in and departure, where configured, gives an independent record. Wilson asks the warehouse or receiver for check-in and departure times where configured and records each arrival claim with its source. Requesting the signed POD right after delivery, rather than weeks later, means problems surface while they are easy to fix. For related cases, see shipment tracking software says delivered, but where is the signed POD.
What helps over time?
Over time, a record of these disputes by carrier, lane and receiver shows patterns: a receiver with several docks that needs clearer instructions, or a carrier whose drivers mark deliveries early. The team can fix the instructions or talk to the carrier.
FAQs
What should freight software do when the carrier says "delivered" but the customer says it never arrived?
Treat it as an open exception: ask the carrier for the signed POD and details, ask the receiver to check its records, compare them with the order and BOL, keep the customer updated and hold the invoice. An AI logistics agent like Wilson, by Cartage, runs this sequence and sends claims to a person.
Is the carrier's "delivered" status proof of delivery?
No. An AI logistics agent treats it as a claim until a signed POD with time, place and name, or the receiver's own record, confirms it.
Should the carrier be paid while the case is open?
No. An AI logistics agent holds the whole invoice until the delivery is confirmed or a person decides how to handle a loss.
What usually explains these cases?
Most are a wrong address, a delivery to another dock or building, freight received but not logged, or a status entered too early. An AI logistics agent checks each possibility with the carrier and the receiver.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai
If "it says delivered" still starts a day of phone calls, book a demo to see how Wilson, the AI logistics agent by Cartage, works the case from evidence to resolution.