Arrive at the customer
For supported delivery-type orders in the customer-arrival phase, the active detail can show Arrived to customer. Use this guide to recognize that pre-action state and distinguish arrival from the separate Delivery complete control.
This source-only procedure stops before either control is selected. It does not change an order to the client arrival target, complete delivery, publish GPS location, notify anyone, or prove that the running service accepts either transition.
Availability
The reviewed arrival control requires:
- an active detail in a supported customer-arrival phase;
- a delivery-type order supported by this flow;
- detail content that is not loading; and
- the current client permission, connectivity, and action-loading state.
The same client phase can also admit Delivery complete, which targets a different completion path. A visible or enabled-looking control is not proof of server ownership, transition eligibility, current location, or deployed behavior.
Before you start
- Confirm that you are reviewing the intended active-order detail.
- Identify Arrived to customer separately from Delivery complete and Delivery Failed.
- Review only visible permission or location-validation warnings.
- Do not change permissions, GPS/location, connectivity, media, PIN, proof, or order state for this guide.
- Stop before pressing any arrival, completion, or failure control.
Mounting the detail can already start API reads, current-location work, location follow/validation, sockets, assets, and provider behavior. A visible map marker or simulator location is not trusted arrival evidence.
Complete the task
The admitted task is a pre-action review:
- Open the current delivery detail.
- Locate Arrived to customer in the order information area.
- Confirm that the detail is not loading and note whether the control is visibly disabled.
- Distinguish it from the separate Delivery complete control.
- Review any visible permission or location-validation issue.
- Leave all action controls untouched and use back once if you are only reviewing the state.
If selected outside this guide, missing local permission routes toward permission guidance. Otherwise the arrival branch invokes client location validation and a target-status request. Delivery complete uses another target and can add media or secure-delivery inputs. Those paths require separate accepted procedures.
Verify the result
The only accepted result is recognition of the current client state:
- the correct detail is visible;
- Arrived to customer is visible, absent, disabled, or accompanied by a prerequisite; and
- no arrival, completion, failure, location, or media action was selected.
Do not verify this guide by looking for an internal arrival or completion status, a customer update, location trail, history record, message, notification, socket event, proof, review, or provider result.
States and variations
| Visible state | Meaning | Safe next step |
|---|---|---|
| Detail loading | Order/detail state has not settled. | Wait for content or error. |
| Supported customer-arrival phase and delivery type | Reviewed source can show Arrived to customer. | Review only. |
| Delivery complete also visible | The completion contract is separately eligible-looking in the client. | Do not confuse it with arrival or press either. |
| Arrival control absent | Effective state, delivery type, loading, or another condition does not admit it. | Do not force a status or route. |
| Control disabled | Loading, connectivity/offline, or another action blocks interaction locally. | Wait or report; do not repeat taps. |
| Permission guidance | Local permission state does not admit the action path. | Use the permission guide; request is not grant. |
| Location-validation warning | Client rules did not accept current location evidence for arrival or completion. | Do not refresh, mock, or change location to force it. |
| Completion media/PIN form | Separate completion configuration requires additional inputs. | Leave it; arrival is not completion. |
| Error or stale detail | The current client/provider result is unusable. | Return once and re-enter from current active delivery. |
Troubleshooting
| What you see | What to check | Safe recovery |
|---|---|---|
| Arrived to customer is missing | Effective state, delivery type, detail loading, and order ownership | Do not use another product or status action to force it. Recheck the active detail once. |
| Delivery complete appears before arrival is recorded | Client visibility rules for completion and arrival are distinct. | Leave both controls untouched and ask the order owner which state is current. |
| Permission guidance appears | The current local permission result did not admit the action. | Use Location permissions; do not infer grant from a prior prompt. |
| Location validation reports a problem | Client freshness, distance, or configured rules rejected the available evidence. | Follow the visible recovery guidance; do not mock or manually change location. |
| A proof, PIN, or media form appears | You entered the separate completion path or its configuration requires additional input. | Leave without entering data and use the complete-delivery guide. |
| An action was pressed accidentally | An arrival/completion/failure request and follow-ons may have started. | Do not repeat it. Escalate immediately with sanitized time and visible state for server reconciliation. |
| The UI changes but the result is unclear | Primary status, location, history, socket, notification, message, proof and other follow-ons are separate. | Stop and let the order owner verify the current result. |
Related guides: Active delivery · Arrive at business · Complete delivery · Location permissions · Navigate the Driver App