Festive Sale Readiness — A Checklist for Online Stores
Peak sales expose every weakness in a store at the moment it costs most. Use this checklist to prepare for Diwali, end-of-season, and other major sales, covering speed, checkout, coupons, tracking, and what to watch during the event.
Short answer: prepare in three stages. Two weeks out, fix known friction and freeze risky changes. In the final days, test every coupon and the full checkout on a phone. During the sale, watch real sessions and errors in the first hour and at each traffic peak. Most sale-day losses come from a broken coupon, a slow page, or a payment problem that a test order would have caught.
Table of Contents
Two Weeks Before
Fix what you already know
- [ ] Review your purchase funnel by device and fix the weakest step
- [ ] Watch twenty recent mobile checkout sessions for friction
- [ ] Clear outstanding JavaScript errors on product, cart, and checkout pages
- [ ] Check real-user load times for top landing and product pages on mobile
Reduce risk
- [ ] Freeze theme changes and new apps or plugins
- [ ] Remove unused apps and scripts to lighten pages
- [ ] Confirm hosting and payment gateway limits with your providers
- [ ] Back up the site
Record a baseline
- [ ] Funnel conversion by step and device
- [ ] Payment success rate by method
- [ ] Page speed
- [ ] Normal error levels
Without a baseline, you cannot tell on the day whether a number is alarming or ordinary (comparing periods).
The Final Days
Offers
- [ ] Test every coupon code on a phone, including minimum order rules (coupon UX)
- [ ] Confirm automatic discounts apply to the right products
- [ ] Check that sale prices display consistently on listing, product, and cart pages
- [ ] Verify free-delivery thresholds and any COD fee
Checkout
- [ ] Place a real test order with each payment method
- [ ] Test UPI from a social app's built-in browser (UPI drop-off)
- [ ] Test COD and its confirmation step
- [ ] Check address and pincode validation
- [ ] Confirm order emails and messages are sent
Pages
- [ ] Load the sale landing page on a mid-range phone over mobile data
- [ ] Check that every campaign link goes to the right page, with UTM tags (UTM guide)
- [ ] Check stock levels and what an out-of-stock product shows (out-of-stock pages)
- [ ] Check banners and popups do not cover the buy button on mobile
Tracking
- [ ] Confirm purchase events fire once, with the correct value
- [ ] Check your session allowance. A sale can use a month's quota in days. DeepSync pauses recording at the cap and never charges overages, so upgrade beforehand if you need full coverage (session limits)
People
- [ ] Decide who is watching what, and when
- [ ] Agree what triggers a rollback or a pause in ads
- [ ] Brief support on the offers and likely questions
Launch Hour
The first hour finds most problems.
- [ ] Watch real sessions arriving from the campaign. With live session view on Pro and above you can watch as they happen
- [ ] Confirm real orders are completing, by each payment method
- [ ] Check for new errors on cart and checkout
- [ ] Check the coupon is applying for real shoppers
- [ ] Watch page speed as traffic rises
- [ ] Look for rage clicks on sale pages
If orders are not completing, pause paid traffic while you find out why. Every click during a broken checkout is wasted spend.
During the Sale
Check at each traffic peak, usually evenings and the final hours.
| Watch | Sign of trouble |
|---|---|
| Funnel step conversion against baseline | A step falling sharply |
| Payment success rate | A method failing |
| Errors by sessions affected | A new group appearing |
| Page speed | Slowing under load |
| Stock | Best sellers running out |
| Coupon failures | A spike in error events |
| Support messages | Repeated complaints about one thing |
Watch a handful of non-converting mobile sessions each day. Problems under load differ from problems in testing.
Avoid shipping changes mid-sale unless something is broken. If you must, change one thing and watch it.
Afterwards
- [ ] Conversion and revenue by campaign, from attribution
- [ ] Funnel against baseline: which step held and which did not
- [ ] Payment failures by method and browser
- [ ] Refusals and returns over the following weeks, by campaign (COD)
- [ ] Errors encountered and when they began
- [ ] What new customers looked at
- [ ] A written list of what to do differently
Write this within a week, while recordings and memory are fresh. It is the most useful document you will have for the next sale.
Place a test order every morning of the sale
On a phone, with the sale coupon. It takes three minutes and catches what monitoring misses.
Key Takeaways
- Fix known friction and freeze changes two weeks ahead.
- Test coupons and every payment method on a phone.
- Watch real sessions and errors in the launch hour.
- Write up lessons within a week.
Conclusion
A sale multiplies everything about your store, including its faults. Find them in a test order before your customers find them in a real one.
Frequently Asked Questions
Related articles
Stay in the loop
Get the latest insights on product analytics and user behavior delivered to your inbox.



