Kitchen Display System buying guide: a screen vs a real KDS

Most restaurants in the US that “have a KDS” actually have a screen with tickets. That’s not the same thing. A real Kitchen Display System changes the rhythm of the line — it tells you what’s late, what’s coming, what’s 86’d, and what station owns each ticket. A glorified ticket monitor just replaces paper with glass. Here’s how to tell the difference before you buy.

The features that separate the two

When a vendor demos their KDS, watch for these. If they breeze past any of them, you’re looking at a screen, not a system.

• Per-ticket timer that pulses red.Every ticket needs a clock. At 6 minutes (or whatever your service standard is), the ticket should change color and pulse. The line cook should never have to ask “how long has this been here?” The 6-minute default is a casual-dining heuristic, not a law of physics — fine dining tunes longer for slow-cooked mains, QSR tunes shorter (often 3–4 minutes) because the whole drive-thru target window is around four minutes door-to-door.
• Drag-to-reorder columns. When a 12-top walks in and their order needs to jump the queue, the expediter should be able to drag it to the front. Static order is a non-starter.
• Recall a sent ticket.Tickets get bumped by accident. A KDS without “recall last bumped” means you’re re-firing from memory. Good systems keep a 30-minute recall window so the expediter can pull back a ticket the runner swears never came out.
• Course timing for fine dining.Apps fire now, mains fire on the cue from the expediter. The KDS has to support multiple courses on one ticket. Look for explicit “hold & fire” controls — the expediter releases mains when the apps are halfway eaten, and the hot station only sees the proteins at that moment. Without coursing, the kitchen plates everything at once and apps arrive cold next to mains.
• Channel tagging. Dine-in, delivery, pickup, and third-party should each have a visual marker (icon, color, badge). Cooks plate differently for delivery — they need to see it at a glance.
• Modifier prominence.“No onions” cannot be 8pt grey text under the item name. It needs to be bold, contrasting, and impossible to miss. Toast, Square, and Revel all publish modifier-display configs in their KDS docs — if your vendor can’t show you a settings panel that makes modifiers larger and recolors them, the system is rigid.
• Station routing. Cold station gets the salads. Hot gets the proteins. Dessert gets desserts. One ticket, three screens, each showing only what that station owns. Routing rules should be item-level, not category-level — a salad with grilled chicken should fan out to both cold (greens, dressing) and hot (chicken) so the components arrive at expo together.
• Allergen highlighting.When a ticket has a flagged allergy, the entire ticket should change color. Allergen errors are lawsuits. The FDA recognises nine major allergens in the US, and the KDS should support a configurable list, not just “peanut / gluten / dairy” hardcoded.
• POS integration for 86’d items.When the cook marks the lobster bisque 86’d on the KDS, it disappears from the POS, the QR menu, and the WhatsApp ordering bot immediately. Not on the next sync.

Coursing, station routing, and recall in practice

These three features deserve their own pass because they’re the ones operators get wrong on a demo and then suffer with for years.

Coursingin fine dining is more than a hold flag. The expediter needs a clean view of which courses are fired, which are held, and how long each held course has been waiting — because a hold that drifts past 12 minutes is worse than no coursing at all (apps sitting in the window, mains never started). The KDS should expose a timer per course, not just per ticket, and the “fire mains” button should re-stamp the course with a fresh clock so the hot station is graded on its own pace, not the table’s elapsed time.

Station routingsounds simple until you have shared components. A burger fires to grill (patty), fryer (fries), and cold (lettuce, tomato, side slaw). Bad routing duplicates the whole ticket on every screen. Good routing fans the ticket out by item or modifier and reassembles at the expo screen, so each cook sees only what they own and the expo sees the full plate. Ask the vendor to show item-level routing on a dish with three components — if they only have category-level routing, you’re going to spend Friday nights explaining tickets to confused cooks.

Recallis the unglamorous feature that saves comps. Tickets get bumped early because a runner shouted “all day” across the line, or because a cook reached for the bump bar and hit the wrong button. A good KDS keeps every bumped ticket in a recall buffer for at least 30 minutes, recoloured so the line knows it’s a re-fire and not a fresh order. Without recall, the only fix is to re-ring the ticket through the POS, which prints duplicate item counts in the daily sales report and makes inventory reconciliation a nightmare.

The hardware question

Two camps in the US market. Both work, but they have very different economics.

Hardware-coupled (Toast, Clover):The KDS is a proprietary screen the vendor sells you for roughly $700–$1,200 each, plus a monthly software fee per screen. The benefit: tight integration, decent durability, vendor handles support. The cost: lock-in, per-screen recurring fees, and replacement is on the vendor’s terms. Toast publicly lists its KDS hardware and a per-display software add-on on its website, and that per-screen recurring line is the one operators most often miss when budgeting. (See FoodyOS vs Toast for the full hardware-cost contrast.)

