The Best Thing You Can Do to Your Ecommerce Site Before Black Friday Is Nothing
Black Friday is on 27 November this year. Adobe forecasts it will again be the biggest single day of the year for UK online spending, at around £1.24 billion, with the four-day Black Friday to Cyber Monday weekend expected to reach £4.05 billion.
When an online shop falls over in a week like that, the cause is often not the traffic. It's a change someone made a few days earlier: a plugin update, a new tracking pixel, a tweak to the checkout, a "quick" fix that nobody tested on mobile. The site was fine. Then it was touched.
So the most useful thing most ecommerce businesses can do to their website in the run-up to peak is stop changing it.
What a change freeze actually is
A change freeze is an agreed date after which nothing structural changes on your site until the busy period is over. It isn't new, and it isn't only for big retailers. Large technology companies routinely run freezes of a week or two around Black Friday and again over Christmas and New Year.
The point isn't to stop work. It's to stop risk at the exact moment risk costs the most.
What to freeze
The obvious one is code. The less obvious ones are the changes people don't think of as development work, which is where a lot of the trouble comes from. Configuration, app and extension updates, infrastructure, tracking scripts and pricing or promotion rules can all take a store down.
In practice, that means pausing:
- Theme, template and layout changes
- Plugin, app and extension updates (security patches are the exception, see below)
- New tracking scripts, pixels and tag manager changes
- Checkout, payment and pricing logic
- Hosting, DNS and CDN changes
Tracking deserves a specific mention. A significant change to conversion tracking close to Black Friday can leave your ad campaigns relearning at the worst possible time, and your reporting unreliable for the period you most want to measure.
What can carry on is content. Updating copy, swapping a banner, publishing a landing page or a blog post through your CMS, using templates that already exist, is normal business. The line is between editing what's there and changing how it works.
If you're reading this in late November, you're a little late
A common rule of thumb is no major deployments in the two weeks before Black Friday, which for 2026 meant Friday 13 November. Some retailers freeze a month or more ahead. If those dates have passed and you're still making changes, the answer isn't to panic. It's to stop now. A freeze that starts late is still far better than no freeze.
What to check before you lock it
A freeze only protects you if the site is in good shape when it starts. Before you stop, it's worth an hour on the basics:
- Put a real transaction through. Every payment method, every enquiry form. Check the confirmation email arrives, and arrives somewhere a person will see it.
- Check your backups. Not that they exist, that you know how to restore one.
- Check renewal dates. Domain, SSL certificate, hosting and any paid plugins. A renewal that lapses over the holidays is an outage nobody planned for.
- Know who has access. Who holds the logins, who's available over the period, and when your agency or developer is closed for Christmas.
- Make sure alerts go to a human. Uptime monitoring that emails an inbox nobody checks in December isn't monitoring.
- Write down what "normal" looks like. Current versions, current page speed, current conversion rate. If something goes wrong, you need a baseline to compare against.
Plan for the exception
Freezes break down when there's no agreed way to handle the thing that genuinely can't wait. The usual example is a critical security patch. Many retailers that freeze still let the most critical patches through, and that's the right call, as long as it's handled deliberately.
Decide now, not on the day:
- Who makes the call on an emergency change
- Where it gets tested first (a staging copy, if you have one)
- That a backup is taken immediately before it goes on
- That it goes live at a quiet time, not 8pm on Black Friday
- How you roll it back if it goes wrong
A freeze with no exception process tends to get quietly ignored. A freeze with one gets respected.
Not selling online? The same applies at Christmas
If Black Friday isn't your peak, the same discipline still applies to the Christmas close-down. Enquiry forms need to work in the last two weeks of December, leads need to land somewhere while the office is shut, and the person who would normally fix a broken form may be on holiday. If your site depends on plugins and integrations only one person understands, find that out before the break. We've written before about why your digital foundations decide how painful growth will be.
Keep a January list
Everything you decide not to do during the freeze goes on a list. The plugin updates, the new tracking setup, the redesign idea someone had in a meeting. In January, when traffic has settled, you work through it properly, one change at a time, with testing.
Some of those items will turn out not to matter. Some will point to a bigger question about whether the site needs fixing or replacing, which is a separate conversation.
The short version
Peak periods reward stability more than cleverness. Test the site, back it up, agree who's in charge, and then leave it alone until January.
If you'd like a second pair of eyes on your site before you lock it down, or help turning that January list into a proper plan, get in touch.













