How to Manage Orders in a Small Dhaba

Thalis grow in waves—dal first, then sabzi, then another basket of roti—while a traveller at the hatch wants three parcels for the car. That floor needs one open ticket per table for every add, separate parcel tickets for the highway window, and payment marked when they stand up, not when the first plate left the kitchen.

Another roti on the same table

Dhaba service fails when each roti round becomes a new slip. The table ticket should stay open so the next basket appends to the same order the family already has. Staff reopen that table on the phone, tap the lines, and keep the running total honest. Whether a dhaba needs a full POS suite is a different decision; does a small dhaba need POS software covers that choice. This page stays on the thali rhythm: adds belong on the open ticket until checkout.

• New slips for every roti basket on the same table
• Mixing hatch parcels into occupied table numbers
• Waiting until midnight to invent payment modes
• Losing the running total when a second waiter joins

Highway parcels are not tables

Travellers who never sit still need parcel tickets—optional name or vehicle note as a reference—so the hatch queue does not steal a dining table slot. Several parcels can stay open while thali tables linger. When the bags leave, close that parcel with amount and payment. Completed orders store items, amount, payment mode, and time, which matters when the owner asks what the highway window sold yesterday and filters history by date.

Cash or UPI when they stand up

Checkout at a dhaba is often abrupt: guests stand, someone waves a phone for UPI, or cash hits the counter. Staff should mark UPI, Cash, Card, or Other on the ticket at that moment. The mark is a record, not a payment gateway. Summary then shows the day’s collection and can compare a period or list top items by quantity—useful when you wonder whether roti volume really outran sabzi last week—without rebuilding a register.

No inventory module, kitchen display, e-invoice, or diner QR menu is required to keep this pattern. What is required is the discipline that “another roti” is an add, and “three parcels for the car” is not Table 4. When those habits stick, arguments about who ordered the extra basket fade, and the till matches the closed tickets.

“

Keep the thali ticket open for every roti round; send highway bags out on their own parcel tickets.

Evening owners who missed the rush still filter history by date and read what closed—items, amount, payment, time—without calling the lunch crew back. That calm audit is the quiet payoff of finishing tickets when guests stand up.