Open Ticket Detail
Open the operational detail for a Harbor Soho TPV ticket so staff can confirm the account context, ordered products, payments, totals, and optional invoice or fiscal information without changing the ticket.
In this article
Use this guide when floor staff, cashiers, or shift managers need one operational view of a TPV account during service.
Opening the detail is a read-only action. It loads the ticket information and supporting context, but it does not take payment, print, create an invoice, or change products by itself.
Before you start
- Harbor Demo Group and the Harbor Soho location are selected in the app.
- The operator has `tpv:use` for the location. Printing, invoicing, and KDS actions require their own additional permissions.
- The ticket belongs to Harbor Soho. With only `tpv:use`, the backend only allows tickets from the active service session.
- The route includes a valid `ticketId`. The GB demo runtime provides `TPV_TICKET_ID`, `TPV_PAID_TICKET_ID`, `TPV_TERMINAL_ID`, and `TPV_STAFF_ID` for Olivia Hart at Harbor Soho.
Instructions
- 1.
Open the ticket
From the TPV floor, open the relevant table or ticket. The app opens `LocationTPVTicketDetail` with the ticket, terminal, staff member, and `sourceTab=floor` context so the back action can return to the originating TPV tab.
- 2.
Wait for the detail to load
The screen loads the ticket detail and the supporting TPV context. Wait until the loading state is replaced by the ticket header, product list, payment state, and totals.
- 3.
Check the ticket header
Confirm that the correct account is open. The header identifies whether the ticket is linked to a table or quick account, and shows the ticket label, status, and operational context.
- 4.
Review products
Review items, quantities, and preparation state before taking payment or printing. Product metadata can enrich each line with kitchen routing and display names when the related product exists.
- 5.
Review payments and totals
Check the total, paid amount, and outstanding balance. Payment and print controls may be available when the ticket is still mutable and the operator has the required permissions.
- 6.
Check invoice information
If the ticket has no invoice, invoice generation can appear only when the ticket is fully paid and the operator can invoice. If an invoice already exists, the detail can show invoice data, VAT breakdown, delivery attempts, fiscal validation, and VERI*FACTU status when those records exist.
Validations and limits
- The frontend requires selected organisation, selected location, a non-empty `ticketId`, and `tpv:use` before it enables the ticket detail query.
- The backend returns not found for an empty ticket id or for a ticket outside the selected location.
- With only `tpv:use`, backend access is limited to tickets in the active service session.
- Ticket, KDS, or service-session-calendar read permissions can satisfy backend access paths, but this frontend screen still blocks without `tpv:use`.
- Invoice, delivery history, VERI*FACTU, and fiscal validation are optional and should only be documented when the runtime ticket actually contains those records.
- Tickets in `void` or `closed` state can be shown, but mutation controls are disabled.
Expected result
The operator lands on a read-only operational ticket detail showing the account context, products, payment state, totals, and any available invoice or fiscal information.