Free kitchen display system for restaurants

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.

  • Runs on the screens you own
  • As many screens as you like
  • Board, Pass and Recall
  • No credit card required

What is Tabres KDS?

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.

€0
Per screen, per kitchen, per month.
0
Hardware to buy. It opens in a browser.
€0
Printer cost. The board takes the place of paper tickets.
Board · Pass · Recall

Three views of one board.

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.

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.

Pass

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.

Recall

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.

The ticket

Everything a cook needs, nothing they don’t

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.

  • The order number, large, with an icon for dine-in, pickup, delivery or self-service
  • Where it came from: the register or a guest’s phone
  • Who it is for: a table, or a name
  • Progress as 3/4 ready
  • Quantity by count, weight or volume, then the product, variant and add-ons
  • Notes and allergens per line, in the cook’s language
  • A NEW badge for the first seconds after a ticket lands

An allergy note is impossible to miss

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 menu

Lines go to the right station

Grill, 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.

Moving work forward

One button per ticket, never a choice of four

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.

  1. Queued
  2. Firing
  3. Ready
  4. Served, at the pass
Nothing started
Start

The whole ticket goes on.

Something cooking
Mark ready

Or tap one dish to step just that one forward.

Everything plated
Bump

It clears the board and waits at the pass as Hand out.

Bump has undo, not “are you sure?”

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.

A dish stops at Ready on the board

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.

Timers that tell the truth

The clock is the server’s, and it starts when you accepted the order

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.

Amber at 5, crimson at 8

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.

  • 5 min
  • 8 min

Minutes, even past 59

A long ticket reads 72:14, not 1:12:14. No one should have to work out what an hour and twelve minutes means.

Late count, always in view

The late count sits in the topbar all shift, and is announced to screen readers as it changes.

How orders reach the kitchen
Stations

Filter to your station without losing the ticket

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.

All-day count

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.

Station load

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.

  • Grill 9 items
  • Bar 2 items
  • Breakfast 0 items
Built for a busy room

The screen always tells you if it is live

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.

It reloads every time

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.

Live, or Reconnecting…

A small label at the top tells you which one it is. It never says "Live" when it is not.

It wakes up fast

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.

Offline, it does not pretend

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.

One screen, every shift

A manager sets the screen up once. Cooks sign in with a PIN.

The whole shift shares one screen. So there are two logins: one for the screen, and one for the cook using it.

  1. 01

    A manager sets up the screen

    They do this once, at the screen. The system saves who did it, so a manager can remove the screen later.

  2. 02

    The screen has its own login

    It is not linked to a person. The screen remembers which kitchen it belongs to. One screen, one kitchen.

  3. 03

    Each cook starts with a PIN

    The PIN comes from the staff list for that branch. No email, no password. A manager does not need to be there.

  4. 04

    Ending a shift is one tap

    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.

Quiet decisions

The board shows food, not money or personal details

No prices, no phone numbers

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.

In the cook’s language, dark by default

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.

  • 44px touch targets
  • Keyboard operable
  • Reduced motion respected
  • Wall, tablet and phone layouts
Get Tabres KDS

Open it on the screen already in the kitchen

Kitchen Display System

Tabres KDS

A live screen for the kitchen. It shows orders, timers and stations. One tap moves a dish forward.

  • Web
  • Windows soon
  • Android soon
  • macOS soon
  • iOS soon
  • Linux soon

What you need to start

  • A screen with a browser and an internet connection
  • Your stations set up in Manager, under Kitchen
  • A manager to enrol the screen, and PINs for the cooks

Add another screen whenever you want one. There is no per-screen fee to think about.

All Tabres apps
Questions

Questions restaurants ask first

Which orders show up on the kitchen board?

Every order your business takes in Tabres: POS orders, QR orders from the table, table orders, takeaway and delivery. They all come to the same board. Each ticket shows where it came from, so the kitchen can see at once if it is a delivery order or table 12. You do not need to set up anything for each channel.

Is Tabres KDS really free?

Yes. You pay nothing for each screen, each kitchen or each month, and you do not buy any hardware.

What do I need to put my kitchen on a screen?

A screen with a browser and an internet connection. A manager sets up the screen one time, at the screen. After that, each cook starts a shift with a PIN, so you do not need a manager at every shift change.

How does a cook sign in to the kitchen display?

The screen has a login of its own, set up once by a manager, and it is not tied to a person. A cook then taps their name on that branch’s staff list and types their PIN — no email, no password, and no manager needed at the shift change. Ending a shift is one tap: the board closes and the staff list comes back for the next cook.

When does the ticket timer start?

It starts when your business accepts the order, not when the guest sends it. A QR order can wait ten minutes for approval. It still starts at zero, because the kitchen has only just got it. The time comes from the server, so a tablet with a wrong clock changes nothing.

I bumped a ticket by mistake. Can I get it back?

Yes. A toast shows the ticket number with an Undo on it for a few seconds. After that the ticket waits in Recall, newest first, so a mis-bump goes straight back onto the board. The Recall window is set on the server and starts at 30 minutes.

Can I run more than one screen in one kitchen?

Yes, as many as you want. You set up each screen on its own, and you choose which station it shows. The grill uses one screen, the pass uses another.

Does the kitchen board show prices or guest details?

No. No prices, no totals, no payment details, no phone number, no email and no delivery address. The board shows only a name, and only when the pass needs to call one. For dine-in orders, it shows the table.

What happens if the kitchen screen loses Wi-Fi?

The board keeps the last orders on the screen and says that it is reconnecting, so nobody trusts an old screen. You cannot move a dish forward until it is back online. All orders are saved on the server, so the screen updates in full when the connection comes back.

Everything you need to run the restaurant. Nothing to cancel.

Sign-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.

Create free accountAsk us on WhatsApp

No credit card required.