Black Friday Readiness Checklist for Shopify and WooCommerce

Black Friday is Friday, November 27, 2026, and Cyber Monday is Monday, November 30, so there are about three and a half weeks left. The sales weekend rarely fails because of traffic alone. It fails because of something nobody tested: a discount that stacks, a script that blocks checkout on phones, a purchase event that stops firing. This Black Friday readiness checklist is a three-week plan to find those problems early, fix the ones that matter, and then stop changing things. The dates below count back from 2026. Shift them for other years and the plan still works.

Week one: find out where you stand

Start with facts, not worries. These six jobs take a day or two and decide what the rest of the plan needs to cover.

1. Take a speed baseline. Test your home page, a busy collection page, a busy product page and the cart on a phone, and write down the numbers. The Core Web Vitals thresholds are the targets. If a page is clearly slow, the Shopify mobile speed guide shows how to find the cause.
2. List every app, plugin and script. For each one, write who uses it and what happens if it fails. Remove what nobody uses. Fewer moving parts means fewer surprises.
3. List every promotion. Write down each offer, its rules, its start and end time, what it can be combined with and who owns it. Discounts are where most last-minute damage comes from.
4. Check how stock reaches the store. If stock comes from a supplier file, a warehouse system or an app, find out how often it syncs and what happens when it is late. Overselling is a technical problem before it is a customer service one.
5. Check your numbers. If the purchase event does not fire exactly once per order, your sale-weekend data will mislead you. The GA4 tracking audit for Shopify walks through the checks, and most of it applies to any store.
6. Choose a freeze date and a rollback plan. Write both down now, even if you will refine them later.

Shopify stores: what to check

Shopify handles hosting and scaling, so your risk sits in your own configuration.

• Work on a copy. Make changes in a duplicate theme, and keep your last known-good theme in the library so you can republish it if something goes wrong.
• Test app by app. Switch each app embed off in the duplicate theme and compare speed and behavior. Popups, upsell widgets and review carousels are the usual suspects, because they run on every page. The app audit guide has a method and an audit sheet for this.
• Test the discounts you plan to run. Codes, automatic discounts and free-shipping thresholds each behave differently, and combinations matter. Use realistic carts: several variants, a bundle, a gift card, a subscription item. Shopify’s discount documentation explains the types and the combining rules.
• Be careful with checkout customizations. If you use checkout extensions, Shopify Functions or a custom pixel, retest them end to end after every change, and avoid new ones this late.
• Check that nothing still depends on Shopify Scripts. Shopify announced that all Scripts would stop running on June 30, 2026. Did a Script once handle a discount, a shipping rate or a payment rule on your store? Confirm the same rule now runs through Shopify Functions or an app. Then add it to your test carts. Shopify’s Scripts deprecation notice points to a report that lists what can move.
• Test each market you sell to. If you use several currencies or regions, place test orders in the United States, Canada and Australia, and check displayed prices, taxes, shipping thresholds and payment methods in each.

WooCommerce stores: what to check

WooCommerce gives you control, and the same control makes capacity and caching your job.

• Know your hosting limits. Ask your host about CPU, PHP workers and burst limits on your plan. Checkout cannot be page-cached, so each shopper uses real server time. WooCommerce publishes its server requirements, and the slow checkout guide shows how to measure where the time goes.
• Load test a staging copy. With your host’s permission, run a tool such as k6 against staging: first the product page, then the cart, then checkout. Never load test production without telling your host.
• Check the caching rules. The cart, checkout and My account pages must never be served from a page cache, and requests carrying WooCommerce’s cart cookies must skip it.
• Finish updates early. Update WordPress, WooCommerce and plugins on staging in week one or two, then turn off automatic updates until the sale is over. An update that lands on Black Friday morning is an outage you chose.
• Clean up background work. Clear the Action Scheduler backlog, make sure cron runs on a schedule rather than on page loads, and take a backup the evening before the sale begins.
• Confirm the payment gateway. Check live keys and webhooks, test a refund, and tell your payment provider about the volume you expect. Sudden spikes can trigger reviews.

Week two: test the money path

Test the whole route from landing to confirmation email, on real phones. This is the table I would run through, with a second person doing it so that nobody tests their own work.

Sort what you find into two piles: things that would stop a sale, and things that are merely untidy. Fix the first pile this week. Write the second on a list for after Cyber Monday.

Week three: freeze, watch, rehearse

Shopify has no official code freeze. It is a rule you set yourself, and it is one of the cheapest ways to protect a sale.

• Freeze changes a few days to a week before Black Friday. Allow content, prices and stock changes. Allow code changes only for emergencies, reviewed by a second person.
• Monitor from outside. Set up an external uptime monitor on the home page, a product page, the cart and checkout, with alerts to a phone someone will actually carry. On Shopify, check the web performance reports in the admin. On WooCommerce, watch the server’s CPU and error logs.
• Name who is on call for each day, and how to reach them.
• Rehearse the rollback. On Shopify that means republishing the previous theme. On WooCommerce it means restoring a backup or switching off a plugin, which you can do from the command line if the admin is down:

# Switch off one plugin without the admin (WP-CLI)
wp plugin deactivate plugin-folder-name

• Prepare support. Update your shipping and returns answers for the sale. Shopify’s BFCM checklist covers the inventory, shipping and customer service side that this guide leaves out.

The sales weekend: what to watch

Thursday, November 26 is Thanksgiving in the United States. Black Friday follows on the 27th, Small Business Saturday on the 28th and Cyber Monday on the 30th. For the weekend itself:

• Check time zones. A sale that begins at midnight begins at a different moment for American, Canadian and Australian shoppers. Check the zone on every discount, banner, countdown and scheduled email, and test with a discount set to start a few minutes from now.
• Watch the ratio, not only the total. Orders per hour against sessions per hour shows a broken checkout faster than a sales total does.
• Watch for declines and errors. A jump in failed payments or error pages needs an answer within minutes.
• Keep stock honest. Hide or limit anything that is about to sell out, if your setup allows it.
• Do not deploy. If something breaks, decide whether a workaround is safer than a fix.

After Cyber Monday

Within a week, reconcile your analytics with the store’s own reports, write down what broke or nearly broke, remove temporary code and banners, and lift the freeze. The list you made in week two of untidy things is next. A short written review now is what makes next year’s version of this plan easy.

When it is worth getting help

Get help if you have a heavily customized theme, several apps that touch checkout, a WooCommerce site on shared hosting, or tracking you do not trust, and a deadline that will not move. A fixed-scope technical review plus the top-priority fixes usually takes one to two weeks, so the window to start before a freeze is short. I have done performance work, QA and production support on a Shopify Plus store, and I audited a large WooCommerce build, both in selected work. If you want a second pair of eyes, send me the store address and the symptoms. I will reply with what I think is causing it and what I would check first.