Tag Archives: Checklist

WooCommerce Black Friday Readiness: The Orders, Payments and Checkout Checklist

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).

Bar chart from Adobe Analytics 2025: Black Friday $11.8 billion, Cyber Monday $14.25 billion, Cyber Week $44.2 billion. 57.5% of Cyber Monday sales came from mobile and buy now pay later reached $1.03 billion on Cyber Monday.

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

Four-phase timeline. Two to four weeks before: update, test and freeze; verify webhooks and firewall; real server cron; CAPTCHA and rate limits; clean-slate scan. Week before: final test purchase, backup and restore test, on-call rota, alerts tested. Black Friday to Cyber Monday: two-hourly checks or automated alerts; restore sales first. Week after: full scan and reconcile, check stock, resume updates, prepare returns.

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)

  1. 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.
  2. Pending / Failed / Cancelled: any real customers with payment references?
  3. Scheduled Actions: is the past-due count climbing?
  4. Email log: are confirmations going out?
  5. 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

  1. Restore sales first. Roll back the last change, disable the offending plugin, or switch to a backup payment method. Diagnose later.
  2. Communicate. A banner or email (“We had a brief checkout issue; it’s fixed, and your discount still applies”) recovers lost buyers.
  3. 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

The 15-Minute Weekly WooCommerce Order Health Check (Free Checklist)

Most WooCommerce maintenance advice is about the site: update plugins, back up the database, optimize images, check uptime. That’s all sensible. But it misses the thing that actually pays the bills: are the orders right?

A store can be fast, secure, fully updated and perfectly backed up while quietly:

  • leaving paid orders on Pending payment,
  • charging some customers twice,
  • shipping orders that were already refunded,
  • never emailing receipts,
  • and recording totals that don’t match the money.

None of these produce error messages. They show up as customer complaints, chargebacks and reconciliation gaps weeks later.

This article gives you a 15-minute weekly routine for checking order health, explains what each step catches and why, and shows how to automate most of it so it keeps happening on the busy weeks too.

Why weekly?

  • Daily is ideal for high-volume stores, but it’s rarely sustained by hand.
  • Monthly is too slow. Customers who paid and received nothing won’t wait a month.
  • Weekly catches most problems while customers are still patient, and it’s frequent enough to become a habit.

Pick a fixed slot (Monday at 10:00 works well, after the weekend’s orders) and put it in the calendar.

The 15-minute routine

Timeline of a 15-minute weekly routine: paid but not moving (3 minutes), On hold, duplicates, refunds, background queue and email, totals, and order volume (2 minutes each). Do it at the same time every week, or let the Ordafide weekly summary do the checking.

Minute 0–3: Orders that are paid but not moving

Check: filter WooCommerce → Orders by Pending payment, Failed and Cancelled for the last 7–10 days. Open any that look like real customers (real names, sensible addresses, not card-testing junk).

Look for: a gateway transaction ID, a payment note, or a paid date on an order that isn’t Processing or Completed.

Why: these are customers who paid and won’t receive anything. Webhook failures and the Hold stock auto-cancel timer are the usual causes. (Full guide)

Action: verify in the gateway, move to Processing, resend the confirmation email, apologize.

Minute 3–5: The On hold queue

Check: filter by On hold.

Look for: bank transfers you haven’t matched, card authorizations that need capturing before they expire, payments that are actually settled at the gateway.

Why: On hold orders fall outside the Processing queue your team works from. (Full guide)

Minute 5–7: Duplicates

Check: sort recent orders by customer or email and scan for the same customer, same total, minutes apart.

Look for: two orders with the same transaction ID (one payment, two orders) or two different transaction IDs (charged twice).

Why: duplicate charges are a leading cause of “duplicate processing” disputes. (Full guide)

Minute 7–9: Refunds that don’t add up

Check: filter by Refunded and spot-check a few for refund records. Then look at Processing orders older than your normal fulfilment time for red refund lines.

Look for: “Refunded” orders with no refund, fully refunded orders still in Processing, refunds larger than the order.

Why: refunded orders get shipped; promised refunds never arrive. (Full guide)

Minute 9–11: The background queue and email

Check: WooCommerce → Status → Scheduled Actions → Pending. Are there many past-due actions? Check the Failed tab too. Then send yourself a test email from your SMTP plugin.

Why: when the queue stalls, emails, stock updates and some payment processing stop, silently. (Full guide)

Minute 11–13: Totals

Check: open three or four recent orders that used a coupon, a different currency, or an unusual shipping method. Do items − discounts + shipping + fees + tax equal the total?

Why: pricing, tax and currency plugins can leave orders that don’t add up. ([Full guide](/blog/woocommerce-order-total-wrong/))

Minute 13–15: Volume sanity check

Check: compare this week’s order count and revenue with the same week last month or last year in WooCommerce → Analytics. Look at day-by-day: is there a day with suspiciously few orders?

Why: a day with almost no orders is often a broken checkout nobody noticed. A day with hundreds of failed orders is often card testing. (Checkout guide · Card testing guide)

What you’ll typically find (and what to do)

Here are the kinds of findings a first audit usually turns up on an established store, and how to handle each one.

“Order #5520, Cancelled, $142. Order notes show a Stripe payment ID.”
The webhook didn’t arrive within the Hold stock window, so WooCommerce cancelled a paid order. Check Stripe: payment succeeded. Restore to Processing, check stock, resend the confirmation, ship, and email an apology. Then find out why the webhook failed. One stuck order usually means others.

“Orders #5531 and #5532, same customer, $38 each, 40 seconds apart, different transaction IDs.”
A genuine double charge. Confirm with the customer that they wanted one, refund #5532 from the order screen, and look at checkout speed.

