Self-Service Kiosk

Kiosk mode turns a tablet or touchscreen terminal into a full-featured self-service point: the guest chooses dishes themselves, builds the order, and pays — without staff assistance. The order is automatically sent to the kitchen and appears in the general order feed, just like a regular order placed via QR menu.

The interface runs in a browser on any tablet: Android, iPad, or Windows terminal. It is configured in the App Store — via the "Self-Service Kiosk" card in the integrations block of the selected location. The extension is included in Premium and higher plans.

Next to the "Configure" button on the card, there is "Open Kiosk" — this is a standard link to the storefront with the ?kiosk=1 parameter. The mode is remembered in the device's browser itself, so a tablet "stuck in kiosk mode" can be restored by opening the URL with ?kiosk=0.

Guest Order Flow#

The kiosk guides the guest through a fixed route:

1. Attract screen — displayed in idle mode. The guest taps the screen to start.
2. Order type selection — "Dine-in" (at the table) or "To go" (pickup). Available types are configured in the settings — you can keep only one so that the step is skipped automatically.
3. Menu — a full touch-optimized interactive catalog: large category tiles, photos of dishes, options (size, doneness, etc.), and add-ons. The guest adds items to the cart directly from the screen; a counter and order total are always visible at the bottom.
4. Cart — a list of selected dishes with the ability to change the quantity or remove a menu item.
5. Payment — the guest selects a payment method and confirms the order (more details below).
6. Order number — after confirmation, the screen displays the number. The guest says it at the counter or waits to be called. After a few seconds, the kiosk returns to the splash screen on its own, ready for the next guest.

You can go back between any steps — the order is not created until it is confirmed.

Payment#

On the payment screen, the kiosk displays the following buttons:

Online buttons are pulled from the location's Payments settings: only the providers that are enabled and support the venue's country and currency are displayed. There is no separate toggle for online payment in the kiosk settings.

Card on a terminal next to the kiosk. If a bank terminal is connected to the same computer via the hardware bridge, a third button appears on the kiosk — payment by card right on the spot, without redirecting to a provider's page. The terminal is linked to the kiosk in the "QR Codes" section → "Devices" tab (the panel must be opened directly on the kiosk computer itself — it only detects its own local terminals). After a successful payment, the kiosk marks the order as paid and, if enabled, prints a receipt and fiscalizes the sale.

Card decline — the guest can retry the attempt or proceed to pay at the POS: the order remains the same, preventing duplicates. If the connection drops during the charge, the kiosk checks with the terminal; when the outcome cannot be verified, the retry button is not displayed — the guest is invited to the POS to prevent double charging.

If online payment is not configured, the "Pay at POS" button is always displayed — even when the toggle is turned off, ensuring the kiosk is never left without a payment method. Providers can be connected in the Payments section.

Card payment on the kiosk terminal#

If a bank terminal is connected to the kiosk computer via the hardware bridge, the guest pays on the spot, without navigating to a provider's page or approaching a cashier: the kiosk displays a "Pay by card on terminal" button, sends the amount to the terminal, and guides the guest step by step — "insert card", "processing payment", "paid". Once approved, the order is immediately marked as paid (including the terminal transaction details), and the receipt is printed and fiscalized via the bridge if printing and POS integration are configured.

What happens in non-standard situations:

Linking the kiosk to the terminal is done once directly on the kiosk computer: "QR Codes" section → "Devices" tab → device code and selection of the bridge terminal. The bridge only listens to the local computer, so the setup must be accessed right from it. Do not confuse this with the separate "Devices" section in the admin panel — that section manages staff devices, not the kiosk.

On the same screen, if the corresponding options are enabled, the guest enters their name and selects tips; the venue's service charge is automatically added to the total.

Idle Auto-Reset#

If a guest does not interact with the screen for a specified time (configured in seconds), the kiosk:

• displays a warning with a countdown (15 seconds; the "Continue" button brings the guest back to their order);
• clears the incomplete order;
• returns to the screensaver.

This protects against "abandoned" carts at busy locations. Completed and paid orders are not affected by the reset.

Interface Protection#

In kiosk mode, a guest cannot:

• switch to the standard menu or QR interface;
• open settings or other sections of the app;
• exit the mode accidentally.

To exit the mode — for example, to reload settings — there is a hidden gesture: 5 consecutive taps in the top right corner. If a PIN is set in the settings, the kiosk will prompt for it; if no PIN is set, it will exit immediately.

⚠️ The PIN only protects the gesture. The Ctrl + Shift + K key combination exits the mode immediately without asking for a PIN — which is why it is best not to connect a keyboard to the kiosk at all.

