Tag Archives: Maintenance

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

A Plugin Update Broke Your WooCommerce Checkout? The Safe Update Playbook

It’s Monday morning. Weekend sales look oddly quiet. You try a test purchase and the checkout spins forever, or shows a blank error, or the Place order button does nothing at all.

You check the plugin list. Three plugins auto-updated on Friday night.

This is one of the most common and most expensive things that happens to WooCommerce stores, and it’s rarely discussed honestly. The update itself usually takes a few minutes to fix. The real cost is the hours or days between the break and someone noticing. During that time your ads keep running, your emails keep sending people to a dead checkout, and every visitor who tries to buy leaves.

This guide covers two things: how to recover quickly when an update has already broken checkout, and how to update in a way that makes it almost impossible to lose a weekend again.

Why updates break checkout in particular

Checkout is the most fragile page on a WooCommerce store because it’s where everything meets:

  • your theme (templates, scripts, styles)
  • WooCommerce itself (classic shortcode or block-based checkout)
  • the payment gateway plugin and its JavaScript
  • shipping, tax, coupon and fee plugins that change totals
  • checkout field editors, address validators and upsell plugins
  • caching and optimization plugins that combine, defer or delay scripts
  • security plugins and CAPTCHAs that intercept requests

An update to any one of them can break the interaction with another. A few patterns cause most incidents:

  1. JavaScript errors. One plugin’s updated script throws an error, and everything after it stops running, including the payment form.
  2. Optimization plugins delaying or combining a gateway’s script so the card field never loads.
  3. Template overrides. Your theme overrides a WooCommerce template that changed, leaving the checkout using an outdated version.
  4. Block vs classic mismatches. An extension supports one checkout type but not the other.
  5. PHP fatal errors on the checkout or the Store API endpoint after a PHP or plugin version jump.
  6. Payment gateway changes that require new settings, new webhooks or reconnection.

What merchants report

Browse r/woocommerce or the WordPress.org support forums and the same stories repeat:

  • “Checkout spinner never stops after update.” Usually a JavaScript error in one plugin stopping the payment script.
  • “Card field disappeared.” Frequently an optimization plugin delaying or combining the gateway’s script.
  • “Customers can pay but no order is created.” A fatal error after payment, or a webhook endpoint broken by a security plugin update.
  • “Block checkout broke but the classic shortcode works.” An extension that doesn’t yet support the Store API that block checkout relies on.
  • “It only fails for logged-in customers” (or only on mobile, or only for one payment method). That’s the hardest kind to spot, because the owner’s own quick test passes.

The common thread is that the store owner discovered the problem from customers or from falling sales, not from any tool. That’s the gap worth closing.

The silent part

Here’s why these incidents last so long. When checkout breaks, almost nothing looks broken:

  • The home page loads, so your uptime monitor stays green.
  • Product pages load, so casual checks look fine.
  • Traffic continues, so analytics looks normal at a glance.
  • No orders means no failed orders, so WooCommerce shows nothing unusual. It just shows… less.

The only signal is an absence: fewer orders than usual. Absences are hard for humans to notice, especially at weekends.

Already broken? Recover in this order

1. Confirm and capture the error (5 minutes)

  • Try checkout in a private window as a guest and as a logged-in customer.
  • Open your browser’s developer tools Console tab and note any red errors, especially ones naming a plugin.
  • Check WooCommerce → Status → Logs for fatal errors since the update.
  • Note which plugins, theme or WooCommerce version changed, and when (your host’s logs or the plugin list will show recent updates).

2. Restore sales first, diagnose second

Your priority is taking money again, not finding the perfect fix.

  • If you know which update caused it, roll that plugin back to the previous version (many hosts keep backups; some plugins offer rollback; you can also reinstall a previous version from the plugin’s WordPress.org page under Advanced View).
  • If you don’t know, restore the most recent pre-update backup of files and database if no orders have arrived since, or roll back the updated plugins one at a time.
  • If an optimization plugin is involved, exclude checkout and cart pages from script delay/combine features, or temporarily disable it.

3. Confirm with a real purchase

Place a real order with a real card (then refund it), or use a 100% coupon if your gateway supports zero-value orders. Confirm the order arrives as Processing, the confirmation email arrives, and the gateway shows the payment.

4. Measure the damage

Compare orders per day with the same days in previous weeks to estimate lost sales. Check for orders that did come through during the outage but are incomplete: stuck on Pending payment, missing emails, or duplicated by frustrated customers who tried several times. (See WooCommerce order stuck on pending payment.)

5. Tell affected customers

If abandoned-cart emails captured anyone, a short “sorry, our checkout had a problem, it’s fixed now” with a small discount often recovers a surprising number of sales.

What a silent outage really costs

Bar chart of lost sales for the same broken checkout: about $25 if noticed in 15 minutes, $360 if noticed the same evening, and about $5,670 if noticed Monday morning after 63 hours, for a store making about $90 an hour.

It’s worth putting a number on this, because it changes how seriously teams treat updates.

