Batch identical items when the shared preparation is genuinely the same, the orders can be ready at the right times, and cooks can still identify each guest’s food. Keep orders separate when a modifier changes the cooking process, an instruction requires separate handling, or combining work would make one order wait too long.
A kitchen display’s all-day count can show how many items are needed. It does not, by itself, decide which items should be cooked together. Set that rule with your cooks and test whether the screen helps them follow it without losing the individual tickets.
Start with two orders, not an aggregate count
Hypothetical example: A counter-service kitchen receives two orders for the same grilled chicken bowl. Order A is due at 12:10 and needs sauce on the side. Order B is due at 12:16 and needs extra sauce. Each has one chicken portion and the same base. Neither instruction changes how the chicken is cooked.
The all-day demand is two bowls, but the six-minute gap matters. The cook could prepare both chicken portions together and keep them identified for their respective tickets. The cook could also prepare the first portion now and the second later. A third option is to cook and assemble both bowls together; that risks making B wait after assembly or making A late while the kitchen waits for B.
For this example, choose shared chicken preparation only if the kitchen’s established holding procedure keeps B suitable until its assembly time. Otherwise, cook the portions separately. In either case, assemble and sauce the bowls against their own tickets. The shared item name is not permission to combine every step.
Use the worksheet below to record the decision before asking a vendor for a demonstration. The alternatives are production choices, not claims about what a particular screen can do.
| Decision point | Shared preparation | Separate work | Acceptance check |
|---|---|---|---|
| Chicken portions | Cook together only if the later portion can be held under the kitchen’s procedure. | Cook separately if timing or handling makes a shared batch unsuitable. | Cook can identify the portion for each ticket. |
| Sauce and assembly | Gather common base ingredients together. | Apply A’s side sauce and B’s extra sauce separately. | Each completed bowl matches its own modifier. |
| One portion finished | Continue the remaining portion when appropriate. | Keep the unfinished item visible in the team’s workflow. | Staff can tell which ticket is ready and which still needs work. |
| Order B changes | Reuse unchanged preparation only if the revised instruction permits it. | Stop and reassess B; do not alter A by assumption. | Cook and expediter can identify the affected ticket and next action. |
The table makes the key distinction visible: a batch is a way to organize a task, while the ticket remains the record of what a particular guest needs. Write a similar row for each high-volume item where staff are tempted to combine work.
Batch preparation, then return to each ticket
Break the item into stages. For a bowl, those might be cooking the protein, portioning the base, adding toppings, applying sauce and handing off the finished order. Ask at each stage whether both orders still require the same action. If they do not, split the work at that point rather than treating the entire item as one batch.
Common preparation can be useful when portions use the same ingredients, equipment settings and handling method. A cook might place two plain portions on a grill at once, for example, while keeping the portions and their destinations identifiable. That does not make two differently finished bowls interchangeable.
Choose a practical maximum batch size for each item and station. The limit should reflect equipment capacity, the cook’s ability to track portions, and how long food can wait under the restaurant’s own procedures. A batch that fits on the grill may still be too large if the cook cannot reliably match its portions back to tickets. Start conservatively and adjust only after observing a supervised service period.
Set a timing limit too. Decide how far apart due times may be before a cook must split the preparation. There is no useful universal number: a crisp item, a slow-cooked item and a cold garnish have different quality windows. Write the limit next to the menu item, along with who can approve an exception.
Finally, define the handoff. The cook should know which ticket receives each portion; the expediter should check the item and modifiers before it leaves. If the screen groups a view of demand, ask how staff return from that view to individual orders. The guide to routing tickets by preparation station can help with the related question of who sees each part of the work.
Test partial batches and changed orders
A useful screen must support the team’s actual decisions, not just display a total. Ask the vendor to demonstrate the example using a supported training environment. Make it clear that this is a simulation: it must not take a real payment, send a guest message or dispatch a courier.
- Enter the two example orders with their different modifiers and due times. Have the cook find both tickets and explain what can be prepared together.
- Simulate finishing only A’s portion. Ask the cook and expediter to show how they know A is ready for its next step while B still needs work. If the screen cannot represent that state directly, ask the team to demonstrate its agreed manual method.
- Change B’s instruction in the simulation. Have the cook identify B, stop the affected work and explain whether any prepared component can still be used. A should remain identifiable throughout.
- Simulate the final check. The expediter matches A to sauce on the side and B to extra sauce without relying on memory alone.
Acceptance rule: Each person must be able to identify the affected ticket, its current status and the next action. The team must also be able to distinguish the finished portion from the unfinished one and match both modifiers at handoff. If a step depends on a verbal call or a physical marker, record that step and the person responsible; do not count an undocumented workaround as a screen feature.
Ask the vendor what happens when an item is changed after work has started, and how staff see or acknowledge the change. Also ask how partial completion, cancellation and any return to an earlier ticket are handled in your intended setup. Do not assume every system supports these actions in the same way. If the answer is a workaround, decide whether it will hold up during your busiest period.
After the simulation, run a supervised live service pilot with normal orders and the agreed workflow. Observe handoffs and clarify mistakes as they occur. A simulated pass shows that staff can follow the scenario; a live pilot checks whether the process remains workable under service pressure. Neither proves that every future exception will be caught.
Write stop rules for instructions and time-sensitive food
Give cooks a short list of conditions that end shared preparation. A stop rule should tell the station what to do next, not just say “be careful.” For example: stop the batch when an instruction changes an ingredient, cooking method, equipment or handling requirement. Check the affected ticket and use the restaurant’s established procedure before continuing.
Special instructions deserve particular attention because an apparently minor note may change the whole process. Do not infer that an ingredient can simply be removed after cooking. If the instruction is unclear, pause the affected item and have the designated person clarify it through the restaurant’s normal process. Keep unrelated tickets identifiable while the question is resolved.
For time-sensitive food, separate orders when a shared batch would leave an item waiting beyond the kitchen’s quality or holding procedure. Likewise, do not delay an earlier order merely to fill equipment capacity. Record the decision point in terms the station can use: which item, which stage, who calls the split and where the waiting portion goes.
A manager should revisit these limits when the menu, equipment or service pattern changes. An item that batches well during a quiet lunch may be difficult to track when several modified orders arrive together. The goal is a repeatable decision, not the largest possible batch.
Compare screens against the rule your kitchen needs
Bring the completed worksheet to each demonstration. Show vendors the same two-ticket scenario and ask them to follow the same sequence, including the partial batch and changed order. Look at how quickly the cook can find item names, quantities, modifiers and timing information, then trace each item back to its order.
Fleksa’s kitchen display system is linked to restaurant orders and describes order types, item names, quantities, modifiers, future held orders and configurable timing and color indications. Ask to see how those details appear in your setup and how your team would handle the worksheet’s exception steps.
Also ask how the display receives orders from your restaurant POS system, how stations are configured, and what devices or additional screens are required. Get the proposed setup and costs in writing. A screen that shows an aggregate count may still require a separate process for tracking individual portions, so include that process in staff training and in the buying decision.
Next step: Choose one frequently ordered item, fill in the worksheet for two differently modified tickets, and use it to compare your KDS requirements with Fleksa’s available workflows.
Frequently asked questions
Can cooks batch orders with different modifiers?
Yes, when the shared preparation remains identical and each portion stays identifiable. Split the work before a modifier changes the ingredients, handling or assembly, and follow the restaurant’s procedure for special instructions.
Does an all-day count tell cooks what to batch?
No. It can show aggregate demand, but the team still needs rules for due times, preparation steps and individual ticket tracking.
What should happen if an order changes mid-batch?
Stop the affected work, identify the changed ticket and check whether its prepared components still meet the instruction. Keep the other order separate and use the screen or an agreed manual process to communicate the next action.
