Skip to main content
Deleting a guest removes the customer from active management lists and selectors and cannot be undone in the documented UI. Tapp retains the underlying record as a soft-deleted guest. Existing orders and bookings keep their guest ID and operational history; the delete action does not erase or detach those records.

​
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 verify their name, ID, contacts, orders, and bookings.
  2. Choose the delete control and read the confirmation. Make sure you are not trying to correct data that should be edited instead.
  3. Confirm deletion once and wait for the request to complete.
  4. Return to the guest list and verify that the record is absent.
  5. When reviewing prior orders or bookings, expect their operational data and original guest link to remain. The deleted guest is no longer an active choice for new work. Do not recreate a guest merely to alter historical records unless a supported workflow explicitly requires it.

​
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. New orders cannot be associated with a soft-deleted guest. Existing order and booking links remain stored.

​
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

  • Deletion fails when the guest does not exist, belongs to another store, or your role is not Owner/Manager.
  • The action has no restore function in the documented UI. If deletion was accidental, escalate with the guest ID and store context. The historical links are retained, but the guest does not automatically return to active lists.