Black Friday 2026 falls on 27 November, the day after US Thanksgiving, and Cyber Monday follows on 30 November. If you are reading this in mid-November, you have roughly two weeks. That is enough time to prepare a WordPress store properly, as long as you stop adding new things and focus on the ones that decide whether a sale goes well: a fast site, a checkout that works, stock numbers you can trust, emails that send, tracking that records, a plan for fraud, and a support inbox you can survive.
This is a two-week plan, not a wish list. It is written for WooCommerce and other WordPress stores alike, and it assumes you are a small team. It tells you what to test, what to freeze, and what to leave alone. WPMusk has not run a promotion for you or measured anything for this article, so there are no promised uplifts here. The plan rests on how WordPress stores generally fail under load, and on checks you can verify yourself.
Key takeaways
- Freeze big changes about a week before the sale. New plugins, theme edits and redesigns belong after Cyber Monday.
- Test the full purchase path on a phone, with real payment methods in test or low-value live mode, every day in the final week.
- Prepare inventory, shipping promises and customer emails before the traffic arrives, not during it.
- Check tracking and email deliverability early. Both fail silently and are hard to fix once the sale starts.
- Write down who does what on the day, and how to roll back if something breaks.
The timeline at a glance
Count back from the sale. Adjust the dates to your own start time, since many stores begin early or run a whole week.
| Days before | Focus |
|---|---|
| 14 to 12 | Decisions: offers, scope, change freeze date, roles. Baseline measurements. |
| 11 to 9 | Performance work and hosting capacity checks. |
| 8 to 6 | Checkout and payments testing. Tax, shipping, coupons. |
| 5 to 4 | Inventory, product data, email and tracking setup. Change freeze begins. |
| 3 to 2 | Fraud rules, support preparation, backups, monitoring, dress rehearsal. |
| 1 | Final checks. Schedule emails and offers. Clear the decks. |
| Sale days | Watch, respond, do not change things unless necessary. |
Days 14 to 12: Decide the offer and set your limits
Technical work is wasted if the offer is unclear. Settle these first.
Define the offers precisely
Write each promotion in one sentence, including the start and end time with a time zone, which products it covers, whether it combines with other coupons, and any minimum spend. Ambiguity produces support tickets and refunds. Decide whether the sale is site-wide, category-based or limited to a few hero products. Fewer, clearer offers are easier to test.
Set a change freeze date
Pick a date, ideally about a week before the sale, after which nothing changes without a reason you can write down. This includes plugin and theme updates. Updates that arrive during the freeze can wait unless they are security fixes. If you must update, do it on staging first and test the purchase path again. The freeze is the single most valuable habit in this plan.
Assign roles
Even a two-person shop needs it written down. Who watches the site? Who answers customers? Who can change prices or disable a coupon in a hurry? Who has access to hosting? Make sure each person can actually log in now, and that two-factor devices are at hand. Two-factor authentication for WordPress protects accounts, and having it set up before the sale avoids a lockout at the worst moment.
Take a baseline
Record how the store performs now: mobile PageSpeed Insights and field data for home, category, product, cart and checkout; your typical conversion rate and order volume from analytics; your usual support volume. You will compare against these during and after the sale. If you do not have a method, the PageSpeed Insights guide explains the readings.
Days 11 to 9: Performance and capacity
Traffic spikes expose weak spots. A page that is fine with ten visitors can crawl with a hundred at once, particularly the uncached cart and checkout.
Measure the pages that matter
Test home, a category, a top product, the cart and the checkout on mobile settings. Note the largest content element, the server response time and the number of scripts. The Core Web Vitals guide explains the metrics. For a method that finds causes in order, see the WooCommerce speed checklist.
Fix the biggest items only
You do not have time to optimise everything. Pick the three largest wins from your tests. Common ones before a sale:
- Oversized images on landing pages and hero banners. Resize and convert; see the image optimisation guide.
- Heavy third-party scripts. Remove tags you do not need. Every extra widget is a failure point under load.
- Slow queries on cart and checkout. Find them with a profiling plugin on staging. The caching plugins comparison and the Redis object cache guide cover options for dynamic pages.
Check caching rules for the sale pages
If you use page caching, confirm that cart, checkout and account pages are excluded, and that your new sale landing page is cached. A common error is a sale banner that is cached with stale prices or a countdown that does not update. Also check that your cache clears when you change a price or stock level, or a customer sees an old price at the product page and a new one at checkout.
Ask your host about capacity
Many hosting plans limit concurrent PHP processes or CPU. Contact your host and ask, in writing: what are our limits, what happens when we reach them, can we raise them temporarily, and what is the process if the site goes down? Some hosts offer a short-term plan upgrade. Do this now, not on the day. If you are on a plan that has struggled before, consider moving earlier; hosting by use case has comparisons, but do not migrate in the last week, since a move is a risk of its own.
Load test, carefully
If you are able to, run a modest load test on staging or at a quiet hour with your host’s permission. Some hosts treat load tests as abuse, so ask first. Even a simple test, with several colleagues placing test orders at once, can reveal a locking problem or a slow plugin. Do not run heavy tests against production without permission and a rollback.
Consider a CDN and bot protection
A CDN can serve static assets from nearby locations and absorb some traffic. A web application firewall or bot rules can reduce scraping and brute-force attempts that waste capacity. If you use Cloudflare, check your rules before the sale; the Cloudflare setup guide covers caching and security settings. Do not enable new aggressive rules in the last days, since they can block real customers or payment webhooks.
Days 8 to 6: Checkout, payments, tax and shipping
Checkout is where the money is. Test it as a customer would, not as an admin.
Run the full purchase path
Do these on a real phone and on desktop, as a guest and as a logged-in customer:
- Land on a sale page from an email link or an ad.
- Open a product, pick a variation, add to cart.
- Apply a coupon, remove it, apply it again.
- Change quantity, remove an item, add another.
- Go to checkout, fill in the form, choose shipping.
- Pay with each enabled method.
- Check the thank-you page, the order in the admin, the customer email and the admin email.
- Refund the order.
Repeat after any change. Keep a written script so anyone can run it. For ideas on removing friction before the sale, read the checkout optimisation guide.
Check each payment method and its limits
For every gateway, confirm it is in live mode, the keys are correct, webhooks are reaching your site, and the account has no limits or holds that will bite during a spike. Payment providers can apply review holds or rolling reserves to accounts with sudden volume jumps, and policies vary, so read your provider’s terms and contact them before the sale if you expect a large increase. A wallet button (Apple Pay, Google Pay) usually needs a verified domain, so test it on a real device. The payment gateways comparison helps you check you have a sensible mix, and a backup method is worth having in case one provider has an outage.
Verify tax and shipping rules
Run test orders to your main destinations and compare totals against what you expect. Check that tax is shown correctly, that shipping thresholds (“free shipping over a set amount”) work with discounted totals, and that international rates and restrictions are right. If you sell into the EU or the US, tax rules differ by country and state, and the details change, so confirm with your accountant or the official sources instead of relying on a plugin’s defaults. See the tax setup guide and the shipping setup guide.
Test coupons hard
Coupons are a common source of expensive mistakes. Check that a code cannot stack unexpectedly with a sale price, that usage limits work, that expiry dates and time zones behave, and that a code does not apply to excluded products. Create a few test scenarios: one item, many items, a discounted item, a bundle. Try codes with the wrong case or trailing spaces.
Mind the order of countdowns and promises
If you show a countdown or “ships by” date, check it against your real fulfilment capacity. A promise you cannot keep is worse than no promise. For delivery cut-offs, state them clearly on product and checkout pages.
Days 5 to 4: Inventory, product data and the freeze
Reconcile stock
Count physical stock for your sale items, and compare with the numbers in WordPress. Fix discrepancies now. Decide what happens at zero: hide the product, show “sold out”, or allow backorders. Backorders can be useful, but only if you can state a realistic delivery date. Check that low-stock thresholds and notifications are on, and that stock reduces when an order is placed, not only when it is paid, if your risk of overselling is high.
Check overselling risk
When many customers buy the last few units at once, race conditions can allow more orders than stock, depending on your setup and payment flow. Limit the risk: keep limited-quantity items to a few well-tested products, avoid showing exact stock counts, and be ready with a polite cancellation and refund message. If you sell on several channels at once, sync stock between them, or hold back some units for each.
Prepare product data
Review sale product pages: prices, sale price schedules, images, short descriptions, variation labels, shipping classes and weights. Check that the sale price start and end dates, if scheduled, use the correct time zone. A product with a missing weight can show wrong shipping, and a wrong price can lose real money. Export a copy of your products before bulk edits, so you can restore it. If you use a spreadsheet for bulk edits, test with a handful of products first.
Begin the change freeze
From here, the rules are strict: no new plugins, no theme changes, no major updates. Allow only fixes for bugs you find in testing, and re-run the purchase script after each. Write a short change log so you know what changed and when, in case something breaks.
Days 5 to 4: Email that actually arrives
Transactional emails, such as order confirmations, are the ones customers expect within seconds. Promotional emails drive the sale. Both can fail.
Check deliverability
Send tests of the order confirmation, shipping notification and password reset to several mailbox providers, and check that they arrive in the inbox and not spam. Make sure your domain has proper SPF, DKIM and DMARC records, set up with your email provider’s instructions. WordPress’s default mail function is often unreliable, so many stores send through a dedicated mail service or SMTP plugin. If order emails are not arriving, fix that before anything else, since customers who do not get a confirmation write to support or file a chargeback.
Plan the promotional sequence
A common structure is: a teaser before the sale, a launch email on the day, a reminder near the end, and an extension or “last chance” message. Keep it honest: do not claim scarcity that does not exist. For segmentation and automation, see FluentCRM for email marketing on WordPress or the options in Mailchimp alternatives. Check that your sending limits are enough for your list size, and schedule the sends. If your list is large and you have not sent for a while, warm up by sending to your most engaged subscribers first, to reduce spam-folder risk.
Abandoned cart emails
Abandoned cart flows tend to matter more during sales, since people browse many stores. Review the sequence, discount rules and timing, and test that a cart abandoned on mobile triggers the email and restores correctly. The abandoned cart emails guide gives structure and examples. Make sure the cart recovery does not stack a second discount unintentionally.
Compliance
Marketing emails need consent and an unsubscribe link in most jurisdictions. Check your rules where you operate, and keep consent records. Do not buy lists.
Days 5 to 4: Tracking and analytics
You cannot judge the sale without trustworthy numbers, and tracking breaks without warning.
Test every event
Walk through the purchase path and confirm that the events you rely on fire once: product view, add to cart, begin checkout, purchase. Use your analytics tool’s real-time or debug view. Check for duplicated purchase events, which inflate revenue, and for missing ones, often caused by consent banners, script blockers or caching. Test with and without cookie consent, as your banner may change what is recorded.
Add campaign tagging
Use consistent UTM parameters on email, social and ad links, so you can tell channels apart. Write the naming convention down. Inconsistent names such as “BlackFriday”, “black-friday” and “bf” split your data.
Match revenue across systems
Compare analytics revenue with store orders for a few days. Perfect matches are rare, because of blockers, consent and refunds, but a large gap deserves investigation now. Decide in advance which number is the source of truth: the store’s order data.
Check Search Console and ad platforms
If you run paid ads, confirm that conversion tracking works and that feeds are current, with accurate prices and availability. Mismatched prices between feed and site can lead to disapproved products. Google Search Console for WordPress helps you watch crawl and indexing for the new landing pages.
Days 3 to 2: Fraud, backups, security and monitoring
Plan for fraud
Sale periods attract card testing and stolen-card orders, since fraudsters hope that busy teams review less. Practical steps:
- Turn on the fraud tools your payment provider offers, such as address and security-code checks, and learn how to read their flags.
- Protect checkout from bots that test stolen cards: rate limits, a challenge on suspicious behaviour, and a limit on failed payment attempts. Many security and firewall tools include this; check yours.
- Define a review rule: orders that are high value, ship to a different country than the billing address, use free email providers with unusual patterns, or request express shipping to a new address get a manual look before shipping. Do not ship flagged orders until verified.
- Know the dispute process of your payment provider, including deadlines for submitting evidence, and keep proof of delivery.
Be careful not to over-block, as strict rules reject genuine customers. Start with flags and review rather than automatic cancellation until you see your own patterns.
Harden the site
Update credentials, remove unused admin accounts, check that only needed users have elevated roles, and confirm that your security plugin or firewall is working and not blocking payment webhooks. Review the WordPress security guide and the security plugins comparison for a baseline. Sales are also a time when attackers expect distraction, so check login protection and file-change alerts.
Back up, then test the restore
Take a full backup (files and database) immediately before the freeze ends and again the day before the sale. Confirm where it is stored and that you can restore it. Know how long a restore takes, so you can decide in an emergency whether to roll back or fix forward. A store backup also holds customer data, so store it securely. The backup plugin guide covers options, and for stores, consider backup frequency during the sale: orders arrive constantly, and a restore from yesterday would lose them. Ask your host whether they offer database snapshots, or order exports you can take at intervals.
Set up monitoring and alerts
Use an uptime monitor that checks your home page, a product page and, ideally, the checkout from outside, every minute or so, with alerts to a phone. Also watch for PHP errors and failed payment webhooks. Decide thresholds in advance: if the checkout is down for five minutes, who does what?
Prepare a rollback and a “break glass” plan
Write the steps: how to disable a plugin without admin access (rename its folder over SFTP), how to turn off a coupon, how to switch on maintenance mode, how to put a banner up, how to reach hosting support at speed. Keep these steps where they can be reached if your site is down, not only on the site.
Days 3 to 2: Support preparation
Expect more questions than usual. The aim is to answer common ones before they are asked and to answer the rest fast.
Write the answers in advance
Prepare saved replies and a short FAQ page covering: shipping times and cut-off dates, returns and refunds during the sale, order changes and cancellations, discount code problems, payment declines, and how to track an order. Put key points on product and checkout pages, since a clear promise at the point of purchase prevents tickets.
Decide on policies now
Are sale items returnable? Do you price-match or refund the difference if a price drops after purchase? Do you allow order edits after payment? Whatever you decide, write it in plain words and make it visible. Check consumer rules in your selling countries; for example, many places give distance-selling rights to cancel and return, and the details differ. Confirm them rather than assuming.
Plan capacity
Estimate the support load from your baseline and expect a multiple of it. Schedule who answers when, set realistic auto-reply wording (“we reply within the stated time”), and consider a short-term helper. If you use a help desk or shared inbox tool, set tags for the common issues, so you can find patterns fast. FluentSupport is one option in the same family as other tools mentioned on this site, but any ticketing system works if it is set up in advance.
Keep customers informed automatically
Make sure order status emails are on, include tracking links, and use clear wording. Shipping delays are expected in busy periods, and carriers publish their own cut-off dates, so use theirs.
Day 1: Final checks
- Run the full purchase script on phone and desktop, with each payment method.
- Confirm that sale prices, coupons and schedules start and end at the correct times.
- Check the home page, banners, menu links and sale landing page. Fix typos and dead links.
- Send final test emails, and check that scheduled sends are queued.
- Check stock for hero products and fulfilment readiness: packing supplies, carrier pickup times, staff schedules.
- Confirm monitoring alerts reach the right phone.
- Take a final backup.
- Confirm the host’s support channel and the on-call plan.
- Stop. Resist the urge to tweak.
During the sale: what to watch
Keep a simple dashboard: uptime status, current orders per hour compared to your baseline, checkout error messages, payment failures, email queue, and support inbox size. Check the site yourself every few hours as a customer on a phone.
If something breaks
- Decide quickly whether the problem blocks purchases. If checkout is broken, that comes first.
- Check your change log. The most recent change is the most likely cause.
- Use the quickest safe fix: disable the offending plugin, turn off the coupon, or roll back.
- Put a banner up if customers are affected, and communicate honestly.
- Write down what happened for the review afterwards.
If the site is unreachable, contact your host immediately, and consult the plugin conflict troubleshooting guide for isolating a cause. Do not make large changes under pressure unless you must.
After the sale: close the loop
- Reconcile. Compare orders, payments, refunds and stock. Fix discrepancies.
- Fulfil. Ship in order of promise, and keep customers informed.
- Review. Compare results with your baseline: traffic, conversion, average order value, support volume, errors. Note what you would change.
- Follow up. Send thank-you and review-request emails at sensible times, and think about how to bring first-time buyers back.
- Lift the freeze deliberately. Resume updates on staging first.
The broader store guidance in our WooCommerce Black Friday prep plan can be read alongside this one, and it is worth keeping the notes for next year.
Common mistakes
- Launching a redesign or a new plugin the week before the sale.
- Testing only as an admin, on a fast desktop connection.
- Assuming email works because it did last month.
- Leaving payment accounts unchecked, then hitting a hold during peak.
- Caching the cart or checkout, or leaving stale sale pages cached.
- Ignoring time zones in sale start and end times.
- Promising delivery dates that carriers cannot meet.
- Not having a named person who can make decisions on the day.
FAQ
When is Black Friday 2026?
Black Friday is the day after US Thanksgiving, which is the fourth Thursday of November. In 2026, that makes Black Friday 27 November and Cyber Monday 30 November. Many stores begin early or run the offers for a week or more, so choose dates that suit your audience and your fulfilment capacity.
How early should I stop making changes to my store?
A week before the sale is a sensible target for a change freeze, with only essential bug fixes allowed after that. If your store is simple and your testing is quick, a shorter freeze can work, but be strict about it. The risk of a last-minute change is higher than the benefit in almost every case.
Should I upgrade my hosting before Black Friday?
Ask your host about your current limits and what happens when you hit them. If you have struggled with traffic before, a temporary or permanent upgrade is reasonable. Avoid a migration in the final week, since a move is a risk by itself. If you do upgrade, retest the purchase path afterwards.
How do I stop fake orders and card testing?
Use your payment provider’s fraud tools, limit failed payment attempts, add bot protection on checkout, and review unusual orders before shipping. Start with flags and manual review so you do not block real buyers. Also learn your provider’s dispute process in advance, as deadlines are short.
What should I test most carefully?
The purchase path on a real phone: product, cart, coupon, checkout, payment, confirmation email. After that, test the things that fail silently: tracking events, webhook delivery, and email deliverability. A site that looks fine can still lose orders or data.
Do I need to load test my WordPress store?
It is useful but not mandatory for small shops. At minimum, ask your host about concurrency limits, and test with several simultaneous orders on staging. If you run a load test, get your host’s permission first, and do not run heavy tests on a live store without a rollback plan.
How should I handle stock for limited items?
Count physical stock, correct the numbers in WordPress, and decide in advance what happens at zero. Keep limited-quantity items few and well tested, since heavy simultaneous demand can lead to overselling. Prepare a polite message and a refund process in case it happens.
Is it too late to start if the sale is two weeks away?
No. This plan is designed for two weeks. Do the testing and the things that fail silently first, skip nice-to-have optimisations, and be honest about what you cannot finish. A simple store that works is better than an ambitious one that breaks.
Conclusion and next steps
To prepare your WordPress store for Black Friday 2026 in two weeks, decide the offer, set a change freeze, fix the biggest performance problems, test the full purchase path on a phone, reconcile stock, verify email and tracking, plan for fraud, back up and monitor, and write answers to the support questions you can already predict. Then stop changing things and watch.
Start today with three actions: write down the freeze date and the owners, run the purchase script on your phone, and send test order emails to a few inboxes. For deeper background, see checkout optimisation and the WordPress speed optimisation guide, and keep notes as you go, because next year’s plan starts with what you learn this year.
Let your AI assistant do this for you
Open the ready prompt with step‑by‑step instructions for running it through NibWP.