Kitchen display (KDS)

Goal

Work kitchen / expo tickets: start cooking, mark ready, bump, and recall.

Who it is for

Kitchen and expo staff with pos.restaurant.kitchen.send and module pos.

Preconditions

• Restaurant stations configured (Point of Sale → Restaurant).
• Orders fired/sent from frontline, waiter pad, or kiosk so tickets appear on KDS.

Steps

1. Open Point of Sale → Kitchen display (POS app /kds).
2. Load stations and tickets (GET /v1/pos/restaurant/stations, …/kds). Use station tabs or all-day aggregate. Stream/poll refreshes (~5s fallback).
3. Urgency: warn after ~5 minutes, late after ~10.
4. Ticket statuses: new → Start (preparing) → Ready (ready) → Bump (bumped). Recall reprints/restores (recalled).
5. Order types shown: dine-in, takeaway, delivery, quick service.

Result

Tickets advance through kitchen workflow; bumped tickets leave the active queue. Expo can coordinate across stations.

Hard stops

• Missing kitchen permission → route blocked.
• No stations/tickets configured → empty board.
• Offline: rely on poll; confirm network for bump/recall.

Related

• Waiter pad
• Kiosk
• POS apps hub