Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTPV and KDS
Device

Complete a TPV Output Job

Mark a visible pending or claimed TPV output job as completed for Harbor Soho's active service and selected terminal. The existing job is preserved with terminal metadata and completion time; this is an operator acknowledgement, not proof that a printer, bridge, preview, or KDS screen physically processed the output.

In this article

Use this guide when a POS operator, floor manager, KDS supervisor, or support reviewer needs to close an item in the Print and KDS queue after checking the current Harbor Soho service.

The manual path starts in the TPV floor workspace, opens the Print and KDS queue, and uses Mark printed. In the current en-GB runtime, the app may still show Spanish fallback labels such as Cola de impresión y KDS and Marcar impreso.

Before you start

  • Harbor Soho is selected and the POS is opened with terminalId=${TPV_TERMINAL_ID}.
  • There is an active service session for the selected terminal, and Olivia Hart is selected if the terminal asks for staff identification.
  • The user can open the TPV page with tpv:use and can view the queue with tpv:print or tpv:manage.
  • A visible tpv_output_job exists for the active service session and terminal scope, with status pending or claimed.
  • The job is not already completed or failed; failed jobs belong to the retry flow.
  • For the automatic KDS path, KDS is enabled and the operator has kds:use or kds:manage.

Instructions

  1. 1.

    Open Harbor Soho POS

    Open the Harbor Soho TPV floor workspace with the terminal parameter. If the staff selector appears, choose Olivia Hart before continuing.

  2. 2.

    Open the Print and KDS queue

    From More POS actions, open Print and KDS queue. The queue loads output jobs for the active service session and filters them to the selected terminal scope.

  3. 3.

    Choose an eligible job

    Review the job kind, status, ticket or device details, requester, request time, errors when present, and counters. Use a pending or claimed row that belongs to the current terminal.

  4. 4.

    Mark the job printed

    Select Mark printed, or the Spanish fallback Marcar impreso. Antylogic updates the existing output job to status completed and writes terminal_id and claimed_by_terminal_id when a terminal is selected.

  5. 5.

    Confirm the completed state

    Wait for the success message and refreshed queue. The row should show completed status and no longer offer the manual Mark printed action.

  6. 6.

    Review automatic KDS completion

    For KDS jobs, the KDS runtime can claim and complete compatible jobs automatically. Review the completed result from the same TPV output-job queue when the runtime has processed the job.

Validations and limits

  • The action uses PUT /api/app/{orgId}/{locationId}/tpv-output-jobs/{id}; there is no separate /complete endpoint.
  • The backend uses the path id as the job id, checks the job belongs to the current location, and validates terminal_id when it is present.
  • The submitted status is normalised and must be one of pending, claimed, completed, failed, or cancelled.
  • KDS-only access can complete only jobs whose existing job_kind is kds.
  • Completing the job updates the existing tpv_output_job; it does not create a ticket, ticket item, payment, invoice, or new output job.
  • completed_at is set only the first time the job is completed; repeat completion keeps the original timestamp.
  • Manual completion does not increment attempts and does not set failed_at.
  • Manual completion records staff acknowledgement only and must not be described as physical print or bridge verification.

Expected result

The same tpv_output_job is saved as completed, terminal metadata is stored when available, completed_at is set if it was missing, and the refreshed queue stops showing Mark printed for that row.

Related articles