Skip to content

Kitchen & bar

Expeditor & stations

The pass, releasing orders, and setting up stations and routing.

3 min read

Expeditor (/production/expeditor)

For the pass, packing and pickup. Needs expeditor.view; actions need expeditor.dispatch. The screen shows every open order of the branch across all stations, one card per order:

Table 12 · Dine-in · WAITING          08:41
Burger        Grill                READY
Fries         Hot Kitchen          READY
Mojito        Rooftop Bar          PREPARING
Cappuccino    Barista              READY
Cake          Pastry · C2          WAITING   (held)
Missing: Mojito, Cake
Line state Meaning
WAITING not started (or the course is still held)
PREPARING a station is on it
READY the station bumped it ready
DONE completed / served
CANCELLED the station cancelled it

Missing lists what still has to arrive before the order can go.

Lanes

In progress (something missing) · Ready to go (everything ready, or packed) · Released (handed to a runner / the counter, waiting to be confirmed collected).

Actions

Button Does
Fire course n releases a held course to its stations (dine-in courses)
Packed takeaway / delivery: bags checked and closed (packing)
Runner assign the runner or driver
📝 a dispatch note (“no cutlery”, “call on arrival”)
Release the order leaves the pass (released); refused while something is still in production — Release anyway forces it (the missing items follow)
Collected the guest / driver has it: the order’s lines become served, the card leaves the board

Everything a station bumps shows here within a second (realtime; the screen also refreshes every 30 s).

Stations & routing (/production/stations)

Needs production.manage.

Stations

A station is a place that makes things at a branch. New station: code, name, kind (main kitchen, grill, fryer, pizza, bakery, pastry, dessert, salad, cold kitchen, bar, cocktail bar, wine station, beer station, barista, juice, smoothie, packing, room service, expeditor, pickup), display (defaults from the kind: kitchen kinds → KDS, bar kinds → BDS, barista / juice / smoothie → barista, expeditor / packing / pickup → expeditor), outlet, colour, target prep (drives the timer colours), flag delayed after (default 150 % of target), auto-accept (skip the Accept step) and sort order. Archiving a station hides it; its tickets keep their history.

Rules — where does a line go?

Without any rule a sent line goes to its item’s default station, else its category’s default station, else the first station of the branch whose kind serves the item’s production kind (kitchen / bar / barista / bakery), else the first kitchen. Items with production kind none (bottled water, services) produce nothing.

A rule overrides that. Every criterion left blank matches anything; at least one is required:

Criterion Example
Item “Chips at the bar”
Category Grill → Grill station
Modifier option “Iced” option → Bar
Production kind every bakery item → Ovens
Order type delivery → Packing
Branch only at Entebbe

Action: Route (this station instead of the default), Also route (a copy here too — “takeaway orders also print at the pass”), Skip (nothing is produced).

Which rule wins? The most specific: item › modifier › category › order type / branch › production kind, then the higher priority. Every matching also route rule adds its copy as long as the line is produced somewhere. The station chosen and the rule that chose it are written on the ticket’s fired event, so a wrong destination is explainable from the ticket history.

Demo rules (Kampala · Kololo)

Grill → Grill, Desserts → Pastry, Bakery → Ovens, Cold drinks → Barista, Cocktails → Restaurant bar, Pizza → Hot kitchen, “Mineral water needs no production” (skip), Delivery / Takeaway → Delivery Packing (also route); Entebbe: Grill → Kitchen, Hot drinks → Barista.