Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTPV
Device

Add a Product to a TPV Ticket

Add a Harbor Soho catalogue product, such as Fish and chips, to an open TPV ticket. Antylogic creates an unpaid draft line or increases the quantity of an existing matching line, then refreshes the ticket totals.

In this article

Use this guide when front-of-house staff need to add a catalogue product to an open TPV account during service. The normal motion is a single product-card tap from the ticket detail screen.

Antylogic keeps the operator out of manual price, tax, production-status and payment-status entry for a normal catalogue add. Kitchen dispatch, printing and payment stay as separate follow-up actions.

Before you start

  • The operator is working in Harbor Demo Group and the Harbor Soho location context.
  • The ticket detail can be opened from the TPV floor flow or from the ticket detail deep link for `TPV_TICKET_ID`, `TPV_TERMINAL_ID` and `TPV_STAFF_ID`.
  • The ticket is open in the UI and is not void or closed.
  • The operator has `tpv:use` for the location. Without `tickets:manage`, the ticket must belong to the active service session.
  • The product catalogue and product type filters load on the ticket detail screen.
  • The product being added belongs to Harbor Soho or is available globally for the location.

Instructions

  1. 1.

    Open the ticket detail

    Open the active TPV ticket from the floor flow or by using the ticket detail deep link. In the GB demo, the context should be Harbor Soho with Olivia Hart as the TPV staff member.

  2. 2.

    Find the product

    Use the catalogue categories or search to locate the product to add. Stable Harbor Soho examples include Fish and chips, Beef pie, Cheddar and leek soup and Sticky toffee pudding.

  3. 3.

    Tap the product card

    Tap the product once. If the same clean draft unpaid line is not already present, the ticket receives a new line with quantity 1. If that clean line already exists, Antylogic increases its quantity instead of creating a duplicate row.

  4. 4.

    Review the refreshed ticket

    Check the product line, quantity, line total and ticket total after the screen refreshes. Prices are treated as tax-inclusive when tax data is present.

  5. 5.

    Continue service actions separately

    Adding a product records it on the ticket, but does not send it to kitchen, print kitchen jobs, mark it served or take payment. Use the production, output or payment actions after the item is on the ticket.

  6. 6.

    Resolve blocked adds

    If the catalogue is disabled or the add does not complete, check that the ticket is still open, the operator can work in the active service, and the selected product belongs to the current location.

Validations and limits

  • The ticket detail screen must be visible without an access error.
  • Void or closed tickets are read-only from the UI. The verified backend path explicitly rejects void tickets; closed-ticket backend behaviour was not proven by the analysis.
  • A normal catalogue tap creates an unpaid item in draft production status, unless it increments an existing matching clean line.
  • The operator does not manually enter price, tax category, production status or payment status for the standard product-card flow.
  • `product_id` is the preferred source for product name, price, tax category and kitchen requirement enrichment.
  • A positive item discount is outside the normal catalogue tap and requires `tickets:manage` or `tpv:discount`.
  • Adding the product does not create `tpv_output_jobs` and does not send the item to kitchen.

Expected result

The open TPV ticket shows the added product or increased quantity, with line amounts and ticket totals recalculated and the item still unpaid until a payment action is completed.

Related articles