Last updated

Shipment Lifecycle

This page provides an overview of the shipment lifecycle for ocean shipments in Project44's visibility solution. It explains how and when we initiate tracking shipments, the different statuses that can occur during the lifecycle, and how we handle updates from ocean carriers.

When Does P44 Initiate Tracking?

Project44 initiates tracking only when all the following conditions are met:

  • The ocean carrier is in the project44 network. See the Appendix for the complete list.
  • The shipment has the required identifiers (see Create a Shipment).
  • Any required internal configurations are in place for the ocean carriers you wish to track.

Internal Configuration Details

  • Some ocean carrier connections are open by default; others require configuration to enable data retrieval.
  • Configuration may involve setting credentials, endpoints, or other access parameters.
  • Contact your Project44 representative or support to ensure necessary configurations are enabled for your target carriers.

How to verify initiation:

  • Look for the TRACKING_INITIATE event in the /getshipmenteventhistory response.
    • A dateTimes entry with source = P44 and a sourceIdentifiers entry of CARRIER_SCAC indicates initiation for the carrier.
  • The latest shipment state at this point is typically SCHEDULED.

When Does P44 Start Tracking?

Project44 starts tracking shipments when at least one update is received from the ocean carrier.

How to verify start:

  • Look for the TRACKING_START event in the /getshipmenteventhistory response.
    • A dateTimes entry with source = P44 and a sourceIdentifiers entry of CARRIER_SCAC indicates tracking started on the carrier connection.
  • The latest shipment state will be IN_TRANSIT or AT_STOP depending on the latest update.

More on the shipment states:

  • IN_TRANSIT indicates that the shipment is on the move, meaning it has departed from a stop. Events like DEPARTURE_FROM_STOP, GATE_OUT_EMPTY, or GATE_OUT_FULL would trigger this state. More information on the events mentioned can be found in the $.event schema guide.
  • AT_STOP indicates that the shipment is currently at a stop and is not moving. Events like GATE_IN_FULL or ARRIVAL_AT_STOP would trigger this state. More information on the events mentioned can be found in the $.event schema guide.

When does P44 Stop Tracking?

Project44 stops tracking shipments because of one of the following reasons:

  • A terminal event has occurred, such as the shipment being delivered or empty container being returned.
  • The container shipment has been removed from the booking.
  • The shipment has been manually ended by the user.
  • The shipment has received a warning event which prevents the shipment from further tracking. For more details see the Appendix for descriptions of Warning Event Type.
  • The shipment has not received any updates for a certain period of time.
    • The shipment remains incomplete 180 days after its creation.
    • No updates are received for 90 days in the push model.
    • No updates are received from the carrier for 60 days in the pull model.

How to verify stop:

  • Look for one of these events in /getshipmenteventhistory response: TRACKING_STOP, TRACKING_END_BY_USER, TRACKING_END_DUE_TO_TIMEOUT or REMOVE_FROM_BOOKING.
    • A dateTimes entry with source = P44 and sourceIdentifiers = CARRIER_SCAC indicates stop on the carrier connection.
  • The latest shipment state will be COMPLETED.

For more schema details, see:

Previous page
Next page