Fast food ordering software, because speed is the whole business
Fast food runs on throughput — orders in, food out, queue moving, every minute of service.
Built for how fast food runs
Lunch arrives in twenty minutes and leaves in twenty minutes, and the thing that limits how many people you serve is almost never the kitchen. It is how quickly they can decide. Reading the board, changing their mind, asking what comes with it — all of it happens at the till, in front of the queue, while somebody is also trying to take money.
Separating those two jobs is the whole trick. Let the deciding happen at a screen that never gets impatient and never mishears, and the till goes back to doing the fast part. Nothing about the menu changes, because it is the same menu — edited once, right on every surface at the same moment.
After that the constraint moves to the counter itself. A guest with no way of knowing whether their food is coming asks, and asking costs somebody thirty seconds each time. A number on a board above the counter turns the crowd back into people waiting rather than people queueing twice.
Where the queue actually stops
Deciding at the till
A counter screen takes the order — categories, search, dietary filters and the same step-by-step builder the table menu uses. The till takes money.
The ticket somebody walked away from
The order waits until it is paid for. The cashier takes payment and only then does the kitchen see it, so nothing is cooked for a screen that got abandoned.
A number instead of a question
Finishing an order prints a ticket number. When the kitchen bumps it ready, that number goes up on the pickup board over the counter, and the counter stops being a waiting room.
Two screens, one menu
A dish whose ingredients have run out stops being orderable at the kiosk at the same moment it stops being orderable everywhere else. There is no second menu to keep in step.
Tickets that route themselves
Items carry a station, so a single order splits across the fryer, the grill and the drinks without anyone sorting it. The order is Ready when every station has reported, not when the first one is done.
Numbers that reset with the day
The ticket sequence runs per day in your venue's own time, so the first ticket of Saturday is the first ticket of Saturday however late Friday ran.
Relevant modules
Common questions
What hardware does the kiosk need?
A screen with a browser. A tablet in a floor stand is the usual answer. The pickup board is any second screen and does not need to be touch.
How many kiosks can we run?
As many screens as you want to open the address on. They share one order stream and one ticket sequence.
Does the kiosk take card payments?
Payment stays at the till, where the order is released to the kitchen. Bring your current setup to the demo and we will walk through how the two sit together.
Can guests order in another language?
Yes — whichever languages you have switched on, priced in a currency they recognise. The kitchen ticket comes through in yours.
What happens when something sells out?
It stops being orderable everywhere at once — the kiosk, the tables and the wall board — because all three are reading the same menu.