No category
The carrier email and tracking feed disagree. Which one wins?
Key Takeaways
Neither source should win automatically. Lean toward the update that is newer, more specific and closer to the truck, then confirm with the carrier before anyone tells the customer.
Updates conflict for four common reasons: different update times, different sources, manual entries and plans that changed after the feed last refreshed.
A carrier email with a new ETA and a reason usually beats a tracking page that still says "on time," but only a confirmation from the carrier dispatcher or driver settles it.
Wilson, by Cartage, is an AI logistics agent that tracks each load with the best source available and emails or calls the carrier when status needs confirming, then tells the team and the customer one confirmed answer.
Every update, call and change belongs on the shipment record, so the next person doesn't have to work out which version was right.
Why do carrier emails and tracking feeds disagree?
Carrier emails and tracking feeds disagree because different people and systems update them at different times. A feed shows the last event a system recorded; an email shows what a dispatcher knew when they wrote it. Until someone confirms with the carrier, the safe answer to the customer is "we're confirming," not whichever version someone saw first.
This affects any manufacturer or distributor whose team reads carrier portals and inboxes for the same loads. Customer service checks the website, logistics reads the email, and the customer gets whichever one the person on the phone opened. Reliable visibility is still the exception: in a March 2025 BCI Global survey of 240 supply chain leaders, only 35% reported end-to-end visibility.
Thursday 6:10 a.m. On an FTL load from a manufacturer's plant to a distributor, the carrier's tracking page records its last event and shows "in transit, on time, delivery Friday 10:00 a.m."
Thursday 11:20 a.m. The carrier dispatcher emails the logistics coordinator: the truck has a mechanical issue, repair expected by 4:00 p.m., new delivery Friday afternoon.
Thursday 1:15 p.m. The distributor's receiving manager calls customer service. The rep opens the tracking page, sees "on time" and confirms Friday 10:00 a.m.
Thursday 3:40 p.m. The coordinator, back from a meeting, reads the email and starts carrier follow-up (the emails and calls a coordinator makes to get a status, ETA or document from a carrier). The dispatcher confirms: repair done, delivery Friday 3:00 p.m.
Friday 10:00 a.m. The distributor's dock crew is waiting. The truck arrives at 3:10 p.m.
Both sources were right when written. Nobody owned reconciling them before the customer heard an answer.
What makes shipment updates conflict?
Updates conflict because of timing, source, manual entry and changed plans.
Timing
A carrier website or API shows the last event the carrier’s system recorded. An email written after the last refresh is newer; an email from yesterday is older than this morning’s GPS ping.
Source
GPS or ELD (electronic logging device) data comes from the truck, so it tells you where the truck is but not why it stopped. The dispatcher’s email tells you why, but only as of their last call with the driver.
Manual entry
On many LTL loads, status depends on someone scanning or keying an event against the PRO number (the carrier’s tracking number for the shipment). A missed scan or a wrong code shows a status that never happened.
Changed plans
When a dispatcher swaps drivers or reschedules a delivery appointment, the email reflects the new plan first; the feed shows the old ETA until a new event arrives.
Situation | Lean toward | Confirm before telling the customer? |
|---|---|---|
Email is newer and gives a reason and a new ETA | The email | Yes, if the delivery date or appointment changes |
GPS or ELD shows the truck moving; an old email says delayed | The GPS or ELD data | Yes, ask the carrier for the current ETA |
Feed shows “delivered”; no POD and no email | Neither | Yes, ask for the POD before closing the load |
Feed hasn’t updated for hours and no email arrived | Neither | Yes, call the carrier |
POD (proof of delivery) is the signed delivery receipt; a “delivered” status without one is a claim, not a record.
How should the team decide which update to trust?
Use the newest, most specific update from the source closest to the truck as the working assumption, confirm it with the carrier, then record it and send one answer to everyone affected.
Compare times. Check the timestamp on each update, not the time you read it.
Compare detail. An update with an ETA, a location and a reason outranks one with a status word only.
Confirm with the carrier. Ask the dispatcher, or the driver if your SOP allows it, for the current location and ETA.
Record the confirmed status on the shipment with who confirmed it and when.
Notify once. Send customer service, sales and the consignee the same confirmed ETA, and update it only when it changes. See late freight customer update rules.
For how a carrier’s reply should change the shipment record, see the carrier replied by email. Did the shipment record change?
Common mistakes
Quoting the tracking page to the customer without checking the inbox. The customer plans a dock crew around an ETA that changed hours ago.
Treating “in transit” as “on time.” A status word without an ETA hides a delay until the delivery window has already passed.
Confirming by phone without writing it down. The next person sees the conflict again and repeats the call.
Letting customer service and logistics answer from different screens. The customer hears two dates from the same company and trusts neither.
How does Wilson, by Cartage, handle conflicting shipment updates?
Wilson tracks each load with the best source available, reads carrier replies onto the shipment, and emails or calls the carrier when status needs confirming, then sends one confirmed update to the people the company has chosen. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
A visibility platform shows where a load is. Wilson monitors loads as part of executing them, so it goes to the carrier instead of leaving two answers on a screen.
Step | Trigger | What Wilson does | When a person steps in |
|---|---|---|---|
1. Track | Load is in transit | Uses the carrier API, GPS or ELD data, or the carrier website by PRO number | Not required |
2. Follow up | No source available or no update | Emails or calls the carrier at the frequency set in the SOP | Not required |
3. Read replies | Carrier sends an email | Records it on the shipment | Not required |
4. Confirm | Status needs confirming | Emails or calls the carrier; saves the call transcript on the order | If the carrier can’t confirm |
5. Late load | ETA slips | Gets the new ETA and the reason | Not required |
6. Notify | Status is confirmed | Tells the team by Slack or Microsoft Teams, and the consignee by email or SMS if configured | Not required |
7. Escalate | The delay needs a decision | Escalates to the team | Deciding on recovery |
Customers can follow their shipments on a tracking link with the company’s branding, so customer service and the customer read the same confirmed status. For how Wilson reaches drivers and dispatchers, see can software call the carrier?
Controls
The company sets the rules: which channels Wilson uses, how often it follows up (for example, calling every hour until a load is picked up) and who is notified about what. Notifications to customers can be set to wait for approval, and Wilson starts with assisted execution, with autonomy expanded step by step as trust builds.
Wilson escalates when it can’t resolve something, for example when a carrier can’t confirm status or a decision exceeds the approval rules. Every message, confirmation and change on each shipment is recorded in a change history, so the team can see which update arrived when and what the carrier confirmed. If a delay leads to a rebooking, Wilson only uses carriers the company has approved.
What should you ask a vendor to show in a demo?
Ask the vendor to take one of your in-transit loads, create a conflict between the tracking source and a carrier email, and show how the conflict gets resolved and communicated.
Show which tracking source is used for this load and what happens when that carrier has no API or GPS data.
Forward a carrier email that contradicts the feed and show where it lands on the shipment.
Show the confirmation call or email to the carrier, including the saved transcript.
Show the update the consignee receives and the one your team receives in Slack or Microsoft Teams.
Open the change history and walk through every update in order.
To measure the change, compare the lanes the new process runs with how they ran before: time from exception to notification, manual touches per load and the number of ETAs sent to customers that later had to be corrected. For the broader category, see what is an AI logistics agent.
FAQs
What should I do when tracking and the carrier's email disagree? Treat the newer, more specific update as your working assumption, then confirm with the carrier before telling the customer. Record the confirmed status so the conflict doesn't come back.
Why do tracking feeds and carrier emails conflict? They're updated by different people and systems at different times. Missed scans and plans that changed after the last feed update are the most common causes.
Which source does Wilson use for tracking? The best source available for each load: the carrier's API, GPS or ELD data, or the carrier's website by PRO number. When none exist, Wilson emails or calls the carrier.
Does Wilson call carriers to confirm status? Yes. Wilson calls carriers and drivers for check calls and ETA follow-ups, at the frequency set in the company's SOP, and call transcripts are saved on the order.
Who does Wilson notify when a load is running late? The company chooses. Typically the team gets updates in Slack or Microsoft Teams, and the consignee gets them by email or SMS.
Is there a record of every update? Yes. Every message, confirmation and change on each shipment is recorded in a change history.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, and that one fee covers the full shipment lifecycle: create, quote, tender, track, audit and pay.
Conclusion
When a carrier email and a tracking feed disagree, the worst outcome is two people at your company giving the customer two different answers. The fix is a rule everyone follows: lean toward the newer, more specific update, confirm with the carrier, record the confirmed status and send one answer.
Wilson, by Cartage, runs that rule on each load: it tracks with the best source available, reads carrier replies onto the shipment, calls or emails the carrier when status needs confirming and sends one confirmed update to the people you choose. Bring one load where your team found two different ETAs last week and watch Wilson confirm it with the carrier and update everyone in a demo at cartage.ai.
Sources
BCI Global, March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Cartage, Wilson product FAQ, October 2026: https://cartage.ai
Other latest news and success stories
January 25, 2022
Best AI Tools for Carrier Follow-Up in 2026
Read more →
January 25, 2022
Best Bill of Lading (BOL) Software for Manufacturers in 2026
Read more →
