Tracking
Это содержимое пока не доступно на вашем языке.
Each container or RORO trip has a physical lifecycle separate from the trader’s view of “where is my car.” Tracking shows both.
Container statuses
Section titled “Container statuses”| Status | Meaning |
|---|---|
booked | Forwarder confirmed the booking. |
loaded | Cars physically loaded into the box at the origin terminal. |
cut | Container reached the cargo cut-off; cannot add more inside. |
released | Released to the carrier for loading onto the ship. |
at_sea | On the vessel, between ports. |
arrived | Container reached the destination terminal. |
cleared | Customs cleared (import permit issued). |
delivered | Released to the consignee or CFS for unloading. |
RORO uses a similar but slightly different set (no “loaded into a box” phase).
Auto-propagation to cars
Section titled “Auto-propagation to cars”When a container or RORO trip is marked arrived, the platform finds every linked car still in shipped status and bulk-advances them to arrived. The car’s locationId is also set to the container’s destinationLocationId if one was picked at booking time.
This is the only place container status auto-bleeds into car status. Earlier statuses (loaded, cut, released) are tracking-only; they don’t move cars.
Timeline view
Section titled “Timeline view”Open a container detail to see the <ShipmentJourney> widget — a horizontal timeline of every status event with timestamp, who triggered it, and a free-text note. Useful for “when exactly did this clear customs?” disputes.
Manually editing status
Section titled “Manually editing status”You can manually advance status (forwarder side) if a tracking integration didn’t fire — open the container, click the next-status button. Skipping ahead works (booked → arrived) but emits a single event covering the gap.