Restaurant billing software in Kottivakkam.

Move diners to another table without ordering their food twice

The Corporation-hosted 2018 delimitation document names Kottivakkam Kuppam and Kottivakkam Beach Road. Our original beach-road illustration uses those coastal references symbolically; it is not a street map or a photograph. When arranging a restaurant demonstration in Kottivakkam, send the full street address, entrance and floor rather than only a beach landmark. DeccanPro visits restaurants by arrangement; this guide does not imply a local branch or an existing customer installation.

Local reference: Greater Chennai Corporation: 2018 delimitation document, PDF page 187. Use the restaurant exercises below with your own menu.

Start with one order and a clear preparation state

Use fictional order K12 at table 4: two meals at Rs.150 each and two lime sodas at Rs.50 each. The sample item subtotal is Rs.400 before configured taxes, discounts or other charges. Both sodas have been served; the two meals are still being prepared. Write those states beside the order reference in your training record. A table number tells staff where guests are sitting, but the saved order reference identifies what they ordered.

Check the destination before moving the guests

The family asks to move to table 9. The captain checks that it is available and suitable, then tells the cashier and the person serving unfinished dishes. In a demo, ask the operator to show the supported way to change a table association and the permission needed. Do not assume that a vacant-looking table on one device is free, or that a table-transfer control exists in every setup. If the workflow needs a manual coordination record, agree who maintains it and how staff find the original order.

Preserve the original food request

Reconcile K12 before and after the demonstrated move: the same two meals, the same two sodas and the same Rs.400 item subtotal. A move adds no food and takes no payment. Check what appears on the captain device, cashier view and kitchen record instead of assuming all three update together. Do not enter the four items again at table 9 to make the screen look right; that could create another kitchen request. If the software cannot preserve the intended order safely, stop the rehearsal and ask for the supported procedure.

Tell the kitchen where the unfinished meals should go

The kitchen may still have a printed KOT labelled table 4. Keep that original reference connected to an explicit table 9 destination through the restaurant’s agreed handoff. Ask the kitchen lead to acknowledge the change before the meals leave the pass. Already-served sodas remain served; a location change is not a request to pour two more. Have a colleague read the record without coaching and explain which food is unfinished, which table receives it and which order it belongs to.

Keep a later addition separate from the move

At table 9 the family orders one more lime soda. This is a new food request: one soda at Rs.50, making three sodas and two meals overall, with a sample subtotal of Rs.450. Demonstrate how the supported update reaches the relevant preparation station. The operator must distinguish the original four items from the one added drink. Any earlier payment must be checked against the saved payment record separately; neither a table move nor a changed subtotal confirms money has been received.

Reopen the old table only after reconciling the move

Before seating another party at table 4, confirm that its display and the staff handover no longer point to the moved family’s open order. The new party must have its own reference. At the end of the rehearsal, a replacement cashier should locate K12 at the agreed destination, explain the Rs.450 example and check payment without using the old table number as the only clue. Bring your floor plan, sample menu and captain-to-kitchen handoff to the Kottivakkam demo. Use this as an acceptance exercise, not a promise of automatic transfer, synchronisation or kitchen-ticket rewriting.