Skip to main content
Adding a guest to the cart links the order to a store guest record. This supports identified history and contact-aware follow-up. In the current enforced flow, the guest picker and guest creation require Owner or Manager even though POS ordering itself also supports Staff.

​
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. In Point of sale, start the cart and select Add guest.
  2. Search the guest picker by name, email, or phone. Select an existing record to attach it; selecting the same active guest again removes the selection.
  3. If no correct record exists, choose Add guest. Enter a name and at least one contact method: email or phone. Correct invalid email formatting before saving.
  4. Submit. If the email or phone already matches an active guest in this store, the API updates that record and preserves its ID instead of creating a duplicate. A previously deleted guest is not treated as an active match.
  5. Check the guest name in the cart, then continue. Tapp sends the guest ID when creating or updating the order.

​
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 an active guest ID; a soft-deleted guest cannot be attached to a new 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

  • A Staff operator may see Add guest, but the underlying guest search/create APIs require Owner or Manager. Link or control visibility does not expand permission.
  • If creation returns an existing active guest, review the updated profile rather than retrying. If the order rejects the association, verify that the guest is still active and belongs to the same store.