1. A digital menu helps guests choose
A browse-only QR menu shows dishes, descriptions, prices and options. Guests still place orders with staff. For a café where the main problem is an outdated printed menu, this may be enough. Decide who updates prices and unavailable dishes, and how guests without a suitable phone see the menu.
2. Ordering needs someone to receive the order
With QR table ordering, guests select items and submit an order linked to their table. Write down who checks it, how it reaches the kitchen and what the guest sees next. An illustrative busy restaurant might need ordering because staff repeatedly retype handwritten tickets; a digital menu alone would leave that step unchanged.
3. Agree the difficult cases before building
Use actual menu options and table arrangements in the walkthrough. Define the expected behaviour for each case instead of assuming every ordering product handles it the same way.
- An item sells out while a guest is choosing it.
- A guest taps submit twice or loses their connection.
- A table moves, adds another order or asks to cancel an item.
- A guest needs help with an allergy or a request staff must confirm.
4. Payment and POS are separate decisions
Guests can order digitally and still pay with the cashier. If table payment is required, confirm the payment provider, payment status, failed-payment handling and refund responsibilities in the scope. QR ordering is not a POS replacement. Existing POS or kitchen-printer connections need a feasibility check for the specific system; a QR code does not establish that connection.
5. Test one complete service journey
Before rollout, have a guest and a staff member run through scanning, choosing options, submitting, receiving and serving an order. Test the agreed exceptions and a manual fallback. Compare order corrections and staff steps with your current process. An attractive guest screen is useful only if the team can reliably work from what arrives.
How O2 scopes QR ordering
O2 separates a browse-only menu from ordering. QR Ordering covers the table menu, order submission and calling staff; payment at the table is included only where agreed. Bring your menu, table layout, current tools and one troublesome service scenario so the proposed workflow can be checked against your restaurant.