Restaurant POS Kitchen Routing Checklist, how to map menu items to stations without bottlenecks

A bad routing setup feels like a four-way stop with no signs. Tickets stack up, cooks start shouting, expo turns into a pile of plates, and the guest only sees the delay.

When I build a kitchen routing checklist, I treat it like traffic control. The goal isn’t to send every item everywhere. The goal is to send each item to the one place that owns it, with clear rules for who supports it and when it should fire.

Start with the kitchen reality, not the POS screen

Before I touch routing rules, I walk the line in my head (or on paper). I name the stations the way the team actually talks: Grill, Fry, Saute, Salad, Dessert, Bar, Expo. If the kitchen calls it “Hot Side” but the POS says “Line 2,” I fix that first. Clear names prevent mistakes during a rush.

Next, I decide what “primary” means in this building. A burger’s primary station is Grill, even though fries ride with it. Fries are a secondary station, but they shouldn’t steal ownership of the ticket. That ownership decision matters because splitting tickets too often creates noise, duplicate work, and expo confusion.

I also make expo a first-class stop in the flow. Expo is the pass, but it’s also quality control and pacing. If expo doesn’t see the right items at the right time, you’ll get “mystery plates” that sit, die in the window, or get remade.

Finally, I think in courses, not menu categories. Appetizers, entrees, desserts, and drinks often need different fire timing. Course-based routing keeps the kitchen calm because the ticket order matches how food should hit the table.

My kitchen routing checklist before I map a single item

I’ve learned that routing fails when people treat it as “send it to a printer.” I build rules that match production, timing, and human habits.

Here’s what I lock down first:

• Define station ownership: Every menu item has one primary station. One. That station is accountable for the dish leaving the window.
• Consolidate prints/screens: If two stations can share a screen without chaos, I combine them. Fewer destinations means fewer misses.
• Use secondary stations for sides and mods: Fries, sauces, and add-ons should support the main ticket, not fragment it.
• Set hold vs fire rules: “Hold fries until steak is dropped” is a rule, not a hope. Same for salads held until the table is sat.
• Decide what expo must see: Expo should see complete, readable tickets, not a flood of partial chits.
• Name devices like you mean it: “KDS 1” is useless. “Grill KDS” and “Fry Printer” save time when something breaks.
• Plan for failure: A KDS outage needs a printer fallback (or the reverse) with a simple switch.

When I’m asked to provide Restaurant POS Support, I’m also doing Small Business IT. If your KDS depends on Cloud Infrastructure and Cloud Management (or you run multi-site), I check Secure Cloud Architecture, Cybersecurity Services, Endpoint Security, and Device Hardening on every POS and KDS device. Many operators tie this work to Office 365 Migration, Data Center Technology validation, and Infrastructure Optimization as part of a broader Digital Transformation. The right Business Technology Partner brings Technology Consulting, Tailored Technology Services, Innovative IT Solutions, Kitchen Technology Solutions, and IT Strategy for SMBs that keep Managed IT for Small Business and Business Continuity & Security in focus.

Routing table template and a 10-item sample mapping

I like a routing table because it forces decisions in plain language. It also stops the common mistake of building routing item-by-item inside the POS until the system becomes a patchwork.

Here’s a template you can paste into Sheets or Excel:

Menu Item	Course	Primary Station	Secondary Station(s)	Printer/KDS Screen	Hold/Fire Rules	Notes

Sample mapping for a mixed casual menu (10 items)

Use this as a starting point, then adjust for your kitchen’s layout and staffing.

Menu Item	Course	Primary Station	Secondary Station(s)	Printer/KDS Screen	Hold/Fire Rules	Notes
Classic Burger + Fries	Entree	Grill	Fry	Grill KDS	Fire fries with burger	Toast bun timing
Chicken Wings	Appetizer	Fry		Fry KDS	Hold sauce separate	Ranch on side
House Salad	Appetizer	Salad/Garde Manger		Salad Printer	Fire on order	Dress light
Ribeye Steak	Entree	Grill	Saute	Grill KDS	Hold veg until steak is down	Temp notes matter
Fettuccine Alfredo	Entree	Saute		Saute KDS	Fire pasta, hold sauce if needed	Allergy flag
Side Fries	Side	Fry		Fry KDS	Fire with entree	Season at drop
Cheesecake	Dessert	Dessert		Dessert Printer	Hold until fired	Plate berries
Margarita	Drink	Bar		Bar KDS	Fire now	Salt rim mod
Draft Beer	Drink	Bar		Bar KDS	Fire now	Glass note
Coke	Drink	Bar		Bar KDS	Fire now	No ice mod

Troubleshoot bottlenecks, then prove the fix in a peak simulation

When service drags, I don’t start by adding more routes. I start by finding where tickets are piling up and why.

Grill overload (too many items land on one screen)

• Move shared items to secondary stations (example: “add bacon” routes to Grill only as a modifier, not a second full ticket).
• If you have a Saute station finishing steaks or chicken, let Grill own the item and Saute support it, not the other way around.
• Watch for “everything prints to Grill” defaults in the POS.

Fry station queues (fries become the pacing problem)

• Use hold-fire rules for sides so fries don’t die in the window.
• If wings and fries share oil space, separate their routing screens so the cook can prioritize.
• Consider a backup fry route only during peak shifts (don’t run it all day).

Expo congestion (tickets complete, but the pass is buried)

• Make expo see the full order once, not five partial tickets.
• Route “ready” signals by course, so expo isn’t juggling appetizers and entrees at the same moment.
• Keep duplicate modifiers off the expo chit unless they affect plating.

Duplicate tickets (the quiet killer)

• Check for both printer and KDS firing on the same station.
• Confirm reprint settings and resend behavior at the terminal.
• Standardize device names so admins don’t route to the wrong destination.

One-page kitchen routing checklist (print this)

1. List every menu item by course
2. Assign one primary station per item
3. Add secondary stations for sides and key modifiers
4. Map each station to a printer or KDS screen
5. Define hold vs fire rules per course
6. Add notes for plating, temps, allergy flow
7. Consolidate routes to reduce ticket splits
8. Test at low volume, confirm every destination
9. Simulate peak volume with timed fires
10. Verify no duplicate prints or double KDS bumps
11. Train staff on ownership and expo flow
12. Review monthly, adjust with menu changes

A kitchen routing checklist isn’t “set it and forget it.” It’s a living map. When I keep ownership clear, avoid needless splits, and test under peak load, the kitchen stays calm and the guest feels the difference. If you want one fast win this week, run a 30-minute peak simulation and fix the first bottleneck you can measure, then lock it into your routing rules.