Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTPV
Device

Create Table Ticket

Create a standard pending table account from the Harbor Soho TPV floor plan, assign the selected available table or joined tables, set the guest count, and continue from the new ticket detail.

In this article

Use this guide when a front-of-house operator needs to open a table account from the TPV Floor tab during an active Harbor Soho service.

The flow creates the account only. Adding products, sending orders, taking payment, issuing invoices, and closing the ticket are handled by later TPV actions.

Before you start

  • Harbor Demo Group and Harbor Soho are selected.
  • The operator has access to use the location TPV with `tpv:use`.
  • Harbor Soho has an active service session, such as Soho lunch service.
  • The TPV Floor tab has a loaded floor plan with at least one available table.
  • If staff access is required by PIN, selector, or card, Olivia Hart or another authorised staff member is selected before using the workspace.

Instructions

  1. 1.

    Open the Floor tab

    Open the TPV at `${APP_DEEPLINK_BASE}${ORG_ID}/${LOCATION_ID}/tpv?tab=floor`. The screen loads the active service, staff context, floor layout, and existing tickets so each table can show its current state.

  2. 2.

    Select available tables

    Tap one or more available tables on the floor plan. The create action appears only while at least one available table is selected.

  3. 3.

    Open the account modal

    Press `Crear cuenta`. The modal opens for the selected table set and starts with a valid party size of `1`.

  4. 4.

    Confirm the guest count

    Enter a positive whole number in `Numero de personas` and confirm with `Crear ticket`. Empty, zero, or non-numeric values are rejected before the account is created.

  5. 5.

    Continue from the new ticket

    Antylogic creates the pending standard ticket, links the selected table assignments, clears the floor selection, shows the success message, and opens the ticket detail so products can be added.

Validations and limits

  • If there is no active service, the TPV workspace is replaced by the no-active-service state and the account modal does not open.
  • If employee access is required and no staff member is selected, the workspace stays blocked until staff context is set.
  • Occupied, partially paid, or paid tables open the existing ticket instead of starting another account on the same table.
  • Reserved tables open reservation context instead of this table-account flow.
  • With only `tpv:use`, creation is restricted to the active service session; creating against another service requires `tickets:manage`.
  • The created account is normalised to a `standard` source kind and `pending` status.
  • When several tables are selected, the first normalised table becomes the primary table and every selected table is stored as a `ticket_table_assignment`.
  • The new account starts without items, payments, or an invoice, so totals remain zero until later TPV actions.
  • There is no documented capacity check that compares `party_size` with table capacity.

Expected result

The selected available table or joined tables are no longer available on the floor plan because they now belong to the newly created pending table ticket.

Related articles