On this page
For cooks, bartenders, baristas and chefs. Production boards
(/production) lists the stations of your branch with their open ticket
counts; open the board of the station you are working on the screen at
that station. Every board is the same screen with the same buttons — the
station only changes what each item shows.
Where tickets come from
When a waiter or cashier sends an order, every line is routed to a station (see Stations & routing): burgers to the grill, mojitos to the bar, cappuccinos to the barista, and so on. One ticket per order and station appears on that board in the Active lane the moment the order is sent (a sound can be switched on with the bell button). Later courses arrive held (dashed, “C2 · held”) and cannot be worked until the waiter or expeditor fires the course.
Reading a ticket
| Part | Meaning |
|---|---|
| Table / customer / order number | who it is for; order type (dine-in, takeaway, delivery…), guests, assignee |
| Timer | time since the ticket was fired: green → amber at 70 % of the station target → red and flashing when late |
| Status pill | New · Accepted · Preparing · Ready · Completed · Delayed · Recalled · Re-fired · Cancelled |
| RUSH / VIP badges | priority tickets sort to the front; VIP comes from the customer tier or a VIP table |
| Allergy warning | never truncated; from the order and from each line |
| re-make ×n / spillage ×n | how many times the ticket was re-fired or a drink was spilt |
| Items | quantity, name, modifiers (kitchen) or the drink spec (bar / barista), notes in amber, seat number, per-item allergy |
Tap an item to mark it ready; when the last item is ready the ticket is ready.
Working a ticket
| Button | Does | Needs |
|---|---|---|
| Accept | you have seen it (stations with auto-accept, e.g. barista, skip this step) | kitchen.complete / bar.complete |
| Start | preparing; the order’s lines show preparing at the POS and the expeditor | same |
| Ready | done at this station; the ticket moves to the Ready lane and the pass sees READY | same |
| Bump | completed and off the board (in the Done lane) | same |
| Recall | bring a ready / bumped ticket back (wrong plate, sent back) | same |
| ⋮ Mark delayed | flag it delayed with a reason (also automatic past the station’s delayed after time) | same |
| ⋮ Re-fire / Re-make | make it again; asks for a reason, counts a re-make | same |
| ⋮ Spillage | bar & barista: record a spilt drink (counts, no re-fire) | bar.complete |
| ⋮ Rush / VIP | priority; rush tickets sort first on every board | same as complete |
| ⋮ Bartender / Barista / Assigned to | who is making it | same |
| ⋮ Cancel ticket | this station will not make it (the order line stays) | same |
| ⋮ History | every event with its time | view |
A ticket changed on another screen refuses your tap with “This ticket changed on another screen. Reloaded.” — the board refreshes itself.
The three displays
- Kitchen (KDS) — modifiers as text under the item (“+ Medium rare”, “+ Extra cheese”), notes, seat, allergy per line; course number.
- Bar (BDS) — spirits, beer, wine, cocktails, mocktails, soft drinks, bottle service, shots, mixers, draught beer: the drink’s measure (single / double), ice, garnish and the recipe from the active recipe version; spillage and re-make actions.
- Barista — drink, size, milk, shots, decaf, sugar, syrup, temperature, ice, toppings as chips; customer, order, table and dine-in / takeaway in the header; auto-accept by default. States: New → Preparing → Ready → Collected (bump) / Re-make.
Lanes
Active (new, accepted, preparing, delayed, recalled, re-fired; rush and VIP first, then delayed, then oldest), Ready (waiting at the pass) and Done (completed and cancelled since the start of the day). The header counts late tickets.
Offline
Boards need the server: they keep showing the last tickets and poll every 30 s; bumps are refused while offline (the outbox does not cover production actions — a ticket bumped on a dead connection would be lost to the pass).