Open a Ticket from a Reservation
Turn an assigned reservation into an active TPV ticket for the current service from the floor plan. Antylogic reuses an existing reservation ticket when one is already open, links one matching active table ticket when appropriate, or creates a new pending ticket with the reservation and table context preserved.
In this article
Use this guide when guests arrive for a reserved table and the front-of-house team needs a TPV account for that party.
The action starts on the Harbor Soho TPV floor during an open service session and ends in ticket detail, with the reservation, table assignment and selected staff context kept together.
Before you start
- The operator is signed in to Harbor Demo Group with Harbor Soho selected.
- The operator has `tpv:use`; the reservation data used by this action also requires `reservation:view`.
- Harbor Soho has an open `service_session` for the active Soho lunch service occurrence.
- The reservation is not cancelled or marked no-show, and its assigned tables can be resolved on the floor plan.
- If TPV employee access is enabled by PIN, selector or card, a staff member such as Olivia Hart is selected or authenticated.
- For captures, use the GB runtime values for `ORG_ID`, `LOCATION_ID`, `TPV_STAFF_ID`, `TPV_TERMINAL_ID` and `BOOKING_DETAIL_RESERVATION_LABEL`.
Instructions
- 1.
Open the TPV floor
Open Harbor Soho at `/:orgId/:locationId/tpv?tab=floor`. The workspace appears only when the active service session is available and any required employee selection is complete.
- 2.
Select the reserved table
Find a table shown as reserved for the active occurrence and tap it. Tables with active tickets take priority over reservation state, so occupied, payable or paid tables are not shown as reserved.
- 3.
Review the reserved table modal
Check the reservation context in the `Mesa reservada` modal, then use `Abrir cuenta` when the guests need an account tied to the reservation.
- 4.
Open or create the account
Antylogic first opens a non-closed, non-void ticket already linked to the reservation. If there is exactly one active ticket on the assigned tables, it links that ticket. Otherwise it creates a new pending ticket using the reservation party size, assigned tables and selected staff member when available.
- 5.
Continue in ticket detail
After reuse, linking or creation, the app navigates to `/:orgId/:locationId/tpv/ticket?ticketId=:ticketId&terminalId=:terminalId&staffId=:staffId&sourceTab=floor`, where the account is ready for normal TPV work.
Validations and limits
- If there is no active service session, the TPV floor does not render the operational workspace.
- Cancelled and no-show reservations are not shown as reserved table candidates on the TPV floor.
- No duplicate ticket is created when a direct active ticket already exists for the reservation.
- A fallback table ticket is linked only when exactly one active ticket is found across the assigned tables.
- A new ticket requires `service_session_id`, is created with status `pending`, and keeps the first normalised table as the primary assignment.
- Opening the account does not add products, take payment, print, invoice, close the ticket or change `reservation.status` to seated.
Expected result
The reservation is connected to one active TPV ticket for the current service, with reservation context and table assignments preserved where available.