Table service
Floor-first ordering with seats, courses, and the kitchen in sync.
The service flow
Table Service (Lite+) turns the register into a dining-room workflow: the register opens on your floor map, orders belong to tables, and food goes to the kitchen in courses.
- 1Tap an open table on the floor.
- 2The start sheet asks for the guest count and any table allergies (they stay pinned in red at the top of the ticket).
- 3Ring drinks and food from your menus.
- 4Send — the kitchen gets the items and you're back on the floor for the next table. Or Send & Stay to keep ringing on this ticket.
- 5When the guests are done, tap the table → Pay.
Courses: Send vs Fire
Items ring into the current course; New Course starts the next round. Courses never have gaps — remove the last item of a middle course and everything renumbers.
Send = the kitchen starts cooking those items now.
Fire = tell the kitchen the guests are wrapping up, start the NEXT course. On a KDS the table's ticket blinks red; on printers a separate fire slip prints (name the course, or list its items — your setting).
Tap a course header on the ticket for the Send / Fire modal for just that course.
The ticket never disappears
A table's ticket is only ever cleared by paying or voiding. Sent items are marked with a * and stay visible.
Removing an already-sent item warns you to tell the kitchen (automatic kitchen VOID tickets are a Pro feature).
All Orders shows the three states of every order: Open (still ordering), Paid — needs tip (card ran, tip pending), and Closed.
Guest checks & paying
- 1Print Check hands the guests an itemized pre-check (with dual pricing it shows both card and cash totals).
- 2Pay opens the payment view inside the register — cash, card, gift, or split.
- 3Paying frees the table on the floor. Walk-ins and To-Go orders work without a table.
