Restaurant billing software in Rajakilpakkam.

Reuse a table without carrying the previous party’s order forward

Chennai Om Sri Skandasramam lists its address on Kambar Street in Rajakilpakkam, and the municipal places-of-interest page identifies the temple as a local landmark. Our original temple-street illustration is a simplified neighbourhood reference, not a photograph or an architectural drawing. For a restaurant visit, share your own street, entrance and map pin; the temple is not a DeccanPro office or meeting point. We visit restaurants by arrangement from our Chennai office.

Local reference: Chennai Om Sri Skandasramam: official address; Municipal places of interest: Rajakilpakkam temple. Use the restaurant exercises below with your own menu.

Give the first party an identifiable practice order

Choose one table in a supervised training setup. Call the first party A on your worksheet and enter two meals at a fictional Rs.120 each. Record the software’s actual order or bill reference alongside the table number. A table label tells staff where to serve; the saved reference helps distinguish separate visits to that table. Keep this rehearsal apart from live transactions using the procedure agreed with the demonstrator.

Resolve food still in progress before settling the bill

Add one coffee at a fictional Rs.30, then ask the kitchen representative to identify whether it is still pending, ready or already served. Agree what happens before party A leaves: serve it, or rehearse the supported cancellation process with kitchen acknowledgement. A settled bill alone does not tell the cook whether to prepare a dish. Do not ask staff to infer food readiness solely from a ticket disappearing from a display.

Record the first bill before freeing the table

If the coffee is served, the example item subtotal is Rs.270: two meals at Rs.120 plus one coffee at Rs.30. If it is cancelled through the agreed process, the example subtotal is Rs.240. Review taxes and any other configured adjustments separately. Have the cashier demonstrate the actual settlement and table-release steps, then locate the saved bill. Record what the screen shows at each step instead of assuming a particular reset button or automatic release behaviour.

Start party B and inspect every carried-forward field

Seat a second practice party at the same table and enter one dosa at a fictional Rs.80. Before kitchen transmission, inspect the order reference, dish list, quantities and any notes. Party A’s meals and coffee must not become B’s instruction. The expected item subtotal for B is Rs.80 before separately configured adjustments. Check the printed KOT or display used by your restaurant and ask the cook to identify which party each active instruction belongs to.

Test a late query without modifying the new party’s order

While B remains open, ask a different cashier to find A’s saved bill and explain whether its coffee was served or cancelled using the available records and staff handoff. Return to B and verify that its one dosa is unchanged. If your procedure requires a bill copy or a correction after settlement, demonstrate the supported process separately; this exercise does not promise unrestricted reopening or an automatic kitchen status history. Record any ambiguity on the demo scorecard and retest it before launch.