Review order details
Order detail brings the available order information into one authenticated screen. Depending on the returned data and configuration, it can show a header, business and customer sections, custom fields, products, comments, bill lines, payment events, spot or vehicle information, and controls for maps, messages, contact, review, assignment, or delivery status.
This overview is viewing-only. A visible field or control does not prove that the data is current, complete, safe to share, authorized for another action, or confirmed by the running service.
Availability
Order detail can open from a registered order card, history card, logistics request, in-app notification transition, or supported opened-push target. The route and current authenticated state must supply an order or an order reference that the detail controller can use.
The result varies by order type, status, grouping, logistics state, configuration, payment data, permissions, platform, connectivity, lifecycle, and provider availability. Navigation to detail does not prove that its reads succeeded or that the Driver remains eligible for a visible action.
Open this capability
- Open the relevant order from its current Driver App list.
- Wait for the detail to show content or an error instead of the loading placeholders.
- Verify the masked or configured order reference and visible status in the header before reading further.
- Expand Custom fields, Business details, or Customer details only when you need that information for the current delivery.
- Review Order Details for comments and product items.
- Review the bill and payment-event presentation as display data only.
- Leave map, message, contact, review, assignment, status, media, PIN, proof, and provider controls untouched unless you are following their dedicated accepted guide.
Use the header back control once to return to the previous Driver App screen. Returning does not cancel or reverse any request that might already have started.
What drivers can understand
| Area | Information that can appear | Boundary |
|---|---|---|
| Header | Masked/configured order reference, visible status, delivery position, order type, payment method, placed/delivery time, and type-specific fields | Status, payment, time, and priority presentation are not currentness or settlement proof. |
| Custom fields | Returned key/value pairs | Values can contain private operational data and are not globally standardized. |
| Business details | Available name, email, phones, address, notes, location-derived distance, and external map/contact links | Visibility is not permission to contact, share, or open a provider. |
| Customer details | Available identity, rating, contact, address, notes, delivery option, and related fields | Treat all values as private; participation and contact authorization are separate. |
| Order Details | Order comment and expandable product items with options and prices | It is not a cart editor, reorder flow, or proof that items were fulfilled. |
| Bill | Subtotal, discounts/offers, taxes, fees, delivery fee, tip, total, and available payment events | Display does not prove payment capture, cash handling, payout, refund, settlement, or accounting correctness. |
| Spot or vehicle | Type-specific spot and available vehicle fields | These fields are operational context, not verified identity or ownership. |
| Conditional controls | Back, map, messages, copy/contact, review, arrival/pickup/delivery, accept/reject/failure, or other status controls | Each control has separate prerequisites, requests, effects, and failure states. |
Grouped and logistics details can render member orders differently from an ordinary detail. Never assume that one group's fields, status, bill, or action apply atomically to every member.
States and variations
| Visible state | Meaning | Safe next step |
|---|---|---|
| Loading placeholders | Detail and related reads are still settling. | Wait for content or error. |
| Populated ordinary detail | Current client result contains one order. | Review only the necessary sections. |
| Grouped/logistics detail | The result contains group or assignment structure. | Keep member outcomes and controls separate. |
| Error/not found | The controller did not produce usable detail. | Return to the current list; do not open a private route. |
| Section collapsed | Optional/sensitive fields are hidden from the current view. | Expand only when needed, then avoid copying/sharing. |
| Missing optional field/logo/image | Returned data or asset is unavailable. | Use remaining context; do not invent or fetch private data elsewhere. |
| Payment lines absent/present | The current result has no/available payment events. | Do not infer unpaid/paid/settled state from presence alone. |
| Conditional action visible | Client status/configuration/permission logic rendered it. | Use the dedicated task guide; visibility is not eligibility. |
| Data changes after reconnect/realtime | A later read/event updated the client state. | Reverify the visible detail without assuming which event won. |
Troubleshooting
| What you see | What to check | Safe recovery |
|---|---|---|
| Detail stays loading | Connectivity, current session, source list state, and related detail/business/message reads | Return once and reopen from the current list. Do not repeat an order action. |
| Detail shows an error | The order may be unavailable, unauthorized, changed, or the read failed. | Return to the list and report the visible error class without order or account data. |
| Header and body disagree | Different client fields or later realtime/read state can settle independently. | Stop before actions and let the order owner verify current server state. |
| Contact, address, or custom data looks wrong | Detail displays returned operational data and optional fields. | Do not correct it through another product; report only the field category, not the value. |
| Bill or payment lines look unexpected | Display calculations, configuration, currency, and payment-event data have separate owners. | Do not collect, refund, settle, or infer payout from the screen; use the payment contract. |
| A map, message, review, or status control appears | Client visibility rules admitted the control. | Leave it untouched and use the dedicated guide before any handoff or mutation. |
| Group members differ | Member reads/statuses/effects are not guaranteed atomic. | Review each visible member and escalate; do not normalize the group manually. |
Related guides: Active delivery · Delivery history · Cash orders · Delivery map · View order conversations