How it works

Every mozo order follows the same path, whether it’s a single guest or a table of eight splitting a shared tab.

1. The table has a QR code

Each table gets its own printed QR code, generated from the restaurant’s dashboard. The code identifies the table, nothing more. There’s no check-in, no reservation to match.

2. A guest scans it

Scanning opens a short landing page in the guest’s own phone browser — no app to install. First-time guests choose whether to just browse the menu or sign up/sign in to order; a phone mozo already recognizes skips straight to the table. If a second guest at the same table scans the same code, they’re offered a request to join the table’s shared tab instead of starting a new one. See Sharing a tab.

3. The guest orders

The menu is organized into categories (starters, mains, drinks) that the restaurant controls, including which categories are even visible right now based on time of day. The guest adds items, optionally with variants (a size, a temperature, a side), and places the order.

4. The order reaches staff instantly

There’s no polling, no refresh button. The order appears on the restaurant’s dashboard the moment it’s placed, and on the same TV or tablet display used to route orders to the kitchen or bar if the restaurant has that set up. See Destinations.

5. Staff work the order

A staff member marks the order in process, then delivered, as it moves through the kitchen. The guest sees the same state changes reflected on their phone in real time, so “is my order coming?” stops being a question that needs asking.

6. The guest asks for the check, or for help

Two dedicated actions exist outside the normal order flow: requesting a waiter, and asking for the check. Both notify staff immediately and put a visible flag on that table in the dashboard until it’s cleared.

7. The tab closes

Once everything is settled, staff close the table’s tab. Payment itself still happens the way it always has, staff take it via the restaurant’s usual method. mozo tracks the order and its total; it doesn’t process payment on the guest’s behalf yet.

Two threads run through all of this: what the guest sees (For guests), and what the restaurant configures and manages (For restaurants).