docs
/
Appmint Mobile

Prep, production and workflows

Route and manage work through prep stations, production stages and service workflows.

Prep provides a focused station view, while Pipelines opens general workflow tasks. Send to prep routes selected unsent order lines into their configured workflow. Use stations for food preparation, printing, assembly, pickup, service appointments or other production work. The workflow supplies the stages and actions; it is not limited to restaurant service.

Picking a workflow

Choose Prep display in Device setup for a dedicated production workstation. Set the workflow and station once, then use that view through the shift. Front-desk, server and cashier devices can keep their own layouts while working the same order records.

A print shop might use Received → Artwork review → Printing → Finishing → Ready; an assembly area might use Received → Assembly → Inspection → Dispatch. Configure those stages centrally, then work them on mobile.

The dropdown at the top lists the workflow definitions in your organization. Orders fire into prep-pipeline by default, whose stages are:

StageMeaning
ReceivedThe ticket has arrived at the station
PreppingSomeone has started it
ReadyDone — the tab shows a Ready chip on the Tabs screen
DeliveredTaken to the guest

Other workflows have their own stages; the screen shows whatever the definition says.

Nothing to pick?

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

ActionWhat it does
AdvanceMove to the next stage
Mark doneComplete it outright
Add noteA note visible on the task's history
SnoozeHide it for a while without losing it
EscalateEscalate now rather than waiting for the SLA to breach
ReassignHand it to another person or station
CancelDrop 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". For additional production, add the intended new work and send it as a new batch.

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 seeWhat it meansWhat to do
No workflows configuredThe organization has no workflow definitions yetThey appear on first use — fire something from the POS, or create one in the admin under Workflows.
Pick a workflow and nothing loadsNo workflow is selectedChoose one from the dropdown at the top.
No active tasks in this workflowNothing is in flightExpected between rushes. Tickets appear when items are fired from the POS.
No tickets for this stationThe station filter is on and has nothingSwitch to All stations to see the pass.
A fired item never appearedIts product has no prep station, or you are filtered to another stationCheck All stations; set the product's station under menu and stock.
All requested items are already fired back at the POSEverything on the tab has a ticketAdd a new line and fire that — firing does not duplicate.
A ticket stays overdue after the guest was servedIt was never advanced past ReadyAdvance to Delivered, or Mark done.
Reassigning lost the previous ownerThe email list replaces the assigneesReassign again with every address that should be on it.
A cancelled ticket is still on the billCancelling the task does not touch the orderRemove the line in the POS if it should not be charged.