The mode is saved on the device: the tablet remains a kiosk after a reboot or page refresh until explicitly exited from the mode.

Kiosk setup in the admin panel#

1. Open Admin Panel → App Store.
2. Go to the integrations list by location and select the location you need.
3. Find the "Self-Service Kiosk" card and click "Configure".
4. In the wizard that opens, set the parameters:
   • Enabled — activation toggle.
   • Order types — "Dine-in", "Takeaway" or both (at least one is required).
   • Payment at POS — whether to show a payment-to-staff button.
   • Idle timeout — from 15 to 600 seconds, 60 by default.
   • Ask for guest name — optional, displayed in the order.
   • Tips — whether to show a tip prompt on the payment screen.
   • Exit PIN.
5. Save the settings. Next to it is an "Open Kiosk" button — it opens your location's menu in kiosk mode. Open it on the tablet (or copy the address into its browser) — the device will remember the mode.

The welcome text on the splash screen is taken from the location's Appearance settings ("Welcome text" field).

Hardware and Browser#

The kiosk works in any modern browser. Recommendations for stationary use:

• Android tablet or iPad: lock the browser in kiosk mode (Guided Access on iOS, pinned apps or owner mode on Android).
• Windows terminal: Edge or Chrome kiosk mode (--kiosk flag) so that the user cannot close the tab.
• Screen size from 10 inches — a smaller screen will result in an inconvenient interface.
• Set portrait or landscape orientation and lock it in the tablet settings.

An internet connection is required: the order is created in real time.

What you need to get started#

• A tablet or touch terminal with a browser — Android, iPad or Windows.
• The kiosk switched on in the App Store — the "Open kiosk" button is there too.
• A menu with photos and prices — the kiosk shows the same storefront as the QR menu.
• A payment method: online payment on the storefront, or payment at the POS by order number.
• The bridge — if the guest pays by card on a bank terminal connected to the same computer.
• A queue display — if the guest needs to see the number of a ready order.

Limitations#

• Terminal payment through the bridge has not been run on real hardware. It is written and will only reach POS computers with a new bridge release — plan for payment at the POS as the primary scenario.
• Online payment is not available everywhere. There are few live payment integrations, and on the Russian brand there is currently no online payment at all (Payments).
• The queue display shows one pickup point. Several windows and spoken announcement of the number are in the backlog.
• The kiosk is a cloud surface: it does not work without the internet, and guest-facing screens keep their own queue for only an hour.

Troubleshooting#

The kiosk drops out of kiosk mode. The mode is remembered by a URL parameter — pin the tab in the tablet operating system's own kiosk mode and disable gestures.

Payment does not go through. Check which method is selected: if it is card-on-terminal, that scenario has not been verified on live hardware yet; if it is online payment, check whether a provider is connected for your country.

The order is not printed in the kitchen. Printing goes through the bridge on the POS computer, not through the kiosk tablet.

The screen does not reset after a guest. Check the idle auto-reset setting.

A guest cannot see a dish. Same as on the storefront — check the 86 list and the availability schedule.

Related Sections#

• Orders — how kiosk orders are displayed in the feed and change statuses
• Kitchen (KDS) — the kitchen screen where kiosk orders are received
• POS (POS) — staff workstation for employee orders
• Payments — connecting online providers for payments at the kiosk
• QR Menu — alternative scenario: a guest orders from their smartphone

Frequently Asked Questions#

Is a separate app or special software required?#

No. The kiosk runs in a standard browser on any tablet or touchscreen monitor. No additional installations are required.

How does the kiosk differ from a QR menu?#

With a QR menu, the guest scans the code with their phone and orders through it. A kiosk is a stationary tablet of the venue: guests approach it and order right there. Both options can be used simultaneously.

How do kiosk orders look to the staff?#

They appear in the "Orders" section and on the kitchen display screen (KDS) in exactly the same way as orders via QR menu or POS — with the "Dine-in" or "To go" type and the guest's name, if it was asked for. The "kiosk" source is recorded in the order data, but there is currently no separate badge on the order card: to the staff, it's just a regular guest order.

Can the menu be restricted for the kiosk?#

Currently, there is no separate "kiosk version" of the menu — the full catalog of active dishes of the location is displayed. Dishes hidden in the menu settings are not shown to the guest.

What happens if the tablet loses internet connection in the middle of an order?#

The kiosk requires an internet connection to create an order. If the connection is lost before confirmation, the order is not saved. Once the connection is restored, the guest can start over.