The only person here who never signs in: the guest scans, reads, orders and waits — all in a browser they already have.
A QR code on the table or the counter opens the menu. No app, no install, no account.
The menu is published in the languages you choose, with AI translation for the ones you have not written yourself.
Where you enable it, the guest orders from the same page they are already reading.
The order-ready board shows what is being made and what is ready to collect.
A guest holds no account and no permissions. What they can reach is exactly what you publish — nothing else in the system is exposed by the page they are looking at.
Roles are yours to define: these are the defaults a new organization starts with, and every line above is a permission you can grant or revoke.
The barrier that stops most guests ever using a venue's app simply does not exist — it is a web page behind a QR code.
It is generated from the catalog, so an item you marked unavailable at the till is unavailable there too.
The board answers the question the counter keeps being asked, which gives the counter back to serving.
The parts of the system this role spends its day in.
No. The QR code opens a web page in whatever browser the phone already has.
You choose the languages the menu is published in. Anything you have not translated yourself can be machine-translated, and you can edit the result before it goes out.
Where you enable it, yes — the order arrives in the same system as one typed at the till, and reaches the kitchen the same way.
No. The kitchen screen is for staff and shows everything; the board faces the guest and shows only numbers and their state.
The same system, seen from a different job.
Create an organization, invite the team and set what each of them reaches. No credit card required.
Start free →