Parcel Tracking & Delivery Platform

The problem

Delivery status existed only in the driver's head until the end of a run. Customers phoned to ask where a parcel was, the office phoned the driver to find out, and proof of delivery was paperwork that arrived days later. Coverage across delivery routes was inconsistent, so any solution that assumed a live connection would fail in exactly the conditions it was needed.

How we approached it

We designed the driver application offline-first: scanning, status changes and proof of delivery are written locally and synchronise when a connection returns. That decision came before any interface work, because retrofitting offline behaviour into an online-only application is effectively a rewrite.

How it is built

A mobile driver application with local persistence and a defined sync and conflict-resolution model, backed by a central shipment service that feeds both the administrative dashboard and customer-facing tracking. Location is sampled at intervals rather than streamed continuously, to protect battery and data.

What shipped

Where it landed

Shipment status is captured at the point of work and visible to the office and the customer without a phone call. Proof of delivery is timestamped and retrievable rather than paper-based, and the driver application continues to function through coverage gaps.