Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTPV
Device

How to print a TPV ticket

Send the selected TPV ticket receipt to the output queue so the active receipt printer can process it after the request is accepted.

In this article

Use this guide when floor staff need a receipt for an existing TPV ticket at Harbor Soho. The operator opens the ticket, selects Print ticket, and Antylogic queues a `ticket_receipt` job for the active receipt printer.

The action creates output jobs; it does not print synchronously inside the API request. Staff can review the queued result from Print queue and KDS.

Before you start

  • The operator is signed in to Harbor Demo Group and working in Harbor Soho.
  • The operator has a TPV role that makes Print ticket visible, normally `tpv:print` or `tpv:manage`.
  • The ticket exists in the same location and the operator can access it.
  • At least one active receipt printer is configured, either as the default ticket output device or as an active receipt-printer output device.

Instructions

  1. 1.

    Open the ticket

    From the TPV floor, open the ticket that needs a receipt. For documentation captures, use the Harbor Soho ticket detail route with `TPV_TICKET_ID`, `TPV_TERMINAL_ID` and `TPV_STAFF_ID`.

  2. 2.

    Check that printing is available

    Confirm that Print ticket is enabled. The control is unavailable when there is no selected ticket or when the operator does not have the TPV print or manage permission used by the UI.

  3. 3.

    Send the ticket to the queue

    Select Print ticket. Antylogic sends the ticket as a `ticket_receipt` request and confirms that the print job was sent to the queue.

  4. 4.

    Review the queued job

    Open Print queue and KDS to review the receipt job. It starts as pending and stays tied to the ticket, output device and service context while the printer bridge handles the lifecycle.

Validations and limits

  • The request only targets tickets that exist in the same location as the route.
  • If no active receipt printer is selected or available, the request can complete without creating a visible output job.
  • Repeated print requests are not deduplicated and can create duplicate receipt jobs.
  • If the frontend does not send `requested_by_staff_id`, the queue may show the requester as System.
  • Retry, failure handling and marking printed belong to output-job lifecycle actions, not this print request.

Expected result

The selected ticket is queued as a pending `ticket_receipt` output job for the active receipt printer, ready for the output runtime or bridge to process.

Related articles