Two restaurant brands sharing a kitchen need a reliable way to tell tickets apart at every point of preparation. The safest buying decision is to choose a display setup where staff can see the brand alongside the order details they need, then prove that the distinction survives station routing and the handoff to expo.
Do not rely on an order number or item name alone. Both brands might sell a chicken bowl, and both might produce order 104. A cook who sees only “104 — chicken bowl” cannot tell which recipe to make or which branded packaging belongs at the pass.
The kitchen manager should own this decision, with the expo lead and whoever manages the brands’ order systems involved in the demonstration. Together, they can decide what staff must see, what happens when information is missing and whether the proposed setup fits the way the kitchen actually works.
Decide where the brand must be visible
Start with the journey of one order rather than a list of screen features. An order may arrive at a prep station, move to a cook station and finish at expo. The brand identifier needs to remain useful wherever someone makes a brand-dependent decision.
At a prep station, that may mean choosing the right sauce or modifier. At expo, it may mean matching the finished food to the correct ticket, packaging and pickup process. The person looking at the screen should not have to infer the brand from a recipe, a familiar customer name or the location of a ticket in a queue.
Write a simple visibility rule: the brand name must be readable with the order identifier and relevant item details on every view where staff act on the ticket. If a station uses a compact view, ask to see that view in the demonstration too. A label on the full ticket is less useful if the cook’s normal screen hides it.
Also settle who can see which orders. A shared view may be appropriate for staff working across both brands. It does not, by itself, establish that one brand’s business data is isolated from the other. If restricted access matters, ask the vendor to demonstrate permissions and reporting boundaries separately.
Compare the practical display approaches
A shared queue with visible brand labels can give a cross-trained crew one place to manage work. It depends on the label being clear enough to read quickly and remaining visible on the views staff actually use. Ask whether the label can be confused with an order source, service type or customer name. A shared queue may be a poor fit if staff are not authorized to see both brands’ orders.
Separate brand views may make it easier for a dedicated team to focus on one menu. Ask how staff switch views, whether a shared station can see work from both brands and how expo finds all items belonging to an order. Separate screens or filters can create another problem if an employee must watch both but can only see one at a time.
A station-first view with brand labels can suit a kitchen where the same cook prepares items for both brands. The station sees its own work while the label tells the cook which recipe applies. Ask what expo sees when an order has items prepared at different stations, and whether the brand remains visible through that handoff.
These are operating patterns to demonstrate, not promises that any particular product offers every configuration. Square describes station routing and expeditor functions for its KDS; Toast offers a kitchen display product. Fleksa offers a kitchen display system linked to restaurant orders. For each option, ask to see your intended workflow rather than accepting a generic feature list.
Use a two-brand worksheet
The following example is hypothetical. Harbor Bowls and Juniper Kitchen both receive order 104 for one chicken bowl. Harbor’s bowl calls for citrus sauce; Juniper’s calls for herb sauce. Both brands use the same prep station and expo pass. The duplicate order number and item name are intentional: they expose whether the brand is doing useful work on the screen.
The worksheet sets an expected result and an owner for each decision. The owner is the person responsible for the next action, not necessarily the person who configured the system. Adjust the station names and modifiers to match your menus before a demonstration.
| Checkpoint | What the team should see or do | Expected result | Next-action owner |
|---|---|---|---|
| Incoming tickets | Two order 104 tickets, each with its brand, chicken bowl and sauce | Staff can distinguish Harbor from Juniper without guessing | Kitchen manager checks labels |
| Prep station | Both tickets in the view used by the prep cook | Cook can read each brand and its correct sauce | Prep cook prepares the matching bowls |
| Expo | Completed items matched to their respective branded tickets | Expo can distinguish the two orders and choose the right packaging | Expo lead verifies each handoff |
| Missing brand | A ticket arrives without a readable brand in the simulated scenario | Staff hold the item and resolve its identity rather than guess | Kitchen manager checks the source and records the resolution |
For the first two tickets, the pass condition is not simply that both appear somewhere on a screen. The prep cook must be able to identify Harbor’s citrus bowl and Juniper’s herb bowl in the normal working view. Expo must then match each finished bowl to the correct brand and order. If the display groups items, hides modifiers or abbreviates labels, check whether the remaining information is still enough for that decision.
The missing-brand row tests a different problem. Agree on a manual recovery path before the demonstration: hold the ticket, have the manager check the originating order information through an authorized channel, and tell prep and expo the resolved identity. Decide how the team will mark or communicate that resolution. Do not assume the display can edit, recall or reroute a ticket; ask the vendor what is possible.
If the kitchen also splits one order between stations, add a ticket that reflects that pattern. Have the vendor show what each station sees and how expo knows which pieces belong together. The important result is an accurate handoff, not merely separate station screens. For more on this narrower setup decision, read the guide to routing tickets by preparation station.
Set pass and fail criteria before the demo
Send the vendor your worksheet and ask for a demonstration in a vendor-supported training environment. Use simulated orders only. The exercise must not trigger a real card payment, guest message or courier dispatch. Confirm the environment and its safeguards before entering the sample tickets.
- Create the collision. Enter the two simulated order 104 chicken bowls with their different brands and sauces. Pass if the normal incoming view makes both tickets distinguishable. Fail if staff must guess or open an unrelated system just to identify the brand.
- Follow the station work. Show the exact view a prep cook would use. Pass if the cook can see the brand and the sauce needed for each bowl. Fail if the label or modifier disappears from that working view.
- Follow the expo handoff. Show the view and steps expo would use after preparation. Pass if expo can match each bowl to the correct brand and ticket. Fail if the team cannot make the match using the agreed workflow.
- Handle the exception. Simulate a missing or unreadable brand. Pass if staff can stop and use the agreed manual recovery path before proceeding. Fail if the only workable response is to guess. If the training environment cannot create this exception, walk through the recovery procedure and record it as untested in the simulation.
- Check support. Ask who to contact if a brand label disappears during service, what information support needs and how the kitchen should work while waiting. Pass if the response gives your manager a usable escalation and fallback plan.
Record the result for each checkpoint, including the screen view and any manual step. A pass that depends on an extra device, a separate lookup or a manager’s intervention is still useful information, but it may not suit a busy shift. Ask for that dependency to be included in the proposed setup and quote.
After staff practice in the training environment, plan a supervised live service period with a named manager watching the handoff. Live service uses actual orders and normal operating controls; it is not a practice scenario. Start with a manageable period and agree how the team will pause or fall back to its existing process if a ticket is unclear.
Check the full setup before committing
Bring the order flow into the conversation. Ask how each brand’s orders reach the display, where the brand label comes from and who can change it. If you use a restaurant POS system or other order tools, have the vendor demonstrate the connections needed for your actual setup rather than assuming they will work together.
Request a written quote for the screens, setup, recurring software charges and support relevant to your configuration. Ask separately about device requirements, additional screen fees, menu routing and what happens when connectivity is interrupted. Compare the operational totals on the same basis, including any known setup and recurring charges; ask about costs for exceptions that are not covered. A quote for software alone is not necessarily the cost of running the full setup.
Finally, decide who maintains the rules when a menu or brand changes. The person managing your restaurant management software should coordinate with the kitchen lead so a new item name, modifier or label is checked before staff depend on it.
Take the completed worksheet to a vendor demonstration. Compare your KDS requirements with Fleksa and confirm feature availability for your brands, stations and expo workflow before committing.
Frequently asked questions
Is an order number enough to identify a shared-kitchen ticket?
Not always. Two brands can use the same number. Pair a readable brand identifier with the order number and the item details staff need at each station and at expo.
Should each brand have its own screen?
Not necessarily. Separate views may help dedicated teams, while a labeled shared view may suit cross-trained staff. Test how shared stations and expo will see both brands before deciding.
Does a shared KDS keep each brand’s data separate?
A shared display does not establish data isolation. If access restrictions matter, ask the vendor to demonstrate user permissions and reporting boundaries for your proposed setup.
