How Table-Specific QR Ordering Works (and Prevents Wrong-Table Orders)
Understand cryptographic table tokens, 30-minute idle scan expiry, and how modern Kitchen Display Systems keep dine-in ordering fast and accurate.
Why generic menu links break down once ordering is turned on
Asking hurried guests to type their own table number from a dropdown invites typos — leading to chilled drinks delivered to Table 5 instead of Table 3, or playful remote orders from someone who left the café two hours earlier.
Cryptographic per-table QR tokens and 30-minute idle protection
Every table in Menzy receives a signed opaque token (`tq_...`) backed by a table QR version hash. The server resolves the exact table strictly from that valid token.
- Cross-table isolation: A guest scanning Table 3 cannot inject orders or waiter calls into Table 5.
- 30-minute inactivity rescan guard: If no order is placed from that device for 30 minutes, the browser asks the diner to rescan the table QR — blocking old sessions after guests leave.
- Instant QR rotation: Replace a damaged tent and invalidate the previous table QR token in one click.
Live Kitchen Display (KDS) & floor staff terminal
Orders stream directly into `/orders` via real-time Server-Sent Events with synthesized bell alerts, variant breakdowns, special instructions, and status progression from Pending → Preparing → Ready → Served.
Quick Answers
What happens if a customer tries ordering from a screenshot scanned yesterday?+
Sessions expire automatically after 30 minutes without placing an order, prompting the browser to rescan the live QR code on the table.
Can managers disable online ordering temporarily during kitchen peak hours?+
Yes. Staff and owners can toggle New Orders on or off anytime without hiding the visual digital menu or AI waiter.
Set up your menu in minutes with 3D dish visuals and signed table QR codes.