OrderStation
Request a demo Start free

Product

A kiosk your guests' own AI can operate

At the centre is the self-order kiosk. Guests tap it, steer it from their phone, or hand the order to their own AI assistant. Around it, every other order lands on the same kitchen screen: from the table, from the waiter, from the street. It all runs in a browser.

At the counter

Self-order kiosk

Any tablet or touch screen with a browser will do. Pair it with a code from your cockpit: no technician, no app store.

  • Live AI remote. The guest's own assistant orders for them on the big screen, described below.
  • Picture menu with categories, options, sides and sizes.
  • Promotions priced on the server. Combos, tiers, happy hour, and the line that tells a guest what they saved. The kiosk only displays the finished amounts.
  • Accessible on every plan, Free included. Reach mode for seated guests and a remote on the guest's own phone, described below.
  • Attract screen with your own video or images, branded per device.
  • Stays logged in. If the network or the server drops, the screen keeps showing the menu and retries. It goes back to setup only when you revoke its key.
The kiosk attract screen: a sesame bun in mid-air on black, the button Start your order, and a row of eleven language flags.
Attract screen with the restaurant's own video and the language row.
The kiosk menu: categories on the left, coffee and tea tiles with photos and prices, the running order numbers at the top, and the checkout bar at the bottom.
The menu in English, with the running order numbers along the top.

Live AI remote

The guest's own assistant as waiter and nutrition advisor

The guest sends a photo of the kiosk's code to ChatGPT or Claude and talks to it the way they would talk to a waiter. The assistant reads your menu and fills the cart on the big screen.

  • One sentence per order. "Two cheeseburgers, one without onions, fries and a large cola" goes into the cart in one step. The assistant sends the request to the kiosk, which applies it directly.
  • Every language and dialect. The assistant translates for the guest. For house names and local words you add aliases to a dish or an option in the cockpit, so "Gurkerl" finds the pickles.
  • A nutrition advisor that knows the guest. The assistant already knows from its own chat that the guest is vegetarian or avoids lactose. It reads the allergen notes on your menu and suggests what fits. The notes are your menu data, not a guarantee; guests with a severe allergy still ask the staff.
  • It asks when something is unclear. Three burgers and the guest said "burger"? The assistant asks. If a request is still ambiguous, the kiosk shows a proposal and the guest answers yes or no, by voice or with a tap.
  • Visible on the kiosk. Every line the assistant adds carries a robot mark, and a band at the top says what it just did. The guest can change anything by hand at any time.
  • Pays when the guest says so. The assistant reads the total from the kiosk, sums up the order and presses Pay after the guest confirms. The card still goes to the terminal. At a kiosk without a card terminal, a five-second countdown lets the guest stop the order before it goes out.
  • Hands-free for every guest. In the voice mode of their chat app, a blind guest or a guest who cannot reach the screen orders without touching it, in their own language.

What the guest needs

An AI assistant on their phone. In Claude or ChatGPT the guest adds OrderStation once as a connector with the address https://order-station.com/mcp. The guide for guests shows each step. Assistants that can use a browser open the kiosk's remote page from the same code instead. There is no account, and the code works for one guest and one order: a second phone or assistant is refused, and the connection ends when the order is done.

What the restaurant needs

The AI remote is part of every kiosk on every plan, Free included. Prices, discounts and the receipt stay on your server and your register; the assistant cannot set an amount. It sees your menu and the guest's order, and the kiosk never sees the guest's conversation.

For every guest

Order from a wheelchair, or without seeing the screen

A 32-inch kiosk in portrait is built for someone standing in front of it. From a wheelchair the upper half is out of reach, and a guest who cannot read the tiles gets nothing from the pictures. Both can order on their own, on every plan including Free.

  • Reach mode. A tap on the wheelchair icon moves every control into the lower half of the screen. Tiles and buttons keep their full size; the list scrolls instead.
  • Phone remote. Scan the QR code on the same sheet, or type the eight-digit code under it, and the guest's own phone steers the kiosk with four arrows, OK and Back. There is nothing to install and no account to create.
  • The phone speaks. A screen reader on the phone reads out what is selected on the kiosk. Guests without one tap the speaker button and hear the name through their phone.
  • Keyboard. The whole order also works with arrow keys, Enter and Escape on a connected keyboard.
  • Nothing to set up. Both options are on every kiosk from the first day, and they switch off by themselves when the order is done, so the next guest finds the kiosk as usual.
The kiosk menu at full height: a category rail on the left, three burger tiles with photos and prices across the top, one Classic Burger in the cart and the Pay by card button at the bottom.
The menu at standing height.
The same order in reach mode: the upper half of the screen shows only the slate background and the order ticker, the category rail, the burger tiles, the cart and the buttons sit in the lower half at the same size as before.
The same order in reach mode. Everything a hand has to touch sits in the lower half, and the tiles are the same size as before.

The menu moves down at full size

