A well-configured KDS setup eliminates ticket confusion and speeds up kitchen throughput

Most restaurants that install a kitchen display system do the bare minimum: plug in one screen, route all orders to it, and call it a day. Then they wonder why the kitchen is still chaotic during service.

A KDS is only as good as its configuration. This guide walks through how to actually set one up — station by station, rule by rule — so your kitchen runs like it should.

---

Before You Start: Map Your Kitchen

The most important step happens before you touch any hardware: draw a map of your kitchen and identify every prep station.

Typical stations in a full-service kitchen:

• Cold prep / Garde manger — salads, cold appetizers, desserts
• Sauté — pasta, pan sauces, sautéed proteins
• Grill — steaks, burgers, grilled proteins
• Fry — fries, fried appetizers, fried proteins
• Expo / Pass — the line where plates are finished and assembled before going to the floor

Each of these stations should have its own KDS screen — or at minimum, should receive a filtered view of the tickets relevant to that station.

Why this matters: If every screen shows every item, your grill cook is scrolling through salad tickets to find his steaks. That's friction, and friction slows service.

---

Step 1: Assign Items to Stations

Every menu item needs a station assignment. This is done in your POS menu configuration — not on the KDS itself.

How to assign items:

In most systems (Toast, Lightspeed, Square), there's a concept called a "course" or "dining option" or "kitchen routing group." You create a group (e.g., "Grill Station"), assign a printer or display destination to it, and then tag every menu item with the appropriate group.

Assignment example:

Common mistakes:

• Forgetting to assign desserts (they end up on no screen, confused prep)
• Putting sides and proteins on different screens without an expo view to coordinate them
• Assigning shared items (e.g., fries as a side) to only one station when they appear across menu categories

---

Step 2: Configure Timing Thresholds

KDS systems use color-coding to show ticket age. Typical default settings:

• Green — Order just received, within target time
• Yellow — Approaching expected completion time (warning)
• Red — Past target time (urgent)

The default thresholds are usually 5 minutes (yellow) and 8 minutes (red). For most full-service kitchens, these are too aggressive. Adjust them to match your actual cook times by station.

Realistic thresholds by station:

To find your real numbers: Run a week of service with your current paper ticket or POS system and log actual ticket times per station. Use those numbers to set initial thresholds, then adjust as your team gets comfortable with the new system.

---

Step 3: Set Up the Expo Screen

The expo screen is the most important screen in the kitchen — and the most often misconfigured.

What the expo screen should show:

• All open tickets across all stations
• Color-coded status for each item within each ticket
• A "ready" status that can be bumped when an item is finished at its station

How it works in practice:

When the grill cook finishes a steak, they bump it on the grill station screen. That item changes status on the expo screen — the expo cook can see that the steak is up, the fries are done, but the salad is still in progress. They know to wait before expediting the plate.

Without an expo view, the expo cook is guessing — grabbing finished proteins and watching them sit while they wait for other items. That's where food quality suffers.

Toast KDS expo mode: Supports this natively with color-coded item status per station. One of Toast's strongest KDS features.

Fresh KDS expo mode: Even more powerful — shows cook time history and can automatically page the expo line when all items on a ticket are ready.

---

Step 4: Configure Bump Bar Controls

A bump bar is a physical hardware controller that lets cooks mark items complete without touching the touchscreen — critical in a hot kitchen where hands may be wet or greasy.

Standard bump bar functions:

• Bump button — Mark the highlighted item/ticket as complete
• Previous / Next — Navigate between tickets
• Done — Complete an entire ticket
• Recall — Bring back a bumped ticket (for when something is bumped by mistake)

Setting up button mapping: Most KDS systems let you customize which physical button triggers which action. Map your most-used action (bump current ticket) to the most accessible button. Put recall in a position that's not accidentally triggered — a bumped ticket that's hard to recover creates real problems mid-service.

Physical placement: Mount the bump bar at counter height where the cook can trigger it with a hip or elbow motion without putting down their tools. If cooks have to reach across to hit the bump bar, it won't get used.

---

Step 5: Set Up Course Firing

Course firing lets servers control when kitchen items are sent to the stations. Instead of all items on a ticket appearing on the kitchen screen immediately, items are "fired" course by course.

How it works:

1. Server takes the order — appetizers and entrées
2. Only appetizers appear on kitchen screens
3. When apps are ready and the table has eaten, server "fires" the entrées
4. Entrées now appear on kitchen screens

Why it matters: Without course firing, a table's steak appears on the grill screen at the same time as their appetizer. The grill cook has to either delay the steak or time it perfectly in their head — which they won't consistently do during a rush.

Configuring course firing:

• In Toast: Under Menu → Dining Options → Courses, enable course-based sending
• In Lightspeed: Under Service Flow → Course Settings
• In Square: Limited course firing — Square's native tools are less granular here

Course categories to create:

1. Appetizers & Soups
2. Salads (can be fired at same time as apps or separately)
3. Mains
4. Desserts

---

Step 6: Train Your Team

The best KDS configuration fails if the team doesn't use it correctly. A 30-minute pre-launch training prevents weeks of bad habits.

Training agenda:

For line cooks (30 minutes):

• How to read the ticket display
• What the color codes mean
• How to use the bump bar
• What to do when a ticket is bumped by mistake (recall)
• Who to tell when the screen is wrong

For expo / expediter (30 minutes):

• How to read the full expo view
• Station-by-station status interpretation
• Communicating with stations when items are running long
• How to handle a stale ticket (past red threshold)

For servers (15 minutes):

• How to fire courses from the POS
• What "fired" means and when to do it
• How to 86 an item mid-service

---

Common Setup Mistakes to Avoid

Mistake 1: One screen for the whole kitchen Every cook sees every item, nothing is organized by station. Chaos.

Mistake 2: Not configuring the expo screen The most common oversight. Expo cooks flying blind is where quality breaks down.

Mistake 3: Default timing thresholds 5-minute yellow alerts for an 18-minute braise means every ticket is red all the time. Cooks tune it out.

Mistake 4: Not training on recall First week, someone bumps a ticket by accident and doesn't know how to get it back. The table waits 15 extra minutes. Train recall before go-live.

Mistake 5: Skipping the pilot Run the KDS alongside your paper tickets for the first week. Don't go full-KDS on day one. Catch configuration issues before they affect service.

---

Which KDS Systems Support This Setup

Our setup recommendation: Toast KDS for Toast POS users, Fresh KDS for everyone else. Both handle multi-station routing and expo views cleanly. QSR Automations is the enterprise choice for large-volume operations and QSR chains.

A well-configured KDS isn't just a technology upgrade — it's a kitchen management system. Invest 2–3 days in getting the configuration right, and your kitchen team will wonder how they ever ran paper tickets.