Complete a delivery
Use Delivery complete only after you have handed the order to the customer and reviewed every requirement shown by the Driver App. The available steps can vary by order stage and project configuration.
Availability
Delivery complete can appear in Order details when the delivery has reached an eligible in-progress or customer-arrival stage. A project-specific rule may keep it hidden until a later arrival stage.
The action can also be unavailable while the order is loading, while another status change is in progress, or when the app reports that status changes are not available offline. The presence of the button does not prove that location permission or location validation is complete.
Before you start
Confirm that you have the correct order and that the handoff has actually happened. Selecting the final Delivery complete button sends a status change that can affect order history, tracking, reports, messages, notifications, and other operational views.
If the app shows a photo or code requirement, complete only the fields shown for this order. Do not reuse another delivery's photo or share a code in chat, support notes, or screenshots.
Complete the task
- Open the active order in Order details.
- Review the customer and delivery information.
- Select Delivery complete.
- If the app opens Request permissions, review the permission request and return to the order when ready.
- If Requirements Not Met appears, review each listed location issue. Use the offered refresh or Settings action when appropriate, then recheck the order.
- If Upload status image appears, take the required photo and review its preview. Select Remove image if you need to replace it.
- If Security code appears, complete the visible field according to your organization's delivery policy.
- Select the final Delivery complete button once.
When neither a photo nor a code field is configured, the first Delivery complete selection can be the submission boundary. When either field appears, the modal's final button is the submission boundary.
A completed Security code field is an app-side prerequisite in the reviewed source. It does not, by itself, prove customer authorization or server-side validation. Follow your organization's exception process if the handoff cannot be verified.
Verify the result
A button press proves only that the Driver App attempted the status change. Wait for loading to finish, then refresh or reopen the order and verify that it is no longer presented as an active delivery before moving on.
A photo upload, location trail, order message, report, realtime event, or notification can settle separately from the primary status request. Do not use one of those follow-on signals as the only proof that the delivery was recorded.
If the result is unclear, do not press Delivery complete repeatedly. Refresh the order and ask a dispatcher to verify its current status.
States and variations
| What you see | Meaning | Safe next step |
|---|---|---|
| Delivery complete is not shown | The order, project, or current stage does not expose the action | Review the latest order state; do not force a later status |
| Request permissions opens | The app's permission gate did not pass | Review the request, then return to the order |
| Requirements Not Met | A configured location check reported one or more issues | Review the listed issue and use the offered recovery action |
| Upload status image | This status is configured to require a photo | Capture and review the correct delivery photo before submitting |
| Security code | This project shows an additional app-side field | Follow organizational policy; do not treat the field alone as authorization proof |
| The final button is disabled | A required photo, code, loading state, or other visible prerequisite is unresolved | Complete the visible requirement or stop and report the issue |
| An error appears or the order remains active | Completion was not confirmed in the app | Refresh once and verify the current status with a dispatcher |
| A grouped order is shown | Member orders can have independent state and effects | Verify each visible member; do not assume one action completed the group |
Troubleshooting
- If location cannot be refreshed, keep the order active and follow the app's Settings guidance. Do not enter or share coordinates manually.
- If the customer location is missing or the app reports that you are outside the allowed area, do not bypass the standard action. Use your organization's documented exception process.
- If the camera is unavailable or the image is rejected, do not substitute an unrelated image. Keep the order active and report the capture problem.
- If the code field cannot be completed, do not guess, reconstruct, or disclose a code. Escalate the delivery according to organizational policy.
- If connectivity changed during submission, reconnect and refresh the order before deciding whether any retry is needed.
Related guides: Driver App overview · Accept a delivery request · Understand startup and loading