Suppose your store averages 40 orders a day at $55 each: about $2,200 a day, or roughly $90 an hour. A plugin auto-updates at 18:00 on Friday and breaks the payment form. Nobody checks until 09:00 Monday. That’s 63 hours. At normal weekend volume you’ve lost something like $5,000–$6,000 in sales, plus the ad spend that sent people to a dead checkout, plus the customers who tried, failed, and won’t come back.

The same break noticed in 15 minutes costs about $25.

The update was identical in both cases. The only difference was detection time. That’s why the playbook below spends as much effort on noticing as on preventing.

A five-step test purchase script

Write this down and keep it where whoever updates the store can find it. Adapt the products and methods to your store.

  1. Product page: open your best-selling product in a private window. Choose a variation if it has one. Click Add to cart. Confirm the cart count changes.
  2. Cart: open the cart. Apply a coupon you keep for testing. Confirm the total updates and shipping options load for a typical address.
  3. Checkout: go to checkout. Confirm the payment form (card field, PayPal button, wallets) appears without console errors.
  4. Pay: complete payment with your normal method (refund afterwards), or with your test coupon set to 100% if your gateway supports zero-value orders.
  5. After: confirm the order is Processing, the customer email arrives, the admin email arrives, and the gateway shows the payment.

If you sell to logged-in customers or use several payment methods, repeat steps 3–5 for the most-used variations. The whole thing takes five minutes, and it’s the cheapest insurance a store can buy.

The safe update playbook

Cycle of five steps repeated for each group of updates: back up, update one group (core, gateway, checkout plugins, the rest), run a test purchase, check the browser console and logs, and watch for 24 hours. Weekday mornings only, never Friday night.

The goal isn’t to stop updating. Outdated plugins are a security risk and accumulate bugs. The goal is to find breakage in minutes, on your schedule, not days later by accident.

Rule 1: Don’t let checkout-critical plugins auto-update unattended

Auto-updates are great for low-risk plugins. For WooCommerce itself, your theme, payment gateways, and anything that touches cart or checkout, update manually, on a weekday morning, when someone can test immediately. Never on Friday afternoon.

Rule 2: Stage first when you can

If your host offers one-click staging, update there first and run through the purchase flow. Use test payment keys on staging, never live ones.

Rule 3: Update one group at a time

Update WooCommerce core, then test. Then the gateway, then test. Then everything else. If something breaks, you know exactly which change caused it.

Rule 4: Back up immediately before updating

A fresh backup turns a disaster into a five-minute restore.

Rule 5: Run the same test purchase after every update

Write down a five-step test: add product → cart → checkout → pay → confirm order and email. Run it every time. Takes three minutes.

Rule 6: Watch the next 24 hours

Some breaks only affect certain browsers, payment methods, products or customer types. Keep an eye on orders and errors for a day after significant updates.

Rule 7: Have monitoring that notices for you

Rules 1–6 depend on people remembering. The last line of defence should be automatic: something that checks checkout on a schedule and notices when orders stop.

Automating the “notice” part with Ordafide Pro

Ordafide Pro is built for exactly the failure in this article: the store is up, but it has stopped taking money.

  • Synthetic checkout monitoring runs every 15 minutes, checking your shop, product, cart and checkout pages and the Store API used by block checkout, with response-time tracking. An optional deep mode adds a test product to a cart. It never places an order, so your data stays clean. A finding is raised only after two consecutive failures, so a single blip doesn’t wake anyone.
  • Order volume anomaly detection compares each hour’s orders with comparable past hours using median-based statistics and flags drops. That’s the absence-of-orders signal humans miss, and it catches breaks that a page check can’t see, such as a payment method failing silently for some customers.
  • Alerts go to Slack, SMS, email or a signed webhook (Discord, Teams, PagerDuty and others), with severity routing and throttling.
  • A signed heartbeat endpoint lets an external monitor confirm Ordafide’s own checks are still running, so you’d know if a broken update took the monitoring down too.

The free Ordafide plugin covers the aftermath. After any update, a scan finds the orders that slipped through badly: stuck payments, paid-but-cancelled orders, duplicate charges from frustrated customers retrying, order totals that no longer add up (common when a coupon, tax or fee plugin misbehaves), and paid customers who never got a confirmation email. It also reports the health of the background job queue, which some updates quietly break.

Your update-day checklist

Before

  • [ ] It’s a weekday morning, and someone is available for a few hours
  • [ ] Fresh backup taken
  • [ ] Changelogs skimmed for WooCommerce, gateway and checkout plugins
  • [ ] Staging updated and tested first (if available)

During

  • [ ] Update in groups: core → gateway → checkout-related → the rest
  • [ ] Test purchase after each group
  • [ ] Browser console checked for errors on checkout

After

  • [ ] Real or zero-value order placed, email received, gateway checked
  • [ ] Ordafide scan run for stuck, duplicate or mis-totalled orders
  • [ ] Orders watched for 24 hours (or monitoring/alerts confirmed active)