What a QR ordering flow actually is
A QR ordering flow is not a QR menu. A QR menu just shows a PDF; the diner still has to call the waiter to order. A QR ordering flow is a complete transactional surface: the diner scans the code, the browser loads the menu, builds a cart, sends the order to the kitchen, and pays — all without downloading anything and without an account. The waiter only intervenes for what waiters actually do: bringing the food, checking on the table, handling exceptions.
Step 1 — Scan and resolve the table
Every QR code on a Disqober deployment carries an identifier for the venue and the table. When the diner scans the code, the browser opens a URL on the restaurant's own domain. Disqober resolves the venue, the table, and the active menu in a single request. No app store, no install prompt, no login screen.
Step 2 — Load the menu
The menu is the same menu that powers the Web App, the Mobile App, the Kiosk App, and the Table App for that venue. Categories, products, modifiers, prices, schedules, and availability rules are read from the shared ordering engine. If the restaurant pauses a product mid-service, it disappears from the QR App on the next page load.
Step 3 — Build the cart and check out
The diner adds items, picks modifiers, and reviews the cart. At checkout the QR App offers card payment (Disqober Online Payments), Apple Pay and Google Pay where available, and any local methods the restaurant has enabled — Bizum in Spain, MB Way in Portugal, country-specific wallets elsewhere. The cart is bound to the table identifier from step 1, so the order is never lost or sent to the wrong table.
Step 4 — Hand off to the kitchen and the POS
The order lands in Work App as soon as the diner pays. If the venue has a POS connected, Disqober writes the ticket into the POS so it follows the same production path as in-house tickets: kitchen printer, kitchen display, expediter screen. Control Center keeps the live state of the table and the order across the venue's screens. No double entry, no parallel queue.
Pay-at-table — the second mode
On many tables, QR is also used for pay-at-table. The diner orders the traditional way through the waiter or the Table App; when the meal is over, scanning the same QR code shows the open POS ticket, optionally lets the diner split the bill, and processes the payment by card. The POS closes the table automatically once the payment settles. Same QR code, two complementary modes.
What the restaurant needs to launch
A menu in the Disqober catalog (imported from the POS or built directly), a QR code per table, and a payments method configured. The Web App and the QR App share the same menu, so a restaurant that already runs Web App orders can switch QR ordering on without rebuilding the catalog. Hardware-wise, the printed QR sticker on each table is enough — no terminal at the table, no kiosk to maintain.
What QR ordering does not replace
QR ordering is not a head-count replacement for waiters. Most restaurants use QR to remove the friction from ordering and paying so the team can focus on service, runners, and dining-room flow. The Kiosk App handles counter self-service, the Table App handles staff-led tablet ordering, and the QR App handles diner-led self-service. Same backend, three flows.