How Store Guard looks after your WooCommerce store
A plugin on your store, a monitoring hub run by Ashbi, and a person who reads the alerts. Here is what happens from the day we install it to the night something breaks.
-
We install and connect it
Ashbi installs the Store Guard plugin on your WordPress site and connects it to our monitoring hub. Each store gets its own ID, and the reports it sends are signed, so the hub only accepts reports from stores it knows. If you take payments with Stripe, we add a webhook so disputes reach Store Guard the moment Stripe opens them.
There is nothing for you to configure. You'll see a Store Guard menu in your WordPress admin with your store's health, errors and disputes.
-
It watches checkout as customers use it
A small script runs on your WooCommerce pages (shop, product, cart, checkout and My Account) and reports problems the moment a customer hits them:
- JavaScript errors and unhandled promise failures
- Failed add-to-cart, cart update and checkout requests
- WooCommerce error messages shown at checkout, on classic and block checkout
The same error from the same browser is only reported once every 30 seconds, and we can switch off patterns that are harmless on your store, so a bad night doesn't turn into hundreds of messages.
-
It checks the parts customers never see
About twice a day, and whenever someone runs it by hand, Store Guard runs a health check and gives your store a score out of 100. Where it can, it offers a one-click fix, for example clearing out failed background tasks.
What the health check covers
- WooCommerce version and core pages (shop, cart, checkout, account)
- Stripe gateway enabled, test mode and webhook address
- Failed Action Scheduler tasks
- WP-Cron switched off
- Orders stuck in pending
- Overdue subscription renewals
- SSL on the storefront
- Database size and session buildup
- PHP memory and execution time limits
- Plugin and theme updates waiting
- Shipping zones and tax settings
- ShipStation connection, if you use it
- Connection to the monitoring hub
Separately, our hub checks your storefront responds every 10 minutes, and notices if your store stops checking in.
-
Alerts come to Ashbi first
Checkout errors, critical health results and new disputes go to the Store Guard hub, which Ashbi watches. The hub groups repeat alerts, so one problem produces one alert. You don't need to watch an inbox or learn a dashboard.
-
We respond, then tell you what happened
We look at the alert, work out whether it affects customers, and fix what we can. You get a plain message: what broke, what we did, and anything we need you to decide, like renewing a payment key or choosing between two plugins.
What leaves your site
Store Guard sends what's needed to spot and explain a problem, to the monitoring hub Ashbi runs. It never sees card numbers; Stripe keeps those.
| Report | What it includes |
|---|---|
| Error reports | Error type and message, page address, browser, time, and the order ID and billing email when the error happened at checkout. |
| Health checks | Each check's result and score, plugin version, and order IDs where a check found a stuck order. |
| Disputes | The disputed order, customer name, email, IP address, billing and shipping addresses, products, amount, reason and response deadline. This is the evidence the card issuer asks for. |
| Store heartbeat | Plugin version, health score and a short integrity summary, so we know the store is still reporting. |
Built to stay out of your customers' way
The front-end script is about 11 KB before compression and loads in the footer, after your page content. It only loads on WooCommerce pages. Health checks run on WP-Cron in the background, never during a customer's page load. The plugin declares compatibility with WooCommerce High-Performance Order Storage (HPOS).
Start with a free store check.
A free store check covers your checkout, background tasks and dispute history. We'll tell you what we'd watch and what it would cost.