PRO Features
What PRO can and cannot detect
Real-world scenarios that show where Commerce Health PRO notices a checkout problem, and where it cannot.
Commerce Health PRO watches your store in the background and tells you when something needs attention. It reads your orders, plugin changes and what checkout visitors’ browsers report. It does not place test orders, it does not fix anything, and it can only report what leaves a trace it can read.
Problems PRO can notice
| What happens | What PRO does |
|---|---|
| A gateway starts declining: 6 of 20 orders in the last hour are marked Failed. | Raises a Critical payment gateway issue (30% failed) and emails you with [CRITICAL] in the subject. See Payment Gateway Monitoring. |
| Checkout with one gateway takes 10 seconds on average to confirm. | Raises a Medium issue. |
| Orders start but don’t finish, much more than usual for that gateway. | Raises a Medium, High or Critical issue. See Stuck Payments Monitoring. |
| A gateway has 4 orders in a day and none paid or failed. | Raises a Medium “silent gateway” issue (High from 5 orders, Critical from 10). |
| A plugin update breaks the Place order button with a script error. | Records the error and raises an issue that gets more severe each time it recurs. See JavaScript Error Detection. |
| You update a plugin, and within two hours a new error appears or payment failures rise by 2 or more. | Raises an issue naming the plugin, as a lead. See Plugin Conflict Detection. |
| Real visitors find checkout slow (LCP over 4 seconds, as the 75th percentile of at least 3 visits in 24 hours). | Raises a Critical issue (at most once per metric per 24 hours). See Checkout Performance. |
| A shipping class has no price, a coupon has expired, or the active theme is broken. | Flags it in the next scan. See Shipping, coupon and theme checks. |
Problems PRO cannot notice
| What happens | Why PRO can’t see it |
|---|---|
| A customer’s checkout fails before an order is created (for example a server error while placing the order). | No order exists, so there is nothing to count. PRO doesn’t see server errors. |
| The payment form doesn’t load, but the browser reports no error. The page is cached, or a style rule hides the button. | PRO only hears about errors the browser raises, and failed or unfinished orders. A silent problem leaves no trace, unless it also leaves orders unpaid. |
| Your payment provider can’t reach your webhook, so paid orders stay Pending. | PRO may notice the effect (unfinished orders) but can’t test whether the provider can reach your site, or say why. |
| A customer is stuck after the redirect back from the gateway, on their phone. | It happens on the customer’s device. PRO sees orders and checkout-page browser errors, not the journey. |
| A gateway marks nothing as Failed and leaves declined orders Pending. | Failures are counted only when the order status becomes Failed. Stuck Payments may notice the pile-up if it is large enough. |
| Problems on the cart, product or other pages. | The error listener and the speed measurement run on the checkout page only. |
| Errors inside another website’s script (for example a payment widget). | Browsers hide the details and report only “Script error.” |
| Fewer orders because of traffic, pricing, stock or marketing changes. | PRO doesn’t see traffic or sales trends. |
| Your website or its hosting is down, or background tasks stop. | PRO runs inside your site. It can’t send an alert from a site that is not running. |
| A plugin changed over FTP, or a theme or WordPress core update. | Only plugin activations, deactivations and updates reported by WordPress are recorded. |
| Fraud, hacking or malware. | PRO isn’t a security scanner. |
How to use that
- A clean dashboard means PRO found nothing it can detect, not that nothing is wrong.
- PRO emails only the severities you choose (High and above by default) and at most 10 issue emails a day, so check the Issues screen as well. See Issue email alerts.
- Still place a test order on a real phone after updates, and check your payment provider’s dashboard now and then.
- PRO’s alerts are leads. A Plugin Conflict issue and an unfinished-payment spike say “look here”, not “this is the cause”.
Every default threshold is listed in the PRO thresholds reference.
Was this article helpful?
Still need help?
Search the docs first — or open a ticket and our team will pick it up from the Support screen.