Why ONE Tracking Is Not Updating and When It Usually Catches Up

Quick answer: ONE’s customer view updates when real handling milestones are recorded. Before the first actual event appears, your page can look quiet or show plan data. Use the official Cargo Tracking, cross check schedules during quiet periods, and turn on ONE event notifications. Do not assume a fixed refresh timer. Treat each change as…

Tradlinx

December 11, 2025

2–4 minutes

Container tracking, DCSA, event notification, Ocean Network Express, ONE, schedules, shipment status, Track and Trace, Visibility Service

Quick answer: ONE’s customer view updates when real handling milestones are recorded. Before the first actual event appears, your page can look quiet or show plan data. Use the official Cargo Tracking, cross check schedules during quiet periods, and turn on ONE event notifications. Do not assume a fixed refresh timer. Treat each change as confirmation of a real step.

How ONE tracking actually updates

ONE surfaces shipment, equipment, and transport events in Track & Trace. You can track by BL, container, or booking and use Visibility Service features to receive notifications. Schedules help you verify intended legs while you wait for the next actual event.

Cargo Tracking by BL, container, or booking.
Point to Point Schedule and Vessel Schedule for intended connections.
Event notifications in Visibility Service and the Proactive Notification advisory.
Optional Mail Tracking by sending an email to the tracking mailbox.

Note: ONE’s Korea advisory in 2025 describes an enhanced cargo tracking timeline and exception alerts. That improves how irregularities are surfaced but still depends on event postings.

Enhanced cargo tracking advisory.

Why updates lag on ONE

Pre sailing gap: After Gate In, the next visible jump is often Loaded. If a feeder or slot is not final, the record can remain planned until loading is confirmed.
Feeder or transshipment planning: If the onward vessel is not assigned, a named ship may not appear yet. ONE schedules sometimes show placeholders like pending or TBN during planning.
System handoffs: Terminal and inland systems post events to the line. Any delay in EDI or API propagation postpones what you see. This planned versus actual behavior follows Track and Trace standards.
Cut off windows move: ONE’s Port Schedule view notes that schedules are estimates and can change. Do not treat cut offs as guaranteed until confirmed on your booking.

Port Schedule page shows cut off and the disclaimer that schedules are estimated and subject to change.

Status to event mapping

What you see	What it usually means	Standard reference
Gate In	Unit entered terminal yard and awaits loading	DCSA glossary Equipment Gate In
Loaded	Unit loaded on vessel for the leg	DCSA glossary Equipment Loaded
Vessel departed	Voyage leg started	DCSA glossary Transport Departure
Discharged	Unit unloaded at transshipment or discharge port	DCSA glossary Equipment Discharged
Gate Out	Unit released from terminal	DCSA glossary Equipment Gate Out

Tip: If transshipment is involved, treat ETA as provisional until Loaded posts on the outbound vessel.

What to do when ONE tracking seems stuck

Search by BL and container on Cargo Tracking. If nothing moves after cutoff, check the next sailing in Point to Point Schedule or Vessel Schedule.
Subscribe to event notifications in Visibility Service. Use Proactive Notification to get pre alerts when a leg advances or delays.
Use Mail Tracking if portal access is limited.

What could still be confusing: many teams expect a universal refresh clock. ONE does not promise that. Read the next expected actual milestone and act when it appears.