Oldest first
Tickets are sorted by how long they have waited, not by table number, so the order that has waited longest is always at the top.
◈ The pass, run from a screen
A kitchen display
A kitchen display
that sorts by time, not by shouting.
The pass answers one question: what do I make next. Tabbo's kitchen display sorts by how long a ticket has waited, splits the bar and the kitchen onto their own screens, and takes tickets straight from what was rung up at the table — nobody relays an order by voice.
Ring up a table in the demo and watch the ticket land on the kitchen screen in the same moment.
What the screen actually does
A display, not a printer queue — it shows what is waited on, not what was printed.
Its own station
The bar and the kitchen each see only their own tickets — a barman is not scanning past food orders to find a drink.
Straight from the order
A ticket lands the moment a waiter rings the order up at the table. There is no verbal relay and no separate step to type it in.
A void stays visible
A line the waiter voided stays on the screen until someone in the kitchen has seen it — a steak already on the grill does not stop cooking because a row disappeared.
Tied to the table
Every ticket carries its table, so a plate that comes off the pass still knows where it is going.
No paper to lose
Nothing is scribbled and nothing is torn off a printer — the record a ticket leaves is the same one the till keeps for the receipt.
One screen, sorted by what is actually waiting
Most kitchens run on some mix of shouted orders, torn-off dockets and a whiteboard, and all three lose the one thing that matters under pressure: how long something has actually been waiting. Tabbo's kitchen display exists to answer exactly that — it is sorted by age, oldest ticket at the top, so the cook is never guessing which table has been sitting longest.
The bar and the kitchen are split onto their own view. A barman does not scroll past food tickets to find a drink order, and a cook is not distracted by a round of coffees that belongs to someone else's station.
What happens when an order changes
A ticket reaches the screen the instant a waiter rings the order up — there is no second step where somebody types it in from a paper slip, and nothing to lose between the table and the pass.
When a waiter voids a line, it does not simply vanish from the screen. It stays there, visibly struck through, until someone in the kitchen has acknowledged it — because a steak already on the grill does not stop cooking just because a row disappeared from a list. The kitchen needs to see the change, not have it happen behind its back.
| Sort order | By ticket age, oldest first |
|---|---|
| Stations | Bar and kitchen shown separately |
| Hardware | Any screen running a browser — no proprietary display |
| Source of tickets | The order as rung up at the table, no manual re-entry |
| Voided lines | Stay visible until acknowledged in the kitchen |
Questions people ask
Does it replace shouted orders and paper dockets?
That is what it is for — a ticket reaches the screen the moment it is rung up, sorted by how long it has waited, so nobody is relaying an order by voice.
What hardware does it need?
Any screen that runs a browser — a tablet or a monitor at the pass. There is no proprietary kitchen display hardware to buy.
What happens if a waiter voids something after it has been sent?
The line stays visible on the screen, struck through, until someone in the kitchen has seen it — it does not just disappear from under a dish already on the grill.
Can the bar and the kitchen see different tickets?
Yes — each station sees only what belongs to it, so a barman is not scrolling through food orders to find a drink.
Read next
Open your bar in two minutes
No installation and no call with a salesperson. If you do not like it, close the tab.