Guests order from a QR code at the table or a kiosk, onto the table's check
The customer asks: A QR code on each table that opens the menu on the guest's phone, a self-order kiosk at the counter, and the orders on the till for staff to send and take payment
- Verdict: Ready, with limits (4)
- Door: Open check · area: Customers and loyalty › History and CRM
- Recipe: Guest ordering: a QR code at the table and a self-order kiosk
- Sample: S56 — Guest ordering (a QR code at the table and a kiosk, to the table's check)
- Checked: 2026-10-29 · bench
What you build
A code record per table and per kiosk, its signed link and QR picture written by your service when the manager presses Make code, and a print format for the table card. A page your service serves: the register's own menu (its item groups, prices and the dishes' choice groups) and Send order. The order goes to the table's check through the till's open-check door (check_open when none is open, check_add_lines to the one that is), unsent, under a course of its own; a kiosk order opens a tab named by an order code, paid at the counter.
Limits
- The app never sends to the kitchen, prices or takes a payment: the server sends, the till prices and pays.
- One order a table at a time; a table with more than one bill open, or one being paid, is refused.
- The till shows a guest's lines under their course and note, not as the guest's.
- No pictures, allergens or sold out on the menu in this version.
Tell the customer
Your guests order from their phone at the table or at a kiosk; their orders appear on the table's bill on every till, your staff send them to the kitchen, and the bill is paid at the till as usual.
What next
- Tell the customer the 4 limits above, and write them into the proposal.
- Follow the recipe: Guest ordering: a QR code at the table and a self-order kiosk.
- Copy the sample: S56 — Guest ordering (a QR code at the table and a kiosk, to the table's check), and change it.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Send every write twice with the same key: it is written once. Send that key again with other lines: it is refused.
Related needs
- Our reservations app seats a table and opens its order; guests order from a QR menu or a kiosk onto that order, and the till takes the payment — Ready, with limits (7)
- A customer's shopping history or trend on the till: recent visits, the store, who served and the discount on each — Ready, with limits (5)
- Find what a customer bought before by typing their phone number — Ready, with limits (3)
- Our CRM sees our customers and their sales — Ready, with limits (2)
Start a project shortlist with this need · Put it in your blueprint · Every need