Shipments tracked via webhooks remain active until they are manually removed.
However, because shipment numbers — and especially container numbers — can be reused quickly, we've implemented automatic removal policies to help you avoid receiving data that is no longer relevant (e.g. data from a newer container voyage).

When do we automatically remove shipments?

We currently auto-remove shipments in the following cases:

1. Shipment delivered and inactive for over 7 days

We automatically remove shipments that meet all the following conditions:

The shipment's shippingStatus is DELIVERED
A Proof of Delivery (POD) is detected in the data
All container events are at least 7 days old

⚠️
Important: If no POD is detected, the shipment will not be removed automatically.

Some examples:

A shipment stuck in IN_TRANSIT by the shipping line will not be auto-removed.
If we receive a new event dated 3 days ago, we will continue tracking the shipment for at least 4 more days.

2. A new voyage is detected

We will also remove shipments if we detect that a new voyage has started, based on the following:

The new POL (Port of Loading) date is later than the previous POD (Port of Discharge) date, and
The new POL LOCODE is different from the previous POL LOCODE (or both are null), and
The new POD LOCODE is different from the previous POD LOCODE (or both are null)

This helps ensure that you only receive data related to the current voyage, and not outdated or unrelated shipment activity.

Why this policy exists

These auto-removal rules are not designed to limit your shipment tracking time or reduce billing.
They are here to prevent you from receiving webhook updates from future, unrelated voyages using the same shipment or container number.

You can always monitor your tracked shipments using:

GET /easy_shipment

And remove them manually with:

DELETE /easy_shipment