Restaurant billing software in Nandanam.

Confirm a group-lunch revision before it becomes kitchen work

Chennai Metro Rail lists Chamiers Road and the YMCA College of Physical Education among the approaches associated with Nandanam station. They help describe the neighbourhood, but are not a restaurant address or evidence of a customer relationship. Our original illustration uses a symbolic metro entrance and tree-lined street. Share your restaurant’s actual entrance and collection point when arranging a visit; check current access directly rather than relying on an old station-gate instruction. DeccanPro visits customer locations by arrangement from its Chennai team.

Local reference: Chennai Metro Rail: Nandanam station and nearby approaches. Use the restaurant exercises below with your own menu.

Keep an enquiry separate from a confirmed order

Start with a fictional request for lunch for 18 people. The guest has not yet agreed the menu or collection time, so record it as an enquiry using your existing business process. Do not send a live kitchen instruction merely to calculate a price. Ask the demonstrator where an estimate can be prepared in your installation; if that workflow is not available, use a clearly labelled worksheet. This guide does not claim a quotation, catering or scheduled-order module.

Read back the final mix, not only the headcount

The guest confirms 12 standard meals at a sample Rs.120 each and four special meals at Rs.160 each: 16 meals, not the original estimate of 18. The illustrative item subtotal is Rs.2,080: Rs.1,440 plus Rs.640. Taxes, delivery, packaging and other agreed adjustments are outside this arithmetic. Record the confirmed mix, agreed handover time and responsible staff member, then create the order through the supported procedure. Retain its saved reference so the kitchen and cashier discuss the same record.

Resolve a reduction after preparation starts

Now ask to reduce the standard meals from 12 to 10. Before editing, have the kitchen report how many have already been prepared and have the responsible person apply the restaurant’s agreed cancellation policy. If the reduction is accepted with no cancellation charge in this training example, the revised order is ten standard and four special meals: 14 meals with a Rs.1,840 item subtotal. The Rs.240 difference must be explained. A changed screen total does not undo food already prepared or itself refund a payment.

Make the revision visible at each handoff

Have the cook identify the current instruction for ten standard and four special meals, using the demonstrated ticket or screen update. Clearly supersede the earlier twelve-standard instruction through the restaurant’s agreed process. Give the packer the current order reference and check two labelled groups containing ten and four meals. If prepared portions remain after an accepted reduction, record their actual disposition through your normal kitchen and stock procedures; do not hide the difference by changing the original preparation count.

Separate final payment from final quantities

Find the same saved order at the counter and read back 14 meals before checking the revised bill. If the guest has already paid the earlier amount, demonstrate the authorised payment-adjustment procedure separately and retain its evidence. Do not assume that deleting two meals moves money back to the guest. Confirm collection only after the current contents, payment status and collector’s agreed reference have been checked. No automatic refund or collector-authentication capability is implied.

Bring the right people to the Nandanam demonstration

Bring an anonymised group-order example and include the person who accepts enquiries, the kitchen lead and the cashier. Agree who can confirm an order and who can approve a change after preparation. Share your street, entrance and proposed meeting time with our Chennai team. The purpose is to test your actual service decisions before a busy lunch, not to assume every Nandanam restaurant serves office groups.