“Order #5490, Processing, $95. Refunded in full four days ago.”
Stop! Make sure it isn’t in today’s picking list. Change the status to Refunded (carefully, so you don’t trigger a second refund) and find out who refunded it and where.

“Scheduled Actions: 1,240 past-due.”
The queue isn’t running. Check `DISABLE_WP_CRON`, set up a real server cron, and let the backlog drain. Then check whether any customers missed confirmation emails during the stall.

“Order #5544: items + shipping + tax = $72.40; stored total = $67.40.”
A discount was applied without a matching line. Check which pricing plugin did it, and whether other orders are affected.

The first audit is usually the biggest. After that, weekly findings tend to be small and quick, and anything unusual stands out clearly.

Adapting the routine to your store size

  • Under ~20 orders a week: you can open every order. The routine takes 10 minutes. Focus on paid-but-not-moving and refunds.
  • Hundreds of orders a week: sampling stops working. Use filters, sort by customer, and lean on automated checks for full coverage.
  • Thousands of orders a week: a weekly manual check is too slow. Problems need finding in hours, not days. Automate the checks, set alerts, and keep the weekly slot for reviewing trends and fixing root causes.
  • Multiple stores: script it. Running the same check by hand across stores doesn’t last more than a few weeks.

Keep a simple log

Write down what you found each week: date, issue, number of orders, money involved, cause, fix. After a month or two, patterns emerge. Maybe the same gateway keeps leaving orders stuck, or duplicates cluster on mobile. The log turns firefighting into fixing.

Week Issue Orders Value Cause Fixed?
3 Nov Paid but cancelled 2 $118 Webhook blocked by WAF Yes: WAF rule
10 Nov Duplicate charge 1 $45 Double click, slow checkout Refunded; investigating speed
17 Nov None found

Why manual audits fail (and what to do about it)

Comparison. Manual audits get skipped in busy weeks, sample a few orders, can't see gateway-only problems, find issues days late and depend on one person. Automated checks run every time, cover every recent order, compare with the gateway in Pro, alert within the hour in Pro and send a weekly summary.

Be honest: will this routine still happen in the week before Christmas? During a product launch? When you’re ill?

Manual audits have predictable weaknesses:

  • They’re skipped when you’re busy, which is exactly when problems are most likely and most expensive.
  • They’re sampled. You can’t open every order, so you check a few and hope.
  • They miss the invisible. Payments with no order, refunds only at the gateway, and charges that differ from the order can’t be seen from WooCommerce screens at all.
  • They’re slow to react. A weekly check means a problem that starts on Tuesday is found next Monday.

The fix is to automate the checks and keep the human part for deciding and acting.

Automating the routine with Ordafide

[Ordafide Order Integrity for WooCommerce](https://wordpress.org/plugins/ordafide-order-integrity-for-woocommerce/) is a free plugin that does most of the routine above automatically, across every recent order, not a sample:

Routine step Ordafide (free)
Paid but not moving Stuck payment and Paid but cancelled checks
Duplicates Duplicate charge check
Refunds Refund mismatch check
Queue and email Store health: Action Scheduler backlog and failures, WP-Cron status, loopback test, and an order email delivery log with one-click resend
Totals Order total does not add up check with a rounding tolerance

Findings appear in one inbox, sorted by money at risk, each with the evidence and what to check before touching anything. There’s an optional weekly summary email, sent only when there’s something to report, so the routine comes to you. For developers and agencies, WP-CLI commands (`wp ordafide scan`, `wp ordafide findings`, `wp ordafide health`, `wp ordafide digest`) let you script it.

Your 15 minutes becomes: open the weekly summary, work through the findings, done.

Ordafide Pro covers the remaining steps that the free plugin structurally can’t:

  • Gateway reconciliation (Stripe, PayPal, Square, Mollie, Razorpay) for the invisible cases: money with no order, paid orders with no payment, amount disagreements, refunds missing in WooCommerce.
  • Order volume anomaly detection for the “suspiciously quiet day” and “overnight spike” checks, hourly rather than weekly.
  • Synthetic checkout monitoring every 15 minutes, so a broken checkout is found in minutes.
  • Real-time alerts to Slack, SMS, email or webhook, so urgent problems don’t wait for Monday.

Making it stick

A routine only works if it survives busy weeks. A few things help:

  • Give it an owner. One named person, with a named backup for holidays.
  • Put it in the calendar as a recurring meeting with yourself. A fixed slot is far more likely to happen than “sometime on Monday”.
  • Start with the weekly summary email. If Ordafide’s weekly summary arrives and lists nothing, the routine takes two minutes. If it lists findings, you know exactly where to start.
  • Track time saved. Note how long each issue took to fix when found early, versus the customer complaints and disputes you used to handle. It keeps the habit motivated.
  • Review the log monthly. Repeated causes deserve a permanent fix, not another weekly repair.

The aim isn’t to spend 15 minutes a week forever. It’s to fix the causes so the weekly check becomes boring. A boring audit means a healthy store.

The printable checklist

Weekly order health check: 15 minutes

  • [ ] Pending / Failed / Cancelled: any with payment evidence?
  • [ ] On hold: every order has a reason and a next step?
  • [ ] Duplicates: same customer, same basket, minutes apart?
  • [ ] Refunded: every one has a refund record?
  • [ ] Processing: any with refund lines?
  • [ ] Scheduled Actions: past-due backlog or failures?
  • [ ] SMTP test email delivered?
  • [ ] Sample totals add up (coupon, currency, unusual shipping)?
  • [ ] Order volume normal day by day?
  • [ ] Log updated with anything found