This playbook is for the owner of a sweet shop, restaurant, cloud kitchen, cafe or home bakery who wants the festive season to be a record quarter rather than a week of survival. It starts with Diwali, because Diwali is the biggest week of the year for most Indian food businesses, and then applies the same method to Christmas, New Year, Holi, Eid, Pongal and Navratri. By the end you will have a six-week pre-order timeline with your own dates on it, a gift box and bulk order flow, a campaign message for each festival, a capacity plan for three times your normal volume, delivery slots with cut-offs, and a win-back sequence for the quiet weeks that follow. The belief it will change is this: the festive rush is not something that happens to you in the final week. The record week is built six weeks earlier, in the decisions about what to sell, how customers order it, and when you stop taking orders. Searching for diwali marketing ideas for restaurants on Dhanteras is already late. This is the guide to read in September.
The festive year at a glance
Every festival in the Indian food calendar follows the same commercial shape. Customers decide early if you give them a reason, demand compresses into the last three days, and the day after is quiet. The differences are what sells, how far ahead people commit, and how much your volume rises.
| Festival | Usual timing | What sells | Pre-order window | Volume versus a normal week (illustrative) |
|---|---|---|---|---|
| Diwali, with Dhanteras and Bhai Dooj | October or November | Gift boxes, dry fruit, festive thalis, family dinner bundles, party platters | Open 4 weeks before | 2.5x to 3x, half of it in the final three days |
| Christmas | 25 December | Plum cake, hampers, roast dinners, cookies boxes | Open 3 weeks before | 2x for bakers and cafes |
| New Year's Eve | 31 December | Dinner tables, party platters, late-night delivery | Open 2 weeks before | 1.5x to 2x, concentrated in one evening |
| Pongal | Mid January | Sakkarai pongal, full Pongal meals, office catering | Open 5 to 7 days before | 1.5x in Tamil markets |
| Holi | March | Gujiya and thandai, afternoon family lunch | Open 7 days before | 1.5x, with a dead morning and a slammed afternoon |
| Eid ul-Fitr and Eid al-Adha | Moves each year | Biryani trays, sheer khurma, kebab platters, sweet boxes | Open in the last week of Ramadan, or 5 days before Bakrid | 2x, almost all pre-ordered |
| Navratri | September or October | Fasting menu for nine days, vrat thalis | Announce 7 days before | Steady rather than spiky; a second menu, not a rush |
The multipliers are typical shapes rather than forecasts. Pull last year's order count for each festive week from your own records and write your real number next to each row. If you did not track it last year, this year's count is the baseline for next year.
Two things follow from the table. First, Diwali deserves the full six-week method below, and the smaller festivals get a compressed version of it. Second, if you sell nothing that can be gifted or pre-ordered, you are leaving the early-deciding customers to someone else. Even a kebab kitchen can sell a party platter for pre-order. The 52-week WhatsApp campaign calendar places every one of these festivals on a single calendar so the Diwali plan does not collide with Navratri or run into Christmas unprepared.
The six-week pre-order timeline
Work backwards from the festival date. The timeline below is written for Diwali; for Christmas compress it to four weeks, and for Holi, Eid and Pongal to two. The principle does not change: everything that needs a supplier, a printer, a photograph or a temporary hire is decided before you announce anything.
Week by week
| Weeks before | Decide | Do |
|---|---|---|
| 6 | The festive range and the cut-down regular menu. Volume estimate from last year plus list growth. | Order packaging for three times a normal month. Cost every box and bundle. |
| 5 | Prices, tiers and bulk discounts. Which items ship, which are local only. | Confirm suppliers in writing with quantities. Photograph every box open and closed. Build the store page. |
| 4 | Cut-off dates for bulk, shipping, local and pickup. | Open pre-orders. Send bulk quotes to offices, societies and business contacts. Book temporary staff and riders. Submit campaign templates for approval. |
| 3 | Capacity per delivery slot and per pickup window. | Write the day-by-day prep list from early pre-orders. Train staff on the festive menu. Send the first reminder. |
| 2 | Nothing new. Freeze the range. | Close bulk orders. Start producing dry and long-shelf-life items. Place a test order yourself end to end. |
| 1 | Who can pause orders and when. | Close shipping orders, then local pre-orders. Final roster. Brief the whole team, including what to say when something sells out. |
| Peak week | Only what the prep list says. | One person on the order screen. Daily stock count. Daily reconciliation. Greeting message on the morning of the festival. |
The dates you publish
Customers respect a cut-off they can see. Put these four dates on the store page, in the announcement message and on the counter, and repeat them in every reminder.
- Bulk orders close: ten days before the festival. Production for bulk starts the same day with the dry items.
- Shipping orders close: five days before. A courier bag that leaves later than that is a refund waiting to happen.
- Local pre-orders close: three days before, or earlier if your pickup windows fill first.
- Pickup and delivery windows: the two days before the festival and the morning of it, published as two-hour windows with a cap on each.
A clear cut-off does more than a discount. It pulls orders forward into the weeks when the kitchen has capacity, and it gives you a polite, non-negotiable answer to the twenty-box order at 9pm the night before. The festive season operations guide goes deeper on the countdown from the kitchen's side.
Before you announce anything: the checklist
- Every box and bundle costed, priced and photographed.
- Store page live with the festive items, the four cut-off dates and the pickup windows.
- Packaging in stock for the estimated volume, plus a margin.
- Suppliers confirmed in writing for the peak fortnight.
- Temporary packers and riders booked.
- Campaign templates submitted for approval, with placeholders for dates and prices.
- A test order placed from your own phone, paid, confirmed and marked ready.
- Staff told which items are local-only and which can ship.
Gift boxes, bundles and bulk orders
Loose sweets by the kilo and a la carte menus are counter products. Boxes and bundles are what sell online, because the customer can picture what they are sending and the price is fixed before they ask. This chapter builds the range, prices it, and sets up the two order flows: one for individuals, one for the office that wants eighty boxes.
Three or four tiers cover almost every buyer
| Tier | Sweet shop or bakery version | Restaurant or kitchen version | Price band | Who buys it |
|---|---|---|---|---|
| Starter | 250g assorted mithai, simple sleeve | Snack box: namkeen, cookies, a chai blend | ₹299 to ₹449 | Society gifting, staff gifts in bulk |
| Classic | 500g assorted, rigid box | Dinner-for-four bundle, or a party platter for ten | ₹599 to ₹999 | Families and neighbours; the volume seller |
| Premium | Dry fruits and mithai, two-layer box with ribbon | Hamper: dry snacks, dessert, a sauce or pickle, a card | ₹1,199 to ₹1,999 | Clients, in-laws, bosses |
| Build-your-own | Customer picks 4 to 8 varieties for a fixed box size | Customer picks mains, sides and dessert for a fixed bundle price | Priced by size | Regulars who know what they like |
Keep at least one dry, long-shelf-life box in the range even if your reputation is milk sweets or fresh food. It is the only product you can ship to another city, and it is the one that survives being bought on Monday and gifted on Friday. The rule for a build-your-own option in festive week is to let the customer choose only from items you have already prepped in batches, so the kitchen sees ten permutations rather than forty.
Pricing a box: a worked example
This is an illustrative example built from typical numbers, not a named merchant. Take a Classic 500g box priced at ₹699.
- Ingredients for 500g of assorted mithai: ₹320
- Rigid box, sleeve, ribbon and card: ₹60
- Packing labour, at about six minutes per box: ₹25
- Share of local delivery cost across the week's boxes: ₹40
- Total cost: ₹445. Margin at ₹699: ₹254, which is about 36 percent.
Now apply the two discount ideas you will be tempted by. An early-bird ₹100 off for orders placed three weeks out drops the margin to ₹154 per box, and it moves orders into the weeks when you have spare hands, so it is often worth it. A 30 percent off banner in Diwali week drops the price to ₹489 and the margin to ₹44, on the days when you would have sold the box at full price anyway. Discount the quiet weeks, never the busy ones.
The individual order flow
A customer should be able to finish a gift order on their phone without calling you. Every detail the packer and the rider need is captured when the order is placed.
- One link everywhere. The store page lists each box with a photo, contents and price. It goes in your WhatsApp greeting, on Status, on Instagram, on a counter QR code, and on the recorded message of the phone line you will stop answering in peak week.
- Gift fields. Recipient name, delivery address and an optional card message. For several boxes to several addresses, ask for one order per address or take a list and enter it yourself.
- Advance payment. UPI or card at checkout. The person paying is often not the person receiving, so cash on delivery fails more often than usual on gifts. The advance payment guide has the wording and the thresholds.
- A confirmation with a date, not just "order received". The delivery or pickup date is the thing the customer is anxious about.
- Pickup as a first-class option. A collection window at the shop clears a third of the delivery load, and gift buyers often prefer to hand the box over themselves.
Sweet shops that have moved the counter queue onto the phone describe the mechanics in the self-pickup for sweet shops guide. The full Diwali box version, including shipping, is in the Diwali gift box pre-order playbook.
The bulk order flow
Offices, housing societies, schools and shops that gift their own customers buy in multiples of fifty, decide three weeks early, and decide once. One message with a price list to every business contact you have is the highest-return action in this entire playbook. The flow:
- A bulk price list with three tiers: 25 to 49 boxes, 50 to 99, 100 and above, with a 5 to 10 percent step between tiers. More than that gives away the margin that makes the order worth the packing.
- A quote sent on WhatsApp with box photos, per-box price at their quantity, delivery date and the advance required.
- A 50 percent advance by payment link to confirm, the balance before dispatch. The order is confirmed when the money arrives, not when someone replies "please proceed".
- A GST invoice on the business name, with the buyer's GST number captured at quote stage so the bill does not need a second round of messages.
- One address and one two-hour window for delivery. Eighty individual employee addresses is a different product and is priced as one.
- Personalised cards or a logo sleeve at a small charge. Companies like it and a local printer turns it around in a day.
A worked bulk order, illustrative: an office takes 80 Classic boxes at the 50 to 99 tier, ₹699 less 8 percent, so ₹643 each, ₹51,440 in total. Advance of ₹25,720 by payment link on the quote day, balance ₹25,720 two days before dispatch. At ₹445 cost per box the margin is ₹198 per box, ₹15,840 for one delivery to one address, before the logo sleeve at ₹15 extra per box. The quote and advance mechanics, including what to do when a buyer goes quiet after the quote, are in the catering and bulk orders on WhatsApp guide.
Campaign templates for each festival
Three short messages carry almost every festive campaign: an announcement that opens pre-orders, a reminder two days before the cut-off, and a greeting on the morning of the festival with one quiet offer. The templates below follow that pattern for each festival. Replace the bracketed parts, keep each one under sixty words, and send only to customers who have opted in.
Sending rules that apply to all of them
- Consent first. A festival greeting with a link is marketing. Send it to customers who agreed to updates when they ordered, and honour every opt-out the same day.
- Template approval. On the WhatsApp Business API, marketing messages outside a live conversation must be approved templates. Submit them four weeks out with placeholders for dates and prices; the template approval guide explains the wording that passes first time.
- One offer per message. Three offers in one message get none of them ordered.
- A link and a date in every message. The link is the store page; the date is the cut-off or the day the offer ends.
- Send at the right hour. Announcements late morning, cut-off reminders early evening, day-of greetings by 10am.
- Segment by region and by history. A Pongal message in Jaipur, or a gift box message to a customer who only ever orders biryani at midnight, costs you a block.
Diwali
Diwali boxes are open for pre-order at [Shop]. Classic 500g box ₹699, premium dry fruit box ₹1,499, and a build-your-own option. Order at [store link]. Local pre-orders close [date]; shipping orders close [date]. Offices and societies: reply "bulk" for the price list.
Pre-orders for Diwali boxes close on [date] at 9pm. [Store link] takes two minutes. Pickup windows on [date] and [date] are filling up; delivery slots on Diwali eve are nearly full.
Happy Diwali from all of us at [Shop]. Thank you for ordering with us this year. If nobody wants to cook tonight, our dinner-for-four is ₹[price] with delivery slots till 10pm: [store link].
The greeting goes out on Diwali morning. It is the one message of the year almost nobody minds receiving, and the link at the end turns goodwill into dinner orders without a discount. Sixteen more angles, including Dhanteras lunches and a sweet with every order, are in the Diwali marketing ideas for restaurants and sweet shops.
Christmas and New Year
Christmas pre-orders are open at [Bakery]: plum cake 500g ₹[price] and 1kg ₹[price], cookie hampers, and a roast dinner for four. Order at [store link] by [date] for collection on 23 and 24 December.
New Year's Eve at [Restaurant]: tables from 8pm with a set menu at ₹[price] per head, or the party platter for ten delivered till 11pm. Book or order at [store link] by [date].
Christmas is a bakery festival with a collection-day problem, solved by capped pickup windows on the 23rd and 24th; the Christmas cake pre-order guide covers batch baking against the pre-order list. New Year is a single-evening festival where the New Year promotions guide argues for a fixed menu and prepaid tables rather than a discount.
Holi
Holi is on [date]. Gujiya boxes of 12 and 24, thandai by the litre and a snack platter for guests are open for pre-order at [Restaurant]. Order by [date] at [store link] for delivery on Holi eve.
Happy Holi from [Restaurant]. After the colours, lunch is on us to cook: family thali for four at ₹[price], delivery slots from 1pm to 4pm. Order at [store link].
Eid
Eid pre-orders are open at [Restaurant]: biryani trays for 6 and 12, sheer khurma by the litre, seekh kebab platters and sweet boxes. Order by [date] at [store link] for delivery or pickup on Eid morning from 9am.
Eid Mubarak from all of us at [Restaurant]. If guests are arriving and the kitchen is full, our Eid platter for 6 is ₹[price] with delivery till 10pm: [store link].
Pongal and Navratri
Pongal special menu at [Restaurant] from [date] to [date]: sakkarai pongal, ven pongal with sambar, medu vadai and payasam, plus a full Pongal meal for ₹[price]. Pre-order for Thai Pongal morning at [store link]. Offices: reply "Pongal" for the per-head list.
Navratri vrat menu at [Restaurant] for all nine days: sabudana khichdi, kuttu puri thali, fruit platters and vrat sweets. Order daily till 9pm at [store link]. Weekly vrat thali subscription available; reply "nine" for details.
Nine regional templates with timing tables are in the Holi, Eid and Pongal campaign templates. For a festival not covered here, the structure is the same four parts: greeting by name, one offer, the link, the date.
What a festival campaign costs: a worked example
Illustrative, with the response rate as an assumption you replace with your own after the first send. A sweet shop has 1,200 opted-in customers and sends the three Diwali messages above, 3,600 messages in total. Assume ₹1 per message for the arithmetic, which puts the campaign at about ₹3,600; the actual per-message rate is shown in your campaign wallet before you send. If 4 percent of recipients place a gift box order at an average of ₹699, that is 144 orders and roughly ₹1,00,000 in pre-sold revenue, against a message cost that is less than the margin on fifteen boxes. The same ₹3,600 on delivery app ads in festive week, when every restaurant in the city is bidding, buys far less and the customers it wins belong to the app.
Handling three times the order volume
Festive operations fail in a predictable order: the phone first, then packaging stock, then the kitchen's prep, then delivery, and finally the staff on day three. Each failure is cheap to prevent six weeks out and impossible to fix on the day. This chapter is the operations plan that sits under the marketing.
Shrink the menu, then pre-sell it
A kitchen that triples its output cannot also triple its variety. Cut the regular menu to the 60 percent of items that sell, add a short festive range, and freeze both a week out. Every item on the peak-week menu should be something you can make in batches of fifty. Bundles do most of the work here: a dinner-for-four, a gift box in three sizes and a party platter for ten are each one line on the prep list and one decision for the customer.
Then pre-sell. Pre-orders with a date and a cut-off turn a guess into a production list. A sweet shop that knows on Friday that 340 boxes go out on Tuesday makes the dry items on Saturday and the perishable ones on Monday, and buys exactly that much khoya.
Capacity: a worked example
Illustrative. A cloud kitchen does 80 orders on a normal day and expects 240 on each of the three peak days. Its kitchen can plate about 30 orders an hour with the regular menu, which is 240 in eight hours only if nothing goes wrong and nobody eats lunch. Three changes make it workable:
- Pre-sold bundles: 120 of the 240 are pre-ordered dinner-for-four bundles, cooked in batches of fifty through the afternoon and packed by 5pm. The kitchen's live load drops to 120 orders across the evening.
- Two extra packers and one extra batch cook, booked four weeks out at roughly ₹800 to ₹1,000 a day each, so about ₹9,000 for the three peak days. Against 360 extra orders at a ₹450 average, the extra wages are under 6 percent of the extra revenue.
- Pickup windows for 40 of the evening orders, so riders handle 80 live deliveries instead of 120.
Prep by the list, stock count by the clock
- A prep list per peak day with quantities, built from the pre-order numbers plus a walk-in margin, on the wall and ticked as it is done.
- Par levels for every batch item: litres of gravy, number of boxes assembled, kilos of dough.
- Dry and long-shelf-life items first each morning; perishable last.
- A fifteen-minute stock count every night in peak week: packaging, ghee, dry fruit, and the three ingredients that would stop production.
Staff: one role each, one person on orders
Book temporary kitchen hands, packers and riders four weeks out, because every kitchen in the city is booking them in the same fortnight. Give each person one role for the week: cooking, packing, order screen or dispatch. The person on the order screen does nothing else and is the only person who talks to customers. Brief everyone the week before on the menu, the cut-offs, the slots, and exactly what to say when something runs out: "we are out of kaju katli but the dry fruit box is available for pickup at 4pm" saves the sale and ends the argument. Rotate real breaks into the afternoon lull; day-three mistakes come from people who have stood for eleven hours.
Take orders without the phone
One person can take about 25 phone orders an hour on a good day, and festive week has no good days. Moving orders to a store page or a WhatsApp ordering bot means the customer enters their own address, picks their own box and slot, and pays before you have done anything. The order lands in a list with the details complete.
- The store link in the WhatsApp greeting, on Status, on the counter QR and in the phone line's recorded message.
- Status updates instead of calls: confirmed, being prepared, out for delivery, ready for pickup. Every update you send is a "where is my order" call you do not receive.
- Cut-offs enforced by the system, so the store says "closed" or "next slot" and staff never have to say no.
- A pause rule: if the kitchen is drowning at 6pm, stop new orders for forty minutes rather than take orders you will deliver at 10pm. Decide in advance who can press it.
Money in the peak week
Advance payment on every pre-order and gift box. Cash on delivery only for small local orders, if at all; a rider carrying ₹40,000 in notes on Diwali eve is a risk you do not need. Reconcile every night: orders, payments received, cash in hand, refunds. GST bills on every order, so the bulk invoices do not need rebuilding in January.
Running this on Tezzu
Tezzu puts the festive range on your free store page as bundles, including build-your-own, and customers order on your own WhatsApp number or the page without downloading anything. Pre-orders carry a chosen date, payment is by UPI or card through Razorpay or cash on delivery where you allow it, and every order lands in the live dashboard and the staff app with the box, slot, address and payment status filled in. The staff app sounds an alert for each new order so nobody watches a screen, staff roles let a packer see orders without seeing revenue, KOTs print to a thermal printer, GST bills print with each order, and menu scheduling by weekday and time keeps the festive items visible only in the slots you can produce them.
Delivery slots, pickup windows and cut-offs
Riders are scarce in festive week, roads are slow, and the radius that works in August produces 90-minute deliveries in Diwali week. The fix is to sell time windows you can keep, cap each one, push pickup, and shrink the map.
The festive slot pattern
| Window | Who orders it | Cut-off | Notes |
|---|---|---|---|
| 11am to 1pm, two days before to festival morning | Gift box deliveries, bulk drops | Previous evening | Group by locality; one rider does one neighbourhood |
| 3pm to 5pm | Gift boxes, party platters | 12 noon same day | Quietest window; use it for the far zones |
| 7pm to 9pm | Family dinners, festival-night bundles | 5pm same day | Widest window because the roads are slowest |
| Pickup, 10am to 12 and 4pm to 6pm | Anyone who prefers to carry the box | Previous day | Capped per window; a packed order with a name on it |
| Shipping to other cities | Children gifting parents, NRIs ordering for family | Five days before the festival | Dry items only; state the expected delivery date before the customer pays |
Two-hour windows are a promise you can keep; a specific time is a promise you will break. Customers who want an exact time are offered pickup, where a collection time is a point you can hit. The general method, with same-day slot cut-offs and reminders, is in the scheduled delivery and pre-orders guide.
Slot capacity: a worked example
Illustrative. You have three riders and a 3 km festive radius. In festive traffic each rider manages about four drops an hour when orders are grouped by locality, so a two-hour window holds 24 deliveries across three riders. Cap the window at 70 percent of that, 17 orders, for the first festival you run this way, and raise it next year when the slots were consistently met. Add two pickup windows of 40 orders each, and the evening handles 97 orders without a single late delivery. Over-selling a slot is how a record week turns into a week of refunds.
Shrink the radius, surcharge the edge
- Switch off or surcharge the outer delivery zones for the three peak days. A 6 km radius becomes 3 km; customers beyond it get pickup or a slot on a quieter day.
- Raise the free-delivery threshold for the peak days, or remove it, so small far-away orders do not claim a rider.
- Pay your own riders a per-drop bonus for the week. Every platform in the city is offering incentives in the same fortnight.
- Quote honest times before the customer orders. The order you lose to honesty costs less than the refund on a false promise.
Shipping boxes to other cities
Ship only dry fruits, baked goods, chikki, dry laddoos and sealed namkeen, in a rigid outer box with filler, with the inner box sealed. Milk sweets and fresh khoya stay local and the menu should say so. Close shipping orders five days before the festival and give the expected delivery date before the customer pays rather than after dispatch. The guide to shipping Diwali sweet boxes walks through which mithai travels, pricing the box and the steps from order to courier pickup.
The messages between order and delivery
A gift customer has a long gap between paying and seeing the box arrive, and silence in that gap becomes a call. Three messages close it: a confirmation with the date at booking, a "packed and going out between 11am and 1pm" message on the morning of delivery, and a delivered message that asks for a rating. On Tezzu, delivery zones carry distance-based charges and per-zone free-delivery thresholds that you can tighten for the peak days, self-pickup points have collection times, scheduled orders carry their date into the kitchen's list, and out-of-city boxes are best confirmed with the customer directly, with the courier booked by you.
After the festival: win-back and the quiet weeks
You have just served more new customers in ten days than in the previous two months, and most of them will not think of you again until next Diwali unless you do something in the following six weeks. This chapter turns the festive list into a regular list.
The first 72 hours
- A "we are cooking today" message the day after the festival, when people are tired of sweets and want a normal meal and do not know who is open.
- Bhai Dooj boxes two days after Diwali: the range is already built; message past buyers with a smaller box and same-day delivery. It is the easiest repeat sale of the season.
- Rating requests after every festive delivery, and a Google review request to the happy ones. Reviews earned now compound through the wedding season.
- A thank-you to every bulk buyer, with a lunch or catering offer for their next event. Corporate buyers are rarely thanked and they remember it.
Segment the festive customers before you message them
| Segment | How to spot them | What to send | When |
|---|---|---|---|
| First-time gift buyers | One order, a gift box, a different delivery address from the payer | An introduction to the regular menu with free delivery on the first normal order | Day 10 after the festival |
| Bulk buyers | Business name on the invoice, 25 boxes or more | Thank-you, then a catering or office-lunch quote | Day 3, then day 30 |
| Regulars who ordered more | Existing customers whose festive spend was above their usual | Nothing special; keep the regular cadence and a thank-you | Normal schedule |
| Festive-only customers from last year | Ordered last Diwali and nothing since | The three-message win-back sequence below | Day 10, 24 and 45 |
The post-festival win-back sequence
Three messages over six weeks, with an offer that gets stronger, then stop. More than three turns a win-back into spam, and blocks damage the standing of the number you use for every other customer.
Hi [Name], thank you for ordering Diwali boxes from [Shop]. The regular menu is back, and our weekday lunch thali is ₹199 this month. See it at [store link].
Hi [Name], we would like to see you again. Use code BACK50 for ₹50 off your next order of ₹300 or more, valid till Sunday. Order on WhatsApp or at [store link].
Hi [Name], this is our last offer message for a while. Your next order ships free with code LASTFREE, valid for 3 days. If you would rather not hear from us, reply STOP and we will remove you from offers.
Free delivery or a flat rupee amount beats a percentage; it is easier to picture and cheaper on small orders. Avoid 30 to 50 percent off as the first move, because it teaches customers that going quiet is how to get a discount. The thresholds for who counts as inactive by business type, and the measurement, are in the WhatsApp win-back campaigns guide.
Measure it, then write next year's plan
Record four numbers per message: delivered, read, orders using the code, and STOP replies. Then, six weeks after the festival, record what matters more: how many festive customers placed a second, full-price order. Illustrative: 144 Diwali gift buyers, 31 of them order again within 45 days at an average of ₹420, which is about ₹13,000 of revenue that did not exist last year, from a list you did not have last year. On Tezzu, the dashboard's customer insights show who ordered when, coupons can auto-apply from the campaign link so nobody types a code, and order reviews after delivery tell you whether the returning customer had a better experience this time.
Finally, before the memory fades, write one page: what sold out, what did not sell, which slot broke, which supplier was late, which message got the most orders. Next year's six-week plan starts from that page in week six.
Your 90-day plan
This plan assumes the festival falls on day 60, so weeks six to one of the timeline occupy days 18 to 59. Shift the dates to your own festival and keep the order of the steps.
| Days | Focus | Done when |
|---|---|---|
| 1 to 10 | Pull last year's festive numbers, decide the range (three or four tiers plus bundles), cost every item, decide what ships and what stays local | A one-page range with costs and prices, and a volume estimate per peak day |
| 11 to 17 | Order packaging for 3x, confirm suppliers in writing, photograph the boxes, build the store page with the four cut-off dates | Store page live but not announced; packaging delivered |
| 18 to 31 (6 to 4 weeks out) | Submit campaign templates, open pre-orders, send bulk quotes to every business contact, book temporary staff and riders | Announcement sent; first bulk advances received |
| 32 to 45 (4 to 2 weeks out) | Set slot capacities and pickup windows, write the day-by-day prep list, train staff on the festive menu, send the cut-off reminder, close bulk orders | Prep list on the wall; bulk production started with dry items |
| 46 to 56 (2 weeks to 4 days out) | Place a test order end to end, freeze the menu, close shipping orders, final roster, team briefing with sold-out scripts | Everyone knows their one role and what to say when something runs out |
| 57 to 62 | Close local pre-orders, run the peak days from the prep list, one person on the order screen, nightly stock count and reconciliation, greeting message on festival morning | No slot over-sold; every evening reconciled |
| 63 to 70 | "We are open" message, Bhai Dooj or equivalent follow-on sale, rating and review requests, thank-you to bulk buyers | Reviews collected; bulk buyers thanked within three days |
| 71 to 90 | Segment the festive list, send win-back messages one and two, record the four numbers per message, write the one-page review for next year | Second-order rate known; next year's plan drafted |
Frequently asked questions
When should a restaurant start Diwali marketing?
Six weeks before the festival for decisions about the range, packaging and suppliers, and four weeks before for the public announcement and bulk quotes. Corporate and society buyers decide about three weeks out and decide once, so a quote that arrives in Diwali week is too late. Individual customers order in the final ten days, which is when the reminders and the greeting message do their work.
What are the best Diwali offers for restaurants?
A gift box range with a pre-order cut-off, bulk pricing for offices, a festive thali or set menu at one price, a dinner-for-four bundle for the nights nobody cooks, and a small sweet with every order over a minimum. Early-bird pricing three weeks out pulls orders forward. Deep percentage discounts in Diwali week itself give away margin on days you would have been full anyway.
How do I handle three times the orders during Diwali without more staff?
You will need some extra hands, usually packers and one batch cook, but the bigger lever is selling less variety and selling it in advance. Cut the menu to the items that batch well, sell bundles and boxes as pre-orders with a cut-off, cap each delivery slot, push pickup windows, and move ordering off the phone so every order arrives complete. The kitchen then cooks from a list instead of reacting to a ringing phone.
Should I take cash on delivery for festive gift orders?
Prefer advance payment by UPI or card for gift boxes and pre-orders, because the person paying is often not the person receiving, and a refused box on Diwali eve cannot be resold. Keep cash on delivery, if at all, for small local orders from known customers, and ask riders to offer UPI at the door so they are not carrying a day's takings in notes.
How do I keep festive customers after the festival?
Ask for a rating after every festive delivery, thank bulk buyers within three days, and send a short "the regular menu is back" message about ten days after the festival. For customers who go quiet, run a three-message win-back sequence over six weeks with free delivery or a flat rupee amount off, using a unique code so you can count the orders it brought back, then stop.