Here’s a scenario that plays out on WooCommerce stores every day.

A plugin auto-updates overnight. The home page loads. Product pages load. Your uptime monitor shows a green tick. But the checkout throws a JavaScript error, or the payment step silently fails, or the cart empties itself on the way to checkout.

You find out two days later, when someone finally emails to say they couldn’t pay. Or you don’t find out at all, and just wonder why sales were slow that week.

Uptime is not the same as “customers can buy.” This guide explains what actually needs monitoring on a WooCommerce store, the free and paid ways to do it, and a practical setup for both single stores and agencies.

Why uptime monitoring isn’t enough

A typical uptime monitor requests your home page every few minutes and checks it returns a 200. That catches a crashed server. It misses almost everything that loses money in WooCommerce:

• A broken cart or checkout page (PHP or JavaScript error on one page only)
• A payment gateway that’s misconfigured, expired, or rejecting every payment
• Webhooks being blocked, so paid orders never advance
• The WooCommerce Store API failing, which block-based cart and checkout rely on
• Background jobs stalling, so emails and stock updates stop
• Caching serving a stale or broken checkout page
• A sudden drop in orders because something upstream broke (ads, DNS for a payment script, a geo-blocking rule)

What to monitor on a WooCommerce store

Think about it in four layers.

Layer 1: Can people reach the buying pages?

Not just the home page, but shop, a product page, cart, and checkout, plus the Store API endpoints the block checkout uses. Each should load quickly and without errors.

Layer 2: Can they get to the payment step?

The real test is adding a product to the cart and reaching checkout. That’s where most plugin conflicts show up. This is called synthetic monitoring: a script behaves like a shopper on a schedule.

A word of caution: synthetic tests should not place real orders. Test orders pollute your reports, trigger fulfilment, and can create real charges. Good synthetic checks stop before payment.

Layer 3: Are orders that come in actually correct?

Orders can be created and still be wrong: stuck on Pending payment, charged twice, cancelled despite payment, missing a confirmation email. That needs integrity checks on the orders themselves. (See stuck pending orders) and double charges.)

Layer 4: Is order volume normal?

Sometimes nothing is technically “broken” by any test, but orders stop anyway. Comparing the current hour’s orders against comparable past hours (same day of week, same time of day) catches drops and spikes that point to a problem. The trick is avoiding false alarms on naturally quiet hours, which is why median-based comparisons work better than simple averages.

Alerts: the part people get wrong

Monitoring is useless if the alert goes to an inbox nobody reads, and equally useless if it fires so often everyone mutes it. Good alerting means:

• The right channel: Slack or SMS for “checkout is down,” email for “weekly summary.”
• Severity routing: urgent things wake someone, minor things wait.
• Confirmation before alerting: one failed check could be a blip. Two in a row is a problem.
• Throttling: one alert per issue, not one every five minutes.
• A delivery log: so you can prove an alert was sent.

A free starting setup

You can get decent coverage for free:

1. An uptime monitor on your home page *and* your checkout URL.
2. WooCommerce → Status → Scheduled Actions checked weekly for past-due actions.
3. ‘Tools → Site Health’ checked for loopback and REST API problems.
4. [Ordafide Order Integrity for WooCommerce] (free) to scan orders for stuck payments, paid-but-cancelled orders, duplicate charges, refund mismatches, total mismatches, and customers who were never emailed. It also shows background queue and email delivery health, and sends an optional weekly summary when there’s something to report.
5. A manual test purchase after every significant update, using a coupon to make it zero-cost or refunding immediately.

That covers layers 1 and 3 reasonably well. It leaves gaps in layers 2 and 4, and it relies on someone remembering to look.

A complete setup

[Ordafide Pro](https://www.premium-themes.co/ordafide-order-integrity-for-woocommerce/) fills those gaps:

• Synthetic checkout monitoring every 15 minutes across shop, product, cart, checkout and the Store API, with response-time tracking. An optional deep mode adds a test product to a cart. It never creates orders, and a finding is raised only after two consecutive failures.
• A signed heartbeat endpoint so an external monitor can confirm the store’s own checks are still running.
• Order volume anomaly detection that compares the current hour with comparable past hours using median-based statistics, flags drops and spikes, and resolves itself when things return to normal.
• Alerts via Slack, SMS (Twilio), signed webhooks (for Discord, Microsoft Teams, PagerDuty and similar) and email, with severity routing, per-check throttling, retries and a delivery log.
• Read-only gateway reconciliation with Stripe, PayPal, Square, Mollie and Razorpay to catch payments with no order (see how to reconcile WooCommerce with Stripe and PayPal).

For agencies: monitoring client stores

If you maintain WooCommerce stores for clients, a broken checkout is an emergency you want to hear about before the client does, not from them.

What matters at agency scale:

• One dashboard for all stores, not 20 logins.
• Per-store alert routing, so the right person or client channel gets the right alert.
• Silence detection, so a store that stops reporting entirely gets flagged rather than quietly looking “fine.”
• Privacy. Clients’ order data shouldn’t be copied into a third-party service.
• CLI access for scripted checks across many sites.

Ordafide’s free plugin includes WP-CLI commands (`wp ordafide scan`, `wp ordafide findings`, `wp ordafide health`, `wp ordafide digest`). Ordafide Pro adds a multi-store agency dashboard built on signed hourly snapshots that contain only counts and totals, not customer data. It flags any store that’s been silent for two hours, and the Agency licence adds per-store alert routing.

A monitoring checklist

• [ ] Uptime checks on home and checkout
• [ ] Synthetic check that reaches checkout without placing an order
• [ ] Order integrity scan (stuck, duplicate, refund and total mismatches)
• [ ] Background queue and email delivery monitored
• [ ] Order volume compared against normal for the hour
• [ ] Alerts routed to Slack/SMS for urgent issues, with throttling
• [ ] Manual test purchase after major updates
• [ ] For agencies: one dashboard and per-store routing

Frequently asked questions

How do I know if my WooCommerce checkout is broken?
Uptime monitors usually won’t tell you. Use synthetic monitoring that loads the cart and checkout on a schedule, plus order-volume anomaly detection and order integrity checks.

Can I monitor WooCommerce checkout without creating test orders?
Yes. Good synthetic monitoring checks shop, product, cart, checkout and the Store API, and can add an item to a cart, without ever placing an order. Ordafide Pro works this way.

How do I get Slack alerts for WooCommerce problems?
Use a monitoring plugin that supports Slack. Ordafide Pro sends Slack, SMS, email and webhook alerts with severity routing and throttling.

What’s the best way for an agency to monitor many WooCommerce stores?
A central dashboard that receives privacy-safe summaries from each store, flags stores that go silent, and routes alerts per store. WP-CLI commands help with scripted checks.