Peblla Team
Restaurant Technology
Blog
/
Eficiencia Operativa
How Many Kitchen Display Screens Does Your Restaurant Need?
It is not a hardware question. Count the places that need to see a different part of the order.

In this article
The question behind the question
One screen, set up as expo
When a second screen starts to pay for itself
Deciding what each screen sees
The problem stations create
Where the timer belongs
What more screens will not fix
Where Peblla fits — and where it does not
Frequently asked questions
The Question Behind the Question
Almost every kitchen display conversation starts the same way: how many screens do I need? It sounds like a hardware question, and vendors are happy to answer it like one.
It is not a hardware question. The number of screens is a consequence of how your kitchen is already organized — which people cook which things, where they stand, and what has to leave the pass together. Get that description right and the screen count answers itself. Get it wrong and buying more screens makes the kitchen worse, not better.
So the useful version of the question is this: how many places in my kitchen need to see a different subset of the order?
One Screen, Set Up as Expo
A small kitchen does not need a screen per person. It usually needs one screen that sees everything.
That configuration is called an expo screen. It shows every item on every order, with all the modifiers, exactly as the guest asked for it. One cook, or one person calling the line, reads the whole ticket off it. This is the right starting point for most counter-service rooms, cafes, and any kitchen where two or three people can see the same monitor without walking.
It is also the honest answer for a lot of full-service kitchens that think they need four screens. A bubble tea shop with three people behind one counter, or a bakery where the same two hands do pastry and sandwiches, gains nothing from splitting the order across screens.
Orders reach that screen from every channel you run — the counter POS, a self-order kiosk, your website, your app, and delivery platforms. The kitchen should not be able to tell where an order came from unless you want it to.
When a Second Screen Starts to Pay For Itself
The trigger for splitting is physical distance, not order volume. If the person making salads cannot read the same monitor as the person on the grill without leaving their station, you have two stations and you need two screens.
The second trigger is pace mismatch. A drinks station and a wok station work on completely different clocks. When they share a screen, the fast station spends its day reading past items that are not its problem, and the slow station's tickets get buried under drinks that were done in twenty seconds.
A pizzeria feels this the moment it adds a fryer: pies run eleven minutes, wings run four, and one queue makes both worse. A sushi bar hits it when the hot kitchen opens behind the cold case.
A kitchen with genuinely separate stations usually ends up with one screen per station — hot line, cold, soups, drinks — plus the expo screen that still sees everything and coordinates the plate-up. The expo screen does not go away when you add stations. It becomes more important.
Deciding What Each Screen Sees
Once you have more than one screen, the setup work is not physical. It is deciding, item by item, which screen an item belongs to.
Each screen is registered during setup and you choose which items route to it. The hot screen gets only hot items. The cold screen gets only cold. The expo screen keeps everything. This is a one-time configuration that follows your menu, so a new item added later gets assigned the same way.
Two mistakes are common. The first is routing by category name instead of by who actually cooks it. In a taqueria a category called "sides" holds chips from the fryer and guacamole from the cold station, and sending both to one screen sends half of it to the wrong person. The second is forgetting modifiers: an item may be simple but its modifiers may belong to another station, and that is worth checking before service rather than during it.
The Problem Stations Create
Splitting an order across screens solves one problem and creates another. Each station now sees only its own part, which means nobody can see whether the table is ready to go out together.
This is the failure mode most kitchens discover about three weeks in. The cold station finishes a salad in four minutes, sends it, and the guest eats alone while the entree is still eight minutes out. Nothing broke — the system did exactly what it was told, and the information that would have prevented it was on a different screen.
The fix is to let each ticket show what else belongs to the same order elsewhere. Not a vague marker that something exists on another station, but the actual item names, quantities and modifiers. A cook who can see that the same table has two entrees still firing knows to hold. A cook who only sees "other items" learns to ignore it within a week.
This matters most in rooms where the table is the unit, which is why it shows up hardest in full-service and in grill-table formats where the whole party shares what arrives.
Where the Timer Belongs
Every ticket carries its own clock, and you decide when that clock turns yellow and when it turns red. Yellow means hurry. Red means it has passed the time you yourself set.
The point is not to make cooks anxious. It is that a promised time — a pickup window, a delivery quote, a table waiting — becomes visible in the kitchen without anybody walking back to ask. Set the thresholds to numbers you actually stand behind, because a screen that is permanently red teaches the kitchen to stop looking at color.
Each screen also keeps a running count of how many of each item are still open on it. Eight orders of the same dish spread across five tickets read as eight, which is what a cook needs to batch during a rush. That count is worth turning on after your menu has been running a while, not on day one.
What More Screens Will Not Fix
Screens do not fix a menu that takes too long to cook. If your ticket times are bad because three dishes each take fourteen minutes, no display arrangement changes that.
They do not fix being short-staffed. A station with nobody at it shows red faster, which is information, not a solution. That belongs with scheduling.
And they do not fix orders that reach the kitchen wrong. If the modifier was never captured correctly at the counter, on a handheld, or in your digital ordering, the screen faithfully displays the wrong thing.
Where Peblla Fits — and Where It Does Not
With Peblla KDS each screen is set up for you, you choose which items route to it, set your own yellow and red thresholds, and leave one screen as expo. Tickets can show what the same order has waiting at other stations, item by item, so a station that finishes early knows whether to hold.
It is not the right purchase for every kitchen. If one person can see one monitor from everywhere they work, a second screen is spending without a return. If your printed tickets are working and nobody has complained, the honest move is to start with one screen and keep the printer during the first weeks rather than replacing anything on day one.
Where it earns its place is a kitchen that has genuinely split into stations and has started losing the whole-table picture as a result. More on the approach at why restaurants choose Peblla.
Frequently Asked Questions
How many kitchen display screens does a restaurant need?
Count the places in your kitchen that need to see a different part of the order and cannot read the same monitor from where they stand. A small kitchen usually needs one screen configured as expo. A kitchen with separate stations typically runs one screen per station plus an expo screen that sees everything.
What is an expo screen?
An expo screen shows every item on every order with all modifiers, rather than only one station's portion. It is how a single-screen kitchen operates, and in a multi-station kitchen it is what coordinates the complete plate-up.
How do I decide which items go to which screen?
Assign by who actually cooks the item, not by menu category. Categories often mix stations, and routing by category name is the most common setup mistake. Check modifiers separately, since a modifier can belong to a different station than its item.
Does a kitchen display system replace my kitchen printer?
It does not have to. Printing to the kitchen, printing a label and sending to the screen are separate choices per order. Many restaurants run both during the first weeks and drop the printer once the kitchen trusts the screen.
Can one screen show orders from delivery apps and my own website?
Yes. Orders from the counter, a kiosk, your website, your app and delivery platforms all arrive on the screen that item routes to, so the kitchen works from one queue instead of several. A quick-service room running four channels at lunch should still see one line of tickets, not four separate queues to reconcile by eye.
How do I stop half a table going out before the rest?
Make sure each station's ticket shows what the same order still has open elsewhere, with the item names and quantities rather than a generic marker. A cook who can see two entrees still firing will hold the salad; a cook who only sees that something exists somewhere will not.
If you want to map your stations before you buy screens, book a walkthrough and we will go through your kitchen with you.
