Overview
DishInk uses table sessions as the container for every dine-in bill. A session opens when a waiter (or the POS) seats a party, collects orders as they’re taken, and closes when the bill is paid. Every session is scoped to:- One table (or a merged group of tables — see Merging Tables)
- One terminal (the till that opened it — see Terminal Setup)
- One primary waiter, plus any others who added items later (see Assigned Tables)
Session Statuses
Every session moves through a fixed lifecycle. Filter chips at the top of the Active Tables list show live counts per status.The Charge button unlocks when every item is
ready/served or the session is in billing / served / pending_payment. This prevents charging for food that might still be voided in the kitchen. See Creating Sales.Opening a Table
Tables are opened by the waiter on the Waiter App. See Opening Tables. For quick counter service that still needs a running tab (e.g. a bar tab), the POS can open a temporary session directly — pick New Session in the Active Tables list.The Terminal Lock
Every session is locked to the terminal that opened it. This is enforced atomically in the database so two cashiers on two terminals can never charge the same bill. If a cashier on Terminal B tries to charge a session opened on Terminal A, DishInk shows the Transfer prompt. A manager confirms, the session unlocks from A, and instantly locks to B. See Terminal Setup — Terminal Transfer. Managers with the All Terminals permission bypass this lock and see every session live.Waiter Restrictions
Waiters see only tables they’ve been assigned to for this shift unless they have the View All Tables permission (usually reserved for supervisors and hosts). Managers can override this per user via Settings → Roles & Permissions — see Roles & Permissions.Adding Items After Payment (Reopening)
You can’t add items to a paid session. If a customer wants “one more coffee” after paying, either:- Open a new session for the same table (fastest, keeps the accounting clean), or
- Void the existing sale and re-run the full bill (only if within the same day — see Voids).
Merged Tables
When two tables are merged, the session shows asT2 (+ T1, T3) in the bill list — the primary table first, then linked tables in parentheses. Every item taken on any of the linked tables is billed to the primary session. See Merging Tables.
Multiple Waiters on One Session
If a second waiter adds items to a table an existing waiter opened, DishInk credits both correctly:- Item revenue is split proportionally by who punched what (see the Shared notes in Batch Invoice Cash Out).
- Transaction count stays with whoever contributed the biggest share of the bill.
Step by Step
1
Waiter opens the table
On the Waiter App, tap the empty table → Open. See Opening Tables.
2
Take orders
Add items, modifiers, and notes. Tap Send to Kitchen — the KDS lights up instantly and the session flips to Ordering.
3
Serve
Kitchen marks items Ready. Waiter delivers and marks Served on the Waiter App.
4
Bill request
Customer asks for the bill. Waiter taps Request Bill → the POS shows a Bill Request toast, session flips to Billing.
5
Charge
Cashier picks the session on the POS and charges. See Creating Sales.
6
Close
Payment confirms, ZRA Smart Invoice submits, receipt prints, session closes. Waiter can now clear the table on the Waiter App. See Closing Tables.
A table session moving from Ordering → Served → Billing → Paid.
Tips & Best Practices
- Encourage waiters to mark items Served — that flag is what triggers the Served filter and lets managers see who’s ready to pay.
- Use the Billing filter at the cashier till during peak hours; leave the till on All off-peak.
- If a customer walks out without paying, use Close Without Payment (manager PIN required) — the write-off shows on the Batch Invoice under Manager Overrides.
- Merge tables before taking orders when possible. Merging after items are taken works, but the merged-in table’s items keep their original waiter attribution.
Common Mistakes
- Opening a new session for a party that already has one. Always check the Active Tables list first. Duplicate sessions on the same table cause split kitchen tickets and confusing bills.
- Trying to charge from the wrong terminal. You’ll be prompted to transfer — this needs a manager and slows you down. Set clear terminal ownership per station.
- Charging with items still cooking. The Charge button is locked. Wait for the kitchen or mark as Awaiting Payment.
- Deleting a merged-in table before the merge is undone. Unmerge first, then delete. See Unmerging Tables.