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. Choose Accept when preparation starts, choose Finish when the ticket is complete, and use Recall Last only to restore the last relevant ticket. 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.
Accept kitchen work
- Select Accept when preparation starts.
- Confirm the intended ticket moves to its next preparation state or shows a queued action.
Finish kitchen work
- Select Finish only when the intended ticket is complete.
- Confirm the ticket leaves the active preparation state or shows a queued action.
Recall the last ticket
- Select Recall Last only for the most recent relevant completed ticket.
- Confirm that one ticket returns to the visible working state.
Expected result
One accepted status change moves the intended ticket to its next valid state or clearly remains queued. 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
Accept, Finish, or Recall Last is missing for the intended kitchen ticket.
Confirm the KDS PIN session, branch, station, ticket status, and connection. Station scope and ticket state control which actions appear. Do not use another station to bypass the restriction; report the station and safe ticket reference without the PIN.
A kitchen action remains queued or the ticket appears in an unexpected column.
Use the visible board and queued indicator as the record. After reconnection, verify whether the ticket changed once before selecting any action again. Retry only when the original status remains and no queued action exists.
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.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