Antylogic
DemoApp login

399 operational guides

Docs sections
DocsPOS
Device

List POS tickets

Review Harbor Soho POS tickets for the active service, filter the loaded accounts, and open an account when item-level ticket detail is needed. This read-only guide is scoped to the selected location and service session.

In this article

The POS ticket list gives front-of-house teams a live view of accounts during service without changing ticket state. In Harbor Soho, the Tables view surfaces active-session accounts on the floor plan, while All accounts turns the same loaded tickets into a list for review.

Tables and All accounts request detailed ticket data with include_details=true, so the POS can show order lines and related payment, allocation, and invoice context when those records exist. Open an account when the operator needs item-level detail.

Before you start

  • You are signed in to Antylogic with access to Harbor Demo Group and Harbor Soho.
  • Your role can use the POS for Harbor Soho, normally through `tpv:use`.
  • Harbor Soho has an active service session, such as the Soho lunch service in the GB demo runtime.
  • The capture runtime provides Olivia Hart plus `TPV_TICKET_ID`, `TPV_PAID_TICKET_ID`, `TPV_TERMINAL_ID`, and `TPV_STAFF_ID` for reliable ticket examples.

Instructions

  1. 1.

    Open Tables

    Open Harbor Soho's POS on the Tables tab. The screen resolves the active service session, loads tickets for that session, and uses them to show occupied tables, active accounts, and entry points into each ticket.

  2. 2.

    Review All accounts

    Switch to All accounts to review the tickets already loaded for the active session. Operators see ticket number, status, total, diners, tables, staff, reservation context, and payment information, with higher ticket numbers shown before older accounts.

  3. 3.

    Filter the loaded accounts

    Use the All accounts filters to narrow the working list by status, search text, total range, diner count, tables, and payment method. These controls filter the tickets already loaded by the POS; they are not extra backend filters for terminal, date range, table, payment method, or pagination.

  4. 4.

    Open an account for detail

    Open the account from Tables, Accounts or All accounts when the team needs its items and production state. Tables and All accounts use detailed loading with include_details=true so order lines, payments, allocations, invoices, and fiscal context can appear when those records exist.

  5. 5.

    Respect access limits

    Everyday POS operators work against the active service session. Users with broader ticket permissions can list location tickets with service-session and status filters, while service-calendar access only allows reading tickets for a closed service session in the same location.

Validations and limits

  • Normal POS use requires `activeSession.id`; without an active service, the operator flow cannot load active-session tickets.
  • Ticket listing is always scoped to the selected `locationId`.
  • Without include_details=true, the endpoint returns `Ticket[]`; with include_details=true, it returns `TicketDetail[]`.
  • The backend list action supports `service_session_id`, optional `status`, and include_details; it does not implement pagination, backend search, terminal, table, payment-method, or date-range filters for this action.
  • The visible status set used by the POS is `pending`, `partially_paid`, `paid`, `closed`, and `void`.
  • A POS-only or KDS-only user cannot list an arbitrary or closed session unless another permitted access path applies.
  • Invalid include_details values behave as false, and invalid status is not documented as a controlled validation path for this action.
  • If detailed loading cannot fetch required related data, the detailed list fails instead of returning partial ticket detail.
  • When there are no tickets, the English empty state is `No tickets yet.`

Expected result

The operator can review Harbor Soho's current POS accounts, narrow the visible list, and open an account for item-level order review without creating, editing, paying, voiding, closing, printing, or invoicing tickets.

Related articles