What is QR code ordering?
QR code ordering lets a guest scan a printed code with their phone camera, see the restaurant's live menu in their browser, build an order and pay — with no app to install and no staff member taking the order. The order goes straight to the kitchen display like any other channel.
It suits dine-in tables, counter queues, takeaway waiting areas, flyers and delivery bags. The same mechanism covers all of them; what changes is what the code is bound to.
What makes a QR code more than a link
ThaliPOS generates a code per location and per area within it. Scanning a code on a dine-in table and scanning one at the takeaway counter can open different menus and different prices, because they are genuinely different services in the same building.
- Opaque short codes. The printed URL carries a short random code, not your internal ids. Nothing about your setup is guessable from a printed card.
- Rotate without reprinting everything. A code can be rotated or revoked — useful when a card walks off, or a flyer campaign ends — with an audit trail of what changed.
- Scan analytics. Scans are counted per code, so "did the table tents work" is a question with an answer.
- Graceful downgrade. If a code points at something that is no longer available, the guest lands on the right restaurant's menu rather than an error page.
- Print formats that survive contact with a printer. Individual SVG and PNG, or a bulk PDF sheet for a whole property.
What the guest experiences
- Scan with the phone camera. No app, no download, no account.
- The menu opens already scoped to that table or counter — correct items, correct prices.
- Browse and build a cart anonymously. Nobody is asked to sign in to look at food.
- Identify at checkout, pay with a card in Stripe's payment form, and the cart carries over intact.
- The order lands on the kitchen display with its channel marked, and the guest gets a friendly order number to watch on the order board.
If a guest already had a cart on their phone from an earlier visit, ThaliPOS asks what to do with it rather than silently wiping it. Losing somebody's order because they scanned a second code is a small bug with a large consequence.
QR ordering and the offline hub
QR ordering is a guest-phone channel, so it depends on the guest's own connectivity to reach your storefront. What it does not depend on is a perfect connection in your kitchen: once an order is placed, it routes to the in-store hub and onto the kitchen display like every other channel.
More on the offline-first architecture →
Which restaurants use it most
Thali houses and dine-in for re-orders mid-meal without flagging down a server. Chaat corners and street food to split a counter queue in two. Cloud kitchens printing codes onto delivery bags for the reorder. Catering and events where a printed code is the whole ordering infrastructure.