Black Friday and Cyber Monday are the days when everything in your store is under the most pressure, and when a failure costs the most.
The numbers are big even at a national level. Adobe reported that US shoppers spent $11.8 billion online on Black Friday 2025 and $14.25 billion on Cyber Monday, with the five days from Thanksgiving to Cyber Monday reaching $44.2 billion. 57.5% of Cyber Monday online sales came from mobile devices, and buy-now-pay-later passed $1 billion on that one day (Adobe, December 2025).

For your store, the arithmetic is simpler: if you normally make a week’s revenue over Cyber Week, then one hour of broken checkout on Black Friday can cost more than a whole normal day. And peak is exactly when the conditions for failure are worst: maximum traffic, maximum plugin activity (discounts, countdowns, popups), maximum payment volume, and minimum spare attention from you.
Most Black Friday checklists cover marketing, hosting and caching. This one covers the part that turns traffic into money: orders, payments, webhooks, email and checkout, before, during and after peak.
What goes wrong at peak (and why)
| Failure | Why peak makes it worse |
|---|---|
| Checkout breaks after a last-minute plugin change | Changes made in a rush, under pressure, often on a Friday |
| Payment webhooks blocked | WAF and bot protection set to aggressive mode to handle traffic, and they block gateway servers too |
| Paid orders auto-cancelled | Slower webhooks + a 60-minute Hold stock timer + high volume = more paid orders cancelled |
| Duplicate charges | Slow checkout under load → more double clicks and request replays |
| Background queue backlog | Thousands of scheduled actions (emails, stock, analytics) pile up faster than WP-Cron runs them |
| Confirmation emails delayed | Queue backlog and mail provider sending limits |
| Discount math wrong | Several discount, BOGO and pricing plugins interacting for the first time |
| Card testing attacks | Attackers know merchants are distracted and volume hides their traffic |
| Overselling | Stock held by stuck orders, or not restored by cancelled ones |
Phase 1: Two to four weeks before

