Paper chits
- Clip to the rail
- Shout the amendments
Chits fall off. Order matters until it does not. Nobody knows which table has been waiting longest, and when it gets busy the answer to "where is table nine" is somebody walking the pass and reading.
Kitchen display · UAE & GCC
Kitchen Display System for UAE Restaurants
Tickets land on the screen the second they are sent — from the till, from a guest’s phone, from any channel — routed to the station that cooks them, with a timer running from the moment they arrived.
- Runs on any screen in a browser — a spare tablet is a station
- Modifiers and allergy notes on the ticket, not shouted across the pass
- Bilingual tickets, so the item reads the same to whoever picks it up
The grill station board, as it ships.
More than a printer
The pass stops running on memory
A paper chit tells you what to cook. It does not tell you how long it has been waiting, which station owns it, or whether the amendment shouted two minutes ago ever reached the person cooking.
Tahlib KDS
- Ticket appears
- Routed to a station
- Timer running
- Start
- Ready
- Served
- Order closes
Every ticket arrives with its modifiers, its notes and a clock. Stations see only their own work. When the last item is ready the order flips to ready by itself, so the front of house is told without anyone having to say it.
The kitchen still cooks the same food. It just stops spending attention on remembering what is where.
How a ticket moves
From sent to served, on one screen
Three states, guarded so a ticket cannot skip one or go backwards by accident.
The order is sent
From the till, from a table QR scan, from takeaway or delivery. The channel changes nothing about how it arrives here.
It lands on the right station
Items route to the station that cooks them, so grill sees grill. Filter to one station on a screen, or leave it on all.
It announces itself
The ticket appears without a refresh, marked just sent, with an optional sound so nobody has to be watching the screen.
The clock starts
Elapsed time runs from arrival in seconds, then minutes. Past your threshold it flips to overdue, in a colour you notice from across a kitchen.
Start cooking
Bump an item to cooking, or start the whole ticket at once. The state is shared, so a second screen shows the same thing immediately.
Mark it ready
Item by item, or finish the ticket in one tap. When every live item on the order is ready, the order itself flips to ready.
Mark it served
The pass clears it, and the order carries on to payment at the till or on the guest’s phone.
Later rounds arrive as their own ticket
A table that orders again does not amend a ticket already cooking — the round fires fresh so it cannot be missed behind work in progress.
A ticket can only move queued → cooking → ready. Invalid jumps are rejected rather than quietly accepted.
What you get
What a screen has to do to earn its place
Grouped by the problem each part solves at the pass.
Tickets that carry everything
The information that otherwise travels by shouting.
- Modifiers and add-ons printed on the item, not appended somewhere else
- Kitchen notes and allergy warnings from the order
- Table number, takeaway or delivery marked on the ticket
- Item names in English and Arabic, so the ticket reads to whoever picks it up
- New items on an existing order flagged so they are not mistaken for old work
Stations and views
One kitchen, several jobs, several screens.
- Route items to stations you define — grill, cold, bar, whatever your kitchen calls them
- Filter a screen to one station, or show everything
- Classic three-column board: new, cooking, ready
- Full-screen grid view built for a kitchen tablet, with the Kitchen Grid product
- New-ticket sound, mutable per screen
- Arabic interface with right-to-left layout
Timing the pass
The reason a display beats paper.
- Elapsed timer per ticket, running from the moment it arrived
- Seconds while it is fresh, minutes once it is not
- Overdue state once a ticket passes your threshold
- The oldest work is visibly the oldest, without anyone reading the rail
Bumping without mistakes
Fast to operate, hard to get wrong.
- Bump a single item, or start and finish a whole ticket in one tap
- A guarded state machine — an item cannot skip from new to served
- When the last live item is ready, the order flips to ready by itself
- Voided items drop out without holding the ticket open
- Screen-reader labels on every bump control
Keeping up in a rush
What happens when twenty tickets land in ten minutes.
- Live updates over a realtime connection when it is configured
- A three-second poll as the fallback, so a screen is never stale for long
- A pending queue for orders awaiting acceptance — accept to send to the kitchen, or reject with a reason
- A refresh failure says so on screen and keeps polling rather than silently freezing
- Runs in a browser on any screen, so a spare tablet is a spare station
Timing the pass
Knowing which table has waited longest
It is the question every service turns on, and the one a rail of paper cannot answer without somebody walking it.
The clock starts when the ticket does
Elapsed time runs from arrival, not from when someone noticed. It counts in seconds while a ticket is fresh and switches to minutes once it is not.
Overdue is a state, not a judgement call
Past your threshold the ticket changes colour and says how many minutes over it is. Nobody has to hold the standard in their head at eight on a Friday.
Every screen agrees
Bumping is shared state. The grill screen and the pass screen show the same ticket in the same state, so two people cannot both start the same item.
The order closes itself
When the last live item on an order is ready, the order is promoted to ready — the front of house is told without the kitchen having to tell them.
Connected operations
What feeds the screen, and what it feeds
The kitchen display is not a destination. It is the middle of a line that starts at an order and ends at a bill.
- POS & QR
- Orders
- Kitchen Display
- Inventory
- Tax invoice
Point of Sale
Tickets sent from the till arrive with their modifiers and notes. A round added later fires as its own ticket rather than amending one already cooking.
QR Ordering
Guests ordering from the table produce exactly the same ticket a cashier would. The kitchen does not need to know which it was.
Inventory
Firing a ticket is what deducts stock for linked recipes, so the count follows the kitchen rather than the till.
Kitchen Grid
A full-screen, dark-mode board built for a wall-mounted kitchen tablet, with station filters and glanceable states.
Orders
The live board across every channel, where the same order is visible to managers and front of house.
Analytics
Order volume by hour tells you when the pass is actually under pressure, rather than when it feels like it.
Products are switched on individually — see the full catalogue and prices on the products page.
Where it fits
What changes, by type of kitchen
The screen is the same. The failure it prevents is not.
- Cafés
- One screen behind the counter replaces a printer nobody wanted to buy paper for. The timer matters more than stations when there is one person making everything.
- Casual dining
- Several stations, one pass. Grill sees grill, cold sees cold, and the pass sees which table has been waiting longest without walking the line.
- Quick service
- Volume arrives in bursts. Tickets appear without a refresh and the sound means nobody has to keep half an eye on a screen while their hands are busy.
- Shisha cafés and late-night
- Tables order in rounds all evening. Each round arriving as its own ticket is the difference between a late order being cooked and being found at close.
- Delivery-led kitchens
- No dining room to read the room from. The overdue state is the only signal that a ticket is aging, and it is the one that matters most when a rider is waiting.
Built here
The details that matter in a UAE kitchen
Written for kitchens where not everyone reads the same language.
Tickets in both languages
Item names carry English and Arabic together, so a ticket is legible whether the person who picks it up thinks in one or the other. The interface itself flips right-to-left too.
No dedicated hardware
It runs in a browser on any screen. A spare tablet becomes a station, and a failed screen on a Friday night is replaced from the stockroom rather than ordered in.
Ramadan service patterns
Everything arriving at once at iftar is exactly when timers and the overdue state earn their place — and when a second screen for a second station costs nothing to add.
Works on the connection you have
Live updates when a realtime connection is configured, and a three-second poll as the fallback — so the board keeps moving even when the venue Wi-Fi does not.
Getting started
How to get Kitchen Display
The kitchen display is one of the essentials, so it arrives with your plan rather than carrying a price of its own.
Start with a Tahlib plan, then add the products you need — or move to a plan that already includes them.
Questions, answered
What kitchens ask before the paper goes
What screen do I need for a KDS?
Any screen with a browser. A tablet on a stand, an old laptop, a monitor on a mini PC — all work. There is no dedicated kitchen terminal to buy, and adding a second station screen costs nothing beyond the device.
How quickly do tickets appear?
Effectively immediately. When a realtime connection is configured the ticket is pushed to the screen; without it the board polls every three seconds. Either way nobody has to refresh anything.
Can I split tickets between stations?
Yes. Define your stations and route items to them, then filter each screen to the station it serves. A pass screen can show everything while grill and cold see only their own work.
Do the tickets show modifiers and allergies?
Yes. Modifiers, add-ons and the kitchen note from the order are printed on the item itself, so an amendment travels with the ticket rather than being shouted across the pass.
What happens when a table orders again?
The new round arrives as its own ticket rather than changing one that is already cooking. That way a late addition cannot be missed inside work already underway, and the kitchen is not re-reading a ticket it has half finished.
Can a ticket be marked ready by mistake?
It is guarded. An item can only move new → cooking → ready, and an invalid jump is rejected rather than quietly accepted. Bumping is shared state, so two screens cannot disagree about what has been started.
How does the front of house know food is up?
When the last live item on an order is marked ready, the order itself flips to ready — visible on the orders board, at the till and on the guest’s tracking screen if they ordered by QR.
Does it work in Arabic?
Yes. The interface switches to Arabic with proper right-to-left layout, and item names carry both languages on the ticket so it reads to whoever is cooking it.
Is there an alert when a ticket is taking too long?
Every ticket carries an elapsed timer from the moment it arrived, and once it passes your threshold it flips to an overdue state showing how many minutes over it is. There is also an optional sound when a new ticket lands.
What if the internet drops?
The board tells you it could not refresh and keeps trying rather than silently showing stale tickets. It does need a connection — the ticket, the till and the bill are the same live record.
What does it cost?
Kitchen Display is one of the essentials, so it comes with your plan rather than being priced separately. The full-screen Kitchen Grid board for wall-mounted tablets is a separate add-on.
Take the paper off the pass
Put a screen in the kitchen this afternoon and let the first service show you which table has actually been waiting longest.
No card to start · nothing to install · cancel whenever