Shipment statuses — nine stages and why you see four

Every event reported by a carrier is assigned to one of nine internal stages. There are hundreds of carrier codes, but only nine stages — these are what carry meaning.

Step by step — find out where a parcel really is

1. Find the parcel in Warehouse and logistics → Tracking.
2. Look at the Latest status column, but do not stop there. This column knows only four labels: Initial, Pending, Final success, and Final failure. Every other stage — including the common “In transit” — is displayed as No data.
3. The Latest status filter above the table has exactly the same four options. You cannot filter parcels in transit with it.
4. Click the number in the Order ID column. The order opens.
5. Scroll to the Shipments card, expand the shipment row, and click the parcel number.
6. Read the Tracking history section — it is the only place with the full journey. Each row has a stage badge, a date in DD.MM HH:mm format (without the year), and the raw carrier status name.
7. Milestones appear above the history: First carrier scan, Transit, Delivery, and Return. Only milestones that actually occurred are shown.
8. If the carrier did not provide full history, you will see one entry and the note Showing current tracking status. Full carrier history is not available for this shipment. This is not a system error.
9. When speaking with a customer, use the labels from the order card: Sent, Accepted by carrier, In transit, Waiting for recipient, Delivered, and Problem. If stage data is unavailable, the card shows No data, just like the list.

First trap: it is the highest stage, not the latest one

The Latest status column does not show the latest event. It shows the highest stage this parcel has ever reached.

The consequence is specific: once a parcel is marked delivered, it will never show a lower stage again. If the customer did not collect it and it came back, or it was sent again, this list will still show “Final success”.

This is deliberate — a temporary status downgrade from a carrier should not erase the fact that delivery occurred. When investigating a problem, however, use the history on the order card to assess what is happening now, not this column (Shipment on the order card — full history and actions).

Second trap: five stages appear as “No data”

The shipment list recognises only four stages: 0, 50, 100, and 200. Stages 10, 20, 30, 40, and 60 have no label there and appear as “No data” — even though the parcel has a valid status known to the system.

The most painful case is 60 — In transit, the most common state for a parcel on its way. On the shipment list it looks like missing information.

These five stages also cannot be selected in the Latest status filter.

Third trap: two screens, two sets of labels

The order card uses different descriptive labels from the shipment list:

The same parcel, two different descriptions. When speaking with a customer, use the order card — its labels are closer to what the customer sees on the carrier’s site.

Stage numbers are not chronological order. Carriers use 50 for a parcel waiting for its recipient: it is in a parcel locker or pickup point, or the courier could not reach the recipient. This happens after stage 60 (in transit, out for delivery). Until 24 September 2026, the order card and order list had these two labels swapped: a parcel in transit appeared as “At pickup point” (order 1366944).

The order card and the carrier status column on the order list show the carrier’s latest event, not the highest stage. A parcel that arrives at a parcel locker moves from In transit to Waiting for recipient. Carrier notifications at stage 0 (for example, “SMS sent”) do not move the parcel back to Sent. The Carrier status filter on the order list searches by the same value.

A parcel in a locker has not been delivered yet

A parcel arriving AT a pickup point or parcel locker is not a delivery. Delivery means the customer has collected it. Until then, the parcel is still in Waiting for recipient, not Delivered.

Previously, for several carriers, arrival at a pickup point was treated as the end: Final success. This had three effects at once:

• the order showed Delivered even though the parcel was still in a machine;
• the Parcel delivered automation ran too early;
• the system stopped polling the carrier, so it never learned about actual collection, expiry of the holding period, or a return.

This affected ORLEN (In Transit to Kiosk), DPD (Accepted at Pickup point, Delivered at Pickup point), DHL (recipient decision: alternate address), and InPost (a courier collecting the parcel from a POK). ORLEN was worse: Collected by Customer counted as Problem, so a collected parcel looked like a refusal.

Two other things changed at the same time:

• An unknown code no longer ends tracking. An unrecognised code remains Pending and the parcel continues to be polled.
• A parcel with a final status is polled for another 3 days (every 6 hours), counting from the carrier’s final event and subject to the 30-day limit from parcel creation. This reveals a mistaken mapping instead of silently closing the case.

Non-collection and refusal do not end tracking with InPost, DPD, DHL, or Packeta. The stage immediately becomes Final failure because expected returns and matching the parcel when scanned into the warehouse depend on it. The system keeps asking the carrier until it reports a return or 30 days pass from parcel creation. Without this, a return could never appear in history (see missing shipment status update).

If a branch scan and a return event have the same date, the order card shows the final return event as the current status and places it higher in the history. When the dates differ, event time decides, not the stage number.

An old parcel can suddenly change status. If shipment tracking is stuck, ask NOXTI support to check it. Once polling is restored, the status may update. Notifications and automations for earlier stages are not replayed retroactively.

What happens when a status changes

Every actual stage change — not every carrier poll — sends an event to the workflow system. Automations such as “send an SMS when a parcel goes out for delivery” rely on it. The event carries both the carrier code and the internal status name.

An unknown carrier code is not an error

If a carrier sends a code the system does not recognise, the parcel is assigned stage 50 (Pending) — silently, without a warning. You will not see a signal that the code is unknown; you will see ordinary “Pending”.

See Status dictionaries — external, internal, and mapping to learn where the codes come from and who can change their meaning.