Every kiosk demo looks basically the same: a clean stock menu nobody has touched since it was loaded, no line backing up behind a confused customer, a rep who has run through this exact flow more times than they can count. That's not really a test of anything. The real question is what the software does once your menu gets messy, your Wi-Fi does something unreliable, or someone on your team needs to change a modifier at 4:45 on a Friday because the walk-in cooler just died.
This piece isn't about touchscreens, stands, or card readers — there's plenty written already on which self-ordering kiosk to buy. It's about the software running underneath all of that hardware, and the six questions that tend to separate a purchase you're still happy with in year three from one you're quietly trying to get out of. Start with the one most owners don't think to ask until it's already too late.
Here's a test worth running mid-demo: ask the rep to add a new modifier group right there, live, not a rehearsed flow. Watch what happens next. If the answer involves "our team can usually turn that around in 24 to 48 hours" or "you'd submit that through your account manager," you now know something important — every 86'd item, every price change, every combo you dream up next season is going to sit in someone else's queue before it reaches your customers. What you actually want to see is the rep opening a menu builder in front of you, dragging a new modifier into a category, setting a price, and having it live on the screen before the meeting wraps up. If changing the price of a side of rice takes a support ticket, that's not a menu tool. It's a request form with a nicer interface.
This is where owners tend to get burned quietly, because it doesn't show up in the showroom. A kiosk can look flawless standing alone next to the sales rep's laptop and still fall apart the moment an order needs to land correctly on your kitchen display, with the right modifiers, in a ticket format your line cooks actually read at speed. Push for specifics: which POS and kitchen display systems has this actually been built against, how does order data move between them — a real API, a direct integration, or some middleware nobody wants to name out loud — and can they show you a live order traveling from kiosk to kitchen ticket in under ten seconds. If the rep needs to check with an engineer before naming which of your current systems it talks to, treat that as your answer.
There's a second layer worth pushing on here too: what happens to your reporting once the kiosk gets added. A lot of kiosk software treats itself as a separate sales channel, which quietly means your end-of-day totals now live in two places, and reconciling them becomes a manual step someone on your team has to remember every night. Ask directly whether kiosk sales roll into the same daily report as counter and server-taken orders, or whether you'll be exporting two spreadsheets and adding them by hand.
If you're still deciding whether you even want a kiosk running as its own system versus one built into your existing POS from the start, that's really a separate decision worth thinking through on its own — 了解更多 covers how that trade-off tends to play out.
ADA compliance for self-service kiosks stopped being optional a while ago. Restaurants have been sued over screens that couldn't be reached from a wheelchair, touch-only interfaces with no audio option, and contrast low enough that low-vision customers couldn't read the menu at all. "Our hardware partner handles that" is not an answer — software carries just as much of this as stand height does. What you want confirmed, specifically:
- Is there a screen reader mode, and does it work through the actual ordering flow, not just the home screen?
- Can text size and contrast be adjusted without an admin login?
- Is there a documented compliance statement or third-party audit you could hand to your insurance broker or lawyer if it ever came up, rather than a verbal promise from a sales call nobody wrote down?
If any of those come back vague, that's worth treating as a real gap, not a technicality to sort out later.
A lot of software billed as multilingual translates the greeting and stops there — the modifier names, the allergen notes, the payment confirmation all stay in English. If a meaningful share of your staff, regulars, or neighborhood speaks Spanish, Mandarin, or Korean, a half-translated flow is arguably worse than an untranslated one, because it looks like the job got done when it didn't. Ask to see the entire order flow, start to finish, in a second language — not the landing screen alone. Chowbus's kiosk software runs the full ordering flow — menu, modifiers, payment confirmation — in English, Chinese, Japanese, Korean, and Spanish, which is a fair bar to hold any vendor to before you take "we support multiple languages" at face value.
Nearly every vendor will say their software "supports offline mode." Fewer of them can say what that actually means when your router resets in the middle of lunch. Get specific: can a customer complete an entire order and payment while offline, or does the screen just freeze and refuse new orders until the connection comes back? Does the kitchen still get a ticket printed locally, or does everything sit in limbo until Wi-Fi returns? How long can it run offline before something actually breaks — five minutes, or five hours? The cleanest way to find out is to ask the rep to physically unplug the router mid-demo. Their reaction to that request tells you almost as much as their answer does.
This sounds like a minor operational detail until you're the owner whose kiosk freezes on an outdated version mid-Saturday-dinner-rush because nobody flagged that an update was pending. "We push updates automatically, you won't even notice" is exactly the wrong answer — you should notice, on your schedule, not in the middle of service. What you want instead: updates that happen during scheduled off-hours, advance notice before anything changes the interface your staff and customers rely on, and a rollback option if an update breaks something specific to your setup. Three kiosks quietly running three different software versions because one didn't finish updating overnight is a real failure mode restaurants have actually hit, not a hypothetical — worth asking directly how a vendor prevents it.
Judging kiosk software by a demo alone is a bit like judging a kitchen by a tasting during prep hours: everything comes out right when there's no rush, no substitution, and no ticket rail backed up four deep. What actually matters is how it holds up on a bad Friday, not how it looks on a slow Tuesday afternoon.
None of this means you need the most expensive option, or the one with the longest feature list on the sales deck. What you need is a rep who's comfortable being pushed on all six of these, unprompted, without reaching for a script. Bring your actual menu to the next demo — messiest modifier groups included — not a hypothetical one, and watch what happens when it gets tested in front of you instead of taken on faith. If you want to run through these questions yourself, Chowbus offers a demo where you can push on the same six.
The demo itself costs nothing. A software contract you're locked into for two or three years because nobody stress-tested it beforehand is a different story — and worth weighing against what kind of return a kiosk actually needs to deliver before it pays for itself; walks through how to think about that math. Write these six questions down, bring them to every vendor call this month, and pay closer attention to how a rep reacts to being pushed than to how polished their opening slide looks.
%20(1).png)
The hardware is the touchscreen, stand, card reader, and printer connections your customers physically interact with. The software is what runs on that screen: the menu builder, order logic, payment processing rules, and the connections back to your POS and kitchen display. You can buy the hardware from one company and run software from another, which is exactly why it's worth evaluating the software on its own terms rather than judging it by how nice the screen looks in a showroom.
Bring your real menu, messiest modifier groups and combo deals included, and ask the rep to build or edit it live rather than showing you a pre-loaded example. Ask to see an order travel from the kiosk to a kitchen display in real time, ask them to switch the full interface into a second language if you need one, and ask what happens if you unplug the internet mid-order. A vendor confident in their kiosk software will let you push on all of it in the room, not just the parts they rehearsed.
Most vendors charge either a flat monthly license per kiosk or fold it into a broader POS subscription, and the total can range widely depending on how many terminals you're running and what's bundled in. What tends to catch people off guard isn't the sticker price but the extras — per-edit support fees, multilingual add-on charges, or upgrade fees just to unlock offline mode. Ask for a full breakdown of what's included in the base price versus what triggers an additional charge before you sign anything.
