Board
The queue, oldest first. On a wide screen it becomes full-height columns that scroll sideways, so the oldest ticket sits at the reading edge and nothing hides below a fold.
Turn any tablet or spare screen into the kitchen’s live board. Tickets land the second you accept an order, the timer starts when the kitchen takes it, and one tap moves a dish forward. No fee per screen.
Tabres KDS is the kitchen app in Tabres, a Restaurant & Cafe Management Platform. It shows one kitchen’s open orders as a live board. Every order becomes a ticket. Each line goes to the right station. A timer starts when the kitchen takes the order. A manager sets the stations up in Manager. The cooks work the board. The pass hands the food out. It is free, on every screen in every branch.
All three read the same data, so a ticket is never in two places at once. Cooks work the Board, the pass clears the Pass, and Recall is there for the ticket that got bumped a minute too early.
The queue, oldest first. On a wide screen it becomes full-height columns that scroll sideways, so the oldest ticket sits at the reading edge and nothing hides below a fold.
Tickets with every line plated, waiting to be carried out. They wrap instead of forming a column, because this is a set to clear, not a queue to work down.
What was bumped recently, newest first, so a mis-bump goes straight back. The window is set on the server, and it starts at 30 minutes.
Cooks read tickets from across the line, with full hands. So the order number is big, the timer escalates, and progress reads as a fraction.
An allergy note turns the whole strip crimson. Allergens get their own full-width line, never a narrow chip. The codes are frozen onto the order line at the time of ordering, so the kitchen sees what the guest declared.
Allergens on the menuGrill, Fry, Bar, Pastry: you name the stations for each branch in Manager and route categories to them. The board then puts each line where it belongs, with no one sorting tickets by hand.
A line moves Queued, Firing, Ready, Served. The card shows the one button that fits where the ticket is right now, so nobody in the kitchen has to decide which action applies.
The whole ticket goes on.
Or tap one dish to step just that one forward.
It clears the board and waits at the pass as Hand out.
A toast shows the ticket number with an Undo for a few seconds. After that the ticket waits in Recall. Actions you do all night and can take back get undo; ending a shift is the rare one that asks you to confirm.
Served is marked at the pass, the one place someone can see the guest has the dish. To fix a step, open the ticket: every line has a step forward and a step back at full touch size, next to its times.
A wall-mounted tablet’s clock is often minutes out, so every board response carries server time and the screen corrects itself against it. And a QR order that waited twelve minutes for a waiter’s approval lands at zero, because zero is how long the kitchen has had it.
The number and the bar on the card’s leading edge escalate together, and past eight minutes the count blinks. Never colour on its own. Same thresholds in every kitchen.
A long ticket reads 72:14, not 1:12:14. No one should have to work out what an hour and twelve minutes means.
The late count sits in the topbar all shift, and is announced to screen readers as it changes.
The chip row along the top carries a live count for each station. Filtering dims the other stations instead of hiding them, because a cook on Grill still has to see that the burger ships with fries. Stations themselves live in Manager, under Kitchen.
Every open ticket totalled by dish, biggest first, so a cook drops twelve portions of fries at once instead of one at a time. Weights and volumes add up properly, not just counts.
A meter per station showing how many items it is holding right now. The bands are fixed numbers, not a share of the busiest station, so two items never reads as busy on a quiet night.
Tablets go to sleep. Wi-Fi stops working. Servers restart in the middle of service. This happens often in a kitchen, so the board is ready for it.
Every time the screen connects, it asks the server for the full list of orders again. So it does not matter why it lost the connection. The board is always correct.
A small label at the top tells you which one it is. It never says "Live" when it is not.
When a screen wakes up, it checks for new orders right away. It does not wait. If loading is slow, you still see the orders, not an empty screen.
With no connection, the board keeps the last orders it had. You cannot mark a dish as done until it is back online. All orders are saved on the server, so nothing is lost.
The whole shift shares one screen. So there are two logins: one for the screen, and one for the cook using it.
They do this once, at the screen. The system saves who did it, so a manager can remove the screen later.
It is not linked to a person. The screen remembers which kitchen it belongs to. One screen, one kitchen.
The PIN comes from the staff list for that branch. No email, no password. A manager does not need to be there.
The board closes and the staff list comes back for the next cook. The screen stays set up. Only a manager can remove it, and they can see all screens and when each one was last online.
No prices, no payment details, no email, no delivery address. The board shows a customer name only when staff need to call it out. Tickets for guests in the restaurant show the table number.
The server decides what each screen gets. Bills and contact details go to the POS only. They never reach a kitchen screen.
Station names, dish names, options and allergy labels all appear in the language the cook chooses. RTL languages included, and the whole layout flips right to left. Kitchen teams often speak many languages.
The board is dark. A light theme is one tap away. The theme loads first, so a screen on the wall never flashes white when it reloads.
A live screen for the kitchen. It shows orders, timers and stations. One tap moves a dish forward.
Add another screen whenever you want one. There is no per-screen fee to think about.
All Tabres appsSign-up asks for an email address and a verification code. There is no card capture anywhere in onboarding — nothing to cancel, because there is nothing to start.