Assign each menu item to the station that actually prepares it, then check every destination with the cooks who will use it. Add a second station only when that team has work to do, and decide separately whether expo needs to see the item as part of the complete order.
Start with your real menu and station layout, not the names already in the software. A routing map is useful only if a cook can look at a ticket, understand the job and act on it. The goal is to prevent both missing work and extra tickets that nobody owns.
Map menu items to the stations that prepare them
List the stations you intend to staff during service. These might be grill, fryer, cold prep and expo. Use names your team already recognizes. If the same cook handles two areas at lunch but different cooks handle them at dinner, document both arrangements before choosing a setup.
Next, walk through the menu item by item. Ask who starts it, who finishes it and whether another station has a separate task. Include sides, desserts and items that arrive ready to serve. A packaged drink may need someone to collect it even though nobody cooks it.
The following worksheet uses a hypothetical kitchen with three staffed prep stations: grill, fryer and cold prep. Expo checks the complete order before handoff. The restaurant sells a burger with fries, a fried chicken sandwich, a salad and a bottled drink. This is a planning example, not a claim about any product's configuration.
| Menu item | Prep destination | Work expected | Expo check |
|---|---|---|---|
| Burger with fries | Grill and fryer | Grill cooks burger; fryer prepares fries | Match both parts to the order |
| Fried chicken sandwich | Fryer | Fry chicken and assemble sandwich | Check sandwich against the order |
| House salad | Cold prep | Prepare and dress salad | Check salad against the order |
| Bottled drink | Cold prep | Collect the correct drink | Confirm it goes with the order |
The table records the intended work, not just where a ticket appears. In this example, cold prep owns the bottled drink. If the handoff employee collects drinks instead, change the ownership and ask how that task will be shown. Do not leave it unassigned simply because it needs no cooking.
Use the same exercise for every order channel you accept. Ask whether an item entered at the counter, online or through another channel reaches the same intended stations. The menu name may look similar while the underlying setup differs. Include pickup and dine-in versions if staff handle them differently.
A restaurant POS system is part of this conversation because the way items and options are entered can affect what the kitchen receives. Have the person who maintains the menu join the mapping session with the cooks.
Decide when an item needs more than one destination
In the worksheet, the burger with fries requires two prep destinations. Grill needs the burger task; fryer needs the fries task. Expo needs enough order context to bring the pieces together. That is different from sending the entire order to every station and expecting each cook to filter it.
For this dish, ask the vendor to demonstrate exactly what appears at each screen. Does the fryer see a clear fries task, or only a burger name that requires staff to remember the side? Can grill distinguish a burger that includes fries from one sold without them? Does expo see both components in a way that supports the final check?
Make ownership explicit. If grill assembles the burger and fryer places fries in a separate container, note who brings the components together. If expo assembles the plate, expo needs to know when both pieces are ready. The routing decision assigns work; the expo workflow coordinates the whole order.
Now change one input. Suppose the kitchen stops including fries with the burger and sells them as a separate side. The burger may need only the grill destination; the fries still need fryer. Expo must then match the separately ordered side to the correct order. Check whether staff can enter the revised menu cleanly and whether the display makes the change obvious.
Do not assume a system can split an item, duplicate it to stations or show a separate component in the way you want. Ask what configuration is required and what the cook actually sees. If a shared item appears twice, decide how each station will recognize its own responsibility without treating the other station's copy as a second sale or a second portion to prepare.
Also plan for a station that is closed. If fryer is unavailable, who can change the menu or redirect work? Ask whether the system supports a temporary routing change, who is authorized to make it and how the team can verify it. If it does not, decide whether to remove affected items from sale or use another documented process. Never rely on a silent workaround that only one manager knows.
Trace modifiers, changes and canceled items
Modifiers can change the work even when the main item stays the same. For the hypothetical burger, consider no cheese, an extra patty and a request to leave the fries off. Grill needs to see instructions that affect the burger. Fryer needs an unambiguous instruction if the fries task is removed. Expo needs a final view that helps prevent the wrong combination from leaving the kitchen.
For each important modifier, write down three things: which station must see it, what action it changes and what should appear elsewhere. A note that matters only to grill may not need to clutter the fryer view. A change that removes fryer work must not be buried where the fryer cook cannot find it.
Ask the vendor to demonstrate how modifiers are displayed for shared items. Are they attached to the relevant task? Can long notes be read without opening another screen? If staff must interpret a shorthand, agree on it before service and keep it consistent across ordering channels.
Then trace an edit after the original order has reached the kitchen. For example, a guest changes the burger from one patty to two. Decide what grill should see, whether expo should see the revised order and how staff will tell the current instruction from the original. The answer may depend on the product and its settings, so watch the proposed workflow rather than accepting a general promise that edits are supported.
Run the same exercise for cancellation. If the burger with fries is canceled after both stations receive it, establish what each station should see and how expo will know not to hand it off. Ask whether the system flags a cancellation, removes an item, retains a visible record or requires another action. If the display alone cannot communicate the change clearly, set a verbal confirmation process and assign responsibility for it.
Timing matters. A cancellation before work starts is different from one after a cook has begun. Your procedure should tell staff whom to notify and where to check the latest instruction. Do not assume a deleted line, a changed quantity or a recalled ticket behaves the same way in every system.
For context on the display itself, Fleksa's kitchen display system page describes order type, item names, quantities and modifiers, along with held future orders and configurable timing and color indications. Ask to see how the particular routing and change scenarios you need would work in your setup.
Get cooks to sign off before service
Turn the map into a short acceptance checklist. Include the original item, its options, each expected destination and the action each person should take. Keep the expected results separate from the observed results so the team can spot a missing task rather than rationalize what appeared.
Use a vendor-supported training environment for the first checks. These are simulations, not live orders: they must not trigger a real card payment, guest message or courier dispatch. Confirm those safeguards with the vendor before entering practice tickets. A simulation should not depend on sending an actual order to a guest or delivery partner.
- Single-station item: Enter the house salad. Expect a clear preparation task at cold prep and the agreed order view at expo. Check that grill and fryer are not asked to prepare it.
- Shared item: Enter the burger with fries. Expect the grill and fryer tasks described in the worksheet, plus the agreed expo view. Ask both cooks to state their part without coaching.
- Modifier: Enter a burger without cheese. Expect grill to see and understand that instruction. Confirm the fryer and expo views contain the information each needs.
- Change and cancellation: Change the patty quantity, then run a separate cancellation scenario. Record what each station sees and whether staff can identify the current action.
- Alternate path: Repeat an item through each ordering channel you plan to use, and check any different lunch or dinner station arrangement.
For every check, record pass or fail, the screen or station involved, and the person responsible for resolving a mismatch. A pass means the intended cook received a usable instruction and other affected staff had the information they needed. It does not mean merely that a ticket appeared somewhere.
Have a cook from each station review the results. Ask: Can you read the item quickly? Is your action obvious? Could this view cause you to make an extra portion or miss a change? If the answer is unclear, revise the menu, routing or operating procedure, then repeat the simulation.
Once the simulated checks pass, arrange a separate supervised service pilot with the vendor and your shift lead. Use normal, authorized service orders and watch for missed work, duplicate preparation and unclear changes. Agree beforehand on who can pause the rollout and what temporary process staff will use if routing fails. Review the results after the shift before expanding the setup.
Before choosing a system, use the same checklist in each demonstration. Ask about setup support, devices, additional screen charges and behavior during an interruption, and request a written quote for your configuration. A broader KDS buying guide can help frame those questions; your own station map should determine which answers matter most.
Next step: Bring your menu, station map and five acceptance checks to a Fleksa demonstration. Compare the KDS workflow against your operating requirements, and ask the cooks who will use it to review the results.
Frequently asked questions
Should every station see every order?
Not necessarily. Show each prep station the work and context it needs, and give expo the order view required for handoff. Verify that the chosen setup does not hide essential instructions or create distracting duplicate work.
What if one dish needs two stations?
Assign a clear task to each station and identify who brings the components together. Demonstrate the actual display for both stations and expo before relying on the setup.
How often should the routing map be reviewed?
Review it when the menu, station staffing or ordering flow changes, and after staff report a missed or confusing ticket. Repeat the affected simulation before using a revised setup in service.
