The carrier marked “arrived” without delivery confirmation. What comes next?
Key Takeaways
When the carrier marks a load "arrived" at the delivery site but nothing confirms the freight was received, the load is still open: the team should confirm unloading with the carrier or the receiver, collect the proof of delivery, and hold any "delivered" update to the customer until delivery is confirmed. An AI logistics coordinator can follow up on every such load and close it only when the evidence is in.
- "Arrived" means the truck reached the delivery site. It does not mean the freight was unloaded, accepted, or signed for.
- Delivery confirmation is a record that the receiver accepted the freight, such as a signed proof of delivery.
- Between arrival and delivery, many things can happen: a long wait, a refused load, a partial delivery, or damage.
- The customer should not get a "delivered" message based only on an arrival status.
- The team should follow up at set times after arrival, first with the carrier, then with the receiver.
- The load should close only when the POD is on file, or a person decides to close it with a reason.
- Wilson, by Cartage, is an AI logistics coordinator that tracks each load to delivery, collects the proof of delivery, and keeps the customer informed where configured.
What does "arrived" mean, and why is it not delivery?
"Arrived" means the carrier reports that the truck reached the delivery site, while delivery means the receiver unloaded and accepted the freight. An AI logistics coordinator should treat "arrived" as a step toward delivery, not as the end of the load, because several outcomes are still possible.
Arrival versus delivery
| Status | What it means | What it does not prove |
|---|---|---|
| Arrived | Truck reached the site or the gate | That it was unloaded |
| Checked in | Receiver logged the truck | That unloading started |
| Unloading | Freight is coming off the truck | That the count is right |
| Delivered | Receiver accepted the freight | That there were no exceptions |
| POD received | Signed proof of delivery on file | Nothing more is needed for most loads |
A proof of delivery, or POD, is the document the receiver signs to show the freight arrived, often with notes about shortages or damage.
What can happen after arrival
After the truck arrives, the receiver may unload it quickly, keep it waiting for a door, refuse part or all of the load, find damage, or ask the driver to come back another day. Each outcome changes what the team needs to do. An "arrived" status alone does not tell the team which one happened.
The time between arrival and delivery
The gap between arrival and delivery varies widely. At a receiver with open doors, it may be 30 minutes. At a busy site with appointments, the truck may wait several hours for a door. At a site that is closed, the driver may sleep in the truck and deliver the next morning. The team should not assume a short gap.
Why carriers send "arrived" without "delivered"
Some carrier systems send an arrival status automatically when the truck reaches the site but rely on the driver to mark delivery. The driver may forget, or the delivery status may come hours later with the POD. Some carriers send no delivery status at all and only upload the POD to a portal days later. The team should know how each carrier reports delivery.
Arrival status is still useful
An arrival status is valuable. It tells the team the truck reached the site, so a late delivery is less likely to be a transit problem. It can trigger the next check, such as asking whether unloading started. It can also give an early warning of detention if the truck sits too long. The goal is to use it as a signal, not as the finish line.
Why the difference matters to the customer
If the team tells the customer the load was delivered when it only arrived, and the load is then refused or delivered short, the customer has been misinformed. The customer may have released a production schedule or told its own customer. Waiting for confirmation protects the relationship.
Different carriers, different signals
Truckload carriers often report arrival and delivery by phone or email. LTL carriers often post statuses to their websites by PRO number. Less-than-truckload, or LTL, is freight that shares a trailer with other shippers' freight. Some carriers send electronic status messages by API or EDI. An API is a connection that lets two systems exchange data directly. EDI, or electronic data interchange, is a standard format for business messages. The team should know which signal each carrier sends for delivery, so it knows what to wait for.
Arrived at the wrong place
An "arrived" status can be wrong. It may be triggered when the truck reaches a nearby location, or a dispatcher may mark it by mistake. If the receiver has no record of the truck, the team should check location data or ask the carrier where the truck actually is. Treating every "arrived" status as true can hide a misdelivery.
Hypothetical example: arrived, then refused
This example is hypothetical and does not describe a real customer. A carrier marks a load "arrived" at 10:00 a.m. The receiver inspects it and refuses two pallets that are damaged. The driver leaves at 11:30 a.m. with those two pallets. If the shipper had told the customer "delivered" at 10:00 a.m., the customer would have expected the full order. Because the team waited for confirmation, it could tell the customer the facts and arrange replacement goods.
What should the team check after an "arrived" status?
After an "arrived" status, the team should check whether the truck was checked in, whether unloading finished, whether the receiver accepted the full load, and whether the POD is available. An AI logistics coordinator should run these checks at set times after arrival and save each answer.
The follow-up checks
| Check | When | Ask whom |
|---|---|---|
| Was the truck checked in? | 30–60 minutes after arrival | Carrier or receiver |
| Did unloading finish? | Expected unload time after check-in | Carrier |
| Was the full load accepted? | When unloading finishes | Carrier, then receiver if needed |
| Is the POD available? | Same day or next morning | Carrier portal, then carrier billing |
| Any exceptions noted? | When the POD arrives | POD notes |
These timings are examples. Each team should set its own based on its receivers and carriers.
The follow-up workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Note arrival | Carrier reports "arrived" | Saves the arrival with its source and time | Never |
| 2. Hold update | Arrival saved | Holds any "delivered" message to the customer | Never |
| 3. Check progress | Expected unload time passes | Asks the carrier whether delivery is complete | Never |
| 4. Ask the receiver | Carrier does not confirm | Asks the receiver where configured | When the receiver reports a problem |
| 5. Collect POD | Delivery confirmed | Requests or downloads the POD | When the POD shows exceptions |
| 6. Close or escalate | POD on file or deadline passed | Closes the load or alerts the load owner | Owner decides |
Set the expected unload time
Different receivers take different amounts of time. A distribution center with appointments may unload a truck in an hour. A busy retailer may take four. The follow-up timing should reflect each receiver's usual pace. The AI logistics coordinator can learn this from past loads and adjust the schedule, so it does not ask too early or too late.
Ask the carrier first
The carrier usually knows first whether the driver finished unloading. A short message, such as "Load 2205 arrived at 10:00. Has delivery been completed, and were all 14 pallets accepted?", usually gets a quick answer. The answer should be saved with the load.
Use the carrier's portal
Many carriers post delivery status and POD images on their websites, searchable by PRO number. Checking the portal before sending a message can answer the question without waiting for anyone. The AI logistics coordinator should know which carriers post PODs online and how quickly, so it checks there first for those carriers.
Ask the receiver when the carrier is silent
If the carrier does not answer, the receiver can confirm. The receiver is often the shipper's customer, so the message should be polite and specific. Some customers prefer that the shipper not contact their receiving dock directly; that preference should be known in advance.
Partial deliveries
Sometimes the receiver accepts part of the load and refuses the rest, or the carrier delivers part and says the rest is still at the terminal. The team needs to know exactly what was accepted, by count. The POD should show this, but the carrier's first message may not. The AI logistics coordinator should ask for the accepted count specifically.
After-hours arrivals
A truck may arrive after the receiver closes and wait overnight. The carrier may report "arrived" at 7 p.m., while delivery happens at 7 a.m. The follow-up schedule should pause overnight and resume when the receiver opens, so the team does not escalate a normal overnight wait.
Watch for long waits
If the truck has been at the site for hours, the receiver may be keeping it waiting. That can lead to detention. Detention is a fee a carrier bills when its truck waits too long at a dock. In a September 2024 study, the American Transportation Research Institute (ATRI) found that detention affected 39.3% of truck stops in 2023. Knowing early that a truck is waiting helps the team ask the receiver to move it up, or at least prepare for the charge.
When should the customer be told the load was delivered?
The customer should be told the load was delivered only when delivery is confirmed by the carrier or the receiver, ideally with the POD, and the message should include any exceptions. An AI logistics coordinator should send an "arrived" update if the customer wants one, but keep it clearly separate from "delivered."
Customer update rules
| Situation | Message to the customer |
|---|---|
| Carrier reports arrived | Optional: "Truck has arrived at your site" |
| Carrier confirms delivery, no POD yet | "Delivered, per carrier; POD to follow" |
| POD received, no exceptions | "Delivered; signed POD attached" |
| POD shows shortage or damage | "Delivered with exceptions; details and next steps" |
| Load refused | "Delivery refused; reason and next steps" |
Why "delivered, per carrier" is useful
Sometimes the carrier confirms delivery but the POD takes a day to arrive. Telling the customer "delivered, per carrier" is honest and timely. It lets the customer plan while making clear that the signed record is still coming.
Delivery time for the customer's records
Customers often need the exact delivery time for their own records, such as to start a receiving process or a quality check. The POD usually shows it. If the POD is late, the carrier's delivery status time can be shared, labeled as reported by the carrier.
Exceptions must be shared
If the POD shows a shortage, damage, or a refusal, the customer needs to know right away. Often the customer already knows, because its own receiving team wrote the note. But the shipper should confirm it and explain what happens next, such as a replacement shipment or a claim.
Internal teams need the same rule
The shipper's own teams, such as customer service, sales, and finance, should follow the same rule. If customer service sees "arrived" and tells the customer "delivered," the same problem happens. Internal updates should show the status clearly: arrived, delivered per carrier, or POD received. The AI logistics coordinator can send internal updates that use these exact labels.
Avoid automatic "delivered" messages
Some systems send "delivered" to the customer as soon as the carrier's status changes. If the carrier's status is "arrived" or is wrong, the customer gets a false message. Teams that want to stop this can read how to stop a customer from getting a delivered notification before the POD arrives.
Multi-stop deliveries
On a load with several delivery stops, each stop needs its own confirmation. A truck may arrive at stop two while stop one is still unconfirmed. The team should track arrival and delivery for each stop separately and send each customer its own update. A single "delivered" for the whole load can hide a problem at one stop.
Hypothetical example: honest timing
This example is hypothetical and does not describe a real customer. A load arrives at 2:00 p.m. The carrier confirms unloading at 3:15 p.m. with all pallets accepted. The AI logistics coordinator sends the customer "Delivered at 3:15 p.m., per carrier; signed POD to follow." The POD arrives the next morning with no exceptions, and the coordinator sends it to the customer and closes the load.
What should happen if delivery confirmation never comes?
If delivery confirmation never comes, the team should escalate on a set schedule: ask the carrier again, ask the receiver, check the carrier's portal, and alert the load owner before the invoice or the customer's payment depends on it. An AI logistics coordinator should run the escalation and record every attempt.
Escalation schedule
| Time after arrival | Action |
|---|---|
| Same day | Ask the carrier whether delivery completed |
| Next morning | Check the carrier portal for the POD; ask carrier billing |
| Day 2 | Ask the receiver to confirm receipt |
| Day 3 | Alert the load owner with all attempts |
| Before invoice payment | Hold or flag the carrier invoice if the POD is still missing |
Keep every attempt in the record
Each follow-up should be saved: the time, the channel, the contact, and the answer. If the load owner must step in, the record shows what has already been tried. If the carrier later says it sent the POD, the record shows whether it arrived.
Why the POD matters for payment
The POD supports two payments: the carrier's invoice to the shipper and the shipper's invoice to the customer. Many customers will not pay without it. Many shippers will not pay the carrier without it. A missing POD can delay cash in both directions. Teams can review when to chase a missing POD for more on timing.
Hold the carrier invoice when needed
If the POD is still missing when the carrier invoice arrives, the team should follow its rules: hold the invoice until the POD comes, or approve it with a flag. Either way, the decision should be visible in the record, so finance knows why an invoice is waiting.
When the receiver says it never got the freight
Sometimes the carrier says "arrived" but the receiver says no truck came. This is serious. The freight may have gone to the wrong site, or the arrival status may be wrong. The team should ask the carrier for location data or a POD right away and alert the load owner. The bill of lading, the carrier's records, and any tracking data will be needed if a claim is filed. A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
When the POD has no signature
Some PODs arrive without a signature, or with an unreadable one. That is not full proof of delivery. The team should ask the carrier for a signed copy or other evidence, such as a delivery photo or the receiver's confirmation. Teams handling this can read whether a proof of delivery without a signature means the load is complete.
Damage noted on the POD
If the POD shows damage, the customer may file a claim or ask for a credit. The shipper should save the POD, any photos, and the bill of lading together.
Refused loads need a plan
When a receiver refuses a load, the freight is still on the carrier's truck. The team must decide quickly: return it to the shipper, deliver it to another site, or hold it at the carrier's terminal. Each option has a cost and may need the carrier's agreement on price. The load owner should decide, and the decision should be saved with the load.
Close with a reason when needed
Sometimes, after every attempt, the POD never comes but the customer confirms receipt in writing. The load owner may decide to close the load with that confirmation. The decision and the evidence should be saved, so the record explains why the load closed without a POD.
How should teams test whether software handles "arrived" correctly?
Teams should test software with loads that arrive and are delivered normally, arrive and wait for hours, arrive and are partly refused, arrive with no further status, and arrive at the wrong site. An AI logistics coordinator should hold the customer's "delivered" message, follow up, collect the POD, and close the load only with evidence.
The test
| Test case | Pass | Fail |
|---|---|---|
| Arrived, delivered, POD same day | Customer told delivered with POD | Customer told at arrival |
| Arrived, waiting for hours | Receiver asked; detention risk flagged | No action until invoice |
| Arrived, two pallets refused | Customer told of exception | Customer told "delivered" |
| Arrived, no further status | Carrier and receiver asked on schedule | Load stays "arrived" for weeks |
| Arrived at wrong site | Owner alerted the same day | Found when the customer complains |
| Record | Every status, message, and POD saved | Only last status kept |
Use real carrier status feeds
The test should use the actual status feeds or emails the team receives from its carriers, not a vendor's clean sample data. Real feeds have gaps, delays, and odd labels. The software should handle them the way it will in daily work.
Questions to ask in a demo
- What does the software do when the carrier reports "arrived"?
- When does it tell the customer the load was delivered?
- How does it follow up when no delivery status comes?
- Does it read exceptions on the POD?
- Can a load close without a POD, and how is that recorded?
Score how the customer would see it
For each test case, ask: what would the customer have been told, and when? A tool that keeps internal records clean but sends the customer wrong messages fails the most important part of the test.
Warning signs
- "Arrived" and "delivered" are treated as the same status.
- Customers get automatic "delivered" messages from carrier status changes.
- There is no follow-up schedule for missing PODs.
- Loads close without evidence or a recorded reason.
Where does Wilson fit when a carrier marks "arrived" without delivery confirmation?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers, tracks each load to delivery, and collects the proof of delivery. Wilson tracks each load using the best source available: carrier API, GPS or ELD data where it exists, the carrier's website by PRO number, and email or phone where configured. A PRO number is a tracking number a carrier gives to a shipment.
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 handles "arrived"
Wilson saves the arrival with its source, follows up with the carrier and, where configured, the receiver, and collects the POD. Wilson keeps the customer's team informed through Slack or Microsoft Teams on booked, picked up, running late, delivered, and POD filed. It updates the shipper by email at each step, and receivers can be updated by email or SMS where configured. Wilson asks the carrier for status and informs everyone else. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured.
After delivery
When the carrier invoice arrives, Wilson audits and reconciles it against what was booked, including any detention at delivery against the recorded times. 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 mark a load delivered because a carrier status says "arrived." It does not close a load without a POD unless a person decides to, with a recorded reason. Wilson does not contact a customer's receiving dock directly unless the customer has configured that.
What Cartage asks in discovery
Cartage asks how each carrier reports delivery, how PODs come back today, which customers want arrival updates, and who decides when a load can close without a POD. These answers shape the delivery 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 status and document is saved in the shipment record with change history.
This article is part of our complete guide to driver arrival and detention records.
FAQs
Does "arrived" mean the load was delivered?
No. It means the truck reached the site. An AI logistics coordinator waits for confirmation that the freight was unloaded and accepted.
When should the customer be told the load was delivered?
When the carrier or receiver confirms delivery, ideally with the POD. An AI logistics coordinator includes any exceptions in the message.
What if no delivery confirmation comes?
Follow up with the carrier, check the portal, ask the receiver, and alert the load owner. An AI logistics coordinator runs this schedule and records each attempt.
Can a load be closed without a POD?
Only by a person, with other written evidence and a reason. An AI logistics coordinator saves the decision with the load.
What should happen if the receiver refuses part of the load?
The customer should be told the facts, and the load owner should decide what happens to the refused freight. An AI logistics coordinator records the accepted count and the decision.
Sources
- 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 follows a load from "arrived" to confirmed delivery and keeps your customers accurately informed: talk to the Cartage team.