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. Open the authenticated KDS board, read the full ticket and highlighted alerts, and confirm brand and station context. 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
- Open the authenticated KDS board.
- Read the full ticket and highlighted alerts.
- Confirm brand and station context.
- Use Accept or Finish only for the intended ticket.
Expected result
The board shows current station tickets in their correct status columns with visible age or timing. 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
POS does not let staff open the authenticated KDS board; they cannot continue to read the full ticket and highlighted alerts.
A safe retry starts by confirming: The KDS is opened for the intended branch and station. The device is online unless the guide explicitly describes an offline board state. Keep the same branch and record, reopen /kitchen, and try the blocked action once. If it still fails, stop and send Support the station, safe ticket reference, branch, status, and time; omit the KDS PIN. Capture the displayed state produced when staff open the authenticated KDS board.
The visible ticket and queued-action indicator do not establish one station transition after the final checkpoint: Use Accept or Finish only for the intended ticket.
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. An unresolved mismatch needs Support review with the station, safe ticket reference, branch, status, and time; omit the KDS PIN. Check the saved state after staff use Accept or Finish only for the intended ticket.
Related articles
The public KDS shell still requires branch context and a valid four-digit Kitchen Display PIN before it loads orders.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.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.
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