Understand Kitchen Display sound alerts
Kitchen Display plays a short browser-generated alert when polling finds one or more order IDs that were not on the previous board. Keep the authenticated KDS board open, allow audio in the browser or interact with the page if the browser requires it, and use the visual ticket board as the source of truth. 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
- Keep the authenticated KDS board open.
- Allow audio in the browser or interact with the page if the browser requires it.
- Use the visual ticket board as the source of truth.
- Check speaker volume when new tickets appear silently.
Expected result
New ticket IDs can trigger an audible alert while the visible station board remains the source of truth. 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
Staff cannot keep the authenticated KDS board open because the control is missing, disabled, or rejected before they allow audio in the browser or interact with the page if the browser requires it.
Check the required state before trying again: The KDS is opened for the intended branch and station. The device is online unless the guide explicitly describes an offline board state. Check those conditions on /kitchen and repeat only the blocked step once. Preserve the screen and ask Support to review the station, safe ticket reference, branch, status, and time; omit the KDS PIN. Note whether POS changes as staff keep the authenticated KDS board open.
The visible ticket and queued-action indicator do not establish one station transition after the final checkpoint: Check speaker volume when new tickets appear silently.
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. The final evidence must establish whether staff could check speaker volume when new tickets appear silently.
Related articles
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.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