Why Tracking Across Carriers Gives Conflicting ETAs (and How to Fix It)

Quick answer: Conflicting ETAs happen because each carrier publishes a mix of planned and actual milestones, applies its own ETA policy, and updates after different system handoffs. Anchor your plan to confirmed events like Loaded and Departure. Normalize time zones. Use one shared view with alerts so you act on the same signal. Why do…

Tradlinx

November 17, 2025

2–3 minutes

Container tracking, DCSA, ETA, ETA drift, Freight Forwarding, Global Logistics, import export, logistics operations, LSP, milestone alerts, Ocean Freight, Ocean Visibility, real-time tracking, shipment status, shipping schedules, Supply Chain Management, time zones, Track and Trace, tradlinx, Transshipment

Quick answer: Conflicting ETAs happen because each carrier publishes a mix of planned and actual milestones, applies its own ETA policy, and updates after different system handoffs. Anchor your plan to confirmed events like Loaded and Departure. Normalize time zones. Use one shared view with alerts so you act on the same signal.

Why do carriers show different ETAs

Planned versus actual: A page can show a planned leg until an actual milestone posts. ETAs move when the cutover happens. See the DCSA Track and Trace framing of planned and actual events.
Different source mix: Terminal, feeder, and mainline systems post events on different clocks. Portals reflect those handoffs at different times.
Transshipment naming: The outbound vessel can be pending until assignment is firm. ETAs shift when the connection is confirmed.
ETA policy differences: Some sites display early plan ETAs. Others show conservative estimates. Most schedule pages state that times are estimates and can change.
Time zone confusion: Mixing local time and UTC creates false drift. Consistent formatting removes this noise.

Standards help you read the logic. DCSA Track and Trace defines shipment phases and event names so you can map labels across carriers. The glossary clarifies terms like Actual and Planned.

DCSA Track and Trace documentation and the DCSA shipping glossary.

How to reduce ETA conflicts today

Anchor to confirmed events: Plan around Loaded and Transport Departure. Treat any ETA before those points as provisional.
Keep a single source of truth: Cross check BL and containers in one view and share that view internally so decisions use the same signal.
Normalize time: Log both local time and UTC in ISO 8601 format. Label the IANA time zone.
Adopt an internal ETA policy: Use a simple rule. For example, display the most recent ETA after Loaded unless a later Departure or advisory changes it.
Use alerts instead of manual refresh: Turn on event and ETA change notifications on each carrier portal so the team does not miss flips from plan to actual.

Example: A box gates in at Busan with a planned feeder to a hub. Two carriers show different ETAs for the ocean leg. Wait for the outbound Loaded on the mainline vessel. That is your decision point. Update the internal ETA only after that event posts.

Methods and sources

DCSA Track and Trace: standard documentation, overview, and the shipping glossary.
Carrier schedule disclaimers that times are estimates and can change: Maersk notices and local pages often note this (example advisory PDF states schedules may change), Maersk advisory example; MSC terms note schedules are estimated, MSC USA T&Cs; CMA CGM schedule pages mark schedules as indicative, CMA CGM schedule example; Hapag-Lloyd FAQ notes planned versus actual in tracking, Hapag-Lloyd FAQ example.
Time discipline for logging: ISO 8601 format and the IANA time zone database.

Next steps

Cross check your BL across carriers in one view. Set alerts for key milestones. Want help wiring this into your lane and dashboards? Talk to us.

Prefer email? Contact us directly at min.so@tradlinx.com (Americas), sondre.lyndon@tradlinx.com (Europe) or henry.jo@tradlinx.com (EMEA/Asia)