Scan and order at the table
The first guest hosts the session, others share the cart, and the host submits the table order.
TALLY / HOSPITALITY
From table QR to the kitchen.
A guest scans the code, opens the menu, and orders from a phone with no install and no personal data. The order reaches the cashier, splits across kitchen stations, and returns to the waiter ready for the table.
No guest install or accountA QR opens the table web app
Cashier · Kitchen · Waiter · OwnerEach station gets its work
Many restaurants, one platformEach restaurant's data is isolated
One order, even across four screens.
The guest sees the menu. The cashier confirms. Each kitchen sees its items. The waiter knows what is ready.
Human confirmation before kitchen
A restaurant can require cashier confirmation so no ticket reaches the kitchen without review.
Split by preparation station
Each item reaches its responsible station instead of every ticket piling onto one screen.
Ready returns to the waiter
The waiter sees assigned tables and ready items, while the owner sees service activity and results.
From appetite to table, without a lost ticket.
No state changes until a person confirms it.
01
Scan
QR opens the table session.
02
Confirm
Cashier reviews and sends.
03
Prepare
Stations prepare their items.
04
Serve
Waiter delivers to the table.
The web and backend work. The real restaurant is the test.
The guest app is live and the ordering backend exists, but real menu data, staff accounts, hardware, table codes, and an actual service run remain launch preparation. A restaurant system cannot become ready from a laptop alone.