What to prepare before launch
A tbltap menu is only useful when each physical tap point maps to the right restaurant and table context.
- Publish the menu first so every tbltap, QR menu, and NFC menu points to complete public content.
- Assign each tbltag to the correct table or service area before opening service.
- Use table links as a backup for places where QR or NFC hardware is difficult.
Configure table tap, QR, and NFC menu entry
Use the same menu assignment workflow for table tap menu routes, QR menu codes, and NFC menu tags, and keep the assignment obvious for staff and guests.
- Decide whether each table uses a separate tap menu route or shared room-level routing.
- Test both QR menu scan and NFC menu tap from an average guest phone before service.
- Confirm the table context is correct after pairing; mismatched table context creates support work during service.
Validate before service
Run a practical tap-menu dry run and confirm staff understand what each tbltap entry should do.
- Open each tbltap from a guest device and confirm it opens the right table menu.
- Switch table states and confirm a tap menu can still route correctly when the table enters payment mode.
- Keep a tag-to-table map updated so replacements and troubleshooting are fast.