Goal
Explain code-based proof of delivery.
Who it is for
Drivers, dispatchers, and operations managers.
Expected result
Delivery is moved into proofed state and proof details are visible in mission or route history.
Prerequisites
Steps
01
Use code-based proof
Rouptimize public docs should describe 5-digit customer code verification only.
02
Verify from mobile
Driver enters the customer code from the mobile mission flow after delivery work reaches a proofable status.
03
Review proof details
Dispatchers can inspect proof sent-to, SMS, expiry, attempts, and verified time where available.
Field definitions
Troubleshooting
Code is incorrect.
Code expired.
Mission status is not proofable.
Driver is not assigned to the mission.
Screenshots to capture
Use anonymized product data. These are screenshot requirements for the final docs pass.
docs-mobile-proof-code-entry.png
Mobile proof code entry.
docs-mobile-proof-success.png
Proof success state.
docs-mobile-proof-error.png
Incorrect or expired code state.
docs-route-details-proof-fields.png
Proof fields in route details.
docs-mission-details-proof-history.png
Proof details in mission history.
Related product pages
Related tutorials
Need to try it with your own route data?