When you press Send to prep on a tab, each unfired line becomes a task in a workflow. The Pipelines tile shows those tasks and lets a station advance them. It is the mobile kitchen display, but it is generic: any workflow the organization runs (pickup, service appointments, custody) shows here too.
Picking a workflow
The dropdown at the top lists the workflow definitions in your organization. Orders fire into prep-pipeline by default, whose stages are:
| Stage | Meaning |
|---|---|
| Received | The ticket has arrived at the station |
| Prepping | Someone has started it |
| Ready | Done — the tab shows a Ready chip on the Tabs screen |
| Delivered | Taken to the guest |
Other workflows have their own stages; the screen shows whatever the definition says.
The dropdown only lists workflows that exist in the organization. They are created automatically the first time something uses them — the prep pipeline appears after the first fire, the check-in pipeline after the first walk-in.
What a task shows
Each card is one fired ticket. Its title is chosen in this order: the tab's label, then the service point, then the order number, then the first product — so a ticket reads "Patio 4" or "T7" rather than an internal id when the tab has a name.
Under the title: the lines with quantities and their modifiers, course and seat if set, special instructions, how long since it was fired, and the SLA state. A task past its due time is marked overdue and the tab it belongs to shows Overdue on the Tabs screen.
Tasks are listed in every working status — new, pending, in progress and blocked — plus what was finished in the last 24 hours, so a station can see what just went out.
Stations
If fired lines carry a prep station (kitchen, bar, barista — set on the product), a chip row appears. Pick a station and the list shows only tickets with lines for it. The All view is the pass. A ticket that spans two stations shows under both.
Working a ticket
| Action | What it does |
|---|---|
| Advance | Move to the next stage |
| Mark done | Complete it outright |
| Add note | A note visible on the task's history |
| Snooze | Hide it for a while without losing it |
| Escalate | Escalate now rather than waiting for the SLA to breach |
| Reassign | Hand it to another person or station |
| Cancel | Drop the ticket; the order line stays on the tab |
Advancing to Ready is what flips the tab's chip. Delivering it clears the chip.
Snooze asks how long: pick a preset or Custom (minutes). It pauses the SLA timers for that task, so a ticket waiting on the guest does not go overdue for a reason nobody controls.
Escalate confirms first — Escalate this task to the next tier now? — and pushes it to the next tier immediately rather than waiting for the SLA to breach.
Reassign takes comma-separated emails, and the list you type replaces the current assignees rather than adding to them. Include everyone who should still be on it.
Cancel task drops the ticket. The order line stays on the tab, so the guest is still charged for it unless you also remove the line in the POS.
Refires and duplicates
Firing is idempotent. Lines that already have a ticket are skipped, and if every line on a tab has been fired the server answers "All requested items are already fired". To cook something again, add a new line and fire that.
The manager view
The Operations dashboard (reached from the operations screens' overflow) polls wait times and escalations every 30 seconds: average and longest waits per stage, tickets that have breached their SLA and those about to. It is separate from the ticket list so its polling does not redraw the screens staff are working on.
When something goes wrong
| What you see | What it means | What to do |
|---|---|---|
| No workflows configured | The organization has no workflow definitions yet | They appear on first use — fire something from the POS, or create one in the admin under Workflows. |
| Pick a workflow and nothing loads | No workflow is selected | Choose one from the dropdown at the top. |
| No active tasks in this workflow | Nothing is in flight | Expected between rushes. Tickets appear when items are fired from the POS. |
| No tickets for this station | The station filter is on and has nothing | Switch to All stations to see the pass. |
| A fired item never appeared | Its product has no prep station, or you are filtered to another station | Check All stations; set the product's station under menu and stock. |
| All requested items are already fired back at the POS | Everything on the tab has a ticket | Add a new line and fire that — firing does not duplicate. |
| A ticket stays overdue after the guest was served | It was never advanced past Ready | Advance to Delivered, or Mark done. |
| Reassigning lost the previous owner | The email list replaces the assignees | Reassign again with every address that should be on it. |
| A cancelled ticket is still on the bill | Cancelling the task does not touch the order | Remove the line in the POS if it should not be charged. |