Antylogic
DemoApp login

399 operational guides

Docs sections
DocsKDS and TPV
Device

Open a TPV ticket from KDS

Open the TPV ticket detail for an account already visible on the KDS board. This lets the operator review the account, its items and operational context without changing the ticket or kitchen item statuses.

In this article

Use this guide when an operator needs to move from a live KDS account column to the full TPV ticket detail behind it. The KDS account header shows the account, table and staff member so the operator can confirm the right ticket before opening it.

This action is navigation only. It preserves staff and terminal context when available, and does not serve, prepare, close, edit, invoice or charge anything by itself.

Before you start

  • Select the organisation and location that own the service. In the GB demo captures, this is Harbor Demo Group and Harbor Soho.
  • KDS must be enabled in the TPV settings for the location.
  • There must be an active service session for the location.
  • The account must be visible as a KDS column: the ticket is open and has at least one kitchen-relevant item that is not served or cancelled.
  • The operator needs KDS access and permission to open the linked TPV ticket. In the current app, loading the destination ticket detail requires `tpv:use`.

Instructions

  1. 1.

    Open the KDS board

    Open the KDS route for the location. The board checks KDS access, reads TPV settings, loads the active service session and shows only open accounts with kitchen-relevant work.

  2. 2.

    Find the account column

    Locate the account column for the service ticket. In the GB demo, use the Harbor Soho account associated with Olivia Hart when that ticket is visible on the board.

  3. 3.

    Press the account header

    Press the full header at the top of the KDS column. There is no separate open-ticket button; the account header itself is the touch target.

  4. 4.

    Review the TPV ticket detail

    The app opens `LocationTPVTicketDetail` for the same `ticketId`, carrying the ticket staff member and selected terminal when available. The destination back action returns to the KDS board. Only when the detail has no previous screen, for example after reloading the page on web, does it open the POS on All accounts.

Validations and limits

  • If no organisation or location is selected, KDS does not show account columns.
  • If the operator lacks KDS access, KDS shows the permission state instead of the board.
  • If `enable_kds` is off, the board shows the disabled KDS state.
  • If there is no active service session or no open ticket with kitchen-relevant pending items, there is no account header to open.
  • The KDS account header is pressable only when the operator passes `canOpenTPVTicket`.
  • Opening the ticket from KDS does not update `tickets`, `ticket_items`, `production_status`, `tpv_output_jobs`, payments or invoices.
  • The destination detail requires a non-empty `ticketId`; an empty value shows the missing-ticket state.
  • The current destination screen only enables its main ticket queries when `selectedOrgId`, `selectedLocationId`, `ticketId` and `canUseTPV` are present.
  • The backend rejects blank ticket IDs, tickets from another location and tickets that fail `requireTicketAccess`.
  • Do not document KDS-only users as fully supported for this flow until the current `tpv:use` destination requirement is confirmed or changed.

Expected result

The same open account is shown in the TPV ticket detail with its items, totals and operational context available for review. No ticket data or kitchen status changes are made by the KDS open action.

Related articles