A price with a calendar
How festive pricing usually goes wrong
The manual version has a familiar shape. On the evening of the 19th, someone sits at the terminal and edits menu prices by hand — thirty dishes, one by one, hopefully with no typos. If you run two outlets, someone has to do it twice. The second outlet usually gets done a day late. So for twenty-four hours your Bandra guests and your Andheri guests pay different festive prices for the same thali.
Then comes the failure everyone knows: nobody remembers the way back. January arrives, the decorations come down, and the festive prices quietly stay. Regulars notice before you do — usually with a screenshot of an old bill. Now you're not adjusting prices; you're apologising for them.
The date-window way: a worked example
Date-window pricing means the price itself carries a calendar. You configure it once, in advance, and the window does the switching:
| Item | Regular list | Festive price · Dec 20 – Jan 5 | Jan 6 onward |
|---|---|---|---|
| Butter Chicken | ₹273 | ₹299 | ₹273 — by itself |
| Paneer Tikka | ₹260 | ₹285 | ₹260 — by itself |
| NYE Special Thali | — | ₹549 (window-only item) | off the menu — by itself |
You set those three rows in November if you like. On the night of the 19th, nobody touches a terminal. At midnight the festive prices switch on by themselves. On 6 January the regular list is back. You set the window once, so every outlet switches on the same dates. There is no reminder, no calendar entry and no 2 a.m. menu editing.
Layering it with the rest of your pricing
A festive window doesn't fight the rest of your pricing — it stacks with it, and one rule keeps the whole stack predictable: the setting nearest to the sale wins.
Dining areas keep their differences. If your AC hall and your rooftop VIP section run on their own price profiles, they keep behaving that way through the festive window. The rooftop on New Year's Eve is exactly the seat guests expect to pay a premium for.
Outlet overrides still hold. If Andheri deliberately prices a dish its own way, a centrally-set window doesn't bulldoze that decision. Local calls stay local — the same nearest-wins logic that governs every other price.
Regions scale it. Set the festive window on the Mumbai region's list. Every Mumbai outlet that inherits it gets the same dates. Your Pune region has its own market, so it can run a different window or none at all.
A checklist you can run in ten minutes
1. Pick the window honestly — for the Christmas–New Year season that's typically 20 December to 5 January, wide enough to cover both peaks and the week between.
2. Choose the dishes that carry the premium. Signature mains and party formats, yes; the dal your regulars order weekly, think twice.
3. Set both dates when you configure the price. The end date is the whole point — it's the difference between festive pricing and an accidental permanent hike.
4. On 6 January, glance at one bill. You'll find the regular price back on it — but the glance costs nothing and closes the loop.
The test of a real festive-pricing feature: ask what happens on the day after the festival. If the answer involves a human remembering something, it isn't automation — it's a diary with extra steps.
Festive demand is a seventeen-day gift. Price it once, in advance, and spend the season in the dining room instead of the menu editor.