A QR scan, an added dish and a final statement are three different events. Mixing them up creates duplicate records and confusing customer communications.
Track the visit, not individual scans
A single table visit may contain multiple guests, phones and orders. That visit—not a device—should be the unit staff eventually close. Running totals can help the restaurant during service, but they are not automatically final receipts.
Illustrative sequence only; public operational ordering is not active.
Close only with an authorized staff action
Decide who can close a table, whether unresolved requests block closure and how corrections are recorded. A single final emailed bill, when enabled and approved, should correspond to that one completed visit. Do not send final bills for every intermediate request.
Keep meal payment with the restaurant
A table statement is not an online payment gateway. KyaLoge never processes guest meal payments; restaurant staff collect payment directly through their established method. Any taxes and formal invoice requirements need a qualified local review.
Here's what this looks like in practice.
Illustrative situation, not a claim about a real KyaLoge customer.
Four friends share a table. Two scan the code, order different dishes and add a dessert late in the meal. If the software treats a phone as the billing unit, staff can accidentally create separate 'final' statements for a single table visit.
A better way to handle it
Model the visit as one staff-owned record. It can accumulate multiple accepted requests, corrections and running totals. Only an authorized closure produces a final statement. The restaurant still collects meal payment using its own system.
Create two browser sessions for one test table, submit different items and close the visit once. Verify that intermediate activity cannot generate extra final bills.
Confusing an emailed statement with completed UPI, cash or card settlement.
What to check before making a decision
- 01Submit two requests from the same table.
- 02Confirm only one final statement is produced on closure.
- 03Test an unaccepted late request.
- 04Verify payment is collected entirely outside KyaLoge.
Keep the useful part.
The final bill flow must be tested end-to-end on an approved restaurant account before any public operational launch.
Editorial note. This guide was prepared for restaurant operators using illustrative examples, not customer research or independent professional advice. Verify any legal, tax, dietary or platform-specific requirement with the relevant authority.