Operanse
Sign inSign up

Blog · Guides · Monitoring setup

WooCommerce Monitoring: 5 Tools That Catch Problems Early

The five tools we'd put on any WooCommerce store that takes real money: what each one catches, what each one misses, and the habits that make them worth having.

Most store owners find out about a broken checkout from a customer email, a quiet afternoon in the order list, or a payout that comes in short. By then the problem is hours or days old. Here is the set of tools and habits we would put on any WooCommerce store that takes real money, what each one catches, and, just as important, what each one misses.

No single tool sees everything. A store can fail in four places, and each needs a different kind of watcher:

  1. From the outside: the site is down, or a customer cannot get through checkout.
  2. On the server: payments are failing, renewals are not running, background jobs are piling up, a service the store depends on has stopped answering.
  3. In the customer's browser: a script error that stops the Place order button from working.
  4. In the things around the store: email that never arrives, a plugin with a known hole in it, an update with no way back.

1. Watch the store from the inside: Operanse

Most of what goes wrong on a WooCommerce store does not take the site down. The home page loads, the uptime check is green, and meanwhile:

  • a payment gateway starts declining far more cards than usual,
  • subscription renewals stop running because the background queue has stalled,
  • orders are paid but sit in "processing" because the fulfilment integration is failing,
  • the shipping-rate API times out on one call in three,
  • order confirmation emails stop being sent.

None of these shows up from outside. Operanse is a plugin plus a service that watches these signals from inside WordPress: payments, orders, refunds and renewals, background tasks (Action Scheduler and WP-Cron), the outside services the store calls, the email it sends, its forms and PHP errors. It also records every plugin, theme, WordPress and WooCommerce change, so when something goes wrong you can see what changed just before.

What makes it useful rather than noisy is that it learns what is normal for your store, hour by hour, instead of using fixed thresholds. Four failed payments in an hour might be a crisis for one store and a quiet Tuesday for another. Each incident comes with an estimate of the revenue affected, and on the top plan a critical alert also carries an AI review of the evidence: the likely cause, and what it is based on.

What it misses: Operanse observes; it does not click through your checkout. If a script error stops customers reaching the payment step, it sees the orders stop, typically within about 30 minutes, not the moment the button breaks. It also needs a couple of days of data before it knows what normal looks like for your store. It is read-only: it never changes your site, so it will not fix anything for you either.

Cost: the free plan covers one site and alerts you by email when the store can no longer take orders, background tasks stall or renewals fail. The paid plans add the learned baselines and everything above, Slack, SMS and WhatsApp alerts, and the AI review. See pricing.

2. Test the checkout from the outside: CheckView

The gap above needs a robot customer: something that visits the store on a schedule, adds a product to the cart, goes through checkout and confirms an order comes out the other end. This is the only way to catch a checkout that looks fine but does not work.

Our pick is CheckView, made by the team behind the WordPress agency Inspry. To be clear: we have not run CheckView on our own stores yet. This pick comes from its documentation, its wordpress.org listing and its changelog, not from our own testing.

  • No code. A plugin plus a dashboard: pick the checkout path, set a schedule, done. It also tests your contact and lead forms, which break just as quietly.
  • It goes all the way to an order. It pays with its own dummy payment method or Stripe in test mode, checks that WooCommerce created the order, then deletes the test order. It keeps its test orders out of webhooks, Mailchimp and Shippo.
  • Failures come with evidence: a video of the run, screenshots, console logs and step-by-step detail, so you or your developer can see exactly where it stopped. Alerts go to email, Slack or a webhook.
  • It is used. Over a thousand WordPress sites run it, more than every other WooCommerce-specific checkout tester we looked at put together.

What it misses: tests run on a schedule, typically daily, so a checkout that breaks at 9 a.m. may not be tested until the next run. And it pays with a test method, so a live gateway that has started declining real cards still passes. Both gaps are what an inside-the-store watcher covers: it sees the real orders stop, or real declines climb above what is normal for your store. That is why the first two tools belong together.

If you have a developer: Checkly runs Playwright tests you write yourself, as often as every few minutes. More work to set up and keep working when the theme changes, more control over exactly what is tested and how often.

3. Catch errors in the customer's browser: Sentry

Some of the worst checkout failures are JavaScript errors: a payment plugin's script clashes with a new version of the theme, an optimisation plugin combines files in the wrong order, and the Place order button does nothing. There is no PHP error and no failed order, just customers who leave.

Sentry's browser SDK, loaded on the cart and checkout pages, reports those errors as they happen, grouped so that one broken script is one issue rather than a thousand emails. The free plan is enough for most stores.

Set it up carefully. Turn off session replay and anything that captures form fields or request data, and do not send user details. Checkout pages are full of names, addresses and card fields, and none of that belongs in an error tracker.

4. Make email reliable and visible: a transactional email provider

WordPress sends email through the web server by default, which is the most common reason order confirmations, password resets and "your renewal failed" emails land in spam or never arrive at all.

Send through a proper provider (Postmark, Amazon SES, Mailgun, Brevo or similar) using an SMTP plugin that keeps a log, such as FluentSMTP or WP Mail SMTP. You get far better delivery, and a record of every email the store tried to send and whether it went. Operanse reads those logs, so a sudden run of failed sends becomes an alert rather than a customer complaint.

5. Close known security holes: Patchstack

A vulnerable plugin is a problem waiting for a date. Patchstack tells you when a plugin, theme or WordPress version on your site has a known vulnerability, and on paid plans blocks attempts to exploit it before the plugin author has shipped a fix. The free plan covers a few sites and is worth having on its own.

6. The habits that make the tools worth having

Tools tell you something is wrong. These make sure you can do something about it.

  • Update on staging first. Most breakages follow an update. Try WooCommerce, payment gateway and theme updates on a staging copy, run the checkout once, then update production. Most managed hosts give you staging with one click.
  • Have backups you have restored at least once. A backup you have never restored is a hope, not a backup. Make sure it is stored off the server and that it includes the database, which is where your orders live.
  • Turn on the alerts you already have. Stripe emails you when your webhook endpoint keeps failing; PayPal and other gateways have similar settings. They cost nothing and are easy to forget.
  • Decide who gets woken up. An alert that goes to an inbox nobody reads at 2 a.m. is not an alert. Send the critical ones to a phone, and the rest to a daily or weekly summary.

The whole setup on one page

LayerToolCatchesDoes not catch
Inside the storeOperanseFailing payments and renewals, stalled background jobs, failing outside services, email failures, PHP errors, what changed before a problemA checkout that breaks in the browser, until orders stop
Outside the storeCheckViewA checkout or form customers cannot get throughA break between scheduled runs; a live gateway declining real cards
The browserSentryScript errors on cart and checkoutProblems on the server
EmailSMTP provider and a logging pluginOrder and renewal emails not being deliveredProblems that are not email
SecurityPatchstackKnown vulnerabilities in your plugins and themesProblems that are not security holes
RecoveryStaging and tested backupsNothing: this is how you get back

The first two are the core: one checks what your customers can do, the other watches what your store actually does with their orders. Between them, a broken checkout, a gateway declining cards and a renewal queue that stopped on Friday night all become an alert, instead of a surprise on Monday.