Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTPV
Device

Add a catalogue product to a ticket

Use the TPV ticket detail screen to add one visible catalogue product to an open ticket, creating a new draft unpaid line or increasing a compatible existing line.

In this article

In the TPV ticket detail screen, the operator works from the catalogue panel beside the account. The visible catalogue comes from the active service occurrence or event, or from the default catalogue if the service does not set one.

Each product card tap adds exactly one unit. Antylogic either creates a new draft, unpaid line or increments an existing compatible line, then refreshes the account totals returned by the server.

Before you start

  • The operator is working in the selected organisation and location, for example Harbor Demo Group at Harbor Soho.
  • The operator has `tpv:use` access for the location.
  • The ticket is open from `LocationTPVTicketDetail` with `ticketId`, `terminalId` and `staffId` in the route.
  • The ticket exists in the current location and is not void or closed in the UI.
  • The screen can load TPV settings, the active service session, the ticket, catalogues, products and product types.

Instructions

  1. 1.

    Open the ticket

    Open the active ticket from the TPV floor or a direct ticket link. The screen checks the organisation, location and ticket context before continuing into the catalogue action.

  2. 2.

    Check the catalogue panel

    Use the catalogue panel beside the account. The screen uses the active service catalogue when available, otherwise it falls back to the default catalogue; the operator does not switch catalogue manually here.

  3. 3.

    Filter or search products

    Narrow the product grid with type filters or the search field. Search matches the product name or short name, and only product types used by visible products are shown.

  4. 4.

    Tap the product card

    Tap one product card once to add one unit to the ticket. A new line starts as draft, unpaid and service pass 1.

  5. 5.

    Confirm the ticket line

    Check the account after the tap. If a compatible draft unpaid line for the same product already exists, its quantity increases by one; otherwise the ticket receives a new line.

  6. 6.

    Review totals

    Review the subtotal, tax and total after the server returns the updated ticket detail. Product name, tax category, tax rate and kitchen requirement can be completed from the product setup.

Validations and limits

  • The screen needs organisation, location and ticket context; without `ticketId` it shows that the requested ticket could not be found.
  • The operator must have `tpv:use` for the location. Backend access allows `tickets:manage`, or `tpv:use` when the ticket belongs to the active service session.
  • The UI treats void or closed tickets as read-only for this action; the analysed backend rejects void tickets for add and update item operations.
  • Deleted catalogues are not shown. When the selected catalogue has `product_ids`, only those products are visible; otherwise the loaded products are shown.
  • A tap always adds one unit; larger quantities require repeated taps or later line editing.
  • A compatible line can be incremented only when it is the same product, draft, unpaid, service pass 1, and has no seat, diner, discount or notes.
  • Item payloads must keep quantity above zero and non-negative unit price, discount amount and tax rate; payment and production statuses must be valid.
  • The add-item endpoint receives `product_id` rather than `catalog_id`, so catalogue membership is controlled by the UI product list.

Expected result

The ticket account shows the added product line or the incremented quantity, with subtotal, tax, total and payment status recalculated from the server response.

Related articles