Evergreen container statuses: how bexy reads them

Where the status comes from

Evergreen's tracking record lists every container on the Bill of Lading with its current status and that status's date, for example On Board Vessel or Discharged (Full). bexy shows each status exactly as Evergreen words it, as bexy last read the record.

The record shows each container's current status only, so an earlier event such as a discharge stays visible only until the container moves on.

How bexy reads a status

Arrived at the port of discharge

A discharge that names the port of discharge, or names no place at all, as in Discharged (Full); only one that names the port can date the shipment's actual transit. A status after the sea leg that names the port of discharge counts too: a despatch, departure, arrival, receipt or unloading there, such as Despatched by rail from VANCOUVER, BC (CA) on a Bill of Lading discharged at Vancouver.

Arrived at the place of delivery

The same kinds of status naming an inland place of delivery beyond the port: the container arriving, received or unloaded there, or discharged there.

Delivered

A status reporting a delivery, a full container's pick-up or gate-out, merchant haulage, devanning or unpacking (also written destuffing, unstuffing or stripping), or an empty container returned or gated in. The cargo has left the carrier's hands.

Neither

A transshipment discharge (Transship discharged …) at an intermediate port; a discharge that names another port; loading and on-board statuses such as On Board Vessel; an empty container's pick-up or gate-out, which happens at origin before loading (MTY is the carrier's short form of "empty"); and a receipt, pick-up or gate-out at the port of loading or place of receipt, such as Received at QINGDAO, CHINA (CN), which is the export side.

Scheduled, In transit, Arrived, Delivered

The badge at the top of a tracking page reads Scheduled until the loaded-on-board date. After it, the containers decide first: Delivered when a container reports a delivery, Arrived when one reports an arrival. Otherwise the dates decide: In transit until the estimated arrival and Arrived once it has passed, unless that date is a transshipment call, which is no arrival; Departed when the record has no arrival date at all.

A badge that rests on the dates alone carries "(by schedule)" until Evergreen's own data backs it: In transit once the page's "Carrier data as of" date (the last reading that changed bexy's copy of the record) or a container event is dated on or after the loaded-on-board date; Arrived only once a container event is dated on or after the arrival date. On the voyage route, the stop the dates point to carries the same mark: at the place of receipt or the port of loading it reads "Departed (by schedule)", then "Departed"; at a later stop, "Expected position (by schedule)" until a container event is dated on or after that stop's date, then "Current position".

Why so many records end on an empty return

For most Bills of Lading bexy first reads Evergreen's record after the container has been returned empty, so the latest status it holds is often from after the empty return, and the discharge before it is no longer shown.

In the current data, 19,656 of the 777,484 shipments on the 252 published trade lanes (3%) carry a recorded discharge at the port of discharge that actual transit can be measured from.

When bexy reads the statuses again

bexy reads the statuses again whenever it re-checks the shipment: after its estimated arrival, while someone watches it for email alerts, or when someone searches for it. Re-checks after the estimated arrival stop once a container's status reports the shipment at its final destination — delivered, or arrived at the place of delivery (for a shipment that ends at the port, discharged there) — or 30 days after the estimated arrival if none does.