Review an order before taking action

Open an order to confirm who and what it affects before changing its status or using an external action. The order view combines information from the loaded order, additional reads, and realtime updates, so verify freshness and scope instead of treating every visible field as current or universally available.

Before you start

• Sign in to the intended project and business scope.
• Open Orders, then select the intended order card. On a wide tablet, match the selected card on the left with the detail on the right.
• Restore connectivity and refresh the queue when the order is time-sensitive.
• Treat customer contact, address, payment, and fulfillment information as private operational data. Share or copy it only through an approved workflow.

What the order view can show

Area	What to verify	When it appears	Safe next action
Order header	Order number or configured external ID, current status, order type, payment method, and scheduled or placed time	When the order loads successfully	Match the order and status to the task you intend to perform.
Business details	Business identity and available contact, address, or location information	When corresponding fields are present	Confirm that the order belongs to the intended business.
Customer details	Available name, contact, address, delivery option, and prior review information	When corresponding fields are present	Use only the information needed for fulfillment.
Order Details	Products, quantities, options, comments, and configured item details	When the order contains items or a comment	Review substitutions, options, and comments before preparation.
Totals	Subtotal, discounts, taxes, fees, delivery fee, driver tip, and Total	When the order has a nonzero visible total	Verify the displayed breakdown; do not infer a payment action from it.
Payments	Recorded payment events, methods, wallet labels, or cash-related amounts	When payment data exists	Interpret the information only; the order view does not establish payment execution or refund support.
Fulfillment information	Delivery, pickup, eat-in, curbside, drive-thru, reservation, catering, spot, vehicle, driver, or map details	Only for applicable order data and configuration	Follow the visible fulfillment type and current status.

Fields are conditional. A missing section can mean that the order does not use that feature, the data was not returned, the signed-in scope does not include it, or the current source and deployed service do not match. It is not proof that the information never exists.

Understand available actions

The actions around an order depend on its status, fulfillment type, project configuration, device capabilities, and account scope.

• Pending orders can expose Accept and Reject.
• Later states can expose fulfillment actions such as Ready for pickup or pickup completion outcomes.
• Eligible delivery orders can expose Assign driver.
• The header can expose map and message actions. Copy and ticket-summary actions appear only in eligible non-pending states.
• A completed order can expose Review customer when no review exists.

Each action has its own effect and acceptance contract. Review the exact order and use the dedicated procedure before mutating status, assigning a driver, sending a message, copying customer data, opening a map, or producing output.

Check freshness and ownership

Opening an order can use the order already loaded in the queue or request the order by its identifier. The detail can also receive later order, driver, and message events. These paths do not guarantee a single atomic snapshot.

• Match the order number and business before acting.
• Treat an update notice as a reason to review the order again, not as proof that every amount or related section refreshed.
• If totals or status affect the decision, return to Orders, refresh, and reopen the order.
• If an expected order is unavailable, the service can reject the read because of account or business scope. Ask the project administrator to verify scope; do not use another customer's or business's information.

Verify the result

The intended order number and business match the selected card, the visible status and fulfillment type match the planned task, and the item and total information has been reviewed after an appropriate refresh. No mutation is verified merely by viewing the order.

Limits and variations

• Phone and narrow layouts open a dedicated order page. A wide tablet shows the selected order beside the list.
• Customer, payment, map, driver, message, copy, print, and review controls are conditional. Their visibility does not prove authorization, provider availability, or successful execution.
• Realtime events can update parts of the local order while other values remain from the earlier read. Refresh when accuracy matters.
• Visible payment information is informational. No native payment or refund execution is established by this article.
• Source establishes intended reads and business ownership checks, but the deployed Business App and API relationship is not attested.

Troubleshooting

What you observe	Likely boundary	Safe next action
Loading placeholders remain	The order or a related read has not completed	Wait once, then return to Orders, restore connectivity, and reopen the order.
Network Error or another error appears	The order read failed or the account cannot access it	Return to Orders, refresh, and ask the project administrator to verify business scope if it persists.
The tablet detail does not match the selected task	The selected card changed or the list and detail are out of alignment	Match the order number and business on both sides, then reselect the card.
A field or action is missing	The order status, fulfillment type, data, configuration, scope, or platform does not qualify	Verify the order and project configuration; use only the actions that are visible and supported.
Status changed but totals look unchanged	A realtime update may not have replaced the full order snapshot	Refresh the queue and reopen the order before using the amounts.

Related articles

• Recognize a new order and open it safely
• Interpret order queues and statuses
• Find orders with search and filters

:::note Visual status Visual guidance is deferred pending an authorized synthetic capture program with exact phone and wide-tablet populated, loading, scoped-error, conditional-field, stale-update, and action-gated states plus independent visual QA. :::