Skip to main content
Editing changes the saved guest record used by profile, booking, order, and picker views. It does not move the guest between stores or merge unrelated records, so verify the person and store before saving contact changes.

​
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, select the person, and choose the edit control.
  2. Update the full name; the Management web form requires at least two trimmed characters.
  3. Update email and phone as needed. Empty optional values are stored as no value, and invalid formats are rejected by the server.
  4. Save and wait for the success message. The guest list and detail queries are refreshed after a successful update.
  5. Reopen the profile and verify the result. Check linked bookings and orders only to confirm identity; editing the guest does not rewrite their operational records.

​
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

  • The API rejects an empty update and a guest ID that belongs to another store. Always edit through the correct store context.
  • If save fails, keep the current values available, correct the reported format or permission issue, and retry once. Staff cannot use this administration endpoint.