FooodPosWiki

Accept or reject QR orders

A guest orders from the QR code on the table, and the order waits on the POS until someone accepts it. The chime, the QR waiting chip, the QR key, the QR orders screen part by part, Accept and Reject, what each does, orders accepted by themselves, and what happens with no internet. On the Windows and the Android POS.

Who uses it:CashierManagerWhere:Windows POSAndroid POS
On this page

A guest scans the QR code on their table, chooses dishes on their phone and presses send. The order does not go to the kitchen. It waits on the POS until someone here accepts it.

That is on purpose: a QR order comes from a phone, and anyone can scan a code. When you press Accept, the order goes onto the table's bill and its kitchen tickets print. When you press Reject, it is turned down and nothing is cooked.

Before you start

  • You need the QR right. In your POS access group, QR Incoming Orders: View to see the QR orders, Edit to accept and reject them. See POS access groups.
  • QR orders need the internet. Guests' phones talk to the cloud, never to the POS. No order arrives while this POS is offline, and Accept and Reject wait for the cloud's answer.
  • Table orders may not wait at all. When the QR profile has Accept table orders automatically on, a table's order goes straight to the kitchen and never shows here. Pick-up and delivery orders always wait for a cashier. See QR Ordering: a profile's settings.

How a new QR order reaches you

When a guest sends an order, every Main and Sub POS of the outlet hears it within about ten seconds:

  • A chime. The sound your restaurant chose for new orders, rung for as long as it chose. While an order has waited a minute or more, a soft reminder sounds, at most once a minute.
  • The QR waiting chip in the top bar of the table screen.
  • The orders panel down the right of the table screen, with the order on a card.
  • The QR key in the bar along the bottom.
The table screen with a QR order waiting: the chip, the QR key and the orders panel.
  1. 2 QR waiting, in green: how many QR orders and guests' calls wait for someone here. Tap it to open the QR orders.
  2. 📱 QR: opens the QR orders, always. Right-click it, or hold it with a finger, to close or open QR ordering instead. See Close or open QR ordering now.
  3. Orders: the orders panel, with each QR order on a card and its own Reject and Accept. See The orders panel.

The chime and the reminder are switched on or off, and their volume set, on this POS's Hardware screen: Chime for new QR orders, Remind while an order waits, Volume of the QR chime. See Sound: the QR chime and table calls.

Open the QR orders

  1. On the table screen, tap 📱 QR in the bottom bar, or tap the green 2 QR waiting chip.
  2. The QR orders screen opens over the tables. The chime stops at once: someone is seeing to it.
  3. Accept or reject each order, as below.
  4. Press Close at the top right to go back to the tables.

The QR orders screen, part by part

The QR orders screen (Windows): the calls at the top, then one card for each order waiting.
  1. QR orders, and under it Nothing reaches the kitchen until you accept it.: the screen's name, and the rule it keeps.
  2. 2 waiting, in amber: how many orders wait for an answer. It is not there when none wait.
  3. Close: back to the table screen. Orders you have not answered keep waiting.
  4. Service calls: guests who pressed Call waiter or Request bill on the QR page, one button each, with the table (Table T3, or Counter) and what they want: Wants a waiter, Asking for the bill or Needs help, and the guest's message when there is one. Tap the button when the call is answered (tap to acknowledge). It is there only while a call waits. See Call waiter, Bill please, Help.
  5. 🍽️ Table T6 · 3 min · Aisyah: what kind of order and where. Table T6 for a table, Counter for a dine-in order with no table, 🛍️ Pick-up or 🏍️ Delivery for the others. Then how long it has waited: just now, then minutes, amber from 2 minutes and red from 5. Then the guest's name, when the QR page asked for it.
  6. ~RM 25.90: about what the order comes to. It is only an estimate: Accept prices the order again from your menu, and the bill shows what it really costs.
  7. The dishes: every dish with its quantity, and under it, after a dot, its options and the guest's note for it (· less spicy).
  8. The guest's note for the whole order, in a grey box, when there is one.
  9. Reject: turns the order down. See Reject an order.
  10. Accept: takes the order in and sends it to the kitchen. While it works it says Sending… and both buttons are greyed out. See Accept an order.

The orders are listed oldest first, as a queue is served. The screen reads the list again every five seconds by itself.

Accept an order

  1. Read the order: the table, the dishes, the notes.
  2. Press Accept. It says Sending… while the cloud takes it.
  3. The card leaves the screen. The order is on the bill now.

What Accept does:

  • The order goes onto the table's bill. If the table has a bill open, the dishes join it; if not, a new bill is opened at that table. A second round from the same pick-up or delivery guest joins their first bill.
  • The prices come from your menu, not from the guest's phone: the prices, tax, options and set rules are worked out again when you accept.
  • The kitchen tickets print at once, the usual way, at each dish's kitchen printer. A ticket for a printer this POS cannot reach is left for the POS that can. When the QR profile prints a master slip for each QR round, it prints too.
  • The bill comes onto this POS, so a tap on the table opens it.
  • The guest's page changes to Accepted · with the kitchen.

Reject an order

  1. Press Reject on the order's card. The POS does not ask again.
  2. The card leaves the screen. Nothing is cooked and no bill is opened.

The guest's page shows Not accepted, with Reason: Rejected at the POS. If the guest typed a voucher code, it was never used and stays good: the page says Voucher not used: this order was not accepted.

Accept or reject from the orders panel

The orders panel on the table screen holds the same orders, each on a card with Reject and Accept. They are the same buttons and do the same thing, so you need not open the QR orders screen at all. The panel shows the first three dishes of an order (+1 more for the rest); the QR orders screen shows them all, with the notes. See The orders panel.

Orders accepted by themselves

With Accept table orders automatically on, a table's order goes straight to the kitchen when the guest sends it. It never waits on the QR orders screen. The POS still chimes for it, and its bill still comes onto the POS, so a tap on the table opens it.

Pick-up and delivery orders always wait for a cashier, whatever that setting says.

When the internet is down

  • No new order arrives. The guests' phones send their orders to the cloud, and the cloud cannot tell this POS.
  • The list stays as it was last read, and says so in amber: Not updating — Cannot reach the server. It goes when the list next reads.
  • Accept and Reject need the cloud. Pressed with no line, they say Cannot reach the server in red, and the order keeps waiting. Press again when the line is back.

Everything else on the POS carries on as usual.

On Android

The QR orders screen is the same, with Close at the top right, and these differences on each card:

  • A table's order is headed 🍽️ Dine-in · Table T6, and a delivery wears 🛵.
  • For a pick-up or a delivery, the guest's name and phone follow the wait (· Mei Ling · 012-345 6789).
  • For a delivery, the address is under the dishes (🏠 12 Jalan Contoh), for whoever takes it.

On a phone, or a tablet held upright, the heading, the wait and the total share one line and the guest has the line under it.

The orders panel is drawn only on a wide screen. On a phone, open the QR orders from the 📱 QR key or the QR waiting chip.

What if…