A Self-Ordering Kiosk That Runs On Your Live Menu, Not a Copy of It
Guests pick a branch and an order type, browse the same categories your till shows, build the item with the same variations and modifiers, pay through the same gateway, and walk away with an order number. The kitchen gets a KOT ticket like any other order. Nothing is maintained twice.
Start Free Trial See which concepts it suits1
Menu to maintain — counter, kiosk, QR and online all read the same items
0
Retyping at the till — the guest’s own choices become the order record
+1 lane
Every kiosk is another ordering point at peak, with nobody rostered onto it
RTL
Arabic on-screen keyboard built in for right-to-left guest input
The kiosk is not a second menu. It is the same one.
Most kiosk products quietly hand you a second catalogue to keep: kiosk items, kiosk prices, kiosk photos, and somebody whose job is remembering all of it the morning a supplier raises a price or the fryer goes down. RestioX does not work that way. The kiosk reads the same menu items, categories, variations, modifier groups, tax rules and coupon logic the POS reads. Change a burger price once in Menu Management and the counter, the kiosk, the QR menu and the online store change with it.
Because it is one engine, a kiosk order is not a special case downstream either. It takes an order number, it respects the order types you have configured, it lands in the same order pipeline your managers already watch, and it prints to the kitchen as a KOT ticket alongside everything else. Your expo routine does not change at all.
- Live menu by category — anything hidden or off the menu in the admin never reaches the kiosk
- Variations and modifier groups applied exactly as the POS applies them, with the same price deltas
- Your configured tax rules and coupon codes, calculated by the same logic as the till
- Order types follow the restaurant’s own setup, so the kiosk offers only what you actually run
- Restaurant and branch selection at the top of the flow — one build serves a whole estate
- Arabic on-screen keyboard for right-to-left names and notes
A guest-driven ordering flow, start to finish
No staff assistance, no half-features that push the guest back to the counter. Every step below is part of the shipped kiosk flow.
-
Browse by category, the way the counter does
Categories along the top, items in a touch grid with prices. The kiosk shows the live menu for the branch the guest is standing in — nothing stale, nothing that ran out at eleven.
-
Modifiers are where the upsell actually happens
Every variation and modifier group your kitchen already supports is on screen: size, protein, spice level, extras, sides. A guest reading options at their own pace, with no queue breathing down the counter staff, adds the bacon and sizes up the fries far more often than one answering a rushed question. That is the whole upsell argument for kiosks, and it costs nothing to configure because the modifier groups already exist.
-
A cart they can fix themselves
Items, quantities, modifier lines and the running total stay visible. Guests correct their own mistakes before the order exists — the cheapest possible moment to catch one.
-
Branch and order type up front
The flow opens with restaurant and branch selection, then the order types you have switched on. Multi-outlet groups deploy the same kiosk everywhere.
-
Pay with the gateways you already use
Checkout hands off to the payment methods configured for the restaurant, in-person card terminals included. There is no separate kiosk merchant account to open.
-
Confirmation screen with the number they wait on
The flow closes on a confirmation screen showing what was ordered and the number to listen for. From that second it is an ordinary order in your pipeline, visible to managers and counted in your reports.
-
Arabic keyboard for RTL input
A guest typing a name or a note in Arabic gets an on-screen keyboard laid out for right-to-left entry instead of fighting a Latin one.
Works with the rest of the platform
Five touches from the door to the pickup counter
This is the whole flow. There is no step where a guest has to go and find a member of staff to finish what they started.
-
1
Arrive
The kiosk asks two questions before it shows any food
Which branch, and which order type. On a single-site restaurant the branch step is a formality; on a twelve-site group it is what scopes the whole order — the menu, the prices and the kitchen it will print to.
-
2
Browse
Categories load from the live menu for that branch
The same categories and items your staff see on the POS, in a layout sized for a standing guest and a single finger. Availability is read live, so nobody is offered something the kitchen stopped making at lunch.
-
3
Build
They work through the variations and modifiers themselves
Size, add-ons, no onions, extra sauce. The price moves as they choose, and the cart totals with your tax rules applied — so the number on screen is the number they pay, not an estimate that changes at the till.
-
4
Pay
Checkout uses the payment methods you already configured
Gateways and card terminals set up for the restaurant, plus your coupon rules validated by the same logic the POS uses. A code that works at the counter works at the kiosk, and it discounts by the same amount.
-
5
Collect
The order number goes up; the KOT is already printing
The confirmation screen hands the guest a number and releases the kiosk for the next person. In the kitchen, the ticket has arrived in the ordinary queue. The guest is now waiting on food rather than waiting on a cashier.
The second screen at a staffed till
Not every counter should become a kiosk. Where a cashier is still ringing the order, RestioX can drive a customer-facing display: a second screen turned toward the guest that shows each line as it is added, the modifiers chosen, the discount applied and the total to pay.
It is the kiosk idea pointed the other way. The guest sees the order while it can still be corrected, instead of discovering the wrong size on a printed receipt. Arguments at the counter get a lot shorter when nobody has to remember what was said.
- Driven straight from the POS — there is no separate app for a cashier to launch
- Lines, modifiers, discounts and the running total appear as they are rung in
- Can show a payment QR on the same screen at the moment of payment
- Runs on an inexpensive second monitor mounted at the till
QR-code ordering is the kiosk flow on the guest’s own device. They scan the code on the table, browse the same live menu, choose the same modifiers, and the order lands in the same pipeline with the same kitchen ticket. Plenty of restaurants run kiosks at the door and QR codes on the tables.
See QR and online orderingKiosk, phone or counter — one engine behind all three
The interesting part of this table is how many rows are identical. That is what it means for the kiosk to be part of the platform rather than bolted onto the side of it.
| What happens | Self-ordering kiosk | QR on the guest’s phone | POS counter |
|---|---|---|---|
| Who taps the screen | The guest, at a terminal in your room | The guest, on their own device | Your cashier or server |
| Hardware you provide | A touchscreen and a stand | A printed code on the table | A till, and a person on it |
| Menu, prices and availability | Live menu for that branch | Live menu for that branch | Live menu for that branch |
| Variations and modifiers | Chosen by the guest, unhurried | Chosen by the guest, unhurried | Read out and keyed in by staff |
| Tax rules and coupon codes | Your configured rules | Your configured rules | Your configured rules |
| Payment | Configured gateways and card terminals | Configured gateways | Gateways, terminals and cash |
| What the kitchen receives | A KOT ticket in the usual queue | A KOT ticket in the usual queue | A KOT ticket in the usual queue |
Already running RestioX at the counter?
Then there is almost nothing left to configure. Your menu, modifier groups, tax rules and payment methods are already in place — the kiosk simply reads them.
Concepts that get the most out of a kiosk
Quick service
Between twelve and two the bottleneck is the counter, not the fryer. Two kiosks inside the door take the front half of the queue off the till, so your cashier can concentrate on payment and handoff instead of reciting the menu.
Fast casual
Build-your-own bowls, burritos and burgers are a modifier tree. A guest reading that tree at their own pace picks more from it than one answering questions with six people behind them — and the tree is already configured for your POS.
Food halls and multi-site groups
Branch selection is part of the flow, so one kiosk build works across an estate and every order is scoped to the branch it was placed in — its menu, its prices and its kitchen.
Before you put one in the doorway
No. It reads the same menu items, categories, variations and modifier groups as your POS, scoped to the branch the guest selected. You maintain one catalogue in Menu Management and every ordering surface follows it.
As a KOT ticket, exactly like a POS order. It enters the same order pipeline and prints to the same kitchen printer or kitchen display, so your expo routine, your ticket layout and your prep flow all stay as they are.
The ones already configured for your restaurant. Checkout hands off to your configured payment gateways and in-person card terminals rather than requiring a separate kiosk merchant account or a second settlement report.
Yes. An Arabic on-screen keyboard is built into the kiosk for right-to-left input wherever a guest needs to type, such as a name for the order or a note for the kitchen.
Yes, because it is the same calculation. The kiosk applies your configured tax rules and coupon logic, so a code that is valid at the POS is valid at the kiosk and the totals reconcile without anyone adjusting anything.
Run QR-code ordering instead. It is the same guest-driven flow on the guest’s own phone, feeding the same order pipeline and printing the same kitchen ticket. Many restaurants use kiosks at the entrance and QR codes on the tables.
Put a second ordering lane in the doorway
The kiosk ships with RestioX and reads the menu you already maintain. Choose your order types, point it at a branch, and the queue starts serving itself.
Start Free Trial