The carrier says the truck arrived. The warehouse has no check-in
Key Takeaways
When the carrier says the truck arrived but the warehouse has no check-in, the team should treat it as an open question that needs an answer within minutes: confirm where the truck is, check every gate and building, and find out whether the driver tried to check in. An AI logistics coordinator can contact the carrier and the site at the same time, gather location data, and bring the load owner a clear answer.
- A carrier arrival claim without a matching check-in usually has a simple cause: wrong gate, wrong building, a line, or a missed log entry.
- Sometimes the cause is serious: the truck is at the wrong site, or the arrival status is wrong.
- The first goal is to find the truck, not to decide who is at fault.
- Location data, the driver's description of the site, and the warehouse's gate staff together usually answer the question fast.
- If the truck is at the wrong place, the driver needs the right address and dock instructions right away.
- Every fact should be saved, because the same question may come back on the invoice.
- Wilson, by Cartage, is an AI logistics coordinator that tracks each load using the best source available, contacts the carrier and site when records disagree, and saves the answer with the shipment.
What does it mean when the carrier says arrived but the warehouse has no check-in?
It means one of two records is incomplete or wrong: either the truck is somewhere the warehouse is not looking, or the carrier's arrival status does not match reality. An AI logistics coordinator should treat it as a gap to close quickly, because a truck that cannot find its dock is losing time every minute.
The likely causes
| Cause | How common | What it looks like |
|---|---|---|
| Driver at the wrong gate or building | Common | Truck on site, but at another entrance |
| Driver waiting in a line or lot outside | Common | Truck nearby; not yet at the gate |
| Warehouse did not log the check-in | Common | Driver checked in; no record entered |
| Driver at the wrong site | Less common | Truck at an old address or sister plant |
| Arrival status set too early | Less common | Status set by dispatch or a wide geofence |
| Arrival status wrong | Rare | Truck still on the road |
A geofence is a virtual boundary around a location that triggers an event when a vehicle enters or leaves it. A wide geofence may mark a truck "arrived" when it is still a mile away.
Why the first minutes matter
A truck at the wrong gate can usually reach the right one in 10 minutes if someone tells the driver. A truck that waits an hour before anyone notices may lose its appointment, run into detention, or leave. 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.
Both records may be honest
The driver may truly be at the site, and the warehouse may truly have no record. That happens when the driver is at a different entrance, or when the guard has not yet entered the truck in the log. Treating the gap as a lie on either side slows the fix. The goal is to find the truck.
Who should act
The load owner, or an AI logistics coordinator acting for the team, should take the lead. The carrier's dispatch can reach the driver. The warehouse can check its gates and lot. Someone has to connect them, and that person should not wait for one side to call the other.
Set the waiting time before acting
The team should decide how long to wait after an arrival claim before treating a missing check-in as a problem. At a small site, 10 minutes may be enough. At a large site with a long gate process, 30 minutes may be normal. The AI logistics coordinator should use a time that fits each site, so it acts fast without raising false alarms.
Delivery sites have the same problem
The same gap can happen at delivery: the carrier says arrived, and the receiver has no record. The receiver is often a customer, so the shipper should ask politely and quickly. Customers usually want the truck found as much as the shipper does.
Hypothetical example: the back gate
This example is hypothetical and does not describe a real customer. A carrier's system shows "arrived" at 9:02 a.m. for a 9:00 a.m. pickup. At 9:20 a.m., the warehouse has no check-in. The AI logistics coordinator asks the carrier where the driver is. The driver is at the main office entrance on the north side. The shipping gate is on the east side. The coordinator sends the gate directions through dispatch, and the truck checks in at 9:31 a.m.
What should be checked first?
The first checks are where the truck is, which entrance the driver is at, and whether the warehouse has any record of the truck at another gate or lot. An AI logistics coordinator should send these questions to the carrier and the site at the same time, so the answer comes from whichever side responds first.
First checks
| Check | Ask whom | What the answer settles |
|---|---|---|
| Truck location | Carrier (location data or driver) | On site, nearby, or elsewhere |
| Which entrance or building | Driver through dispatch | Wrong gate or building |
| Any record at other gates or lots | Warehouse or security | Driver checked in elsewhere |
| Was there a line at the gate? | Warehouse | Driver waiting outside |
| Does the driver have the pickup number? | Driver through dispatch | Check-in blocked by paperwork |
Ask in one message, not five
The message to the carrier should ask everything at once: "Load 6612: your system shows arrived at 9:02. Our shipping gate has no check-in. Where is the driver now, which entrance, and does the driver have pickup number 44812?" One clear message gets a faster answer than a string of short questions.
Location data first
If the carrier shares location data, it is the fastest check. Location can come from the carrier's API, from GPS or ELD data where shared, or from the driver's phone. An API is a connection that lets two systems exchange data directly. An ELD, or electronic logging device, records a truck's driving time and can share location. Federal rules require ELDs to record location when a driver's duty status changes and at least once an hour while the vehicle is moving. That can show whether the truck stopped near the site.
Ask the driver to describe the site
If location data is not available, the driver can describe what they see: the building name, the sign at the gate, the street. That is often enough for the warehouse to say, "That is our north office; go to the east gate." A clear description beats a long exchange of addresses.
Paperwork can block check-in
Sometimes the driver is at the right gate but cannot check in because the pickup number is missing or the guard cannot find the load. The driver may then wait in the lot while the carrier calls dispatch. The warehouse may not log anything until the paperwork is sorted out. Asking the driver whether they have the pickup number is a quick check that can save an hour.
Check the warehouse's other entrances
Large sites have several gates, a truck lot, and sometimes more than one shipping office. The warehouse should check all of them. A driver may have checked in at a receiving gate instead of the shipping gate, and the record sits in the wrong log.
The check workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Detect | Arrival claim with no check-in after a set time | Flags the stop | Never |
| 2. Ask both sides | Gap flagged | Asks the carrier for location and the site for any record | Never |
| 3. Locate | Answers received | Identifies where the truck is | When answers conflict |
| 4. Redirect | Truck at wrong gate or site | Sends correct directions through the carrier | When extra miles or delays need approval |
| 5. Confirm | Truck checks in | Records check-in and the cause of the gap | Never |
| 6. Escalate | No answer within a set time | Alerts the load owner with all facts | Owner decides next steps |
What should happen if the truck is at the wrong place?
If the truck is at the wrong gate, building, or site, the team should send the correct address and dock instructions to the driver through the carrier right away, tell the warehouse to expect the truck, and check whether the delay affects the appointment or the price. An AI logistics coordinator can do these steps in minutes and record the cause.
Wrong gate or building
This is the most common case and the easiest to fix. The driver needs the right entrance, the dock number, and any check-in steps. The warehouse should be told the truck is coming around. Most of these delays are short if caught early.
Wrong building on a shared campus
Some companies share a campus with other businesses, or have several buildings with similar names. A driver may check in at a neighbor's building, which has no record of the load. The fix is the same: clear directions and a building name or number in every tender.
Wrong site
If the truck went to a different site, such as an old warehouse or a sister plant, the fix takes longer. The team should find out why: was the wrong address on the bill of lading or the tender, or did the carrier enter it wrong? A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it. A tender is the offer of a load to a carrier. The cause decides who pays for any extra miles or waiting.
Tell the warehouse who is coming
When the driver is redirected, the warehouse should know the carrier name, the trailer number if available, and the expected arrival time at the right gate. That way, the guard can check the truck in quickly and the dock can have a door ready.
Appointments and timing
If the delay makes the truck miss its appointment, the warehouse may fit it in later or move it to the next day. The load owner should know right away, because the delivery promise may be at risk. If the delivery will be late, the customer should hear about it before the delivery window passes.
Charges
If the wrong place came from the shipper's paperwork, extra miles and waiting are usually the shipper's cost. If it came from the carrier, they are usually the carrier's. Any charge should be discussed and confirmed in writing before the invoice, not after. The rate confirmation, which is the document that states the agreed price and terms for one load, decides the amounts.
Do not let the driver leave
If the truck is at the wrong place, the driver may decide to give up and move on to the next load, especially if hours are running short. Federal hours-of-service rules limit how long a driver can be on duty. The team should make it easy for the driver to reach the right dock quickly, and tell the carrier the warehouse is ready, so the pickup is not lost.
Hypothetical example: an old address
This example is hypothetical and does not describe a real customer. A driver arrives at a company's former warehouse, eight miles from the current one. The carrier's system shows "arrived." The current warehouse has no check-in. The AI logistics coordinator asks the carrier for the driver's location and sees the old address. It checks the tender, which had the correct address, and finds that the carrier's dispatch used an old address from its own records. The coordinator sends the correct address, the truck arrives 25 minutes later, and the cause is saved as a carrier data error.
What should happen if the arrival status is wrong?
If the arrival status is wrong because the truck is still on the road or was marked arrived too early, the team should correct the record, get a real arrival estimate, and check whether the appointment still works. An AI logistics coordinator should note the source of the false status, so it is not trusted the same way next time.
How false arrival statuses happen
| Source | How it goes wrong |
|---|---|
| Wide geofence | Truck marked arrived when it enters a large zone around the site |
| Dispatch entry | Dispatcher marks arrived based on the plan, not a report |
| Driver app | Driver taps "arrived" early to start a timer |
| System default | Status set at appointment time automatically |
Statuses typed by dispatch
Some carriers' dispatchers set "arrived" based on what the driver said on the phone, or based on the plan. These statuses can be minutes or hours off. When a carrier's status is typed, the team should treat it as a claim and look for the site's record before relying on it.
Correct the record
The false status should not be deleted. It should be marked as wrong, with the correct time added when the truck actually arrives. This keeps the history honest. If the carrier later bills detention from the false arrival time, the record shows why it does not count.
Get a real estimate
The team needs to know when the truck will really arrive. The carrier should give an estimate based on the truck's current location. The AI logistics coordinator should compare it with the appointment and the dock hours, and tell the load owner if the pickup is at risk.
Customer updates should wait
If the customer gets automatic updates, an early or false "arrived" status may already have triggered a message. The team should check what the customer was told and correct it if needed. Future updates should be based on confirmed events.
Talk to the carrier about the source
If one carrier's arrival statuses are often early or wrong, the team should raise it with the carrier. The carrier may be able to tighten its geofence or change how dispatch sets statuses. Until it does, the team should rely more on site records for that carrier. Teams interested in how tracking claims should be supported can read why every tracking claim needs a timestamp.
When the truck is still far away
If the truck is still far from the site and the appointment will be missed, the team should treat it as a late pickup. The load owner should decide whether the warehouse can wait, the pickup should move, or another approved carrier is needed. The decision depends on the delivery promise and the cost of each option.
Hypothetical example: a geofence too wide
This example is hypothetical and does not describe a real customer. A carrier's system marks trucks "arrived" when they come within three miles of a site. At one plant near a highway, trucks show "arrived" while still on the highway. The AI logistics coordinator notices that this carrier's arrival times at that plant are always 15–20 minutes before check-in. It tells the reviewer to count from check-in for this carrier at that site and asks the carrier to tighten the zone.
How should the answer be recorded and used later?
The answer should be recorded with the stop: the carrier's claimed arrival, the actual check-in, the cause of the gap, and any messages and decisions. An AI logistics coordinator should save it the same day, so invoice reviews, customer questions, and carrier reviews can use it without rebuilding the story.
What to record
| Item | Example |
|---|---|
| Carrier's claimed arrival | 9:02 a.m., carrier system |
| Actual check-in | 9:31 a.m., east gate log |
| Cause of the gap | Driver at north office entrance |
| Messages | Carrier asked 9:20; directions sent 9:24 |
| Effect on appointment | None; loaded by 10:15 a.m. |
| Charges affected | Detention starts from 9:00 a.m. appointment if any |
Keep the record even when it was resolved quickly
A gap resolved in 10 minutes still deserves a short record. Those small records add up to patterns: one site where drivers often go to the wrong gate, or one carrier whose statuses are always early. Without them, each gap looks like a one-time event.
Use at invoice time
If the carrier bills detention, the reviewer can see the claimed arrival, the actual check-in, and the cause. If the gap was caused by unclear site directions, the reviewer may count from the appointment time. If it was caused by the carrier's own error, the reviewer may count from check-in.
Use at the next carrier review
Gaps by carrier belong in carrier reviews. A carrier whose trucks often end up at the wrong gate may need better dispatch notes.
Fix the causes
Each gap points to a cause. Wrong gates mean the site instructions need to be clearer. Old addresses in carrier systems mean the tender should include full directions. Missed log entries mean the gate process needs work. Early arrival statuses mean a conversation with the carrier. Fixing the cause prevents the next gap.
Share patterns with the warehouse
If drivers often end up at the wrong entrance of one site, the warehouse may be able to add a sign, open a phone line for drivers, or change the address it gives out. Data on how often it happens, and how much time it costs, helps the warehouse make the case for those changes.
Send better site instructions
The single most effective fix is often better site instructions in every tender: the shipping gate, the dock numbers, the check-in process, and a phone number for the shipping office. Drivers who know where to go do not end up at the wrong entrance. Teams handling missed pickups can see what to do in the first hour after a missed pickup.
Where does Wilson fit when the carrier says arrived and the warehouse has no check-in?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers, tracks each load, and contacts the carrier and site when their records disagree. 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 closes the gap
Wilson flags arrival claims that have no matching check-in after a set time, asks the carrier for the truck's location, asks the site for any record where configured, and sends corrected directions through the carrier when needed. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured, and it notifies internal teams through Slack, Microsoft Teams, email, or SMS.
Exceptions and payment
When Wilson detects a missed pickup, a cancellation, or a delay, it contacts the carrier, notifies the internal team, notifies the customer where configured, and initiates rebooking from the approved carrier list within the customer's rules or with approval. Wilson audits and reconciles each carrier invoice 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 assume the warehouse is wrong or the carrier is wrong. It gathers the facts from both and reports what it finds. It does not approve extra charges for a redirect above the customer's approval limits.
What Cartage asks in discovery
Cartage asks which sites have several gates or buildings, how check-ins are logged, which carriers share location data, and what instructions go out with tenders today. These answers shape how an AI logistics coordinator handles arrival gaps.
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 claim, check, and decision is saved in the shipment record with change history.
This article is part of our complete guide to driver arrival and detention records.
FAQs
What should the team do when the carrier says arrived but there is no check-in?
Find the truck first: ask the carrier for its location and the site for any record. An AI logistics coordinator asks both sides at the same time.
Why does this happen?
Usually a wrong gate, a line outside, or a missed log entry. Sometimes a wrong site or a false status. An AI logistics coordinator records the cause each time.
What if the truck is at the wrong site?
Send the correct address and dock instructions through the carrier right away. An AI logistics coordinator also checks whether the appointment or price is affected.
How should the gap be used at invoice time?
The reviewer compares the claimed arrival, the check-in, and the cause. An AI logistics coordinator saves all three with the stop.
Can a warehouse miss logging a truck that checked in?
Yes, especially at busy gates or when check-in is on paper. An AI logistics coordinator asks the site to check all logs and gates before treating the arrival as false.
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/
- Electronic Code of Federal Regulations, 49 CFR 395.26, "ELD data automatically recorded": https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/subpart-B/section-395.26
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator finds the truck fast when the carrier and warehouse records disagree: talk to the Cartage team.