Choose the correct ordering flow
For staff setting up or serving an order. Check the configured terminal,
location, menu availability, and channel before starting.
| Flow | Intended use |
|---|
| Seat / dine-in | Order associated with a table and served there |
| Pickup / takeaway | Collection order with the intended due time and handover |
| Delivery | Order with supported delivery availability and address |
| Counter | Staff-built till order; guest device shows payment/receipt rather than a browsable catalogue |
| Kiosk | Configured customer-facing self-order device and supported checkout |
| Shop | Customer catalogue/trolley flow with supported fulfilment chosen at checkout |
The location, terminal, menu, section, and item must support the intended order
type. A type appearing elsewhere in the product is not proof it is enabled at
this restaurant. Do not change a guest link's address manually to force an
unsupported flow.
Order links & QR codes
A terminal link opens its configured flow; a link identifying an existing order
resumes that order instead of intentionally creating a new one. Verify the
reference and current state when returning from a receipt/payment link. A bare
ordering entry can offer supported fulfilment choices.
A menu link is for browsing and is separate from an order/checkout entry. A
counter QR is not a general shop catalogue. Test the actual terminal or website
link through the guest flow before displaying it in the restaurant. An expired,
deleted, or unavailable record needs review rather than a promise that every old
link works indefinitely.
Check fulfilment and payment separately
Collection or delivery checkout availability depends on the restaurant's
configuration and supported payment flow. Verify due time, address where
required, amount, payment result, preparation, and actual handover. A Ready
item, a printed receipt, and a settled order are different outcomes.
Use Tables for terminal configuration and
Location menus for channel availability. For the
shop-specific customer experience see Online store.
Escalate with location, intended flow, terminal/order reference, observed step,
and exact error, keeping guest and credential data private.