Self-order kiosk · Selling
A register with nobody behind it — and every difference follows from that.
A customer-facing screen that takes the order and the card. Card only, no discounts, and no age-restricted items, enforced underneath the screen rather than by it.
What you get
Card only, because there is no drawer and nobody to count one.
No discounts, because discretion belongs to people.
Age-restricted items are refused by the database, not merely hidden by the interface — a bug in the screen still cannot sell beer.
An order says it came from a kiosk because the server checked that the paired terminal really is one, never because the browser claimed it.
Pairs with the kitchen screen, so what a customer typed reaches the station that makes it.
How it runs
A lunch rush, start to finish.
- 1
A customer works through the menu and its choices on the screen.
- 2
Anything age-restricted sends them to the counter instead of pretending.
- 3
They pay by card at the kiosk.
- 4
The ticket prints to the kitchen with the choices on it, and the order is an ordinary sale in the day's books.
The questions people ask
- What stops a kiosk selling alcohol?
- A database trigger, and then separately the fact that this screen never offers it. The order matters: the screen is a convenience, the trigger is the guarantee.
- Does it need its own hardware?
- A screen and a card reader. It runs the same way the register does, as a paired terminal on your own account.
Start with Self-order kiosk switched on.
Every module is part of the same trial — turn on what you need, leave the rest off, and your data exports on any day of it.