How to Run Festival & Seasonal Pre-Order Campaigns on WhatsApp
Short answer: a festival pre-order campaign needs three things a normal day of WhatsApp orders doesn't. A hard cutoff date announced up front, a deposit on every order over a certain size, and a capacity cap you set before you take a single message. Skip any one of the three and Eid, Christmas or Diwali stops being your best week of the year — and starts being the week you dread.
That's a planning problem, not a queue problem, and it needs solving before the first "can I order for Eid?" message arrives — not after.
Why festival orders break kitchens that handle daily orders fine
A kitchen that comfortably runs forty WhatsApp orders spread across a normal evening can still get flattened by forty pre-orders that all need to be ready between 11am and 1pm on the same day. The daily system — confirm, prep, cook, hand over, repeat — assumes orders trickle in. Festival demand doesn't trickle. It arrives in a burst weeks ahead — days of "can I order for Eid?" messages landing before a single one gets cooked — and then has to be produced in a burst on one specific morning, almost all of it out of the kitchen in the same six-hour stretch.
Two things go wrong when businesses treat a festival campaign like an extended version of daily ordering. First, there's no cutoff, so orders keep landing right up to the day itself and some inevitably get missed or rushed. Second, there's no cap. A good marketing push (rightly) brings in more orders than the kitchen can physically produce on the day, and the owner finds that out at 9pm the night before — not two weeks earlier, when there was still time to say no.
Both are fixable with the same fix: decide the limits before you open the campaign, not while you're running it.
Set the cutoff date first, and make it non-negotiable
Pick your cutoff — usually 48-72 hours before the festival date, more if you're doing anything that needs marinating, proofing, or special ingredients ordered in — and put it in the very first message you send about the campaign. Not "order soon," a real date.
🎉 Eid orders are open! Get your order in by Wednesday 6pm to guarantee pickup on Eid day. Orders after that go on a waitlist — we'll only confirm them if we have spare capacity.
The waitlist line matters as much as the cutoff itself. It tells the customer messaging at 11pm the night before that they're not automatically getting food, without you having to write an individual "sorry, we're full" reply to every latecomer. Most of them will order early next time once they've seen you mean it.
Move the cutoff earlier, not later, if last year ran you ragged. A cutoff that feels too cautious the first year almost always turns out to be about right once you've actually cooked through one festival rush.
Take a deposit — it filters the orders that were never going to happen anyway
Every festival season carries a batch of "maybe" orders: people who message to ask, half-commit, and then go quiet. Left unpaid, those sit in your prep count as real orders right up until they don't show. And that's exactly when you can least afford a wasted batch of biryani or a tray of gulab jamun nobody collects.
A deposit — even a small one, £5-10 or 20-30% of the order, whatever suits your prices — turns a "maybe" into a "yes" or a "no thanks" almost immediately. People who were never serious drop off at the deposit step instead of on the day, which is precisely when you want them to drop off. Our WhatsApp order payments guide covers the actual mechanics — payment links versus bank transfer versus cash — but for a festival campaign specifically, skip cash-on-collection entirely. It's the one payment method that does nothing to filter no-shows, because there's no commitment until the customer is already standing in front of you.
To confirm your Eid order, please send a £10 deposit to [payment link/UPI/bank details]. Balance due on pickup. This holds your slot — unpaid orders after 24h go back on the open list.
Say 40 people message asking about your Eid platter over a two-week window. On past form, maybe 10 of those were always going to be window-shoppers — testing the water, never planning to commit. Take no deposit, and all 40 sit in your prep count right up to the day. You only find out which 10 weren't real when they don't show, for food that's already cooked and going cold. Ask for a deposit at the point of confirming instead. Most of that same 10 either pay within a day, because they were serious, or go quiet immediately — while your prep count is still a number on paper, not wasted stock.
Cap your capacity before demand tells you where the ceiling is
This is the step most small operators skip, and it's the one that actually protects the kitchen. Work out — roughly, on paper, before the campaign opens — how many festival-size orders you can realistically batch-produce in the pickup window you're planning. Base it on your ovens, your staff that day, and the fact that festival dishes are usually slower per-unit than your everyday menu.
(There's no universal number here — a home baker doing 15 cake orders on one oven and a restaurant kitchen doing 150 platters are solving the same problem at very different scales. Work out your own ceiling from your own equipment and staffing, then build in a buffer under it, not at it.)
A rough version of the maths: if your kitchen can plate 12 festival orders an hour, and your pickup window runs four hours, your honest ceiling is 48 — not 60, just because 60 sounds like a rounder, more ambitious target. Knock another 10-15% off that 48 as a buffer for the orders that always run slower than planned, and you land closer to 40-42 as the number you actually promise.
Once you have a number, treat it as a hard stop, not a target to aim past. When you hit it, switch your ordering message from "taking orders" to "waitlist only" — a single edit to your WhatsApp catalog description or pinned message does it. Turning away order number 91 when your ceiling is 90 costs you nothing. Order 91 costs you plenty if it means orders 1 through 90 all come out late or under-cooked, because the kitchen was stretched past what it could actually handle.
The message rhythm that keeps a campaign from needing constant babysitting
A festival campaign runs over days or weeks, which means you can't manage it message-by-message the way you'd handle a single evening's orders. Four broadcasts, sent at the right moments, do almost all the work:
- Opening announcement (2-3 weeks out) — dates, cutoff, and how to order. Send it once to your customer list; don't repeat it daily.
- Midpoint reminder (about a week out) — a nudge for people who saw the first message and meant to order. This is usually where the bulk of your volume actually lands.
- Final call (24-48h before cutoff) — short and direct: "last chance, orders close [time/date]."
- Pickup/delivery slot confirmation (day before or morning of) — assign each paid order a specific time window so they're not all arriving at once.
Our WhatsApp broadcast lists guide covers the opt-in and etiquette side of sending these without it reading as spam — worth reading before your first festival push if you haven't set up a broadcast list yet. And if you're building the actual order-confirmation and reminder copy, the order message templates post has ready-to-adapt scripts for the confirm/remind/collect stages that slot straight into a campaign like this.
Give every paid order a slot, not just a queue position
The step that saves the actual pickup day: don't let everyone show up whenever they like. Assign a 15-20 minute pickup or delivery window per order as soon as the deposit lands, and put it in the confirmation message.
Order #23 confirmed — Eid platter x2, £48 total, £10 deposit received. Pickup window: 11:15am-11:30am, [address]. Please collect within your window so the next batch stays hot for the next family.
Spreading collection across a window instead of one single time turns a crowd at your counter into a steady, manageable trickle — the same logic behind reducing order friction on a normal day, just applied to a single high-stakes morning instead of spread across a month.
Putting the whole festival pre-order campaign on one page
| When | What happens | Why it matters |
|---|---|---|
| 2-3 weeks before | Open orders, announce cutoff date | Gives customers time, gives you a real deadline |
| Ongoing | Deposit required to confirm | Filters "maybe" orders before they cost you a wasted batch |
| Any point | Hit your pre-set capacity cap | Switch to waitlist — protects orders already confirmed |
| 1 week before | Midpoint reminder broadcast | Catches the bulk of remaining demand |
| 24-48h before | Final call, then hard cutoff | No more orders land after the kitchen has already planned its batch |
| Day before/of | Assign pickup/delivery windows | Spreads collection instead of one crowded rush |
None of this is specific to Eid, Christmas or Diwali — the same four pieces work for Mother's Day, a local festival, or any date where demand spikes hard. The businesses that dread festival season usually aren't the small ones or the busy ones. They're the ones taking orders with no cutoff and no cap, finding out where their limit was by blowing straight through it. Set yours on paper before the next big date shows up, and the busiest week of your year gets to actually feel like the best one.