Tables and QR ordering

#Layouts and tables

Tables → Layouts. Build a floor plan per branch: name the areas, drop tables in, set shapes and seat counts, and colour-code areas so the plan reads at a glance.

Each table gets a QR code. Tables → QR codes prints them.

#Table sessions

Scanning a table's QR opens a session — the tab for that table. A session:

• Groups several orders from several guests
• Tracks who is at the table and which guest ordered what
• Stays open until it is settled

#Guests

The first person to scan becomes the table host. Others scan and join. Guests can be pending, active, or removed, and the host can approve or eject them.

Everyone orders from their own phone into one shared tab, which removes the usual argument at the end of the meal.

#Settlement

Two modes, set per branch:

Pay now — each guest pays for their own orders as they place them. The table is settled continuously.

At counter — orders accumulate unpaid and the table settles once at the end. Set an unpaid ceiling to cap how much a table can run up before it must pay.

#Idle sessions

A session with no activity for the configured number of minutes is closed automatically, so a table nobody settled does not stay open all night.

#Tips

Enable tipping per branch and pick the basis — a percentage of the subtotal, of the subtotal after discount, or fixed amounts. Tips can be attributed to the staff member who served the table, which is what feeds the tip report in Analytics → Tips.