MageSentinel

MageSentinel on a WooCommerce store: from setup to the first alert

WooCommerce checkouts change whenever a plugin updates, so the value of monitoring is finding out in minutes. Here is what that looks like in MageSentinel, from adding a WooCommerce store to the alert when a gateway stops rendering. Demo data throughout.

All posts2 min read

A monitoring screen showing live data
demo-magento.examplemagento2 · hyvä checkout · EURCURRENT STATEPASSCOMPLETED100 %CLEAN RUNS100 %LAST DURATION21.4 sORDER PLACEMENTOFFLatest checkoutstoreproductcartcheckoutcustomershippingpaymentorder
Store page: current state, completion and duration, and the latest checkout step by step. Demo data.

Setting it up

Add the store URL and a test product — simple, always in stock, published even if hidden from the catalog. MageSentinel handles both the classic shortcode checkout and the Checkout block without configuration.

Pick the schedule and alert channels (Slack, email, webhook), and decide whether runs should stop at the payment step or place a real order. An optional read-only WordPress plugin adds data like installed plugins, scheduled actions and recent errors, which helps with root cause but is never required.

The store page

Each store has a page with its current state, how many recent runs completed, how many were clean, the last duration and whether order placement is on. Below it, the latest checkout is drawn step by step, with the product, price, shipping method and total the run saw.

Business assertions sit next to it — for example a checkout that shifts its layout while loading gets flagged even when it technically passes, because buttons moving under a customer’s thumb is a real problem on mobile checkouts.

storeproductcartcheckoutcustomershippingpaymentorderPAYMENT_NO_METHODSScreenshot of the failed stepnothing to chooseConsole · Network · Trace✕ gateway script blockedPOST /checkout … 200 · 1.2 ssecrets redacted at capture
A failed run on a WooCommerce demo store: the payment step rendered no methods. Demo data.

When the payment step fails

Say an optimisation plugin update starts deferring the gateway’s script. The next run reaches the payment step, finds no method ready, and fails with PAYMENT_NO_METHODS. The run keeps the screenshot, the console error about the blocked script and the network log — the evidence you would otherwise gather by hand following our payment gateway guide.

The failure is confirmed before anyone is paged, and a single alert goes out with the code, the store and a link to the run.

PAYMENT · demo-woo.exampleimpact: all customers · 31 min14:02Checkout fails at payment14:07Failure confirmed · alert to Slack + email14:31Plugin rolled back14:33Run now → PASS · incident resolved
An incident: repeated failures grouped into one, one alert on the way in, one on recovery. Demo data.

Incident, fix, recovery

All the failing runs that follow belong to the same incident, so the channel stays quiet while you work. Roll back the plugin, press “Run now”, and when the run passes the incident closes and a recovery alert confirms it.

Over time the store page shows how often checkout broke, for how long, and at which step — the numbers you need to put a cost on downtime.

Find out your checkout broke before your customers do.

Real checkout checks for Magento and WooCommerce · 14 days free · no card required

Try it on your store

Start a 14-day free trial, no card required. Add your WooCommerce store and a test product, and the first run completes within minutes.

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.

Common questions

How do I set up MageSentinel on WooCommerce?

Add the store URL in the dashboard, or install the free MageSentinel plugin from WordPress.org and connect it.

What happens when a check fails?

MageSentinel re-runs the check to confirm it, opens an incident with the failing step and evidence, and alerts you; it alerts again on recovery.

Does it place real WooCommerce orders?

Only when the store has its own connector installed; otherwise it stops before placing the order.