NFC / QR Table Ordering
Bring each guest into the right table session
Common pain points
- App installs reduce adoption
- Paper menus and re-entry fall out of sync
Key capabilities
- No-app web ordering
- Table identity
- Hub and KDS connection
- Configure table codes Each table gets a QR; supported devices can also use NFC.
- Browse and customize Guests use translated content for items, modifiers, and notes.
- Confirm and send The order enters Hub and the configured kitchen flow.
FAQs
Does every phone support NFC?
No. QR is universal; NFC depends on the phone and browser.
A good place to start when
- Dine-in tables are clearly identified and guests can use their own phones
- The restaurant wants a few-table pilot before a full rollout
Confirm before rollout
- Every QR or NFC tag resolves to the correct table
- Menu, modifiers, price, and sold-out state are complete
- Service for guests without NFC or comfortable phone use
What the system does not do
- Not every phone supports NFC, so QR must work independently
- No app does not remove the need to validate venue network and devices
Observe first after launch
Measure correct table entry, completed order submission, and staff-assistance cases before expanding to more tables.