Kodenzo Commerce Health

No. KODENZO Commerce Health works on any WordPress site. Checks that specifically depend on WooCommerce (payment gateways, checkout configuration, WooCommerce database tables, etc.) report as "Not applicable" if WooCommerce isn't installed or active, rather than failing — the rest of the checks (WordPress version, PHP configuration, SSL, WP-Cron, database connectivity, and more) still run normally.

35 diagnostics across seven categories: Commerce (WooCommerce setup and configuration, checkout page content, checkout address fields, recent failed orders, storefront reachability, cart and checkout page reachability, shipping and tax configuration), Reliability (WP-Cron and Action Scheduler health), Performance (object cache, autoloaded options size), Database (connectivity and required tables), Configuration (PHP version, memory limit, SSL, debug settings, URL consistency, search engine visibility), Security (WordPress core and plugin update status), and Integrations (payment gateway configuration and test mode). Each finding comes with a plain-language explanation and a recommended next step.

No. Every diagnostic is read-only. A scan only reads your site's configuration and recent order counts (never customer details) to report findings, and it never places orders or payments. The separate Test order tool creates a test product and a cancelled test order, but only when an administrator presses its button. See the next question.

On the Test order screen you press "Create a test product for me", which creates one private, hidden, virtual product priced at 1.00. You cannot choose an existing product. Pressing "Run test order" then makes a few requests from your site to itself: it puts the test product in a guest cart, opens your checkout page, and submits the checkout through a hidden test payment method that only exists during that run. The order is cancelled immediately and marked as a test. What to know before you use it:

• It does not test your real payment methods. It never contacts Stripe, PayPal or any other provider, so a pass says nothing about your real gateways.
• It creates a real order that uses up an order number and stays in WooCommerce → Orders until you press "Delete all test orders".
• While it runs, emails from WordPress and WooCommerce are blocked and counted, and WooCommerce's own webhooks are held back. Other plugins can still react to a new order (accounting, ERP, warehouse, shipping, loyalty, analytics or messaging tools), and this plugin cannot stop or undo that.
• WooCommerce reports leave out cancelled orders by default, but other plugins and custom reports may count it.
• It checks the basic checkout only: shipping, tax and coupons are not tested in the free plugin.
• Some hosts and firewalls stop a site from requesting itself. If so, the test says it could not run.
• Only administrators can use it, and nothing is sent to Kodenzo or anyone else.

No scans run by themselves. Scans start only when you run one, from the "Scan store" button on the Overview screen or with WP-CLI (wp kodenzo-ch scan). The plugin has three small scheduled tasks and none of them scans your store: a daily cleanup of old scan history (based on your retention setting), the store health email (daily, weekly or monthly, your choice) and a once-a-day check of recent order dates for the quiet-period warning. The last two only send emails and can be turned off in Settings. If a scan you run finds a new critical issue, or one that had been resolved comes back, the plugin emails the alert recipients. This is on by default and can be turned off on the Settings screen, which also has a test-email button. By default the email goes to the site admin address; under Alert recipients on the same screen you can enter several To addresses and CC addresses (up to 5 in each), for example a shop owner and a developer. Developers can also add recipients in code with the kodenzo_ch_alert_recipients filter.

It tells you when a steady store has stopped getting orders for much longer than usual. The plugin works out how often your store normally gets an order from the week before the latest one, and warns when the gap is 5 times that (and at least 12 hours). It needs at least 14 orders in that week, so small or new stores are never warned. It reads only order dates, runs once a day, and emails once when the quiet starts and once when orders return. A quiet period is not always a problem (a slow day or a finished sale), but it can mean customers cannot check out or pay, so place a test order and check your payment provider. Turn it off in Settings.

Your latest scan score and open issues, your orders, revenue, average order and failed payments for the last 7 days against the 7 days before, a warning if orders have gone quiet, and a link to run a scan. Choose daily, weekly (default) or monthly under Settings, or turn it off. "Send me this report now" sends one straight away so you can see it. It never runs a scan on its own and it goes only to your alert recipients.

