Antylogic
DemoApp login

399 operational guides

Docs sections
DocsPOS settings
Device

Delete a POS output device

Remove a printer, kitchen output, control output or KDS screen from the active POS configuration after confirming the destructive action.

In this article

Output devices are managed from the POS settings area for the active location. Use this guide when a device should no longer be available for tickets, kitchen routing, control output or KDS assignment.

Deletion is permanent for the `tpv_output_devices` row. Antylogic asks for confirmation first, then refreshes the Printers and outputs list so the operator can verify that the device is gone.

Before you start

  • Be signed in to the active organisation and location. The GB documentation runtime uses Harbor Demo Group and Harbor Soho.
  • Have `tpv:manage` at location scope. Without it, the row Delete action is not shown and the backend rejects deletion.
  • Confirm that the output device belongs to the active location. The GB runtime provides `TPV_OUTPUT_DEVICE_ID=0113dc07-05ff-4691-926e-bd84d9f12ee6` for disposable capture use when the runtime can clean it afterwards.
  • Run destructive documentation captures only in the demo runtime with `cleanup_after_run` enabled.

Instructions

  1. 1.

    Open Printers and outputs

    Open `${APP_DEEPLINK_BASE}${ORG_ID}/${LOCATION_ID}/location/tpv?tab=printers` and wait for POS settings to load the printers tab. In the current GB runtime, the table may still show the Spanish fallback label `Impresoras y salidas`.

  2. 2.

    Choose the device to remove

    Find the disposable output device row for Harbor Soho, open its row actions and choose `Eliminar` if that is the visible fallback label. If the Delete action is absent, stop and use a user with `tpv:manage`.

  3. 3.

    Check the confirmation modal

    Review the `Eliminar recurso` modal before continuing. It should include the selected device name and separate `Cancelar` from the destructive `Eliminar` control.

  4. 4.

    Confirm deletion

    Select the destructive Delete action in the modal. The app sends `DELETE /api/app/{orgId}/{locationId}/tpv-output-devices/{id}` using the device id from the route and no request body.

  5. 5.

    Verify the refreshed list

    After a successful 204 response, the modal closes and the Printers and outputs table reloads. Confirm that the deleted device no longer appears, then review POS defaults if that device was used for ticket, kitchen or control output.

Validations and limits

  • `tpv:manage` is required for the UI action and for the backend delete.
  • The backend requires a non-empty `locationId` and a non-empty output device id.
  • A device id from another location is treated as not found, even if the id is known.
  • The delete is not blocked by default-output assignments or historical output jobs; those references can be cleared instead.
  • If the backend returns permission denied, not found, conflict or another error, the UI shows a save-failed toast and keeps the confirmation modal open.
  • The current landing capture catalog does not yet contain the delete-specific capture ids, so this guide should ship without screenshot bindings until those captures are registered.

Expected result

The selected POS output device is physically removed from the active location. The output-device list and POS settings are invalidated, default references can be cleared, and historical output jobs remain without deleting their history.

Related articles