Container tracking: understanding statuses and dates

A status describes a particular event

Tracking helps establish what is known about a shipment, but a single label rarely supports a delivery decision. “Arrival” may describe a vessel; “released” may concern a particular documentary release. Check the object, location, date type and data source before drawing a conclusion.

Use the carrier, forwarder or terminal system relevant to the shipment. This article explains how to interpret information; it does not describe a container-tracking feature in Cargexo.

Separate three kinds of dates

DCSA standards distinguish planned, estimated and actual events. Event Structure Definition 2.2, dated 2021, documents that structure. This version is cited to explain the concepts, not to suggest that every current portal implements that version.

Keep separate fields for the baseline plan, latest estimate and update time, confirmed actual event, and source with observation time. An updated estimate does not mean that the event has happened. A message may arrive after the underlying event occurred. Check the time zone before comparing timestamps from different systems.

Follow the right object

Booking, bill of lading and container references may expose different information. A booking can cover several units that do not move simultaneously. If equipment changes, confirm that the identifier being followed still belongs to the shipment.

A vessel position does not establish that a particular container is aboard. Terminal gate-in is not vessel loading. At transshipment, check the port and journey leg: discharge from a feeder does not complete the entire transport.

Read the sequence

A useful history may include empty collection, packing, full gate-in, vessel loading, departure, transshipment, destination discharge, collection and empty return. Not every provider displays every stage, and labels can differ.

For each critical entry, ask what it confirms and what remains unknown. “Discharged” does not automatically establish customs clearance, documentary release or a collection appointment. Conversely, an absent entry does not prove that an operation has not taken place.

Example of a changing estimate

This example is fictional; D1–D6 are successive days. The baseline vessel arrival was D4. On D1, the latest estimate is D5; on D2, it changes to D6. On D6, actual vessel arrival appears, but container discharge has not yet been reported.

Retain D4 as the reference and D6 as the confirmed arrival. Do not record “container available D6”. The next questions concern discharge, availability, required releases and collection. Arrival is two days later than the baseline; the effect on warehouse delivery is still unknown.

Resolve conflicting information precisely

When two portals show different dates, compare meaning, time zone and update time first. One may refer to vessel arrival and the other to container availability. Do not automatically select the earlier date.

Send the forwarder the unit reference, relevant route leg, both messages with observation times and the decision you need to make. “Can I confirm the collection truck?” requires terminal and release information, not just another copy of the ETA.

Connect monitoring to action

Decide which changes require notifying the warehouse, moving a delivery appointment or reviewing charges. Preserve significant estimate changes instead of overwriting every previous date. Mark information as confirmed, estimated or awaiting verification.

“Empty returned” also needs a location, date and receiving confirmation. The end of a visible timeline does not settle every charge. Plan using verified events and clearly identified assumptions, and direct missing-information questions to the party able to confirm them.

A compact handover record