Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTPV tickets
Device

How to update ticket covers

Update the number of covers on an open TPV ticket from the ticket detail screen or from the selected ticket on the main TPV floor screen. The action changes only the ticket `party_size` value shown as `pax`; it does not recalculate totals, payments, invoice state or production state.

In this article

Covers are stored on the ticket itself, so front-of-house staff can correct the guest count while the service ticket stays open.

Use this flow for Harbor Soho service adjustments, such as changing a table from two to four guests. It is not a closing, charging, invoicing or kitchen production action.

Before you start

  • The user is signed in to Harbor Demo Group with Harbor Soho selected.
  • Olivia Hart, or another authorised TPV staff user, is operating in the active Harbor Soho service session.
  • An open TPV ticket exists for Harbor Soho and is not `void` or `closed`.
  • The user has `tickets:manage`, `tpv:manage` or `tpv:use`. Users with only `tpv:use` can update only tickets in the active service session.
  • For captures, use the GB runtime values for `ORG_ID`, `LOCATION_ID`, `TPV_TICKET_ID`, `TPV_TERMINAL_ID` and `TPV_STAFF_ID`.

Instructions

  1. 1.

    Open the ticket

    Open the active Harbor Soho ticket from the ticket detail screen, or open the TPV floor screen and select the ticket from Accounts. Check the current covers count shown as `pax` before changing it.

  2. 2.

    Choose the people edit action

    Open the ticket actions menu and choose the people edit option. In the inspected en-GB runtime, some labels may still appear as Spanish fallbacks: `Personalizar`, `Editar personas`, `Personas` and `Guardar`.

  3. 3.

    Enter the covers count

    In the People field, enter the new positive whole number of covers for the ticket. For example, enter `4` when four guests are now seated.

  4. 4.

    Save the change

    Select Save. The app sends the new `party_size`, refreshes the ticket data and closes the edit sheet or returns to the selected ticket state.

Validations and limits

  • The covers value must be a positive whole number greater than zero.
  • Blank values, `0` and values that do not produce a positive integer are rejected before saving.
  • The UI disables or blocks the action when the ticket is `void` or `closed`.
  • Users with only `tpv:use` can update only tickets in the active service session.
  • There is no verified backend maximum for `party_size`; document only the positive whole number rule.
  • Updating covers does not intentionally change ticket totals, payments, invoices or production status.

Expected result

The visible `pax` count updates to the saved covers value while the ticket remains open in the same TPV service context.