Logistics & Transportation
Logistics Shipment Tracking And Enquiry Portal
A customer asking where their shipment is is not making a complaint, they are asking a question. Most logistics portals fail them twice: they show nothing useful, and they make the customer open a ticket to get an answer they were entitled to.
The portal was built so that the common question has a direct answer, using whatever the carrier exposes about the consignment. Where the carrier data is delayed or missing, the page says so plainly and gives a route to a person, rather than showing a blank status that looks broken.
Enquiries are routed by consignment rather than by general enquiry, so the team sees the tracking history alongside the message and does not have to ask the customer for a reference number they should never have needed. Partner access is separate from customer access, with different permissions and a different audit trail.
Carrier integration was the hard part. Each carrier exposes different webhook formats, different reference schemes and different ideas about how often to poll, so the normalisation layer was written once and tested against each provider separately.
Testing included the failure paths: a carrier returning nothing for a day, a consignment that sits in transit for longer than expected, and a webhook arriving out of order.
Handover included the mapping table for every carrier connected, which is the document needed when a carrier changes its format.
A customer asking where their shipment is is not making a complaint, they are asking a question. Most logistics portals fail them twice: they show nothing useful, and they make the customer open a ticket to get an answer they were entitled to.
The portal was built so that the common question has a direct answer, using whatever the carrier exposes about the consignment. Where the carrier data is delayed or missing, the page says so plainly and gives a route to a person, rather than showing a blank status that looks broken.
Enquiries are routed by consignment rather than by general enquiry, so the team sees the tracking history alongside the message and does not have to ask the customer for a reference number they should never have needed. Partner access is separate from customer access, with different permissions and a different audit trail.
Carrier integration was the hard part. Each carrier exposes different webhook formats, different reference schemes and different ideas about how often to poll, so the normalisation layer was written once and tested against each provider separately.
Testing included the failure paths: a carrier returning nothing for a day, a consignment that sits in transit for longer than expected, and a webhook arriving out of order.
Handover included the mapping table for every carrier connected, which is the document needed when a carrier changes its format.
- Industry
- Logistics & Transportation
- Category
- API Integration, Customer Portal
- Project type
- Web application
- Project date
- 2025-05
Technologies
Project highlights
- Direct answers to consignment status queries rather than a ticket
- Partner access separated from customer access, with separate permissions
- Carrier webhooks normalised through a single integration layer
- Enquiries routed by consignment with tracking history attached
- Tested against delayed, missing and out-of-order carrier data
- Carrier mapping table included in handover