The quick way to bring a tall screen within reach is to scale the whole picture into the lower half. That halves every touch target, and a guest with a tremor or a weak grip then has to hit targets half the size on glass that already sits at an awkward angle. OrderStation reflows the page instead: the menu, the cart and the buttons keep their size and move into the lower half, with fewer rows visible and more scrolling. The upper half shows the restaurant's background and the order ticker, which only displays. Dialogs, the options sheet and error messages open at the bottom as well, so nothing a guest has to touch ever appears above the middle of the screen.

Why the guest's own phone

Reach mode brings the screen within reach; the screen is still a stranger's touch panel. A guest who cannot hold an arm up for a minute, who cannot aim precisely, or who cannot see the tiles still has to operate it. So the second option on the sheet hands the controls to the guest's own phone. The kiosk shows a QR code and an eight-digit code. Scanning or typing it opens a web page with five large keys, four arrows and OK, and a Back button below them. Each press moves a black-and-white focus ring on the kiosk, the same ring a keyboard user sees, and OK does what a tap would do. The guest orders from their lap and the kiosk reacts in well under a second.

The phone is already set up for its owner. The screen reader, the font size, the contrast, the language and switch control all work on the remote page without the kiosk knowing anything about them. The kiosk sends one thing back, the name of what is selected, in a live region that the screen reader reads aloud, and it accepts six keys in return. Prices, the cart and the payment stay on the kiosk, the card is still held to the terminal, and a second phone that scans the same code is refused. The same page lets a companion steer from their seat while the guest reads along on the big screen.

Animated: the kiosk and the guest's phone side by side. On the phone a key lights up with each press; on the kiosk a yellow focus ring closes the accessibility sheet, lands on Start your order, walks down the category rail to Burgers and Ribs, opens the Classic Burger, picks no mustard and presses Add to cart. The phone shows the name of whatever is selected, ending with the cart line Classic Burger 17.40.
A burger ordered from the lap. Back closes the sheet, Down and OK start the order, the arrows walk down the categories to the burgers, OK opens the options, "no mustard" goes in, then Add to cart. The ring on the kiosk follows every key, and the phone shows what is selected.

Hearing it on the guest's phone

Not every guest with low vision runs a screen reader. For them the remote has a speaker button next to the name of the selected item. A tap reads the name aloud through the phone, in the phone's language. Menu names come as recorded voice files, produced once per menu and language, so that "latte macchiato" and "Leberkäse" sound right. For everything else, buttons and options for instance, the phone uses its own voice. Inside the options sheet the button reads the whole choice as one line, "Classic Burger, no mustard", so the guest can check it before adding. The kiosk itself stays silent, so the sound is private to the guest and the room does not hear the order.

The accessibility sheet on the kiosk's start screen: two options, Controls at the bottom and Control with your phone, a QR code, an address and the eight-digit code 5553 1323, and a note that an AI assistant can be sent a photo of the code.
The sheet behind the wheelchair icon. The address and the eight digits are for guests who cannot scan.
The remote on a phone: at the top the line Selected: Classic Burger 17.40 with a round speaker button, the status Connected to the kiosk, then four arrow keys around a blue OK, a Back button, Add an item and End remote control.
The remote on the guest's phone: what is selected, the speaker button, five keys.
The same remote while the options sheet is open on the kiosk: Selected: no mustard, and underneath Selection: Classic Burger, no mustard, next to the speaker button.
Inside the options sheet the phone shows the whole choice, and the speaker button reads it as one line.

Who this is for

  • Wheelchair users and guests of short stature: reach mode, or the remote from the lap.
  • Guests with low vision: a high-contrast focus ring on the kiosk, the phone's own magnification, and the speaker button.
  • Blind guests: the phone's screen reader speaks what is selected on the kiosk.
  • Guests with a tremor or limited fine motor control: five large keys on a familiar device instead of precise aiming on glass. Switch control and assistive touch work because the remote is an ordinary web page.
  • A companion can steer from their own phone while the guest follows on the kiosk.

The legal frame

The European Accessibility Act (Directive (EU) 2019/882) applies to self-service terminals put into service since 28 June 2025, with EN 301 549 as the technical standard. Among other things it asks for operation with limited reach and limited vision, and for a way to connect a guest's own assistive technology. Reach mode and the phone remote are built for those points, and the kiosk is fully keyboard operable. The kiosk has no speech output of its own; the guest's phone speaks. The mounting height of the card terminal is decided when the kiosk is installed. This is how we read the Act; it is not legal advice.

At the table

QR ordering from the guest's phone

Put a card on each table. A guest scans it, the menu opens, and the order goes straight to the kitchen with the table number already attached. Nobody has to type one.

  • Shared ordering. One code per table, as many phones as sit at it. Seats stay anonymous (Guest A, Guest B), everyone sees the running order, and you can remove only your own lines.
  • Pay first. For counter service with the register module: guests build the order on their phone, and it is placed the moment it is paid, at the kiosk or with staff.
  • Call the waiter, keep ordering. The table stays open for another round until the bill is settled.
  • Pre-order on the way. Guests choose now, in fifteen minutes, in thirty, or a set time, and the kitchen sees when they will arrive.
  • Eleven languages. German, English, Polish, Ukrainian, Dutch, French, Flemish, Turkish, Czech, Hungarian, Arabic. Prices always in Latin digits so they match the printed menu.
  • A switch for each. In-app payment, waiter call, cash and pre-order can be turned on or off per location. Turning one off removes the button and closes the endpoint behind it.
