For most restaurants with two or more kiosks, start by testing one shared line that feeds the next available device. It gives guests one obvious place to wait and lets the first party in line use whichever kiosk opens next. Separate lines can work when demand is light, guests can easily see which line to join, and staff can redirect people if one device slows down.
The right choice depends on more than the number of screens. Check how long parties take to order, how much room the queue needs, and what your team can do when a kiosk is unavailable. The question is about assigning guests to devices, not simply deciding where the devices stand.
Decide who owns the queue
Give one role responsibility for the decision and for exceptions. In a small restaurant, that may be the shift lead. In a busier operation, a front counter employee may watch the line while the manager handles a device problem. The owner of the process should be able to change signs, direct guests, and open the staffed ordering fallback when needed.
With a shared line, parties join one queue and the person at the front goes to the next free kiosk. Someone must make that rule visible and help guests notice an open device. If the front party needs assistance, decide whether an employee will help them or invite the next party to another available kiosk.
With separate lines, each kiosk has its own queue. Guests choose a line when they arrive. That can be easy to understand, but one slow order or an unavailable screen can leave one group waiting while another line moves. Decide whether guests may switch lines and how staff will prevent confusion when they do.
Use guest parties, not individual people, as the starting unit for the worksheet. A family placing one order may occupy a kiosk once, even though several people are waiting. Also note that each kiosk serves only one party at a time; a queue capacity count is not a count of physical tables or dining seats.
Sketch a peak period before choosing
The following is a hypothetical planning example, not a prediction of kiosk performance. A restaurant has two working kiosks. Each party takes three minutes at a kiosk, including order entry and payment. Eight parties arrive during a 15-minute peak period. Assume each kiosk is available for the full period, parties are ready when a screen opens, and the kitchen and pickup counter can handle the orders.
Under those assumptions, each kiosk has capacity for five parties in 15 minutes, so the two devices have combined capacity for 10. Eight arrivals fit within that total capacity, but the total alone does not tell you how long an individual party waits. Arrival timing and the order in which parties choose devices still matter.
Sketch the shared option as arrivals → one line → next free kiosk → kitchen and pickup. The shift lead sets the rule; the front counter employee points the first waiting party toward an open screen. The kiosk handles the guest's order entry, while the kitchen and pickup team handle fulfillment.
Sketch the separate option as arrivals → line A or line B → assigned kiosk → kitchen and pickup. The shift lead marks two lines. Guests choose one, and the front counter employee watches for a stalled screen or a large imbalance. If six parties choose A and two choose B, the six cannot all finish at A within the 15-minute window under the three-minute assumption. Moving a waiting party to B, or allowing a line switch, changes that result.
Now change the assumptions to fit your service. A large customized order may take longer than a repeat order. A burst of arrivals at the start of the window can produce a line even when total capacity exceeds total arrivals. Time several representative orders in a safe practice setting, then observe a live service pilot separately with normal guest consent and procedures. Record arrival patterns, assistance requests, and where the kitchen or pickup counter becomes the bottleneck.
Use the queue selection worksheet
The table compares the two layouts using the same operating questions. Read the cost column as quote and staffing dependencies, not a claim that either layout has a fixed price. Both layouts still need working kiosks and a way to fulfill orders.
| Decision factor | One shared line | Separate lines | What to check |
|---|---|---|---|
| Staff effort | May need a person to point out the next open screen. | May need intervention when lines become uneven. | Who can redirect guests during the busiest period? |
| Guest impact | One joining point; the next-device rule must be clear. | Direct choice of device; a slow line can feel unfair. | Can guests see the signs and understand where to wait? |
| Space and access | Needs one waiting area and a clear route to each kiosk. | Needs room for distinct lines without blocking access. | Can a guest who uses a mobility aid reach a screen and the counter? |
| Cost dependencies | Ask about signs, barriers, setup, and any extra staff time. | Ask about signs, barriers, setup, and any extra staff time. | Compare written installed quotes and expected operating effort. |
| Device limitations | Does not require automatic assignment if staff or signs direct guests. | Does not require automatic balancing if staff manage switches. | Ask what the kiosk displays when unavailable and how staff change its status. |
For the hypothetical restaurant above, choose the shared line for the first pilot. It avoids relying on guests to distribute themselves evenly, and the assumed combined capacity covers the eight-party peak. That recommendation depends on having enough room for one accessible line and a front counter employee who can direct guests when needed. If neither condition holds, test separate lines with a clear switching rule instead.
Do not treat either option as a fix for a kitchen that cannot keep up. Track the time from order submission to pickup separately from time spent waiting for a kiosk. A shorter ordering line can simply move the wait to the pickup area.
Check the software and the full quote
Ask each vendor to show the guest flow your team expects to use. Can staff tell when a kiosk is unavailable? What does a guest see on the screen? Can an employee take the same order at the counter if the device cannot be used? Ask what requires a setting, extra equipment, or a staff action rather than assuming the queue will manage itself.
Also check the ordering flow. Fleksa's restaurant kiosk page describes browsing, item customization, order review, and possible suggested add-ons. Ask which options are available in your setup and how a guest gets help without losing their place. Review the kiosk documentation alongside the demonstration, and ask how the kiosk connects to the restaurant POS system in the configuration you are considering.
Request an installed quote that separates software, hardware, setup, signs or barriers, and recurring charges. Ask about payment processing and support separately, and estimate the staff time needed to manage each queue. A quoted processing fee alone is not the all-in operating cost. For a broader cost comparison, use the self-order kiosk break-even guide. Ask a qualified adviser about contract or tax treatment when needed.
Run an outage drill, then a live pilot
Before selection, use a simulation with staff acting as guests. Make one of two practice devices unavailable, or mark it unavailable without affecting a live ordering service. Use a test environment or a non-transactional walkthrough: the drill must not charge a card, send a guest message, or dispatch a courier. Do not assume a vendor has a test mode; ask how to run the check safely.
For the hypothetical eight-party peak, the remaining kiosk can serve at most five parties in 15 minutes at three minutes per party. That leaves three of the eight beyond the device's capacity for that window. The drill should therefore include a staffed counter option or another agreed way to handle the excess; redirecting everyone to the remaining screen does not restore the lost capacity.
For a shared line, the shift lead marks the failed kiosk unavailable, tells the line which screen remains open, and sends guests who prefer or need help to the staffed counter. For separate lines, the employee stops new guests joining the failed device's line and directs its waiting parties to the end of the remaining line or to the counter. Explain the rule aloud and on a sign so guests are not left guessing.
Pass if the team identifies the unavailable device, stops new guests from joining its queue, explains the move, keeps the route accessible, and offers the agreed staffed fallback. The remaining kiosk and counter must also be able to receive parties without the team assuming the original two-device capacity still exists. Record the time to recognize the problem, the directions given, where parties wait, and any point where staff cannot complete the fallback.
Fail if guests continue to queue at the unavailable device, cannot understand where to go, or have no usable fallback. If the vendor cannot provide a needed display or status change, use a physical sign and a named employee to manage the queue, then repeat the drill. If the counter cannot absorb excess demand, revise staffing or the service plan before relying on kiosks at that peak.
After the simulation, run a separate live service pilot with the chosen layout. Observe actual arrivals, wait points, staff interventions, and pickup delays; change one queue rule at a time. Compare the workflow with your current process, then ask Fleksa to demonstrate the applicable kiosk capabilities for your setup.
Frequently asked questions
Is one kiosk line always faster?
No. A shared line can make the next available device easier to use fairly, but actual waits depend on arrival timing, order duration, assistance, and device availability.
When do separate kiosk lines make sense?
They are worth testing when guests can identify each line, space allows accessible routes, and an employee can handle an imbalance or device outage.
What should happen if a kiosk goes down?
Stop guests joining its line, direct waiting parties to the remaining queue or staffed counter, and explain the change. Check whether the remaining capacity can handle demand rather than assuming it can.
