> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand order details and statuses

> Read an order's guest, items, totals, payment state and next available action.

Open an order to see its current backend status and the actions that are valid from that state.

## Who can do this?

**Owners, Managers and Staff** can read order details for their shop. Available actions are determined by the order status and the endpoint used, not only by the role.

## Where to do it

In **History**, select an order row. The details panel shows the order ID and status first, followed by any next action.

## Read the details

* **DRAFT** is an order still being built; it is normally edited from POS.
* **SUBMITTED** is ready for a payment flow.
* **PAYMENT\_INITIATED** means a remote or device payment is in progress; **PAYMENT\_FAILED** can be retried.
* **PAY\_LATER** keeps the order open for later editing or payment.
* **PAID** has recorded payment and can be marked complete.
* **COMPLETED** is the final served/completed state and supports sending a receipt.
* **CANCELLED** is no longer active.
* **REFUND\_INITIATED**, **REFUNDED** and **REFUND\_FAILED** show the refund lifecycle.

The panel can also show the linked guest, items and quantities, subtotal, discount, VAT/tax amount, total, tips, ratings and staff information where present.

Current menu data can supply images for recognized items, but the recorded order line remains the basis for quantity and money. A later menu-price edit does not rewrite History. Fast Charge lines use their stored description rather than an offering-item ID.

## Why actions change

History offers payment for Submitted, Pay later and in-progress/failed payment states. It offers **Mark complete** for Paid. Receipt sending appears for Completed, while thermal printing supports a wider documented set of statuses. Refund is offered only for Paid, Completed or Refund failed.

## Platform and market notes

Web, mobile, guest and terminal interactions can all move the same order through its lifecycle. Refresh History when another device has acted on the order. Status meanings are shared in GB and Germany; amounts and tax labels are localized.

## Troubleshooting

If the panel says the order is not found, confirm shop and order ID; store boundaries are enforced. If an action vanished, refresh the details because another device may have moved the order to a state where that action is no longer valid.

## Related guides

* [Complete a Pay later order](/en/history/complete-pay-later-order)
* [Refund an order](/en/history/refund-an-order)