Tables, QR ordering and the kitchen screen

Tables / QR — table layout and opening a table

This screen is the layout of the whole floor, divided into zone tabs at the top; each card is one table. Colour shows status: free / seated / awaiting bill close. You need the table.open permission to open a table. To view orders per table, either kds.view or bill.close is enough.

Opening a table, step by step

1. Press an empty table's card
2. Choose the number of guests (adults/children) — if the shop sells buffet, you must also pick the buffet package this table is eating here, since the buffet price is tied to the table from the moment it opens, not at bill close
3. The system issues a table session with a token unique to that sitting, then puts the QR on screen right away

QR ordering

The QR printed for customers is a link tied to "this table + this sitting's token" — print it once and it works for the whole sitting. Scanning it lets a customer order straight to the kitchen/cashier without needing a Korat account. Press "Print" on the QR sheet to print a table tent.

Closing a bill

Press a table that's awaiting bill close to see an itemised bill (read from that table's real orders, not an estimate) — you need the bill.close permission. Taking payment and actually closing the bill happens only in the full business console; this screen lets you preview the bill first, then takes you to the bill screen for the final step.

Kitchen (KDS)

Shows orders for the kitchen to cook in the order they came in. Unlike "Tables / QR", which is the whole floor's layout, this screen only shows food items that need making. You need kds.view to see it; confirming/rejecting an order needs kds.confirm.

Kitchen stations

A shop can split its kitchen into multiple stations (e.g. the wok, drinks, desserts) and assign which menu items or categories route to which screen — add staff names to a station to limit who sees that station; anyone not assigned to any station still sees all of them by default. This setting isn't the actual cooking screen, just a KDS display setting.

Staff-call bell

Customers at a table can call staff over or ask to close the bill from their phone — the message appears as a banner on the KDS screen right away. If loading the bell fails, the screen states plainly "Failed to load" rather than showing silence as if no one had called — those two are very different during a busy service.

Right now, the bill.close permission alone isn't enough to see "requested bill close" alerts — you also need kds.view. The team knows about this and is fixing it server-side; in the meantime, give staff who close bills both permissions.

Buffet packages

Set prices and menus for buffet packages. Unlike "Menu / products", which is the regular menu sold à la carte, editing this needs the menu management permission (catalog.manage).

• Create several packages with separate prices (e.g. Standard buffet / Premium buffet)
• Tick which menu items are included in each package — the same item can be in several packages at once
• Set child pricing tiers by age or height (always stored in millimetres, shown in the shop's chosen unit) — tiers must be contiguous with no gaps; the system won't save a tier set that has a hole
• Choose the service style: ordered to the table (order) / self-serve / mixed
• Pause a package for sale temporarily without deleting it — you can only delete a package no table is currently using; if a table is currently on that package, the system reports how many tables and refuses to delete it

Queue tickets

Issue a queue ticket to a customer before they're served. Unlike "Tables / QR", which is used after a customer already has a table — if a customer doesn't have a table yet and must wait in line first, use this screen instead of the tables screen. Works for any business type, not just restaurants (banks, clinics, service counters can all queue this way). Access needs either queue.operate or table.open.

Setting up queue groups and counters

1. Create a queue group (e.g. "General queue" and "VIP queue") — each group has its own queue code
2. Create counters/service points, tied to the queue groups they can serve
3. Customers scan a QR or request a ticket from the app to get a queue number and real-time position — they can check status without an account

Calling and closing a ticket

Counter staff press "Call next" and the system pulls that group's longest-waiting ticket. Press "Call again" if the customer hasn't shown up, or "Mark" to skip/complete. The queue number on screen is deliberately large so it can be read from across the shop.