Preparing a WooCommerce store for Black Friday

The failures that ruin peak trading are almost never surprises. They are things that were already true in October and only became visible under load.

Here is the preparation, working backwards from the day.

Six weeks out

Get updates done now. Everything current — WordPress, WooCommerce, gateway, theme, extensions. Do it properly, on staging first, with time to fix anything that breaks.

This is the whole point of doing it early: you want the risky work finished while a broken checkout costs you an ordinary Tuesday rather than your biggest day of the year.

Load test. Ask your host what your plan actually supports in concurrent visitors, and be specific: "what happens at 200 concurrent users?" If the answer is vague, assume the worst. Loader.io and k6 both have free tiers for a real test.

Review hosting headroom. Most hosts will let you upgrade temporarily for a month. That is far cheaper than a site that falls over on the day. If your TTFB is already poor, fix it now — load makes it worse, not better.

Audit plugins. Deactivate and delete anything you are not using. Every plugin is code running on every request, and under load that matters more than it does in October.

Four weeks out

Speed work. Images and caching first, because they give the most under load. Check your cart, checkout and account pages are excluded from caching — confirm it, do not assume.

Clean the database. Expired transients and WooCommerce session tables grow quickly and slow queries under load.

Test the full purchase path properly. Every payment method, every shipping option, every coupon type you plan to use. Desktop and mobile. Logged in and guest checkout.

Check stock and tax rules. A tax rule that has quietly stopped applying costs margin on every order.

Two weeks out

Freeze updates. Nothing changes from here unless it is a security fix. The risk is asymmetric — a small improvement against a lost trading day.

Verify backups and test a restore. Not "backups are enabled" — actually restore one to staging and open it. And increase frequency: daily is not enough during peak. Hourly, if your host or plugin supports it.

Set up checkout monitoring. Uptime monitoring of the homepage does not tell you whether people can pay. You want a check that reaches the payment step.

Test your order emails. They fail silently and often, and during peak nobody notices until the complaints arrive.

Write your rollback plan. Which backup, who restores it, how long it takes, and who decides. Deciding that under pressure at 9am on the day is how small problems become large ones.

The week before

Build your promotions on staging, test them, then push. Coupon logic is a common day-one failure — a discount that stacks when it should not, or applies to everything.

Brief whoever handles support. Refund policy, shipping deadlines, what to do if the site is slow.

Check your shipping cut-off dates are accurate and visible.

Confirm your gateway is ready. Some payment processors apply volume thresholds that trigger holds. If you are expecting five times your normal volume, tell them beforehand.

On the day

Do not deploy anything. Not a plugin update, not a theme tweak, not a "quick fix". The instinct to optimise during the event is the most expensive instinct in ecommerce.

Watch three things: checkout completion, server resources, and error logs.

Have the rollback plan open, not just written.

Afterwards

Update everything that you froze, review what broke and why, check whether your hosting upgrade should become permanent, and write down what you would do differently. Next year you will not remember.

If you would rather have someone else run this: our WooCommerce care includes the freeze windows, the staging updates and the checkout testing — and the health check at $249 is specifically designed to be run in October rather than December.