Everything the floor needs and nothing it does not: the menu, the check, the floor plan and payment, on one screen.
Pick the table or takeaway, then the dishes — with the venue's own photos rather than a list of codes.
Variants, modifiers and a note per line, so the kitchen gets the order as the guest actually said it.
Cash, card or split; several payments on one check, and a receipt printed or skipped.
Table statuses and today's reservations on the floor plan, so you know what is free before walking over.
This is the role most people in a venue hold, so it is the one worth getting right. It carries everything the floor needs, and nothing that would let a bad day cost the business quietly.
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 register is the only part of the system a waiter needs, and it is the part that takes minutes to learn — photos, not product codes.
A required modifier group will not let an order through without the choice the kitchen needs, so the ticket arrives complete.
Every void and discount is recorded against the person who made it, which is usually enough that they stop happening.
The parts of the system this role spends its day in.
Yes, once you allow that device. The app runs on Android, on iOS and in a browser; device approval is the owner's decision, so a personal phone works only after it is trusted.
The order stays on the device as a draft rather than being lost, and goes up when the connection returns.
Yes. A table can carry several checks, and each check records who opened it.
Yes, and that is the point — a shared login makes every report and every void anonymous. Each person signs in with their own PIN on the same till.
Create an organization, invite the team and set what each of them reaches. No credit card required.
Start free →