When should a restaurant use shared or table-specific Join QR codes?
Use a shared QR when every guest should open the same restaurant registration form without a specific table reference. Use a table-specific QR when the link should carry a table code for context. Rezervem Join handles guest registration in both cases; neither approach places an order, records a payment or assigns a completed reservation.
A twelve-table venue makes the difference clear
Imagine one QR at the entrance and twelve cards on dining tables. The entrance code can lead to the general guest form, while the table cards can carry different references. Guests still register through the browser, but the restaurant can distinguish which physical card was used when the link is configured correctly.
1. Record where every code is displayed
Create a simple sheet listing the printed location, intended link, optional table code and responsible staff member. Keep the entrance QR separate from table-specific cards. This makes it easier to detect duplicates before printing and correct a card when furniture is moved.
2. Test the exact registration destination
Open each type of printed link on a mobile phone. Confirm the correct restaurant, visible language, basic fields and privacy explanation. A linked Join path and an independent Connect registration path have different consent rules, so do not mix those destinations within one unlabelled sign.
3. Verify the table code in the URL
A table-specific Join QR can carry an optional table parameter. Check that the code matches the actual table and that it remains in the registration context. The presence of a reference does not create a POS order, automatically bill the customer or reserve that table.
4. Check the guest's phone experience
Can someone easily understand that the form asks for an optional guest profile? Does the small screen show first name, last name, phone and configured fields without confusing the consent choices? Ask an employee who did not configure the QR to complete the test without coaching.
5. Repeat the verification after a seating change
If the restaurant renumbers tables or moves cards, update the inventory and rescan. A technically working QR may still carry an outdated table reference. The manager should treat this as part of routine service setup, not a one-time installation detail.
6. Label registration separately from ordering
Write 'Optional guest registration' near a Join code. Label menu, ordering and payment QR experiences separately. If an eligible gift is configured, describe only the benefit and conditions that the venue actually supports; the table reference alone does not grant a reward.
How Rezervem supports the configuration
Rezervem Join provides the mobile guest registration form and optional link context. Manager manages reservations while POS and Pay serve their own operational purposes. The restaurant maintains its printed-card inventory and confirms the link after changes.
Final checks before the first service
Have the host team check two different tables, the entrance card and a second-language version if provided. Record whether each opens the expected venue and whether the guest can finish without assistance. Correct any inaccurate label or table mapping before guests arrive.
One useful stress test is to move a table card intentionally and ask the team to notice the mismatch. This demonstrates why printed-code maintenance matters even when the registration page itself is working. Include that check in the opening routine whenever the restaurant rearranges its floor.
Frequently asked questions
**Does a shared QR always identify the table?** No. It may have no table reference.
**Can table QR registration place a food order?** No. Ordering is a different workflow.
**What needs retesting after table changes?** The physical card, URL and optional table code.