The guest menu on a phone for a demo restaurant called Corner Bistro: category tabs, hot chocolate and tea with prices and a plus button, then the baguettes section.
The menu a guest sees after scanning the table code. Screenshot from a demo restaurant.

At the pass

Kitchen display and pickup screen

Tickets appear the moment an order is placed and sort themselves by station. The board can be read three ways, and a second screen in the dining room calls the numbers.

  • Station routing by product group: cold kitchen, grill, bar. Mark items and tickets done, undo if needed.
  • Unpaid pre-orders are greyed out with the arrival time and sort into place when the guest arrives.
  • Three ways to read the board, switched from the header while a shift runs: one ticket per order, everything grouped by item, or both at once.
  • Pickup screen with two columns, in preparation and ready, filled with order numbers.
  • Set up with a PIN from your cockpit, on any monitor that has a browser.
  • No screen in the kitchen? The cook opens the same board on a phone and taps print. Our Android app sends the ticket to an Epson on the local network, so the room needs only a printer and a network cable. For a place with ten orders a day, a copy by email does the job.
Kitchen display in ticket mode: six light tickets in two columns, two new with an accept button, two in progress with a done button, two ready and struck through, each with its number, target time, station and items.
One ticket per order. The view a line cook works from: everything that belongs to one order stays together, and the colour of the head says new, in progress or ready.
Kitchen display in prep mode: three station columns, cold kitchen, grill and bar, each listing the open items with their total quantity.
Grouped by item. Four Leberkäse rolls in one line instead of four tickets. This is the view for the fryer at seven in the evening.
Kitchen display in hybrid mode: the item list on the left, the tickets on the right, with a line drawn from the selected item to its ticket.
Both at once. Pick a line on the left and a thread shows which ticket it belongs to.
Animated pickup screen as a pixel kitchen. New order numbers appear on the ticket rail under In Zubereitung, two cooks work the line and ring the bell, each finished number flies down to the counter and turns green, and guests walk in to pick up their order while the window shows the afternoon sky.
The pickup screen, for a room full of guests. Same two lists, drawn as a kitchen. Numbers move from the pass to the counter as the food does; the cooks, the window and the clock follow the real day.
The pickup screen on a slate ground: four order numbers under the heading In Zubereitung on the left, two numbers on orange tiles under Abholbereit on the right.
The plain pickup screen. It calls order numbers, which is all the room needs to hear.

On the floor

Waiter app

A web app your team installs on their own phones. Every action is tied to the person on shift.

  • Table overview by area, coloured by order status and live within seconds.
  • Quick entry at the table: three-level menu, list or tiles, search across everything, modifiers, eat-in or take-away.
  • Waiter calls light up the table tile. Guests keep ordering until you settle.
  • Hand-over to the register. The register scans the order code, a QR code or eight digits. Split payment leaves the rest of the table open.
  • PIN login per shift, a seat-by-seat breakdown of who ordered what, and table QR codes you can hand out from the app.
The waiter app table overview: two areas, Dining room and Terrace, with table tiles coloured by status. Ready, in the kitchen, captured, paying and free, plus a joined table 7+8.
Table overview. Colour says what the table needs: green means food is ready to serve.
An open order for table 1 with six lines, modifiers such as oat milk and without onion, status marks for sent and ready, the total of 62.50 and the buttons Send and Cash up.
The full order. Sent, ready and new lines in one list, with the total and the hand-over to the register below.
The waiter app's more-actions sheet over the menu: select all, join tables, show history, show guest QR code and cancel table.
More actions. The rare, heavy steps sit behind one menu, away from the thumb that is taking the order.

Taking payment

Add a register when you need one

OrderStation takes orders. Payment is the job of a register, and in most of Europe a receipt has to come from one the tax authorities recognise. An ordering system cannot issue it on its own.

When you want to take payment, add our register as a separate module, at €49.90 per terminal and month. It is the register retail butlers already runs in retail chains, and it is fiscally compliant in Germany, Austria and Switzerland. Through the fiscal middleware it uses, it also works in Czechia, Croatia, Slovenia, Italy and France. Guests pay at the kiosk, at the table or with a waiter, the order is booked on the register, and the receipt comes back to them.

Already running a register you like? Keep it. Enterprise connects the waiter app's order code to your own system and your own fiscal provider.

Ask us about the register

Try it with your own menu

Free for two locations and twenty items. Request your account, or see it live on a call first.

Start free Request a demo

Free for up to 2 locations and 20 menu items. No card, no time limit. We set it up with you.