Setting up a self-order kiosk

Standing up a kiosk is mostly not a technical exercise. The software configuration is an afternoon; the decisions that determine whether guests actually use the thing are about where it sits, what the menu looks like on it, and how the first fortnight is staffed.

1. The hardware you need

• ✓A tablet. On Opero this is an iPad or Android tablet you already own, run in a locked kiosk mode, rather than a proprietary terminal.
• ✓A stand or enclosure. It should hold the tablet at a comfortable standing height and resist being walked off with. A dedicated kiosk stand is available from us if you would rather not source one.
• ✓Power. Plan this before you choose the location — a kiosk running all day needs a permanent supply, not a battery.
• ✓A supported card reader, if the lane takes payment. One per location is bought from us; each additional lane that accepts cards needs its own.
• ✓Network. Wired is steadier than wireless at a fixed station; if you must use wireless, check signal at the exact spot rather than nearby.

2. Placement decides adoption

The most common placement mistake is putting kiosks where they are convenient to install rather than where a guest walking in would naturally go. A guest entering your restaurant should see the kiosk before they see the queue, or they will simply join the queue.

• ✓In the guest's line of sight from the entrance, ahead of the counter queue.
• ✓Enough clear floor for a person to stand and a short queue to form without blocking the collection point.
• ✓Not so close together that the bank reads as one crowded station.
• ✓Away from direct glare — a screen washed out by a window at 4pm is a screen nobody uses.

3. Prepare the menu before you launch

A kiosk exposes every weakness in a menu that staff have been quietly compensating for. Items with unclear names, missing photos, or modifier chains that only make sense if someone explains them will underperform badly and generate support at the counter.

Do this work first, not after launch. Our guide to kiosk menu design covers the specifics, but at minimum: photograph your top sellers, shorten the category list, and walk the full ordering path yourself on the actual screen before a guest does.

4. Brief the team

Staff decide whether a kiosk succeeds far more than guests do. If the team believes the kiosk is there to eliminate their jobs, they will not steer guests to it, and adoption will stall at whatever level guests discover on their own.

• ✓Explain the role change honestly: fewer people behind a register, more in front of the guest.
• ✓Make one person the kiosk owner for the first fortnight — checking screens, paper and cleanliness at each shift change.
• ✓Give the team a one-line invitation to use on guests: pointing works better than explaining.

5. The first two weeks

Expect the kiosk to be slower than your counter at first. Guests are learning an unfamiliar path, and your time-per-order will be well above steady state. Do not size your kiosk bank or judge the investment on week-one numbers.

• ✓Watch where guests hesitate. A pause in the same place from several guests is a menu problem, not a guest problem.
• ✓Watch abandoned orders. Sessions started and left are the clearest signal something in the path is confusing.
• ✓Check the kitchen. Kiosk tickets arriving with modifiers the line does not understand is a naming problem worth fixing immediately.

Why this is a short project in Opero

Because the kiosk shares one menu spine with the POS, there is no separate kiosk menu to build: the items, prices and modifiers you already use appear on the kiosk, and an 86 at the register removes the item from the kiosk in the same moment. Kiosk orders drop into the same kitchen display queue as counter orders, so the line works one flow rather than watching two screens.

Pricing is per location with unlimited devices, so a trial lane and a fourth lane cost the same in software. If the trial does not work in your room, you have spent a tablet and a stand rather than a hardware contract.