1. The waiter opens the table
They tap + New table on the tablet, pick the zone (Hall 1, Terrace, VIP) and the table. The order gets a unique identifier (e.g. M3-1942 = Table 3, 19:42) and shows on the hall map in green.
🍽️ For restaurant · café · bar
How do I send orders to the kitchen automatically?
A single tap on Send. The system reads the items on the order, groups them by internal station (pizza to the hot kitchen, salad to the cold one, mojito to the bar, coffee to the espresso station) and sends one production ticket straight to the tablet of the right station. The waiter does not decide manually where each item goes — routing is configured by us at onboarding for the whole menu.
⚡ 1 tap · instant routing to every station
🎯 Each station sees only what it prepares · no noise
🔀 Multi-wave · the order builds up over several rounds
🛠️ Set up at onboarding · zero technical work for you
How it works, step by step
The waiter works at the order level. The system works at the station level. Nobody has to remember in their head who is preparing what.
2. Add items (draft)
Quick-search items, pick the quantity, add notes for the cook ("no onion", "extra parmesan"). As long as Send has not been tapped, everything is a draft — you can fix anything without leaving a trace.
3. One tap on Send
For each line the system reads its assigned station plus the order's POS, groups the lines by (POS, station) and generates one production ticket per group. From 6 items you may get 4 tickets, sent to 4 different stations.
4. Tickets appear on the tablets
Each ticket lands instantly on the tablet of its station. The pizza cook sees only pizza; the salad cook sees only salads; the bartender sees only drinks. No mixed lists, no scrolling.
5. Multi-wave · the order builds up
The customer orders a dessert at 20:02 and a mojito at 20:17. Each wave is Sent independently and generates new tickets to the right stations — the parent order stays the same, gathering lines throughout the meal.
6. Ask for the bill + single fiscal receipt
At the end, the waiter taps Ask for the bill. The system checks automatically that every station's ticket is "delivered", and then the cashier issues one single fiscal receipt for the whole table, as required by Moldovan law.
Concrete example · one order → 5 tickets
Table 3 orders in the same wave: Pizza, Salad, Water, Tiramisu, Coffee, Mojito. The waiter taps Send. Here is what happens behind the scenes:
| Ticket | Station | Contents |
|---|---|---|
| #1 | Hot kitchen | Pizza ×1 |
| #2 | Cold kitchen | Salad ×1 |
| #3 | Bar | Water ×1, Mojito ×1 |
| #4 | Pastry | Tiramisu ×1 |
| #5 | Espresso | Coffee ×1 |
5 tickets, 5 stations, each ticket goes only where it should. The pizza cook does not see anybody else's list.
Every ticket has its own life: pizza may be ready in 12 min, salad in 4, coffee in 2, mojito in 5 — the system tracks them all independently and alerts the waiter when each is ready on the pass.
What the cook sees on the tablet
Every station has its own dedicated tablet. The screen is organised into four visual zones — the cook sees exactly which stage each ticket is at.
To accept
Freshly arrived tickets. The cook sees the order number, the table, the item, the customer notes and the age in minutes. They tap Accept to confirm they are taking the ticket, or Reject with a reason (out-of-stock, equipment failure, volume too high).
In preparation
Tickets on which Start has been tapped. That moment is recorded on the ticket, and where you have defined recipes, the system reserves ingredients according to the BOM.
Ready (on the pass)
The cook taps Ready. The waiter is notified on their tablet — they come to pick up the plate from the pass. No more whistling towards the bar, no more running to the kitchen to ask "is it ready?".
Delivered
The waiter confirms Delivered on their tablet after taking it to the table. The ticket is removed from the cook's screen; the order history stays visible on the waiter's side for the current day.
Each transition (Accept, Start, Ready, Delivered) has its own date and time in the order history — useful for retrospective inspection of the workflow.
Special cases the system handles
Two tablets on the same kitchen
You have two pizza cooks, each with their own tablet. Tickets show on both; the first to tap Accept takes it, and the other tablets hide it automatically. No duplicates, no conflicts.
Cancel before preparation
The customer changes their mind after Send has been tapped but before the cook taps Start. The waiter taps pre-prep cancel — the ticket disappears from the station's tablet, with no loss. Clean.
Terrace with different stations than the hall
You have the hall with a full kitchen + a terrace with only a bar and an espresso station. We set routing per POS: in the hall tiramisu goes to pastry, on the terrace it goes to espresso (no separate dessert station). Same menu, routing adapted per point of sale.
We take care of the setup
We do not hand you a 200-page manual so you can configure routing item by item. We do the technical part for you, as part of the Extra HoReCa onboarding package. You describe what is prepared where, and we translate it into the system.
1. Discovery 30-60 min
We talk about your kitchen: how many stations you have, who prepares what, whether the bar is separate from the kitchen, whether the terrace has its own stations. We map your reality.
2. We define the stations per POS
In ~30 minutes we configure the list of stations for each POS (kitchen-hot, kitchen-cold, bar, pastry, espresso, or any other names that fit your venue).
3. We tag the items
Each menu item is assigned its default station. Later changes (adding a new item, moving desserts from pastry to espresso) are done by the manager, or with a small amount of assistance from us.
4. End-to-end test
We send a test order to every station, check that the ticket lands where it should, that customer notes show correctly, and that the Accept / Start / Ready buttons do what they should.
Frequently asked questions
Can the waiter still edit an order after tapping Send?
It depends on the ticket's stage. Before the cook taps Accept — the waiter cancels the line pre-prep, with no loss. After Start — cancellation generates a real loss and requires approval from the shift manager (the system records the reason).
What happens if an ingredient has run out?
The cook taps Reject with the reason "out-of-stock". The ticket returns automatically to the waiter's tablet with an alert. The waiter informs the customer, proposes an alternative, adds the replacement item — new wave, new ticket.
Can the waiter order the sequence in which dishes arrive?
Yes, at wave level. Starters sent in wave 1 arrive before the mains in wave 2 — standard practice is for the waiter to send waves in the desired serving order.
How many stations can I have in a venue?
As many as you need. The system does not limit the number of stations per POS. Licensing cost depends on the number of points of sale (POS terminals), not on how many internal stations each POS has.
Are the tickets also printed on paper at the station?
The screen is the main source — a dedicated tablet per station. If you also want a thermal printer at a station (some older kitchens prefer it for the background noise), ⚙️ available on request based on your hardware setup.
Does the cook see the customer's special notes?
Yes. The waiter adds the note on the relevant line ("no onion", "extra parmesan", "well done", "gluten-free") and it appears clearly on the station's ticket, under the item name. Nothing is lost in oral transmission.
Want a POS system + automatic kitchen routing?
Automatic routing to stations (kitchen-hot, bar, pastry, etc.) with dedicated tablets is included in the Extra HoReCa package. Division setup and product → station routing rules are done by us at onboarding, based on the conversation about your real workflow. Package comparison + current pricing → see the pricing page.
Book a conversation
We show you live what the waiter flow and the cook's tablet look like, then we discuss what your real station map looks like. Routing setup is done by us at onboarding — no technical work for you.
SGAPPS LABS SRL · Chișinău, Moldova · Continuously in production since 2018 · POS · ERP · MEV fiscal register · Android fleet