Guide
Easy
Updated September 2026
How QR ordering works
Scan → order → approve → cook → serve → settle. Why every QR order waits for a human yes.
The flow
- A guest scans the QR code on their table — your menu opens in their phone browser. No app, no sign-up, no login.
- They build a cart — photos, variants, add-ons and per-item notes ("no onion") — and place the order.
- The order arrives at the till as a request, not as food-in-motion: it pops up full-screen in the cashier's approval queue.
- The cashier accepts (it goes to the kitchen and the KOT prints) or rejects with a reason the guest is shown.
- Guests can order more rounds from the same QR — everything joins one table bill.
Why orders wait for approval
A guest scanning a code would otherwise send food straight at the kitchen with nobody in the loop — the item may be 86'd, the table may be leaving, the order may be a misfire. Until a person says yes, a placed QR order is a request. The approval screen shows how many seconds the guest has been waiting, so nothing sits silently.
What makes it reliable
- The menu guests see is live — 86'd items vanish from phones mid-service.
- Each table's QR token is permanent; editing table details never breaks printed codes.
- Guest carts survive a refresh — the cart is kept per table code on the phone.
Was this helpful?