A delivery exception is any deviation from a successful delivery-failed, rescheduled, partial, or refused. Without standardized exception codes, your failed-delivery data is just noise. A consistent code set makes proof-of-delivery workflows, reporting, and dispute resolution comparable across every stop, crew, and store.
Why standardize codes
When one driver writes "nobody home," another writes "couldn't deliver," and a third leaves it blank, you cannot measure or fix anything. Standardized codes turn the messy reality of a delivery day into data you can act on.
A starter exception code template
- Delivered - complete (photo + signature where required)
- Delivered - partial (items short or backordered, noted)
- Failed - customer not available
- Failed - access issue (stairs, gate, no parking)
- Refused - damage
- Refused - wrong item
- Rescheduled - customer request
- Damage reported on arrival (photo evidence attached)
How to roll it out
- Lock the code set so drivers pick, not type.
- Require evidence (photos/notes) on the codes that drive disputes.
- Report failures by code, store, and crew weekly.
- Review the top two reason codes monthly and attack the root cause.
The payoff
Once codes are standardized, patterns surface fast: a single store with high "access issue" failures, or a SKU with repeated damage refusals. You stop guessing and start fixing.
Operator takeaway
Standardize the code set first-everything downstream (POD, reporting, disputes) gets easier. Build it into proof of delivery software and your final mile workflows.