Shipment tracking software: what happens when a load has no updated ETA?
Key Takeaways
When a load has no updated ETA, shipment tracking software should treat the silence as an exception, check every available source, contact the carrier, and record a verified answer. An AI logistics coordinator should not keep showing an old ETA as if it were still true.
- An ETA, or estimated time of arrival, is a prediction. It loses value every hour it is not refreshed.
- A stale ETA is a warning sign. The load may be fine, or it may be late, lost, or never picked up.
- Good tracking software sets a time limit for each load type. When the limit passes, it starts follow-up.
- Follow-up should use the best source available for each load: carrier API, GPS or ELD data, the carrier website, email, or a phone call.
- The answer is not complete until a verified carrier update replaces the old ETA.
- Wilson, by Cartage, is an AI logistics coordinator that tracks each load as part of executing it and follows up with the carrier when updates stop.
Why is a missing ETA update a problem and not just a gap in the data?
A missing ETA update is a problem because people keep making decisions on a number that may no longer be true. An AI logistics coordinator should treat silence as a reason to act, because the cost of a wrong ETA lands on the plant, the warehouse, and the customer.
A plant schedules labor around inbound trucks. A warehouse books dock doors. A sales team promises a delivery date. Each of these plans uses the ETA, and an AI logistics coordinator is often the only party watching all of them at once. When the ETA stops updating, each plan keeps running on old information. The problem shows up hours later, when the truck does not arrive and nobody knew it would be late.
The table below compares a passive tracking screen with an AI logistics employee that treats a stale ETA as work to complete.
| Moment | Passive tracking screen | Tracking as part of execution |
|---|---|---|
| ETA stops updating | Old ETA stays on screen | Load flagged when the time limit passes |
| First check | Someone notices later, if at all | Every available source checked |
| Carrier contact | Coordinator emails when free | Carrier contacted through its channel |
| No reply | Thread waits | Follow-up repeated, then escalated |
| New answer | Typed in by hand, if found | Verified update recorded with source and time |
| People affected | Learn at the dock | Told through their configured channel |
Many visibility tools show useful data. The gap is often in what happens after the data stops. BCI Global surveyed 240 supply chain leaders in Europe and the US in March 2025. Only 35 percent had appropriate, detailed visibility and up-to-date data across their supply chain (BCI Global). An AI logistics coordinator that fills tracking gaps through follow-up addresses one part of that problem at the shipment level.
The cost of a wrong ETA at a plant
A wrong ETA costs more at a plant than almost anywhere else. A production line may wait for one inbound component. If the truck is late and nobody knows, the plant may call in a shift that has nothing to build. An AI logistics coordinator that learns about the delay early gives the plant manager time to change the schedule.
Outbound loads carry a different cost. A customer may plan a promotion, a job site, or a store opening around the delivery. A late load with no warning damages trust more than a late load with an honest early warning. An AI logistics employee cannot make the truck faster, but it can make the bad news arrive sooner and with a real time attached.
What "no updated ETA" can mean
A missing update has several possible causes. The carrier's system may not be connected. The driver's device may be offline in a rural area. The load may sit at a terminal waiting for a transfer. The pickup may never have happened. An AI logistics employee cannot know which cause applies until it checks, so the first job is to find out.
Estimated ETA versus verified update
An estimated ETA is a calculation or a promise. A verified update is a fresh fact from the carrier, the driver, a GPS position, or a delivery scan. Shipment tracking software should label the difference. An AI logistics coordinator should show when each ETA was last confirmed and by which source, so nobody mistakes a guess for a fact.
How long should tracking software wait before it flags a stale ETA?
Tracking software should flag a stale ETA when the time since the last verified update passes a limit set for that load type. An AI logistics coordinator should use different limits for different modes, because a cross-country truckload and a two-day LTL move do not update at the same pace.
There is no single correct number for an AI logistics coordinator to apply. A team should set limits based on how its carriers usually report and how much risk a late load creates. A load that feeds a production line needs a tighter limit than a load of spare parts going to a warehouse.
Who should set the limits
The logistics manager should set the limits, with input from the people who feel the delays. Plant managers know which inbound loads can stop a line. Customer service knows which customers need early warning. An AI logistics coordinator applies the limits the team agrees on, and the team can tighten or loosen them by load type, lane, or customer.
Write the limits down in a simple table. Review them after the first month. If the AI logistics employee flags many loads that turn out to be fine, the limit may be too tight for that mode. If late loads still surprise the dock, the limit is too loose.
Example limits by load type
The limits below are examples for discussion, not industry standards. Each team should set its own limits with its AI logistics coordinator during setup.
| Load type | Example limit without a fresh update | Why |
|---|---|---|
| Full truckload in transit | A few hours | Trucks move steadily, so silence is unusual |
| LTL between terminals | One business day | Freight can sit at a terminal without new scans |
| Load due at a plant today | One to two hours | A late truck can stop a production line |
| Drayage from a port | Same day as the planned pickup | Missed port windows create extra charges |
| Parcel | One business day after expected scan | Parcel networks scan at fixed points |
Why the ELD and GPS signal matters
Many trucks in the United States carry an electronic logging device, or ELD. Federal rules require an ELD to record the date, time, and vehicle location at each change of duty status. It must also make an intermediate recording at least once an hour while the vehicle is moving (49 CFR 395.26). This record exists for hours-of-service compliance, not for shipper tracking, and a carrier may not share it. Where a carrier does share GPS or ELD location data, an AI logistics coordinator can use it as one source among several.
Why silence means different things by mode
Silence on an LTL load often means the freight is at a terminal. LTL, or less-than-truckload, freight shares a trailer with other shippers' goods and moves through a network of terminals. A load can wait a day for the next linehaul trailer. An AI logistics coordinator should check the carrier's terminal events by PRO number before it assumes a problem.
Silence on a full truckload is more unusual. One truck carries one shipper's freight from pickup to delivery. A truck that stops reporting for several hours may be on a break, out of signal, or delayed. The AI logistics employee should contact the carrier sooner on truckload freight than on LTL.
Drayage and parcel follow their own patterns. Drayage is the short truck move of a container to or from a port or rail yard. Silence before a drayage pickup can mean the container is not yet available. Parcel networks scan packages at set points, so silence between scans can be normal for a day. An AI logistics coordinator should apply the mode's pattern before it sends anyone an alert.
Common mistakes when setting limits
- One limit for every load. LTL loads will trigger false alarms, and urgent loads will be flagged too late.
- Limits based on the last ETA, not the last update. An ETA can look fresh because the system recalculated it, even when no new fact arrived.
- No limit after delivery time passes. A load that was due yesterday and shows no delivery is the most urgent case.
An AI logistics employee should count time from the last verified fact. That rule stops recalculated guesses from hiding a silent carrier.
What should the software do after it flags a load with no updated ETA?
After it flags a load, the software should check every source and contact the carrier. It should keep following up until a verified answer arrives or a person takes over. An AI logistics coordinator should record each step, because the steps themselves show the team what is known.
A practical follow-up workflow
Check the connected sources. The AI logistics coordinator checks the carrier API, if one is available, and any shared GPS or ELD location.
Check the carrier website. For LTL freight, it can look up the load by its PRO number. A PRO number is the tracking number an LTL carrier assigns to a shipment.
Contact the carrier. It sends a status request by email, or calls where phone outreach is configured.
Ask a precise question. It asks where the load is, when it will deliver, and whether anything changed, such as a missed transfer.
Wait for a set time. If the carrier does not reply, it follows up again through the same or a different channel.
Record the answer. It saves the new ETA, the source, and the time, and marks the old ETA as replaced.
Tell the people affected. It sends the update to the internal team and, where configured, to the customer or receiver.
Escalate if needed. If no answer arrives by the deadline, it sends the load to a named person with the history.
Hypothetical example: a truckload goes quiet
This example is hypothetical and does not describe a real customer or a measured AI logistics coordinator result. A furniture manufacturer ships a full truckload from North Carolina to a retailer's warehouse in Illinois. The carrier's API showed the truck in Tennessee at 9 a.m. By 1 p.m., no new position has arrived.
The four-hour limit passes. The AI logistics coordinator checks the carrier portal and finds no new event. It emails the carrier's dispatch desk and asks for the truck's location and a revised ETA. Dispatch replies that the truck had a tire repair and lost three hours. The AI logistics employee records the new ETA and notes the source as the carrier dispatcher. It then tells the retailer's receiving team that the truck will arrive the next morning instead of late that evening.
The retailer moves the dock appointment. The manufacturer avoids a missed appointment and a possible fee. The AI logistics coordinator turned silence into a verified answer before the receiver noticed.
What to ask the carrier
The status request should ask for facts the team can use. A vague question, such as "Any update?", often gets a vague reply. An AI logistics coordinator should ask three specific questions: where is the load now, when will it deliver, and has anything changed since pickup.
A short request might read: "Load 48213, picked up Monday in Charlotte. Please confirm the current location, the delivery ETA, and any delay reason. The receiver's appointment is Wednesday at 8 a.m." The message names the load, the stakes, and the facts needed. A carrier dispatcher can answer it in one reply, and the AI logistics employee can record each fact separately.
When the delivery time has already passed
A load past its delivery time with no delivery record is the most urgent case. An AI logistics coordinator should check for a delivery scan or proof of delivery first. A proof of delivery, or POD, is the signed record that the receiver took the freight. If no POD exists, the carrier must confirm whether the load delivered, is still moving, or has a problem.
Do not assume a quiet late load was delivered. A delivery scan without a POD may also need follow-up, because a scan is not the same as confirmed receipt. The AI logistics employee should keep the load open until the evidence is complete.
What counts as a verified answer
A verified answer comes from the carrier, the driver, a fresh location record, or a scan. An answer that only repeats the old ETA is not new evidence. An AI logistics coordinator should ask the carrier to confirm the location and the reason for any delay, so the team can judge whether the new ETA is reliable.
Who should hear about a load with no updated ETA, and when?
The people who should hear are those whose plans depend on the load, and they should hear when the update changes a decision they must make. An AI logistics coordinator should not send every stale-ETA flag to everyone, because too many alerts teach people to ignore them.
Internal team
The logistics team should see every flagged load and its status. A short message works best: which load, the last known fact, what was done, and what happens next. Wilson, an AI logistics employee, sends internal updates through channels such as Slack, Microsoft Teams, or email, depending on the customer's setup.
Plant, warehouse, or receiving team
The receiving team needs to know when a delivery will miss its appointment. They do not need every follow-up step. An AI logistics coordinator should tell them once the new ETA is verified, or when the risk of a missed appointment is clear.
Customer or consignee
The consignee is the party receiving the freight. A customer should hear about a delay when the delay changes their plans. The message should come with a verified new time, not a guess. Where configured, an AI logistics employee can notify the consignee by email or SMS.
What a good delay message looks like
A good delay message states the load, the new time, the source, and the next step in a few lines. Receivers read these messages between other tasks. An AI logistics coordinator should write them so a person can act without opening another system.
For example: "PO 7781 from Dalton Mills will now arrive Thursday at 10 a.m., not Wednesday at 4 p.m. Source: carrier dispatch, confirmed at 2:10 p.m. Please confirm whether the Thursday slot works." The message gives a verified time and asks for one decision. An AI logistics employee should avoid long explanations unless the receiver asks for them.
Notification rules to agree on
| Event | Who hears | Channel example | What the message includes |
|---|---|---|---|
| ETA flagged as stale | Logistics team | Slack, Teams, or email | Load, last update, follow-up started |
| Verified delay | Logistics and receiving | Team channel and email | New ETA, source, reason |
| Missed appointment risk | Receiving and customer | Email or SMS | New time and request to reschedule |
| No answer by deadline | Named escalation owner | Direct message or email | Full contact history and options |
Agree on these rules before go-live. The AI logistics coordinator follows the rules, and the team can change them as it learns which messages help.
How should you compare shipment tracking software on stale ETAs?
Compare shipment tracking software by what it does when updates stop, not by how good the map looks. An AI logistics coordinator earns its place when the data goes quiet, because that is when a person would otherwise have to chase the carrier.
Demo tests for stale ETAs
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Flags stale ETAs by load type | Set a short limit on one load | Flag fires when the limit passes |
| Separates estimates from facts | Open a load with a recalculated ETA | Last verified update and source shown |
| Uses more than one source | Pick a carrier with no API | Website check, email, or call recorded |
| Follows up until answered | Leave a carrier silent | Repeated follow-up, then escalation |
| Notifies the right people | Trigger a verified delay | Message reaches the configured contacts |
| Keeps a history | Review a closed load | Every check, contact, and answer listed |
Demo questions about stale ETAs
- What does the AI logistics coordinator do when a carrier has no API?
- How does the software show the time of the last verified update?
- Which follow-up steps run within rules, and which wait for a person?
- Can the team set different limits for LTL, truckload, drayage, and parcel?
- What happens when the delivery time passes with no delivery record?
- Can the team export the tracking history for a customer dispute?
How to measure stale ETAs work
Measure the share of flagged loads that received a verified update before the planned delivery time. Measure how many flagged loads reached a person with a full history. Check how often receivers learned about a delay before the truck was due. These measures show whether the AI logistics employee resolves tracking gaps or only reports them.
Scoring the stale ETAs demo
Score each demo test as pass, partial, or fail, and note the evidence. A pass means the AI logistics coordinator flagged the load, followed up, and recorded a verified answer with its source. A partial means it flagged the load but the follow-up was manual or the source was missing. A fail means the old ETA stayed on screen with no action.
Weight the tests by how often each case happens in your freight. A team with many email-only carriers should weight the no-API test heavily. A team with many inbound loads to plants should weight the notification test. Share the results with operations and customer service, because both groups depend on the same AI logistics employee.
Common mistakes in tracking evaluations
Buyers often test only loads with good carrier connections. Those loads update well in any system. The real test is a carrier that reports by email or not at all. Another mistake is to judge the software by its alert count. More alerts do not mean better tracking. An AI logistics coordinator should create fewer, clearer alerts, each one backed by follow-up already done.
Where does Wilson fit when a load has no updated ETA?
Wilson, by Cartage, is an AI logistics coordinator that tracks each load as part of executing it, from booking to delivery. When updates stop, Wilson follows up with the carrier and records what it learns.
Wilson tracks each load using the best source available. That can include carrier APIs, GPS or ELD data where it exists, the carrier's website by PRO number, and email or direct outreach, including calls where configured. This AI logistics employee asks the carrier for status and informs the people who need to know.
Exceptions beyond a stale ETA
A silent load sometimes turns out to be a bigger problem for the AI logistics coordinator to handle. The pickup may have been missed, or the carrier may have canceled. When Wilson detects a missed pickup, a cancellation, or a delay, it contacts the carrier and notifies the internal team. It notifies the customer where configured and initiates rebooking from the approved carrier list. Rebooking runs within the customer's rules or with approval, depending on configuration.
What Cartage asks about stale ETAs in discovery
Cartage asks how the team tracks loads today and where the gaps hurt most. Typical questions cover which carriers send updates, which do not, and which loads cause the most surprise calls. Cartage also asks who should receive each kind of update. These answers shape the limits and contacts an AI logistics coordinator uses from the first load.
The team does not need a finished process map. Cartage helps identify the first workflow during discovery. Many teams begin with the loads that create the most phone calls, because that is where an AI logistics employee removes the most follow-up work.
What Wilson does not do for stale ETAs
Wilson, as an AI logistics coordinator, does not promise a fresh location every few minutes for every load. The freshness of an update depends on the source each carrier offers. Wilson is not a standalone visibility platform; it tracks loads as part of moving them. It does not claim route or network optimization. Buyers should confirm notification channels and contacts for their own setup during discovery.
Where teams start with stale ETAs
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, such as inbound loads to a plant that often arrive without warning.
Teams that already struggle with old ETAs can read more about carrier follow-up on a stale ETA. Teams comparing data sources can review carrier API, PRO tracking, and check calls. Both pages explain choices an AI logistics coordinator makes every day. Teams that send ETAs to customers can see why to verify the carrier before a customer ETA update.
FAQs
What happens when a load has no updated ETA in shipment tracking software?
Good software flags the load when a time limit passes. An AI logistics coordinator then checks every source, contacts the carrier, records a verified answer, and tells the people affected.
How is a stale ETA different from a late shipment?
A stale ETA means nobody has confirmed the arrival time recently. A late shipment means the load will miss its promised time. An AI logistics employee checks the stale ETA to learn whether the load is late.
Can tracking software update an ETA without a carrier API?
Yes. It can use the carrier website, a PRO number lookup, email, or a phone call. An AI logistics coordinator records which source produced each update.
Who should receive a delay alert?
The logistics team, the receiving team, and the customer when the delay changes their plans. An AI logistics employee should send each group only the information it needs to act.
Sources
- BCI Global, "No visibility, no resilient supply chain," March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
- Electronic Code of Federal Regulations, 49 CFR 395.26, ELD data automatically recorded, reviewed October 2026: https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/subpart-B/section-395.26
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator flags a load with a stale ETA, follows up with a carrier that has no API, and sends a verified new time to your receiving team: talk to the Cartage team.