Course pacing, modifier fidelity, station routing, printer fallback. A KDS built by people who worked the line, not by people who watched it on TV. Fine-dining course pacing on the same platform as ghost-kitchen ticket routing.
Every capability listed below is included in the base module. No add-ons, no unlock fees, no per-seat surcharges. If you're on xRESTAURANTx, you have this.
Every order lands at the right station with the right modifiers. Cold, hot, sauté, expo, pastry, cold bar, hot bar — the routing map is yours to configure.
Fire starters, hold entrées, release mains on captain call. Course pacing built for tasting menus and prix fixe rooms.
"No garlic, sub olive oil, sauce on the side" — three lines, three visual markers on the ticket, one glance at the pass to confirm.
If the KDS tablet dies, tickets print. If the printer dies, KDS keeps running. Twin path, no single point of failure at the line.
Each dish carries an average and P95 prep time. Expo sees estimated pickup and warns you when a course is running long.
One tap recalls a ticket. Great for staff training, great for the guest who changed their mind mid-course.
Every operator we onboard runs this same tutorial in their first week. Most complete it in one sit-down; the whole team is comfortable inside two shifts.
The KDS is one tablet or one screen per station. Wire them, connect to WiFi, log the station in. The station identity persists across shifts.
For each menu item, define which station(s) fire it and in what order. A caesar salad might fire cold station first, then move to expo. A porterhouse fires hot grill, then rests, then expo.
Every dish gets an initial prep-time baseline. The system learns from actual fire-to-pass times and updates the estimate over the first week. By day 8, prep-time predictions are within 45 seconds for 90% of dishes.
Plug in a thermal printer at expo. Configure it as fallback: prints only when the KDS tablet loses connection or when a manual print is requested. Zero interruption during network events.
10-minute walkthrough. Bump tickets, recall, mark 86, view course status. That's the entire line-cook vocabulary. Chef training adds the pacing controls and station reassignment.
xRESTAURANTx modules are not sold separately. Bundle everything — you pay one flat rate keyed to your restaurant's size, not a per-module upsell.
Concrete scenarios from actual operators using the module in production. Every scenario carries a metric or a mechanism, not a marketing slogan.
Captain fires course 3. Every station knows what it's on the hook for, when to start, when to plate, when to expo. Course-level synchronization at the pass, not shouted timings.
Delivery order comes in for Brand A. Same line. Line cook sees Brand A ticket color, Brand A receipt printer, Brand A packaging cue. Fifteen brands wouldn't confuse it — everything is tagged and routed.
Not if you don't want to. xRESTAURANTx can push tickets to a legacy KDS via industry standard printing formats. Most operators run the full KDS eventually because the course-pacing intelligence isn't available on legacy hardware.
Local network keeps working — the KDS and POS talk to each other on the LAN. When internet returns, the accumulated data syncs. You never lose a ticket.
Yes. Cold station shows a compact list. Expo shows the full order-by-order visual. Grill station shows a countdown-heavy layout. All configurable.
xRESTAURANTx modules are designed to work together. These four are the ones most operators use alongside Kitchen Display System (KDS).
Book a 20-minute demo. We'll walk through Kitchen Display System (KDS) on your actual menu and show you how it lands on the floor.