Order queues
Every order moves through your counter on a fixed rail — pay first, pay at pickup, or pay at the end. Choose the rail per queue; the board, the kitchen, and the pickup screen follow it automatically.

Placed
Preparing
Ready
Flow Studio
Every ORDERING queue runs one of three payment flows. Switch anytime — it applies to new orders immediately.
Customers order → pay at the counter → kitchen prepares → pick up when ready.

Pay first
Fastest at the tillBest for cafés, food trucks, and pharmacies — order, pay at the counter, then collect.

Pay at pickup
One scan, handed overBest for bakeries and espresso bars — the kitchen starts the moment they order.

Pay at the end
One tab per tableBest for dine-in restaurants and pubs — served at the table, settled at the end.
Three stations
The cashier board, the kitchen display, and the pickup rail all read the same order in real time.
Placed
Preparing
Ready
Cashier — a shared, real-time kanban. Any cashier can claim any order; a presence strip shows who's already on it.

Kitchen — big cards, a ticket-age timer, and a stale bar past five minutes. A two-tone chime, and batch mark-ready.
Pickup — a compact rail on the counter, or its own full screen by the door.
One QR, start to finish
Every order gets one QR the moment it's placed. The customer shows it, you scan it, and the exact order opens at the counter — take payment on your own card machine or in cash, tap confirm, done. The same code carries the order through called, paid, and picked up — no reprinting.

If a customer misses the call, the order holds for a configurable window — 30 minutes by default — before it's marked no-show. "Revive & charge" brings it straight back to life if they show up late.
No camera? A 6-character code keypad works everywhere the scanner does.
Pausing, honestly
Ten minutes of silent pause quietly nudges your staff — nobody gets forgotten.
Either way, waiting customers see an honest "Back in a moment" — never a fake ready state.

Keep taking orders; just pause calling customers forward.
Stop taking new orders entirely.
Built for a rush
Orders sit in one shared pool. Claims are atomic on the server — if two cashiers tap the same order at once, exactly one wins, and the other gets a friendly heads-up, not an error. A presence strip shows who has what open, in real time.
Set a batch size and a timeout — orders promote to the kitchen together, whichever comes first. Auto-start preparing, or hold every order for an explicit staff tap (pharmacies verify before they fill).
Eleven ready-made ORDERING templates, each pre-configured with the right flow, batching, and a starter menu.
Questions
No. They scan a QR with their phone camera, and the order page opens in the browser — no download, no account required.
The order holds in a no-show window (30 minutes by default, and you can change it) instead of vanishing. If they show up late, "Revive & charge" brings it straight back to an active order.
Yes. Flow Studio applies to new orders immediately — nothing needs republishing, and orders already in progress finish on the flow they started on.
The board, kitchen, and pickup screens all recover automatically over a shaky connection — orders reconcile the moment the connection returns, so nobody double-serves or loses a ticket.
Yes — that's the default. Claims are atomic, so two cashiers can never end up serving the same order.
A phone or tablet for the counter and one for the kitchen — the browser is the app. No proprietary terminals, no ordering kiosks.
English and German today, with more on the way — the customer-facing order flow and your dashboard both switch with one tap.
Ready when you are
Free to start, no card required. Pick a flow, add your menu, and you're live.