Skip to main content
The Guests area is the store-specific customer directory. Use it to locate a guest by their saved identity or contact data before opening history, editing information, or attaching them to a new operational flow.

​
Who can do this?

Owners and Managers may search and administer guest data. Staff can encounter a navigation link or POS controls, but that does not grant access to the guest APIs.

​
Where to do it

Use Guests in the Management web app for the directory and profile. The shared guest picker also appears in bookings, walk-in seating, and the POS cart. The Management mobile app provides corresponding list, detail, and picker views.

​
Steps

  1. Open Guests and confirm the selected store. Guest records belong to one store and the list does not combine locations.
  2. Type a name, email address, or phone value in search. The web list debounces input before requesting filtered results.
  3. Sort by name, email, phone, or rating using the column headings. Select the same heading again to reverse direction.
  4. Move through the paginated result set rather than assuming the first page contains everyone.
  5. Select a guest row to open the detail panel. Use the displayed ID and contact data to distinguish people with similar names.

​
Platform notes

Web and mobile use the same store guest records. The guest web app manages guest identity for its own ordering flows, but it is not a merchant administration surface. Attaching passes a guest ID; it does not copy the profile into the order.

​
Market notes

The same functionality applies in GB and Germany. Dates, times, and money follow the store market and currency; email and phone values must pass server validation in either market. This reflects the product on 17 July 2026. Guest records are personal data: use only the intended store context, confirm identity before changes, and treat API authorization as binding.

​
Troubleshooting

  • If no result appears, clear search, check the store, and try the normalized email or phone saved on the record. A guest may exist in another location as a separate record.
  • Staff may see a Guests link in navigation, but the list API requires Owner or Manager. A forbidden request is a role mismatch, not proof that the directory is empty.