The Diwali sale is planned. The banners are designed, the discount is agreed, the Instagram posts are scheduled for the morning it starts. What nobody has planned is the store itself: whether it will cope with far more visitors than usual, whether the coupon works for the products it should, and what happens if the payment page stalls at nine in the evening on the busiest day of the year.
Here is a countdown you can follow to prepare a WooCommerce store for a sale, from four weeks out to the week after. It works the same for Durga Puja, Eid, a Christmas offer or Black Friday for customers abroad. The dates change; the order of jobs does not.
Four weeks out: decide what the sale actually is
Most sale-week problems start as vague decisions. “Twenty off everything” sounds clear until someone asks whether that includes items already on sale, gift cards, shipping or one product line you make at a thin margin. Settle these on paper before anyone touches WooCommerce:
- Which products are in, and which are out.
- Whether the discount is a sale price shown on the product, a coupon code typed at checkout, or both.
- Whether the discount stacks with other codes already in circulation.
- The exact start and end time, and in which time zone if you sell abroad.
- The minimum order value, if there is one.
- Who is allowed to change prices once the sale starts.
Write the answers in one short document and share it with everyone involved. When a customer asks on WhatsApp why their code did not apply, the answer should be in that document, not in someone’s memory.
Three weeks out: check the server, the gateway and the courier
Ask your host a direct question
Shared hosting plans have limits on how much processing a site can use at once. Shoppers browsing category pages, filtering and adding to cart create far more server work than people reading a blog post. Tell your host the dates and ask whether your plan is likely to cope, and what happens if it does not. Some hosts throttle the site; some suspend it. You want to know which before the day. Our guide to what WooCommerce hosting needs explains what to ask for if the answer worries you.
Talk to your payment gateway
Log in to the gateway dashboard and check that your account is fully activated, that settlements are going to the right bank account, and whether there are any limits on your account that a sudden jump in orders could hit. If you are unsure, raise a ticket with the gateway and ask. It is far easier to sort out an account question in a quiet week.
Confirm courier pickups
If orders double, does your courier or shipping aggregator collect more often, or will parcels sit for days? Customers forgive a short delay they were told about. They do not forgive silence.
Two weeks out: build and test the offer on a copy
Set up the sale on a staging copy of the store first, not the live site. Then test it the way a sceptical customer would.
- Scheduled sale prices. In the product editor, the “Schedule” link next to the sale price lets you set start and end dates. Variable products need the sale price set on each variation. Schedule a test product to start tomorrow and check it does.
- Coupon codes. In Marketing > Coupons, check the discount type, expiry date, minimum spend, usage limits and product or category restrictions. Then try the code with an included product, an excluded product, a cart under the minimum and a cart over it. If a code misbehaves, our post on why a coupon code shows as invalid walks through the usual reasons.
- Bundles and free gifts. If a plugin adds a gift above a certain cart total, test what happens when the shopper removes items and drops below it.
- Shipping. If the sale includes free shipping above a value, check it applies after the discount, or before, whichever you decided four weeks ago.
- Emails. Place a full test order and read the confirmation email. Check that the discounted price, not the regular price, appears in it.
When it all behaves, recreate the same settings on the live store and keep them scheduled, not active.
Ten days out: freeze the code
This is the step owners are most tempted to skip. Run all pending updates now: WordPress, WooCommerce, the gateway plugin, the theme, everything. Test an order after the updates. Then stop. No new plugins, no theme changes, no “quick tweak” to the checkout, until the sale is over.
The reasoning is simple. An update that misbehaves in a normal week costs you an evening. The same update in the middle of a festival sale costs you the sale. If a security update arrives during the freeze for a plugin you actually use, that is the one exception worth making, and it should be tested on staging first.
One week out: stock, pages and people
Stock counts
Count the physical stock of every product in the sale and correct WooCommerce to match. A sale is the worst time to discover the site thinks you have twelve of something you have two of. Set a low stock threshold so you get an email before a product sells out.
The pages people will land on
Festival sale traffic does not arrive at the home page. It arrives wherever your ads and posts send it: a category page, a landing page, one product. Open each of those links on a phone over mobile data and see how long they take. Large banner images added for the sale are a frequent cause of slow pages; compress them.
Who does what
Decide who watches orders, who answers customer messages, who can be reached if the site goes down, and who has the logins to the hosting and the gateway. Write their phone numbers in the sale document. A technical problem at night is far worse when the only person with the hosting password is unreachable.
The day before: final checks on the live store
- Take a full backup, files and database, and confirm it completed.
- Set up uptime monitoring if you do not already have it; our post on website uptime monitoring explains the options.
- Clear any caching plugin’s cache after the final product changes, so shoppers do not see yesterday’s prices.
- Check that the cart, checkout and account pages are excluded from page caching. Many caching plugins exclude them by default, but a custom setup or server-level cache may not.
- Place one more real order on the live store, then refund it.
During the sale: watch, do not tinker
Once the sale starts, check the first hour closely. Did the scheduled prices actually change? Scheduled sales rely on WordPress’s background tasks, so if those are not running reliably on your server, prices can switch later than you expect. Look at the first few orders for the right discount and the right status.
After that, a rhythm of checks every few hours is usually enough: order count compared with traffic, any run of failed or pending payments, stock on the top products, and messages from customers. If payments start failing, pause the ads before anything else. Spending money to send people to a broken checkout only makes the loss bigger.
Resist changing things mid-sale unless something is actually broken. An unplanned price edit during the busiest hour is how a product ends up at the wrong price for the rest of the night.
The week after: close it down properly
- End the codes. Expire or delete the sale coupons. Codes from big sales can turn up on coupon websites quickly.
- Check prices went back. Spot-check a handful of products to confirm the regular price returned when the schedule ended.
- Reconcile stock. Count physical stock again and compare it with WooCommerce. Busy days expose stock problems that stay hidden in a normal week.
- Reconcile money. Compare paid orders in WooCommerce with payments in the gateway dashboard for the sale period.
- Catch up on updates you held back during the freeze, with a test order after.
- Write down what went wrong. Slow pages, confused customers, stock that ran out early. That list is the start of next year’s plan.
Small stores and big sales
A shop that normally takes a few orders a day can feel the pressure of a festival sale more sharply than a large one, because nothing about it was built with a busy day in mind. The countdown above is not about expensive changes. It is mostly about deciding early, testing on a copy and then leaving the store alone. That is what ongoing webshop maintenance looks like in a busy month: fewer changes, more checking.
If the part that worries you most is whether product and category pages will stay quick when the visitors arrive, our website speed optimisation page explains what that work involves.
Next in this series: How to Update WooCommerce Safely Without Losing Orders
