Handle KDS station scope, expiry, and reconnect
KDS keeps tenant, branch, and optional station scope from its link and token; an expired session returns to PIN entry. Confirm the link belongs to the intended branch and station, enter the PIN after expiry, and when offline, continue only with visible cached tickets and queued actions. Use the visible ticket board as the operational source of truth and verify queued actions after connectivity returns.
Before you start
- The KDS is opened for the intended branch and station.
- The device is online unless the guide explicitly describes an offline board state.
Steps
- Confirm the link belongs to the intended branch and station.
- Enter the PIN after expiry.
- When offline, continue only with visible cached tickets and queued actions.
- Verify queued actions clear after reconnection.
Expected result
The header identifies the intended branch and station, and ending the session returns to KDS authentication. Use the visible ticket board as operational truth and do not repeat an uncertain status transition.
Permissions
- A valid KDS PIN or authenticated station session is required; station assignment limits which tickets and controls are visible.
Troubleshooting
The workflow stops while staff confirm the link belongs to the intended branch and station, before they can enter the PIN after expiry.
Before reopening the workflow, verify: The KDS is opened for the intended branch and station. The device is online unless the guide explicitly describes an offline board state. Return to /kitchen without changing user, branch, or record. Try the blocked step once; if it remains unavailable, stop and provide Support the station, safe ticket reference, branch, status, and time; omit the KDS PIN. For escalation, state what happens when staff confirm the link belongs to the intended branch and station.
The visible ticket and queued-action indicator do not establish one station transition after the final checkpoint: Verify queued actions clear after reconnection.
Check the station, visible ticket, timer, current status, and last accepted or queued transition. Do not repeat an uncertain transition. Retry only when the original status remains and no queued action is visible. When no single result can be proved, pause and provide Support the station, safe ticket reference, branch, status, and time; omit the KDS PIN. Use the visible and saved records to determine whether staff could verify queued actions clear after reconnection.
Related articles
The public KDS shell still requires branch context and a valid four-digit Kitchen Display PIN before it loads orders.Read Kitchen Display tickets
The board shows active tickets, brand, promise time, elapsed time, table or guests, order note, modifiers, item notes, and allergy alerts.Accept, finish, or recall kitchen work
KDS actions move tickets through preparation and can recall the last completed action; offline actions are visibly queued on that device.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback