Long Queues at Lunchtime? Let Customers Order for Themselves
August 2, 2026
2026 guide · 6 min read · By the Skoci POS Team
Short answer
QR table ordering moves the work of taking an order from your cashier to your customer. They scan the code on their table, order from their own phone, and the order lands on the cashier's screen for approval.
Customers install nothing — it all runs in their phone's browser. In Skoci POS the feature is available from the Free plan onwards.
The problem it actually solves
For most cafés and small restaurants, ninety minutes at lunchtime decide the whole day's result.
In that window the cashier is doing three jobs at once: taking orders, taking payment, and answering questions about the menu. All three compete for the same person, and the queue watches the line not move.
What happens next rarely shows up in a report: some people arrive, see the queue, and leave. That lost revenue is never recorded anywhere, because it never became a transaction.
Hiring another cashier solves it, but you pay someone for a whole day to cover ninety minutes. Self-ordering attacks the most time-consuming part — writing the order down — without adding a wage.
How it works
From the customer's side:
- They scan the QR code on the table with their phone camera.
- That table's ordering page opens. They sign in with Google, or choose Lanjutkan sebagai Tamu (continue as guest) without signing in at all.
- Your menu appears with categories and a search box. They pick items, set quantities, and add notes if needed.
- They tap Lihat Keranjang (view cart), review the order, and continue to Checkout.
- Checkout shows an order summary with subtotal, service fee, tax, admin fee, rounding and total. A name is optional.
From your side:
- The order appears on the Order Meja (table orders) screen in the cashier app, showing the table name and every item with its variants and notes.
- The cashier taps Terima (accept) or Tolak (reject).
- Once accepted, the order is forwarded to the kitchen immediately — there is no separate send button to press.
The status page on the customer's phone refreshes itself, so they know the order went through without having to ask.
What you need in place
Registered tables. Open Pengaturan → Meja (Settings → Tables) and add your tables. Until at least one exists, QR ordering stays switched off.
Printed codes. Every table has its own code. Click Lihat QR, then Unduh QR to save it as an image, and print it for the matching table.
A way to print kitchen tickets. Two options, and the second is often cheaper:
- A kitchen printer wired to the register device, configured under Pengaturan → Printer Dapur.
- A separate Android device in the kitchen with Mode Dapur (kitchen mode) switched on. It prints on its own the moment an order arrives, untouched.
The second option can run on an old but working Android phone. For many kitchens that is far tidier than running a long printer cable from the counter.
Four mistakes that kill it in week one
The code goes on the wrong table
A QR code is bound to one specific table, not to the shop in general. That is how the cashier knows where an order came from. Table 3's code stuck on table 5 sends food to the wrong place, and from the cashier's side the cause is nearly impossible to guess.
Print, place, then test each one by scanning it yourself before opening.
No shift is open
This is the most common reason customer orders appear to hang first thing in the morning. A cashier cannot accept orders until a shift is open — a message appears asking them to open one first.
Make opening the shift part of the opening routine, not something done when the first customer arrives.
Codes printed on plain paper
Tables are where drinks get spilled. Plain paper gets wet, tears, and stops scanning within days. Laminate the codes or mount them in a table stand.
The menu is not ready before launch
What customers see is your catalogue exactly as it stands. Confusing product names, prices that were never updated, or sold-out items still listed are all immediately visible — with no cashier in the middle to explain.
Tidy the catalogue before the first code goes on a table.
Does this replace the cashier?
No, and it is better not to treat it that way.
You still need someone to approve orders, take payment, and serve customers who would rather order in person — and there will always be some.
What changes is the mix of the work. Time that went into typing orders shifts to the parts that cannot be automated: checking orders, answering questions, and keeping tables turning.
Offer it as an option rather than a requirement. Forcing everyone to scan a code will drive some of your customers away.
Judging whether it worked
After two weeks, three things worth looking at:
- Laporan → Penjualan Harian (Daily Sales) — compare peak-hour revenue before and after, not total daily revenue. The change happens in the busy window.
- Laporan → Detail Transaksi (Transaction Detail) — watch whether average transaction value moves. Self-ordering often nudges it up, because people browse more comfortably when nobody is waiting on them.
- How many orders get rejected — a high rejection rate usually means the catalogue is out of step with what is actually available, not that the feature is a poor fit.
Frequently asked questions
Do customers have to download an app?
No. The ordering page opens straight in the phone browser after scanning. They can sign in with Google or continue as a guest without signing in at all.
Do customers pay from their phone?
The order goes to the cashier for approval and payment is settled as usual. What moves to the customer is the order-taking — the part that costs the most time when the shop is busy.
What if someone places a joke order?
The cashier taps Tolak and it is not processed. Because every order needs human approval before it reaches the kitchen, nothing gets through without your knowledge.
Does this need a paid plan?
No. QR table ordering is available from the Free plan onwards, as are table management and kitchen ticket printing.
How many tables should I start with?
Start with two or three for a week rather than the whole room. You will find small things — a code placed where nobody looks, a menu note that confuses people — and they are far easier to fix across three tables than twenty.
Trial it on three tables
Set up three tables, print their codes, ask a few people to try them before the rush, and watch where they hesitate.
If all three run smoothly for a week, then roll it out across the room.