Logistics · 11 / 20
Multi-courier scan normalisation
Every courier's own status codes, mapped into one comparable set.
What actually changes
Compare courier performance apples-to-apples instead of five vocabularies you can't line up.
Five couriers report status in five different vocabularies, so nobody can compare on-time performance across them.
See every courier's raw status mapped into one common set instead of five
Spot exceptions classified automatically instead of manually reading through raw scan text
Compare true on-time percentage across couriers on equal terms
What was built
A raw-to-unified status map with an exception classifier and on-time % per courier.
Result
9
unified statuses, all couriers
The mechanics
How this actually runs, step by step.
- 1Each courier's raw scan feed arrives in its own status vocabulary.
- 2A mapping table translates every raw code into one of nine unified statuses.
- 3Statuses tagged as exceptions get an exception class (address issue, refused, lost, etc).
- 4Once normalised, on-time % and exception rates are comparable across couriers for the first time.
Status mappingException classesOn-time %