Skip to content
Parcel

Shipment tracking & delivery operations

Every shipment. One clear view.

Track shipments, understand delivery progress, and keep operations moving from pickup to proof of delivery — on one record that the recipient and the depot both read.

Track a shipmentExplore the platform
Facilities
10
Parcels per day
1.8k
On-time rate
96.4%
Regions
5

Live example

PKL-10482

In transit

AldermereKingsmereETA 18 Aug 2026 · 17:00 UTC

  1. Order created

    Sun 16 Aug · 08:20

  2. Picked up

    Sun 16 Aug · 11:20

  3. At origin facility

    Sun 16 Aug · 13:20

  4. In transit

    Sun 16 Aug · 17:20

  5. At destination facility

    Pending

  6. Out for delivery

    Pending

  7. Delivered

    Pending

Demo tracking — no live carrier data.

Open tracking page

Tracking

Track a shipment right now.

Six worked tracking numbers ship with this template. Enter one — or anything else — and see exactly how a hit and a miss are handled.

Tracking numbers look like PKL-10482. Case and dashes are ignored.

Demo numbersPKL-10482PKL-20841PKL-31765PKL-44120PKL-58291PKL-69314

How it works

From a scan to something a person can read.

Four steps turn raw network events into a tracking page that explains itself.

  1. 01

    Every touch is a scan

    Collection, facility arrivals, trunk departures and the delivery round each write an event with a location and a description.

  2. 02

    Scans become a route

    Events resolve to named facilities, so the shipment's path renders as a route through the network rather than a list of codes.

  3. 03

    Status explains itself

    Delays and exceptions sit on the timeline with the reason attached, at the stage where they happened.

  4. 04

    Delivery closes the record

    Proof of delivery captures who received the parcel, where, how, and the condition it arrived in.

Shipment lifecycle

Seven stages, always visible.

A shipment only ever moves forward. Delays and exceptions are raised at the stage where they happened, so the rail shows both where a parcel is and where it stalled.

  1. Order created

    Sun 16 Aug · 08:20

  2. Picked up

    Sun 16 Aug · 11:20

  3. At origin facility

    Sun 16 Aug · 13:20

  4. In transit

    Sun 16 Aug · 17:20

  5. At destination facility

    Pending

  6. Out for delivery

    Pending

  7. Delivered

    Pending

Route

The path, not a pin on a map.

Facilities are real nodes in the network with a name, a code and a role. The route diagram draws the legs a parcel actually travels — completed, active and still to come.

Demo route visualization — not a map, and not GPS.
  1. ALDAldermere Sort Center
  2. VNTVantry Metro Depot
  3. KGMKingsmere Delivery Station

Operational visibility

One record. Two audiences.

The recipient sees the timeline. The depot sees the timeline plus the notes, the actions and the exception queue.

One shipment model

Public tracking and the operations workspace read the same record. There is no second copy to drift out of date.

Actions that actually change things

Advance a stage, flag a delay, raise an exception or complete delivery — the timeline, proof of delivery and dashboard counts all follow.

Built to be replaced

The dataset sits behind one lookup module. Swap it for a carrier API and nothing above it has to change shape.

Services

Five service levels.

Each with its own routing behaviour, scan cadence and proof-of-delivery treatment.

All services

Coverage

Five regions, ten facilities.

Gateways, sort centers, regional hubs, crossdocks and delivery stations — drawn as one network diagram rather than five disconnected lists.

  • North

    2 facilities

    1–3 working days

  • Central

    3 facilities

    1–2 working days

  • Metro

    2 facilities

    Same day – 2 working days

  • Coastal

    2 facilities

    2–4 working days

  • International

    1 facility

    3–6 working days

Coverage & transit times
Illustrative coverage — demo regions and transit ranges.
Full networkScheduled servicePartner delivered

Performance

Measured, not asserted.

Illustrative figures for the demo network. The operations workspace computes the same shapes from the shipment records themselves.

Facilities
10

Across five regions

Daily throughput
389,900

Parcels handled per day

On-time rate
96.4%

Rolling ninety-day average

Lifecycle stages
7

Tracked on every shipment

Who it's for

Built for the people moving the boxes.

Courier and last-mile

Work the exception queue, not the happy path. Failed attempts and safe-place decisions are recorded against the shipment.

Ecommerce fulfilment

Give buyers a tracking page that reads in plain English and works on a phone.

Freight and consolidation

Palletised consignments carry piece counts, weights and gateway clearance on the same timeline.

Network operations

One dashboard for active volume, out-for-delivery queues, exceptions and on-time rate.

Explore solutions

Get started

See it with real demo data.

Six worked tracking numbers, eighteen shipments across ten facilities, and an operations workspace where every control does something.

Track a shipmentOpen the dashboard