Freeze the stack early
- Finish all plugin, theme and WooCommerce updates at least two weeks before Black Friday, test them, then freeze. Only security fixes after that point.
- Turn off auto-updates for WooCommerce, your theme, payment gateways and checkout-related plugins until after Cyber Monday. (Safe update playbook)
- Install and configure any sale-specific plugins (countdown timers, BOGO, gift with purchase) now, not the night before, and test them with every coupon you plan to run.
Test checkout like a customer, on every path
- Guest and logged-in; desktop and mobile (more than half of peak sales are mobile)
- Every payment method: cards, PayPal, wallets (Apple Pay, Google Pay), BNPL
- Each sale coupon and discount rule, including combinations you didn’t intend to allow
- Confirm totals add up: items − discounts + shipping + fees + tax = total = charge (Guide)
Harden payment confirmations
- Check each gateway’s webhook delivery log. Any recent failures? Fix them now.
- Make sure your WAF/bot protection allows gateway webhook traffic on the webhook paths, and keeps allowing it if you switch to a stricter “under attack” mode during peak.
- Re-confirm webhook signing secrets if the site has been migrated or cloned this year.
- Review Hold stock (minutes) under WooCommerce → Settings → Products → Inventory. If you use slower methods (BNPL, bank-based), consider raising it for peak so paid-but-slow orders aren’t cancelled. (Why this matters)
Make the background queue peak-proof
- Replace visitor-triggered WP-Cron with a real server cron running every minute or few minutes.
- Clear any existing past-due backlog in Scheduled Actions.
- Confirm your SMTP/email API plan can handle peak volume (order emails + marketing emails) without hitting sending limits. (Guide)
Protect against card testing
– CAPTCHA protecting checkout and the Store API, updated to a version that supports block checkout.
– Store API rate limiting enabled (and proxy mode if you’re behind a CDN).
– Gateway fraud rules reviewed. (Guide)
Clean the slate
Run a full order integrity scan now and fix everything it finds, so that during peak, any new finding is new. The free Ordafide plugin checks recent orders for stuck payments, paid-but-cancelled orders, duplicate charges, refund mismatches, total mismatches and un-emailed customers, and shows background queue and email health.
Test mobile and BNPL properly
Because mobile and buy-now-pay-later both peak at the same time, they deserve their own test pass:
- Test on real phones, iOS and Android, not just a resized desktop browser. Wallet buttons (Apple Pay, Google Pay) only appear on supported devices.
- Check that popups, countdown banners and cookie notices don’t cover the Place order button or the payment form on small screens.
- Complete a BNPL purchase end to end. These methods often redirect away from your site and confirm asynchronously, so they’re more exposed to webhook and Hold stock problems than card payments.
- Confirm the confirmation email renders properly on mobile mail apps.
Agree what “normal” looks like
Before peak, note your typical orders per hour at different times of day, and roughly what you expect over the sale. During peak, it’s surprisingly hard to tell whether “40 orders this hour” is great or a sign something’s wrong. Having a baseline written down makes the two-hourly check meaningful. That’s also exactly what anomaly detection automates.
Phase 2: The week before
- [ ] Final full test purchase on every payment method, then no more changes
- [ ] Fresh full backup, and a tested restore procedure
- [ ] Host told about expected traffic; ask about resource limits and their peak support process
- [ ] Gateway contact details and dashboard logins to hand
- [ ] On-call plan: who checks orders when, across the whole weekend
- [ ] Team refund rule reconfirmed: refunds from the WooCommerce order screen only (Why)
- [ ] Alerts tested end-to-end: does the alert actually reach a phone?
Decide your peak-time rules in advance
Decisions made at 2 a.m. under pressure are rarely good ones. Agree these before the sale starts:
- Who can change the site during peak? Ideally nobody except for emergencies, and only one named person.
- What counts as an emergency? Checkout down, payments failing, orders not being created. Not “the banner colour looks off”.
- What’s the rollback plan? Which backup, which plugin versions, who does it.
- When do you switch payment methods? If your main gateway has an outage, is there a secondary method ready to enable?
- Who answers customers? A prepared reply for “my payment went through but I didn’t get a confirmation” saves time and calms people down.
Phase 3: During peak (Black Friday to Cyber Monday)
The two-hourly check (5 minutes)
- Order volume: are orders arriving at roughly the rate you expect for the time of day? A sudden flat line means checkout trouble. A sudden flood of failed orders means card testing.
- Pending / Failed / Cancelled: any real customers with payment references?
- Scheduled Actions: is the past-due count climbing?
- Email log: are confirmations going out?
- A quick test of the cart and checkout on mobile.
It’s tedious and easy to skip at 2 a.m., which is the case for automating it.
Automate the watching with Ordafide Pro
Ordafide Pro is built for exactly this weekend:
- Synthetic checkout monitoring every 15 minutes: shop, product, cart, checkout and the Store API, with response times so you can see the site slowing under load. Optional deep mode adds a product to a cart. It never creates orders, so your peak data stays clean, and it waits for two consecutive failures before raising a finding.
- Order volume anomaly detection: compares the current hour with comparable past hours using median-based statistics, flagging drops (broken checkout) and spikes (card testing). Median-based baselines are less distorted by one exceptional day than simple averages.
- Gateway reconciliation (Stripe, PayPal, Square, Mollie, Razorpay) with read-only keys: money with no order, paid orders with no payment, amount disagreements, refunds missing in WooCommerce.
- Alerts via Slack, SMS, email or signed webhook, with severity routing and throttling, so a real problem reaches your phone and minor ones wait for morning.
If something breaks during peak
- Restore sales first. Roll back the last change, disable the offending plugin, or switch to a backup payment method. Diagnose later.
- Communicate. A banner or email (“We had a brief checkout issue; it’s fixed, and your discount still applies”) recovers lost buyers.
- Sweep up. Run an integrity scan to find orders caught mid-failure: stuck, duplicated, cancelled-but-paid, un-emailed.
Phase 4: The week after
- Full integrity scan across the whole peak period. Fix every stuck payment, duplicate and refund mismatch while customers are still waiting patiently rather than disputing. (Self-inflicted chargebacks)
- Reconcile WooCommerce against each gateway for the peak period. (Reconciliation guide)
- Check stock for drift caused by cancelled and stuck orders.
- Re-enable updates and catch up carefully, one group at a time.
- Prepare for returns. Holiday returns arrive in December and January. The NRF and Happy Returns expected about 17% of 2025 holiday merchandise to be returned. Our sister plugin Recirco has a holiday returns guide.
- Write a short post-mortem: what broke, how fast you noticed, what to change before next year.
The one-page checklist
2–4 weeks out
- [ ] Updates done and tested; stack frozen; auto-updates off for critical plugins
- [ ] Sale plugins installed and tested with every coupon
- [ ] Checkout tested on every device, customer type and payment method
- [ ] Webhooks verified; WAF allows gateway traffic; secrets correct
- [ ] Hold stock timer reviewed
- [ ] Real server cron; Scheduled Actions backlog cleared; email capacity checked
- [ ] CAPTCHA + Store API rate limiting on
- [ ] Integrity scan run and all findings fixed
Week before
- [ ] Final test purchase; change freeze
- [ ] Backup and restore tested
- [ ] On-call rota and alert test
During
- [ ] Two-hourly checks, or automated monitoring with alerts
After
- [ ] Integrity scan and gateway reconciliation for the whole period
- [ ] Stock checked; updates resumed carefully
- [ ] Returns process ready; post-mortem written

