Track and trace systems: designing a status people believe

Events, statuses and the difference between them

An event is a fact recorded at a point in the network: this label was scanned at this location, on this device, by this operator, at this time. A status is an interpretation presented to an audience: in transit, out for delivery, held at customs. Systems that let operators set statuses directly, without an underlying event, produce histories nobody can defend, because the record shows a claim rather than an observation. Keep the event log immutable, derive status from it, and version the derivation rules so historical statuses remain explicable.

Granularity is a service decision with a cost

Every scan point requires a device, a process step and a moment of somebody's time. Networks choose between a light event set, received, in transit, delivered, and a dense one covering each sortation and handover. Denser capture supports better exception detection and stronger chain of custody, but it slows the operation and multiplies data volume. The reasonable approach ties granularity to what will actually be acted upon: an event that never triggers a decision, a claim defence or a customer message is overhead.

Chain of custody and the handover gap

Liability follows possession, and the most contested moments are the ones between parties: a consignment handed to a line-haul partner, a pallet transferred at a hub, a parcel passed to a final-mile subcontractor. Each handover should produce an event on both sides where possible, with quantity and condition recorded. Where a partner will not scan, the practical mitigation is a manifest acceptance record, which is weaker evidence but still better than the silence that otherwise sits at exactly the point where losses occur.

The customer-facing view is a translation, not a mirror

Internal codes are numerous and specific; a recipient wants to know whether the goods will arrive and, if not, why. Mapping many internal reasons to a small set of customer-facing statuses is where operators lose credibility, particularly when a delay attributable to the network is presented in language implying the customer or the authorities caused it. Reason accuracy matters commercially, since enquiry volume falls when the stated reason matches what the recipient can observe. Air movements have long used standardised status vocabularies for this purpose, which is a useful model for anyone designing one.

Frequently asked questions

How does this differ from a visibility platform?

Trace systems record events the operator generates in a network it controls. Visibility platforms aggregate events from parties they do not control and infer a picture from them. The first is an operational record; the second is an interpretation of external feeds.

Should tracking be exposed at item level or consignment level?

Consignment level suits most freight, since that is the unit handled and liable. Item-level tracking is warranted where units are individually valuable, regulated or serialised, and it multiplies both scanning effort and data volume, so it should follow a specific requirement.

What causes most tracking complaints?

Stale or contradictory statuses rather than missing detail. A history that stops for a day without explanation generates more contacts than a sparse but consistently updated one, so exception messaging usually beats extra scan points.