No category
Shipment tracking software for conflicting ETAs: which update should you trust?
Key Takeaways
When ETAs conflict, trust the update that is freshest, most specific, and most independent of guesswork, and confirm it with the carrier before sharing it. An AI logistics coordinator should apply a written source ranking, reconcile the conflict with a direct question when the gap matters, and send customers one verified ETA instead of several competing ones.
An ETA, or estimated time of arrival, can come from a carrier message, a location feed, a calculation, or a customer portal. They often disagree.
The newest update is not always the best one. A fresh calculation built on old data can be worse than a slightly older driver confirmation.
Rank sources by freshness, specificity, and independence, not by habit.
Small gaps can be ignored. Gaps that change an appointment or a customer promise need a direct question to the carrier.
Customers should receive one ETA with a source and a time, not a list of guesses.
Wilson, by Cartage, is an AI logistics coordinator that tracks each load using the best source available, follows up with the carrier, and informs the people who need to know.
Why do ETAs conflict?
ETAs conflict because different sources calculate or report them at different times and with different information. An AI logistics coordinator should expect conflicts and have a rule for choosing, rather than letting each person pick the number they saw first.
A typical truckload may have four ETAs at once. The carrier's tracking feed says 2 p.m. A location-based calculation says 3:30 p.m. The dispatcher's email from this morning says noon. The customer's portal still shows the original 10 a.m. promise. Each number has a reason. None is labeled with how it was made.
The table below lists common ETA sources and how they can go wrong.
ETA source | How it is made | How it can mislead |
|---|---|---|
Carrier API or EDI feed | Carrier system posts an ETA | May not update after a delay |
GPS or ELD calculation | Distance and speed from a location | Ignores breaks, traffic, and terminal stops |
Dispatcher email or call | Dispatcher's estimate, often after talking to the driver | Can be optimistic or out of date |
Carrier website (LTL by PRO) | Carrier's standard transit schedule | Shows planned date, not real progress |
Original promise in the ERP | Set when the order was booked | Never updates on its own |
Customer portal | Copy of one of the above | Inherits the source's errors |
An application programming interface (API) is a direct system connection. Electronic data interchange (EDI) is an older standard for business documents. An ELD, or electronic logging device, records a truck's location and the driver's hours. An ERP, or enterprise resource planning system, holds orders and promised dates. A PRO number is the tracking number an LTL carrier assigns.
The cost of trusting the wrong ETA
Trusting the wrong ETA leads to the wrong action. A receiver schedules labor for noon and the truck arrives at 4 p.m. A plant holds a production run for a part that will not arrive today. A customer is told "on time" and then gets a late delivery with no warning. Each mistake comes from a number that looked official but was not the best one available.
Which loads deserve the most attention
Not every conflict deserves the same effort. A load with a strict appointment, a production-critical part, or a customer that charges late fees deserves a fast reconciliation. A restock shipment to the company's own warehouse can usually wait for the next routine update. An AI logistics coordinator can mark loads by priority and reconcile the urgent ones first, so effort matches risk.
Why conflicts multiply
Conflicts grow as more systems copy ETAs from each other. A customer portal copies the carrier feed. A sales tool copies the ERP. An email to the customer copies whatever the coordinator saw. Soon the same load shows four times in four places. An AI logistics employee that keeps one verified ETA per load, with its source, gives every system a single reference.
Who owns the ETA
One person or role should own the external ETA for each load. Usually that is the logistics team, not sales or customer service. When ownership is clear, other teams know where to look and stop quoting their own numbers. An AI logistics coordinator can hold the verified ETA for the logistics team and publish it to the channels each team uses.
Conflicts are a signal, not just noise
A conflict often means something changed. If the GPS calculation says 3:30 p.m. and the carrier feed still says 2 p.m., the truck may be delayed and the feed has not caught up. Treating the conflict as a reason to ask, rather than a nuisance to ignore, often catches a delay early.
How should you rank ETA sources?
Rank ETA sources by three tests: how fresh the information is, how specific it is, and how independent it is from assumptions. An AI logistics coordinator should apply the ranking the same way on every load and show which source won.
Test 1: Freshness
Freshness is the age of the facts behind the ETA, not the time the ETA was displayed. A calculation shown at 3 p.m. using a 9 a.m. location is six hours old. A dispatcher's email at 1 p.m. after speaking with the driver at 12:45 p.m. is fresh. The AI logistics employee should record the time of the underlying fact for each source.
Test 2: Specificity
A specific ETA names a time and is tied to a known location and status. "2:15 p.m., truck 40 miles out, no stops planned" is specific. "This afternoon" is not. Specific ETAs can be checked. Vague ones cannot.
Test 3: Independence
An independent ETA is based on facts that do not depend on someone's hope. A location from an ELD, a terminal scan, or a receiver's check-in is independent. A dispatcher's estimate is less independent, especially if the dispatcher has not reached the driver. An original promise date is not evidence of progress at all.
Realistic travel time from a location
A location is only useful for an ETA when travel time is realistic. Federal hours-of-service rules limit a property-carrying driver to 11 hours of driving within a 14-hour on-duty period, after 10 consecutive hours off duty. A driver also needs a 30-minute break after 8 hours of driving (49 CFR 395.3). An ETA that assumes nonstop driving can be hours too early. An AI logistics coordinator should allow for required breaks and rest when it turns a location into an arrival time, or ask the dispatcher about the driver's remaining hours.
Sources that should never win alone
Some sources are useful context but should never decide the ETA by themselves. The original promise date shows what was planned, not what is happening. A standard transit time shows the carrier's typical schedule, not this load's progress. A customer portal shows a copy of something else. An AI logistics employee should use these as reference points and look for a fresh fact before sharing a time.
A practical source ranking
The ranking below is an example. Each team should adjust it to its carriers and modes.
Rank | Source | When it wins |
|---|---|---|
1 | Driver or dispatcher confirmation with location, less than an hour old | Fresh, specific, and confirmed |
2 | Shared GPS or ELD location with a realistic travel time | Fresh location, adjusted for breaks |
3 | Carrier API or EDI ETA updated within the set limit | Carrier's own current view |
4 | Terminal scan with the carrier's next-step schedule (LTL) | Freight position is known |
5 | Dispatcher estimate without driver contact | Better than nothing, but check |
6 | Carrier website standard transit date | Plan only, not progress |
7 | Original promise in the ERP | Reference point, never evidence |
Review the ranking with real arrivals
A ranking is a guess until it is tested. After a month, compare each source's ETA with the actual arrival time on the same loads. If one carrier's feed is often two hours optimistic, move it down for that carrier. If shared location data is usually accurate, move it up. An AI logistics coordinator can keep each source's ETA and the actual arrival, so the review uses facts.
Adjust the ranking by mode
LTL freight depends on terminal schedules, so terminal scans rank higher. Truckload freight moves on one truck, so location data and driver confirmation rank higher. Drayage depends on port and rail yard events. Parcel depends on carrier scans. An AI logistics coordinator should apply the right ranking for each mode.
Hypothetical example: ranking four ETAs
This example is hypothetical and does not describe a real customer. A paint manufacturer's truckload is due at a retailer's distribution center at 2 p.m. At 11 a.m., the carrier feed shows 2 p.m. A shared ELD location from 10:50 a.m. puts the truck 230 miles away. The dispatcher's morning email said "on time." The retailer's portal shows 2 p.m.
The AI logistics coordinator ranks the sources. The ELD location is the freshest independent fact. At highway speeds, plus a required break, 230 miles suggests arrival near 3:30 p.m. The coordinator calls dispatch, which reaches the driver. The driver confirms a 3:20 p.m. arrival after a break. The coordinator records 3:20 p.m. as the verified ETA, with the driver as source, and asks the retailer for a later slot.
Put Wilson to work on your freight
Wilson handles quoting, booking, tracking, carrier communication, invoice auditing, and payments. Unlimited use, $0. You pay one rate per load.
How should you reconcile a conflict that matters?
Reconcile a conflict that matters by asking the carrier a direct question that names both numbers, then recording the answer as the verified ETA. An AI logistics coordinator should not average the numbers or pick the one it prefers.
Reconcile before the customer notices
The best time to reconcile is before the receiver sees a conflict. A receiver who checks a portal and sees a different time than the email it got loses trust. An AI logistics coordinator that reconciles as soon as a gap appears can update every channel at once, so the receiver only sees the verified number.
Decide whether the gap matters
Not every gap needs action. A 15-minute difference on a day window does not matter. A two-hour difference on a strict appointment does. A rule might say: reconcile when the gap would move the delivery outside its window, or when it exceeds a set number of minutes. An AI logistics employee can apply the rule and ignore small gaps.
Ask a direct question
A useful message names the conflict. For example: "Load 2208: your system shows a 2 p.m. ETA, but the truck's last location suggests closer to 3:30 p.m. Can you confirm the current location and arrival time with the driver?" The dispatcher sees the problem and checks. Vague requests get vague answers.
Hypothetical example: an LTL conflict
This example is hypothetical and does not describe a real customer. A distributor's LTL shipment shows a Thursday delivery on the carrier's website, based on standard transit. The carrier's terminal scans show the freight still at the origin terminal on Tuesday night, a day behind its usual schedule.
The AI logistics coordinator ranks the terminal scan above the standard transit date and asks the carrier when the freight will move. The carrier confirms it missed Tuesday's linehaul and will leave Wednesday, delivering Friday. The coordinator records Friday as the verified ETA and tells the customer two days before the original date.
Record the reconciled ETA
Once the carrier answers, record the new ETA, the source, the time of confirmation, and the reason for any change. Mark the other ETAs as replaced. The AI logistics coordinator should share only the reconciled ETA with the receiver or customer.
Ask for the reason behind a change
When the carrier gives a new ETA, ask why it changed. A weather delay, a breakdown, a missed terminal transfer, and a late pickup each mean different things for the rest of the trip. A breakdown may need a replacement truck. A missed transfer may mean another day. An AI logistics employee should record the reason with the new ETA, because the reason helps predict whether the new time will hold.
When the carrier cannot be reached
If the carrier does not answer within the set time, use the highest-ranked available source and label it clearly as an estimate. For example: "Estimated 3:30 p.m., based on 10:50 a.m. truck location; awaiting carrier confirmation." That label tells the receiver how much to rely on it.
How often to reconcile
Reconcile when a meaningful gap appears, and again as the delivery nears. A load due tomorrow may need one check today and one the morning of delivery. A load due in an hour may need a check now. An AI logistics coordinator can schedule checks based on the time left before the appointment, so effort goes where the risk is highest.
Common mistakes in reconciling
Averaging ETAs. An average of two wrong numbers is still wrong.
Picking the most optimistic number. It feels better but fails more often.
Picking the newest display time. A new display can hide old data.
Sharing several ETAs with the customer. The customer has to guess which one is real.
Not recording which source won. The next person repeats the work.
Which ETA should customers and receivers see?
Customers and receivers should see one ETA, with the time it was confirmed and a simple note on its source. An AI logistics coordinator should update that single ETA when a better source arrives, and tell them when the change affects their plans.
One ETA, clearly labeled
A clear external update looks like this: "Delivery ETA: Thursday 3:20 p.m. Confirmed with the carrier at 11:40 a.m." The receiver knows the time and how fresh it is. If the time changes, the next update says what changed and why.
When to send an update
Send an update when the verified ETA moves enough to affect the receiver's plans, such as moving past the appointment or the end of the window. Small shifts within the window can wait. Too many updates make receivers ignore them. An AI logistics employee can apply a threshold so only meaningful changes go out.
Words that build trust
Receivers trust updates that are honest about certainty. "Confirmed with the driver at 11:40 a.m." builds trust. "Estimated, awaiting carrier confirmation" is honest and still useful. "On time" with no source invites doubt. An AI logistics employee should use plain, consistent wording so receivers learn what each label means.
Internal teams need the same single number
Sales, customer service, and the plant should all use the same verified ETA. When each team quotes a different number to the customer, trust drops. Wilson sends internal updates through channels such as Slack, Microsoft Teams, or email, and can notify consignees by email or SMS where configured. A consignee is the party receiving the freight.
Updating the receiver's appointment
A new ETA often means a new appointment. The receiver may need to move the dock slot, and the carrier needs the new appointment time. An AI logistics coordinator can request the change from the receiver and confirm the new slot with the carrier, so all three parties work from the same time. If the receiver cannot offer a slot that fits, a person should decide the next step.
When the original promise is no longer possible
If the verified ETA moves the delivery outside the promised date, the customer should hear early, with a real new time. Updating the ERP's promised date may also be needed, depending on the team's process and the connection's scope. Not every ERP connection writes data back, so a person may need to update the order.
Hypothetical example: one message instead of three
This example is hypothetical and does not describe a real customer. A distributor's customer service rep, a sales manager, and the carrier each tell a hardware chain a different delivery time for the same load. The chain's receiving manager calls to complain.
The distributor changes its process. The AI logistics coordinator now holds the only external ETA for each load and sends it to the receiver. Sales and customer service see the same ETA in their team channel and refer customers to it. The receiving manager gets one message per change, each with a confirmed time and source.
How should you evaluate shipment tracking software on conflicting ETAs?
Evaluate shipment tracking software by giving it a load with conflicting ETAs and asking which one it trusts and why. An AI logistics coordinator should show its source ranking, ask the carrier when the gap matters, and share one verified time.
Demo tests for conflicting ETAs
Buyer requirement | Demo test | Evidence to see |
|---|---|---|
Source ranking | Feed three different ETAs | Winner shown with reason |
Freshness by fact time | Show a new display based on old data | Marked as stale |
Gap threshold | Create small and large gaps | Only the large gap triggers action |
Direct reconciliation | Create a large gap | Carrier asked with both numbers |
Single external ETA | Send a receiver update | One time, source, and confirmation time |
Record | Open the load | Every ETA, source, and replacement saved |
Demo questions about conflicting ETAs
How does the AI logistics coordinator know the age of the facts behind each ETA?
Can the source ranking vary by mode and carrier?
What gap triggers a carrier question?
How are external updates labeled when the carrier has not confirmed?
Where do sales and customer service see the verified ETA?
Can the team review how often each source was wrong?
Test with your own loads
Bring a few recent loads where the ETAs disagreed and the delivery went wrong. Ask the vendor to show how its AI logistics coordinator would have ranked the sources, when it would have asked the carrier, and what it would have told the receiver. A replay of your own problem loads shows more than a clean demo load.
How to measure conflicting ETA work
Track how often the verified ETA matched the actual arrival within a set tolerance. Count how many receivers got a changed ETA before the original window passed. Check how many loads had more than one external ETA sent. These measures show whether the AI logistics employee is reducing confusion.
Warning signs in a conflicting ETA demo
The system shows the newest ETA with no source or fact time.
Location-based ETAs ignore driver breaks.
Several ETAs appear side by side with no winner.
External updates carry no confirmation time.
The vendor cannot say how often each source was wrong.
Scoring the conflicting ETA demo
Score each test as pass, partial, or fail. A pass means the AI logistics coordinator chose by the ranking, confirmed large gaps, and shared one ETA. A partial means it ranked correctly but did not ask the carrier. A fail means it showed several ETAs with no way to tell which is right.
Where does Wilson fit when ETAs conflict?
Wilson, by Cartage, is an AI logistics coordinator that tracks each load using the best source available for that load and follows up with the carrier when sources disagree. It replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment.
Wilson's tracking can use 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.
What Wilson records
Wilson keeps searchable shipment records with change history. A team can see each ETA update, its source, and when it changed. That history helps answer a customer who asks why the delivery time moved.
What Cartage asks about conflicting ETAs in discovery
Cartage asks which systems show ETAs today, which customers need appointment updates, and which carriers' feeds the team trusts least. These answers shape the source ranking and update thresholds an AI logistics coordinator applies.
What Wilson does not do for conflicting ETAs
Wilson does not promise a fresh location for every load at every moment. Freshness depends on the sources each carrier offers. Wilson is not a standalone visibility platform; it tracks loads as part of moving them. Specific ranking rules and update thresholds should be confirmed in a demo. Not every ERP connection writes updated dates back to the ERP.
Where teams start with conflicting 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. Teams with strict retail appointments often start there, because a wrong ETA costs the most.
Teams comparing tools for this problem can read about shipment tracking software for conflicting ETAs. Teams seeing carrier emails disagree with feeds can see what to do when a carrier email and tracking feed disagree. Both topics shape how an AI logistics coordinator ranks sources. Teams sending updates outward can review customer ETA alerts versus verified carrier updates.
FAQs
Which ETA should you trust when shipment tracking updates conflict?
Trust the freshest, most specific, and most independent update, and confirm it with the carrier when the gap matters. An AI logistics coordinator should apply a written source ranking and record which source won.
Is the newest ETA always the most accurate?
No. A newly displayed ETA can be built on old location data. An AI logistics employee should judge freshness by the time of the underlying fact.
Should customers see every ETA update?
No. Customers should see one verified ETA, updated when the change affects their plans. An AI logistics coordinator should label it with the confirmation time.
What if the carrier cannot confirm the ETA?
Use the highest-ranked available source and label it as an estimate with its basis. An AI logistics employee should replace it with a verified time as soon as the carrier answers.
Sources
Electronic Code of Federal Regulations, 49 CFR 395.3, Maximum driving time for property-carrying vehicles, reviewed October 2026: https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/section-395.3
Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator ranks conflicting ETAs, confirms the real arrival time with the carrier, and sends your receiver one verified update: talk to the Cartage team.
Put Wilson to work on your freight
Wilson handles quoting, booking, tracking, carrier communication, invoice auditing, and payments. Unlimited use, $0. You pay one rate per load.
Other latest news and success stories
January 25, 2022
Ergomotion books 1,800+ shipments end to end with Wilson
Read more →
January 25, 2022
Flexocraft runs its daily freight operation with Wilson
Read more →
