WooCommerce checkout monitoring: how to watch a WordPress checkout

Automatic updates change checkout for you

WordPress can update plugins automatically, and many hosts turn that on. A payment gateway, a shipping-rate plugin or a checkout-fields plugin can ship a new version overnight. Most updates are fine; the one that is not usually shows up as a payment step that no longer renders or a required field that can no longer be filled.

If you allow automatic updates, the checkout needs automatic checking on the same schedule.

Block checkout and shortcode checkout behave differently

Newer stores use the Checkout block; older ones and many themes still use the [woocommerce_checkout] shortcode. Plugins do not always support both. A plugin that works on one can silently do nothing on the other — a missing field, a gateway that never appears. Switching between them, or a theme update that switches for you, is a checkout change in its own right.

Caching and optimisation plugins

Page caching, JavaScript minification and "delay JS" features are a common source of checkout breakage: the cart page gets cached with someone else’s contents, or a gateway script gets deferred past the point where it initialises. Cart, checkout and my-account should always be excluded — check that they still are after every change to the optimisation settings.

What a useful monitor asserts

If your checkout is already failing, start with what to do when a WooCommerce checkout is not working or a failing payment gateway. Loading the checkout URL is not a test. A useful check adds a real product, confirms the cart shows the right item and price, fills a real address, confirms shipping methods appear, confirms the totals add up, and confirms a payment method is ready to accept input. Each of those is a separate thing that can break, and each deserves its own failure code so the alert tells you where to look.

Weighing manual orders, uptime pings, plugins and hosted testers against each other? See WooCommerce checkout monitoring tools compared; this guide is about setting a monitor up well.

Checks from inside WordPress and checks from outside

There are two places to watch a WordPress checkout from, and they catch different things. From inside, a plugin can read what the store is configured to do: whether the checkout page is still published, whether any payment method is enabled, whether a shipping zone exists, whether scheduled tasks are running on time. These checks are cheap and run on your own server, but they only see settings and counts.

From outside, a browser visits the store like a shopper does. It catches what settings cannot show: a payment form that no longer renders after an update, a theme change that hides the button, a shipping-rate call that errors. Use both. The free MageSentinel plugin for WordPress does the inside checks and emails you when one turns red, and MageSentinel runs the outside check on a schedule.

How to set up WooCommerce checkout monitoring

Pick a test product that is always in stock, cheap and simple — no variations or required options — and keep it published, even if it is hidden from the catalog. Decide which payment method the check should reach, and whether it should stop at the payment step or place a real order.

Then choose how often to run it and where alerts go. Every few minutes is right during sales and campaigns; alerts belong in a channel someone watches, such as Slack or email, not a shared inbox. MageSentinel does exactly this: it walks product, cart, checkout, shipping and payment in a real browser on a schedule, and alerts with the failure category, a screenshot and the console errors. Related: a walkthrough of MageSentinel on WooCommerce and what to do when the checkout is not working.

Check your own store now with the free WooCommerce checkout checker: it walks the checkout in a real browser and shows the step where it stops.