Case study

A delivery tracking app

Routebay · Manchester, UK

We built a tracking product around the scan feed the depot already produced: collected, in transit, out for delivery, delivered, and exception codes the carrier already used.

Angular.NETAzureMaps APIMobile web

Discuss a similar brief

Location: Manchester, UK
Duration: 5–7 months
Industry: Logistics
Project type: Mobile development

About the client

A regional parcel carrier in the North West (one depot, roughly forty vans on a weekday) already scanned pickup, hub and delivery on handhelds. Consignees still rang the depot to ask where a parcel was. Ops answered from a different screen than the driver had just used.

Replacing the handhelds was out of scope. The brief was a customer track page and an ops view that both read the same scan events, plus a named contact path when a stop fails.

Project overview

We built a tracking product around the scan feed the depot already produced: collected, in transit, out for delivery, delivered, and exception codes the carrier already used.

Public side: tracking ID, status timeline, map of the last known scan, ETA only when the round plan can supply one. Ops side: the same history, with a route to the desk that owns the round when a stop fails.

Technologies

Angular.NETAzureMaps APIMobile web

Duration

5–7 months

What we shipped

Mobile development

Page screenshots

1 / 3

Functionality

Tracking by consignment ID from a short link or printed label
Live status from handheld scan events, not a separate spreadsheet
Map of the last known scan and ETA only where the round plan supports it
Operations view of the same history the customer sees
Named contact path to the round desk when a stop fails

Solution

Scan events land in one store. The customer page and the ops desk read that store — there is no second “where is it” sheet.
ETA is shown only when the carrier’s round plan has a window; otherwise the page shows status and last scan without inventing a time.
Failed stops open a contact path to the desk that owns that round, not a generic depot inbox.
First release was mobile web so customers and the desk did not wait on store review. Native wrappers stayed optional for a later phase.

Project results

Depot “where is my parcel” calls fell once tracking links went on labels and confirmation emails.

Ops and the customer argue from the same scan history.

Failed stops reach the round desk instead of a shared inbox.

Map and ETA appear only where the carrier can actually support them.

Customer review

“Customers check a tracking ID instead of ringing the depot. Operations sees the same scans, so we are not arguing about two versions of the truth.”
Mr. Matt W., Operations lead, Manchester, UK

Next step