Antylogic
DemoApp login

399 operational guides

Docs sections
DocsKDS operations
Device

Open Manual Service From KDS

Open an ad hoc service session from Harbor Soho KDS without choosing a scheduled calendar occurrence. In manual mode, Antylogic creates the internal service records needed to make the KDS board active.

In this article

Use this guide when Harbor Soho has no active KDS service and a TPV-authorised operator needs to start kitchen operations immediately from the KDS screen.

Manual opening does not select Soho lunch service or any scheduled occurrence. KDS confirms Manual service, sends no `occurrence_id`, and the backend creates the internal event and occurrence that support the new service session.

Before you start

  • Harbor Demo Group and Harbor Soho are selected in the app context.
  • The operator opens `/:orgId/:locationId/kds` for Harbor Soho, optionally with `?terminalId=${TPV_TERMINAL_ID}`.
  • KDS is enabled for Harbor Soho through `tpv_settings.enable_kds`.
  • The operator has KDS access through `kds:view`, `kds:use` or `kds:manage`.
  • The operator has TPV operation access; `tpv:use` is the proven backend permission for opening the service.
  • Harbor Soho has no `service_session` with `status: "open"`.

Instructions

  1. 1.

    Open Harbor Soho KDS

    Open the KDS route for Harbor Soho. The page checks the selected organisation and location, KDS permission, TPV settings and the active-service state before showing service controls.

  2. 2.

    Open The Service Modal

    Use the KDS header control to open the service modal. If Closest service is offered, switch to Manual service; this guide does not use Soho lunch service or any public calendar occurrence.

  3. 3.

    Confirm Manual Opening

    Confirm with Manual service selected. KDS opens the service without an `occurrence_id`, so Antylogic creates the open service session and its internal calendar event and occurrence for Harbor Soho.

  4. 4.

    Verify The Active KDS

    After success, the modal closes, the service-opened notification appears, and the KDS header moves to the active-service state. Tickets and output jobs refresh for the new service context as downstream board data.

Validations and limits

  • Missing selected organisation or location blocks the KDS screen before this action can start.
  • Missing KDS permission or disabled KDS settings prevent access to the opening controls.
  • A KDS-only operator can view the modal, but opening the service is governed by TPV operation permission; `tpv:use` is the backend-proven requirement.
  • Only one open service session is allowed per location.
  • The manual request must not include `occurrence_id`; adding it changes the action to the calendar-service opening path.
  • The KDS manual modal does not collect staff, opening time, duration, title or layout choices.
  • Opening the service does not open a cash register session, create tickets, collect payments or process output jobs.

Expected result

Harbor Soho has one open `service_session` linked to generated internal service event and occurrence records. The KDS board is now scoped to that active service; ticket creation, payments, cash sessions and output-job processing remain separate actions.

Related articles