No Kodenzo telemetry, ever. All scan results, issues, and settings are stored only in your own WordPress database, and KODENZO Commerce Health never collects or transmits your site or user data to Kodenzo or anyone else. That's a different question from whether the plugin makes any network request at all. It only ever makes requests to your own site, and they are diagnostic, not telemetry. The "Storefront Reachable" check requests your own site's homepage during a scan to confirm it's actually responding to visitors, the "Cart and Checkout Pages Reachable" check requests your cart and checkout pages once each, and the Test order tool, when you press its button, sends a few requests from your site to itself. The plugin never contacts a third-party destination, and nothing about the results is sent anywhere outside your own database. The emails it sends go only to the addresses you set, through your own site's mail. Separately, WordPress core runs its own routine version and plugin update checks on its own schedule — that's native WordPress behavior that happens whether or not KODENZO Commerce Health is installed, not something this plugin initiates. The links on the "Upgrade to PRO" screen and in the small footer strip on the plugin's own screens (Kodenzo logo, Support, Documentation) simply open kodenzo.com, WordPress.org or the KODENZO documentation in a new browser tab when clicked — nothing is sent when you click them.

Yes. Your most recent scan also appears as a "Commerce Health" tab on the built-in WordPress Site Health screen (Tools → Site Health), and as a summary widget on the main wp-admin Dashboard — so you don't have to visit the plugin's own screens to see your current score and top issues.

Yes. From the Overview screen or from any entry in Scan history, you can download a scan as a CSV file or as a branded PDF report — useful for sharing with a client, a developer, or for your own records outside wp-admin.

By default, nothing is deleted. Your scan history, issues, and settings remain in the database even after uninstalling, in case you reinstall later. Data is only removed on uninstall if you've explicitly turned on "Delete KODENZO Commerce Health data when uninstalling" on the Settings screen first — off by default.

Every scan starts at 100 and subtracts points for each warning or failure by severity: Critical 25, High 12, Medium 6 and Low 2 (Info findings subtract nothing). The score is shown as Healthy (75 and above), Attention (60 to 74), Unhealthy (40 to 59) or Critical (below 40). Any Critical finding sets the status to Critical, whatever the number. Each category also gets its own 0-100 score.

Version 1.4.0 adds four checks: Checkout Page Content, Checkout Address Fields, Recent Failed Orders and Payment Gateway Test Mode. If one of them finds something on your store, the score drops by that finding's weight. Open Diagnostics to see which check it is and what to do about it.

Checkout Page Content confirms the checkout page contains the WooCommerce checkout (block or shortcode) and the cart page contains the cart. A page built with a page builder or a reusable block is reported as "could not confirm", not as a failure. Checkout Address Fields reports address fields removed from the classic checkout while the store uses shipping or tax. Recent Failed Orders compares failed with finished orders over the last seven days, using counts only, and judges only after at least ten finished orders. Payment Gateway Test Mode flags an enabled Stripe, PayPal or Braintree gateway still in test mode; it reads only the on/off setting, never keys or credentials.

Yes, once each, and only while a scan that you started is running. The Cart and Checkout Pages Reachable check asks your own site for the checkout page, and the cart page if one is set, the way WordPress calls itself, and reports a server error (such as a 500), a missing page or a redirect that never ends. It sees what your server returns, not what a browser draws, so it cannot find JavaScript or styling problems, and it cannot prove a customer can complete checkout. If a firewall, a rate limit or your host stops the request, the check says it could not tell and does not count against your score. When the PRO add-on is active, PRO checks these pages itself every few minutes and this one-time check steps aside. Nothing is sent outside your site.

Yes. The plugin declares compatibility with high-performance order storage, and the checkout checks recognise both the Checkout block and the classic [woocommerce_checkout] shortcode. The address-fields check applies to the classic checkout.

Open Commerce Health → Settings → Alert recipients. Enter up to 5 addresses in To and up to 5 in CC, separated by commas. Leave To empty to use the site admin address. Use Send test email to confirm every address receives it. Developers can also add recipients in code with the kodenzo_ch_alert_recipients filter.

Only users with the manage_options capability, normally administrators. The same applies to the REST API and the Dashboard widget.

Yes. Add your own checks on the kodenzo_ch_register_diagnostics action, react to new, reopened or escalated issues on kodenzo_ch_issue_changed, and adjust alert recipients with kodenzo_ch_alert_recipients. Results for checks namespaced pro. are hidden from the results endpoint unless the plugin that owns that namespace is active.

Yes. KODENZO Commerce Health PRO is a separate, paid add-on that requires this plugin and adds background monitoring, for example of checkout and payment gateway outcomes, checkout JavaScript errors and plugin changes. This Free plugin has no trial or expiry and no locked screens: the checks, score, store figures, emails and exports described above are fully included. The one deliberate limit is the Test order tool, which in Free is manual and checks the basic checkout only. PRO adds ongoing background monitoring and scheduled test orders. A short "Upgrade to PRO" screen in the plugin menu explains what PRO adds, and a single dismissible note on the Overview mentions it after your first scan.

If a scan finds something you'd rather not fix yourself, you can contact KODENZO at https://kodenzo.com/contact/.