Software-only (FoodyOS, Square KDS app, etc.):The software runs on any iPad or Android tablet you already own, mounted in a $40 wall arm. Hardware cost drops 90%, you replace screens at consumer-electronics speeds, and adding a station screen takes 10 minutes. The trade-off: tablets aren’t built for 110°F line environments. The fix: a heat-rated case (~$80) and avoid the heat lamp area. Square KDS, for example, runs on iPads or Fire tablets and is bundled into the Square for Restaurants plan rather than billed per screen — a fundamentally different pricing shape than Toast.

Pricing models, decoded

There are really three KDS pricing patterns in the US, and the bill looks very different at year three depending on which one you signed.

• Per-screen subscription. Toast and Clover charge a monthly fee for each KDS device on the network. Add a dessert station, add a line item. The math scales linearly with kitchen complexity, which is fine until you open a second concept and realise the four extra screens are another ~$1,440/year.
• Bundled / included. Square for Restaurants and FoodyOS include the KDS app at no per-screen surcharge — you pay one platform fee per location and run as many screens as the kitchen needs. This is the right shape for high-station kitchens (steakhouses, sushi, ghost-kitchen stacks) where five or six screens is normal.
• Tiered by feature.Lightspeed and Revel both gate coursing, conversational display modes, and advanced routing behind higher tiers. Read the feature matrix line-by-line — “KDS included” on a base plan often means a stripped expo screen, not a real multi-station system.

A worked example

A 4-station kitchen (cold, hot, expo, dessert) on hardware-coupled KDS: 4 screens × $900 = $3,600 hardware, plus $30/screen/month software = $1,440/year recurring. Three-year cost: ~$7,920.

Same 4-station setup on software-only KDS using $400 iPads: $1,600 hardware, included in software fee = $0 incremental. Three-year cost: ~$1,600.

That’s a $6,000 difference for the same operational outcome. The only honest reason to pay hardware-coupled prices is if you specifically need vendor-managed hardware lifecycle and you have the budget to fund it.

What to demo, not just talk about

When you’re evaluating a KDS, don’t accept a slide deck. Demo it live with these scenarios:

• Fire 8 tickets in 30 seconds, including one with a modifier and one flagged for an allergy. Watch how the screen handles density.
• Mark an item 86’d. Open your QR menu and your online ordering page on a phone. The item should be gone in seconds.
• Recall a bumped ticket. How many taps? If it’s more than two, your line cooks won’t use it.
• Drag a ticket from position 6 to position 1. Does the ticket animate smoothly, or does the screen lag?
• Pull the network cable. Does the KDS keep working on local cache, or does it freeze? In the US, restaurant Wi-Fi falls over at the worst possible moments.
• Fire a coursed ticket: two apps, three mains, one dessert. Hold mains. Then release. Watch whether the hot station only sees the mains at release, or whether it had them visible the whole time.

What the research actually says about ticket times

Be careful with vendor case studies — almost every KDS marketing page cites a single chain that “saved 30 seconds per ticket” and treats it as universal. The honest read of operator reporting in QSR Magazine and Restaurant Business Online is more nuanced: digital kitchen displays consistently reduce remakes and lost tickets versus paper, and they reliably tighten the variance of ticket times during a rush, but the median speedup depends heavily on what was being replaced. A kitchen migrating from a thermal printer with a single expediter sees the biggest jump. A kitchen replacing a first-generation KDS with a better one sees a smaller, mostly variance-driven gain.

The right way to evaluate is to baseline your own ticket times for two weeks before install — bump-time on every ticket, segmented by daypart — and then compare the same two weeks after the team is trained. That number is yours. Don’t buy on someone else’s.

Why this matters more than POS choice

The POS is mostly a glorified order-taker and payment terminal. The KDS is where your operation actually runs. A bad KDS means missed tickets, slow times, mis-fires, allergy errors, and a head chef who hates you. A good KDS does the opposite: tighter ticket-time variance, fewer comps, fewer allergen incidents, and an expediter who can actually manage the pass instead of refereeing chaos.

Pick the POS your accountant likes. Pick the KDS your line cooks like. They’re different decisions. The broader platform context lives in the restaurant management system buying guide, and the FoodyOS KDS ships included on flat per-location pricing — see pricing or jump to the product walkthrough.

Sources

1. Toast — Kitchen Display System (product page).
2. Square — Square KDS for Restaurants.
3. Revel Systems — Kitchen Display System.
4. Lightspeed — Restaurant Kitchen Display System.
5. QSR Magazine — ongoing coverage of kitchen display systems and back-of-house technology.
6. Restaurant Business Online — technology coverage on kitchen display systems and ticket-time impact.
7. U.S. Food & Drug Administration — Food Allergies (major allergens recognised in the US).