Keeping tickets moving in a long festival season
How a long city festival changes station layout, prep, and the selling screen.
Operators feel a rush first at the pass and the till. The useful preparation is smaller than a new slogan. Decide which items you will actually fire, which modifiers you will refuse after a point in the evening, and who is allowed to void a line. Write those choices into the selling screen before the doors open, in prices your cashiers already speak: rupees.
A short menu beats a long one when the line is outside. Each extra item is a place where stock, a modifier, and a ticket can disagree. For a festival or a public holiday, publish the limited menu on the direct ordering page and on the counter so guests do not order from yesterday’s board.
Prep should be a number, not a feeling. If a recipe decrements stock, the morning count is the only honest start. A manager who adjusts the count at noon should say why, because payroll, purchasing, and the waste note all read that same figure later.
Tender deserves the same discipline. Cash, card, and any other settlement you record must add to the ₹ total of closed tickets. A difference is a shift issue, not a problem to discover on Monday in a spreadsheet.
When the network drops, the selling screen should keep billing and show that it is offline. The kitchen still needs a ticket. Sync is a task for after the rush, with a person assigned to confirm that offline bills arrived once.
Close the day in the product, not in a side file. Lock the period when the manager agrees the ₹ totals. That lock is what accounting and a later review can trust.