Operations

The Festive War Room: A 72-Hour Runbook for Sale Events

Festive events are not won with a deeper discount. They are won with dated freezes, six named roles, and thresholds written before the sale opens.

Key takeaways
  • Dated freezes prevent more damage than any checklist
  • One writer for price, for the whole event
  • Pre-approved thresholds beat live escalation
  • Book the teardown before the sale starts

The calendar you are planning against

Diwali falls on 8 November 2026. Navratri opens in the middle of October. Wave one of the large marketplace events usually lands in the days just before Navratri, which puts the first sale window in the second week of October 2026, with further waves through late October and the Diwali week itself.

Work backwards and the commercial decisions are closer than they feel. Event participation and deal nominations typically close four to six weeks ahead of wave one, so late August is when pricing, funding and assortment get locked. Inbound appointment slots tighten from late September, which means festive stock should be received and sellable by the third week of September, not in transit while the sale opens.

Freeze dates beat checklists

Most festive failures are self inflicted changes made too late. A checklist does not stop them. Dated freezes do. Publish these once, in writing, and hold them.

  • T minus 21 days: no variation or parentage changes. Nothing that can split a review count.
  • T minus 14 days: catalogue freeze. Titles, images, bullets and A plus content all locked.
  • T minus 10 days: price and promotion files locked, with floors written down and signed off.
  • T minus 7 days: advertising structure frozen. Only budgets and bids move after this point.
  • T minus 3 days: no software release that touches inventory or price feeds.

Every freeze needs one named person who can break it and a written record when they do. Freezes that anyone can override are not freezes.

Hour zero and the first six hours

The first six hours decide the event. Run a fixed opening check within 15 minutes of the sale going live, and run the same one repeatedly rather than inventing a deeper check each time.

  • Deal is live and the displayed price matches the approved file, on desktop and on app.
  • You hold the featured offer on the top 50 SKUs. Screenshot the exceptions with timestamps.
  • The inventory feed timestamp is from the last hour, not from yesterday.
  • No campaign is out of budget, and no campaign is spending five times plan.
  • Zero new suppressions or stranded inventory since the catalogue freeze.
  • Coupons and deals are not stacking below the written floor.

Repeat every 30 minutes for six hours, every two hours through the rest of day one, then twice daily. The value sits in the repetition.

Roles, thresholds, and pre-approved decisions

A war room without decision rights is a group chat with better attendance. Name six roles before the event: one incident commander, owners for catalogue, pricing, advertising and supply, and a finance observer who does not get a vote while the sale is running.

Then write the thresholds that let people act without asking. The advertising owner may lift daily budgets by up to 40 percent while blended return stays above the agreed line. The pricing owner may move within the written floor but never below it. Any SKU that turns contribution negative after fees comes off deal inside the hour. Anything outside those limits goes to the incident commander, who carries a 15 minute response commitment for the duration of the event.

Then turn off every automated repricer and any second system that can write price. One writer, one source of truth, for the whole event. That single rule prevents the most expensive festive incident there is.

Five failures that repeat every year

  • Two systems writing price, producing a race and a number nobody approved.
  • Stale safety stock, producing oversell, cancellations, and a defect rate that outlives the event by a quarter.
  • A label or MRP mismatch that triggers a mid event suppression on a hero SKU, usually on day two.
  • Day one budget exhausted before noon, so the highest traffic hours of the year run unsupported.
  • A festive bundle assembled late and never quality checked, which returns as a review problem in November.

None of these are strategic failures. All five are calendar and ownership failures, which is why freezes and named roles pay for themselves.

Teardown in the two weeks after

The event is not over when the sale ends. Book the teardown before it starts, or it never happens.

At T plus 2 days, reconcile promotion funding claimed against funding agreed. At T plus 7, forecast the returns wave and staff for it, because festive return rates run well above baseline and in fashion can approach double. At T plus 15, check settlement against expected fees line by line, including deal fees and commission charged on cancelled units. At T plus 21, write a one page post mortem that ends with next year freeze dates already set in the calendar.

Judge the event on four operational numbers rather than gross sales alone: featured offer hours lost on the top 50, out of stock hours, cancellation rate, and the share of advertising spend that ran against out of stock SKUs. Those four tell you what a better run event would have been worth, which is the only number that changes behaviour next year.

The daily brief

Never miss a move

The moves that move money, every morning.

One email a day. No spam, ever.

FAQ

Quick answers.

Diwali falls on 8 November 2026 and wave one events usually open around the second week of October. Inbound appointment slots tighten from late September, so aim to have festive stock received and sellable by the third week of September.
Two systems writing price at once. A repricer and a feed racing each other produces a price nobody approved, on the highest traffic day of the year. Switch automated repricing off for the event and keep one writer and one source of truth.
One incident commander with a 15 minute response commitment, plus owners for catalogue, pricing, advertising and supply, and a finance observer with no vote during the event. Founders make poor incident commanders because everything routes to them anyway.

Related insights

India's Commerce Engine

Put it
to work.

hello@zane.marketing

Book a meeting