Arrive at the business
For delivery-type orders in the reviewed business-arrival states, the active order detail can show Arrived to business. Use this guide to identify that pre-action state and its permission, location-validation, connectivity, and media boundaries.
This source-only procedure stops before the control is selected. It does not change the order, publish location, capture an image, notify anyone, or prove that the running service would accept the transition.
Availability
The primary reviewed visibility condition is a supported business-arrival phase for a delivery or catering-delivery flow and a detail that is not loading. A derived pickup-phase state can also affect visibility, but it is not a portable status guarantee.
The control can be disabled while the order or another order action is loading, or when the current connectivity/offline boundary does not allow an action. Visibility and enabled appearance do not prove permission completeness, location validity, server eligibility, or current order state.
Before you start
- Confirm that the correct active-order detail is visible.
- Confirm only that the visible effective state and delivery type present Arrived to business.
- Do not change device permissions, location, order status, connectivity, or media state for documentation or troubleshooting.
- Stop before pressing Arrived to business.
Opening the delivery detail can already start location follow/watch, current- location reads, validation checks, API reads, sockets, remote assets, and other provider work. A simulator or visible map does not make the flow hermetic.
Complete the task
The admitted task is a pre-action review:
- Open the current delivery detail from Driver App.
- Locate the Arrived to business control in the order information area.
- Verify that the detail is not loading and that the control is not visibly disabled.
- Review any visible permission or location-validation warning.
- Leave the control untouched and use back once to return if you are only reviewing the state.
The actual arrival mutation requires a separately accepted action procedure. Depending on local state and configuration, selecting the control can redirect to permission guidance, open an image/action form, run location validation, or request a status change. None of those outcomes is verified here.
Verify the result
The only accepted result is recognition of the current client state:
- the correct detail is visible;
- Arrived to business is visible or its prerequisite/disabled state is observable; and
- no action was selected.
Do not verify this guide by checking for a changed status, location trail, notification, message, socket event, image, report, customer update, or other follow-on effect.
States and variations
| Visible state | Meaning | Safe next step |
|---|---|---|
| Detail loading | Order/detail data is not ready. | Wait for content or error. |
| Supported business-arrival phase and delivery type | The reviewed source can show Arrived to business. | Review only; do not press in this source-only lane. |
| Pickup-phase-derived visibility | Client stage derivation also exposes the arrival/pickup area. | Do not infer an exact server status from the presentation. |
| Control absent | Effective state, delivery type, loading, or another condition does not admit it. | Do not force a route or status. |
| Control disabled | Loading or connectivity/offline state blocks interaction locally. | Wait or report; do not repeatedly tap. |
| Permission guidance | The current local permission result 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. | Do not refresh or change location to force the action. |
| Image/action form | Configuration requires an additional pre-submit state for the target status. | Leave without capture; media and submission are separate. |
| Error or stale detail | The current data/provider state is not usable. | Return once and re-enter from the current active-delivery list. |
Troubleshooting
| What you see | What to check | Safe recovery |
|---|---|---|
| Arrived to business is missing | Effective state, delivery type, detail loading, and current order ownership | Do not edit status or use another product to force it. Recheck the current active detail once. |
| The control is disabled | Connectivity, order loading, or another action is still in progress locally. | Wait for the visible state to settle; do not use offline replay as a workaround. |
| Permission guidance appears | The app's local permission gate did not admit the action. | Follow Location permissions; do not infer the effective grant from a prior prompt. |
| Location validation reports a problem | The client rejected freshness, distance, or other configured location evidence. | Follow the visible recovery guidance; do not mock or manually change location. |
| An image form appears | The configured target status requires media in the client path. | Do not capture/upload media in this guide. Leave the form and use the governed media/status procedure. |
| The control was pressed accidentally | A status request and follow-on effects may have started. | Do not press again. Escalate immediately with sanitized time and visible state so the order owner can verify the server result. |
| The UI changes but the result is unclear | Client state, primary status write, location, history, socket, notification, and other follow-ons are separate. | Stop and let the order owner reconcile the current state. |
Related guides: Active delivery · Complete pickup · Location permissions · Navigate the Driver App