A two-person Ahmedabad brand went into last Diwali's sale doing 30 orders/day. Day one of the event: 280 orders. Day two: 310. They celebrated that night. By day four they had 174 unprocessed orders, a printer that had died at the worst hour, a missed courier pickup, and the first SLA penalties of their life arriving in bulk. The sale wasn't the problem. The sale was the easy part.
Sale events compress a month of operations into 72 hours, and they punish exactly one thing: work that needed a decision at the moment of maximum chaos. The whole craft of a festival sale seller checklist is moving every decision out of the storm — backwards into the prep week, or sideways into automation — so the storm itself is just packing. Here is the full plan, T-7 to T+7 and beyond, from sellers who have lived a 10x week and kept their margins. Every number in it is illustrative; every failure mode in it is real, and most of them happened to someone we sat with.
T-7 to T-4: make the warehouse stop lying
Most sale-week disasters are stock disasters that were sitting quietly in the data a week earlier. The panel said 40 units; the shelf had 31; the sale sold 38. Now seven orders must be cancelled — at sale-event cancellation rates and penalties, against sale-event account-health scrutiny.
- Physically count every SKU entering the sale. Not the panel number — the shelf number. Fix the panel to match reality, not the other way around.
- Run a listing-truth pass on sale SKUs: size charts, fabric description, photos. Sale traffic multiplies whatever return-causing errors your listings already have.
- Order packaging at 1.5x expected sale volume — flyer bags, label rolls, tape. Sale-week stockouts of ₹4 consumables have cancelled ₹40,000 days.
- Confirm courier pickup capacity in writing: extra pickups per day, weight limits, the supervisor's number. The default pickup that handles 30 parcels will not absorb 300.
- Check thermal printer ribbon and a backup plan — the neighbourhood print shop's number counts as infrastructure this week.
While counting, make one harder call: which SKUs deserve to be in the sale at all. Sale traffic multiplies whatever each SKU already is — a profitable SKU becomes more profitable, and a quietly loss-making one (high return rate, thin settled margin) loses money faster than it ever has. If you have run a per-SKU profit audit, this decision takes five minutes; if you haven't, at minimum exclude the SKUs whose return rates you already distrust. Selling 200 units of a negative-margin SKU in one weekend is the most efficient way to lose money in this business.
T-3 to T-1: build the line, brief the people, verify the robots
The last three days are for the production line. Lay out the packing table so it flows one way — picked item, slip check, bag, seal, label, done-crate — and run 20 practice parcels through it with whoever is helping. Brief the one-parcel-at-a-time rule (it prevents the wrong-label-wrong-box disaster that doubles at volume). Pre-sort fast-moving SKUs within arm's reach.
Then verify the software side. If your order processing runs on a schedule, confirm the schedule, the document bundling, and the exception behaviour before T0 — a sale is the wrong day to discover a misconfigured run. If you process manually, accept now that the panel will cost you 3–4 hours a day at sale volume, and decide whose hours those are. This is the decision the volume-vs-effort curve below is about.
T0 to T+3: the flood, and the crunch behind it
Sale day feels dramatic but is operationally simple: orders arrive, nothing is due yet. The real test is T+1 to T+3, when every one of those orders hits its dispatch SLA cutoff in the same 48-hour band. This is the crunch that broke the Ahmedabad brand — not the 310 orders, but the 310 deadlines. A normal week spreads deadlines evenly; a sale stacks them into a wall, and the wall does not negotiate.
The crunch survival rules: dispatch in deadline order, not order-number order — pack what breaches first, first. Run the day from five numbers checked at three fixed times (the war room below), not from a panel refreshed forty times. Hold the line on document hygiene — every parcel slip-checked before sealing — because at 10x volume, a 1% wrong-item rate is three angry buyers a day. And batch your physical work but never your label application; labels go on one parcel at a time, always.
Do the throughput arithmetic before the crunch arrives, because it tells you whether your plan is physics or hope. A practiced packer on simple fashion SKUs runs roughly 25–35 parcels an hour. Three hundred orders is therefore 9–12 packer-hours — manageable for two people across a long day if packing is all they are doing. Add 3–4 hours of manual panel work and document wrangling, and the same two people are now at 13–16 hours, which is where the Ahmedabad story comes from. The crunch is rarely a packing shortage; it is panel work stealing packer-hours at the worst possible time.
If you hire festival help, hire for the line, not the panel. A neighbour's teenager can learn slip-check-bag-seal-label in twenty practice parcels; nobody learns a marketplace panel safely in a week, and a helper's panel mistake — a mis-clicked cancellation, a wrong manifest — costs more than their wages. Keep panel access to one trained person, or better, give the panel work to software entirely.
The war room: five numbers, three check-ins
At volume, attention is your scarcest inventory. The failure mode is refreshing the panel every ten minutes — each refresh costs focus and packs zero parcels. The fix is a war-room discipline: five numbers on one screen, checked at 8 AM, 1 PM, and 6 PM, and otherwise ignored. The five: orders synced today; orders processed and documented; SLA headroom of the worst order; exceptions held for a decision; and pickup status for the day. The operations dashboard exists to be exactly this screen.
Why these five and not others? Because each one answers a question that changes what you do in the next hour. Synced-vs-processed tells you whether the software needs you (it almost never does). Worst-order headroom tells you whether to keep packing or switch to dispatch triage. The exception count tells you how many one-click decisions are queued for your next check-in. Pickup status tells you whether tonight's handover is real. Revenue, conversion, traffic — the numbers sellers usually stare at on sale day — change nothing about the next hour, which is exactly why they can wait until T+7.
T+4 onward: the audit and the wave
When the backlog clears, two jobs remain, and skipping them gives back the margin you just earned. First, the money audit: sale-period settlements are the messiest of the year — event fees, commission changes, penalty lines, all landing at maximum volume. Run reconciliation on the sale orders specifically; at 300 orders even a 2% discrepancy rate is six orders' worth of leaks hiding in a statement nobody wants to read.
Second, the returns wave. Sale buyers return more — roughly 1.5–2x your normal rate is a sane planning band (illustrative; measure your own) — and the wave lands from about T+10 to T+21, precisely when you've stopped paying attention. Budget for it before the sale: cash flow (those settled rupees will partially un-settle), shelf space for restocking, and time to open every returned parcel on camera the day it arrives, because sale-period return fraud rides the wave too. The returns surface splitting customer returns from RTO is what makes this two-week stretch checkable instead of overwhelming.
The cash-flow shape of a sale
One more thing to plan with eyes open: the money arrives later than the work. You paid for sale inventory weeks before T0, you paid for packaging at T-5, and you may pay festival helpers in cash at T+3 — while settlements for sale orders land on the marketplace's cycle, typically a week or more after each delivery, minus the deductions you haven't audited yet, minus the returns wave that un-settles a slice of it at T+10 to T+21. A sale can be profitable on paper and still produce the tightest three weeks of cash your business has seen. The planning move is simple but must happen before T0: write down the week-by-week cash out and the realistic week-by-week cash in, and make sure the gap is covered without borrowing at festival-season rates. Gross sales are a vanity number until the wave has passed and the statements are reconciled.
Where Robnu fits
Everything in this checklist that touches a panel — syncing, processing, documents, SLA clocks, exception queues, reconciliation, returns tracking — is what Robnu does as an agentic OMS for AJIO and Meesho sellers (independent software, not affiliated with either marketplace). The physical line, the stock count, the courier supervisor's phone number: still yours. That split is the point — the sale-week hours you have should go to parcels, not panels.
Robnu is free for everyone right now — every feature, every order, no caps, no card — and when paid pricing eventually launches, sellers under 25 orders/day stay free forever, with early users grandfathered at locked rates. Which means you can set it up on a quiet 30-order week and find out what your ops feel like before the next 300-order one arrives.