> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # WooCommerce Version Status, WooCommerce > WooCommerce Version Status. Current WooCommerce plugin version vs latest. WC releases monthly with checkout/payment fixes. Falling >2 minors behind = compounding regressions. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Current WooCommerce plugin version vs latest. WC releases monthly with checkout/payment fixes. Falling >2 minors behind = compounding regressions. Top-3 store-breaker (WC02). ## At a glance > Current WooCommerce plugin version compared against the latest release. WC ships monthly with checkout / payment / API fixes; falling 2+ minors behind compounds regressions. | | | | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `installed_wc_version vs latest_wc_version` (semver). Alerts when more than 2 minors behind. | | **REST API endpoint** | `GET /wp-json/wc/v3/system_status` returns `version`. Latest version polled from the WordPress.org plugin API. | | **VAT / tax / shipping / discounts** | Not applicable. | | **Status filter** | All Woo installs with REST access. | | **Refunds / cancelled / failed orders** | Not applicable. | | **Currency** | Not applicable. | | **Channels / sources** | Affects entire WC install. | | **Self-hosted vs managed-Woo** | Self-hosted owners apply WC updates manually; many wait for compatibility checks across paid extensions. Managed-Woo (Woo.com Cloud) auto-updates within hours. Pressable / WP Engine apply automatically on minor releases. WordPress.com always-current. | | **Time window** | `RT` (polled hourly) | | **Alert trigger** | `version >2 minor releases behind latest`; sentiment\_key `stack_health` | | **Roles** | owner, operations | ## Calculation Calculated automatically from your WooCommerce data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A self-hosted US homewares brand with 3 paid Woo extensions (Subscriptions, Memberships, Bookings). Polled 12 Apr 26. | Check | Value | | --------------------- | -------- | | Installed WooCommerce | 8.4.0 | | Latest WooCommerce | 8.7.0 | | Releases behind | 3 minors | | Alert? | YES | Three observations: 1. **Self-hosted variance is the recurring theme.** This brand delays WC updates because they fear breaking the paid extensions. Subscriptions and Bookings have a known history of 2-4 week lag in declaring compatibility with new WC minors. The merchant's "wait for the paid extension to certify" workflow is reasonable but compounds risk. 2. **WC ships checkout regressions occasionally.** The 8.5.x and 8.6.x branches both shipped checkout-related fixes (cart-block compatibility, order-pay-page rendering). Stores stuck on 8.4.0 may carry unresolved bugs the merchant wrongly attributes to their theme or other plugins. 3. **Plugin-induced data shape variance: HPOS migration.** WC 8.0+ introduced High-Performance Order Storage (HPOS), a new orders table. Stores upgrading from 7.x to 8.x have a one-time migration step. Skipping the migration leaves orders fragmented across `wp_posts` and `wp_wc_orders`, which can confuse the Woo engine briefly. The card detects the version but cannot detect HPOS-migration state, contact support if behaviour is odd after a major bump. ## Sibling cards merchants should reference together | Card | Why pair it with WC Core Version | | --------------------------------------------------------------------------------------------------- | ------------------------------------------------- | | [WC WP Core Version](/nerve-centre/kpi-cards/woocommerce/wordpress-core-version) | WP core itself; WC requires a minimum WP version. | | [WC Plugins Outdated](/nerve-centre/kpi-cards/woocommerce/plugins-out-of-date) | Stack-health peer. | | [WC Plugin Security Breach Alert](/nerve-centre/kpi-cards/woocommerce/plugin-security-patch-breach) | The urgent-action subset. | | [WC SSL Status](/nerve-centre/kpi-cards/woocommerce/ssl-https-status) | Stack-health companion. | ## Reconciling against the vendor's own dashboard **Where to look in WooCommerce Admin:** [WP Admin → WooCommerce → Status](/wp-admin/admin.php?page=wc-status) shows the WC version under "WordPress environment" and "WooCommerce". WC update notifications appear in `Dashboard → Updates` alongside other plugins. **Why our number may differ from WC Admin:** | Reason | Direction | | ---------------------------------------------------------------------------------------------------------------------- | ------------------------ | | **Time-zone**. Update notifications cached in WP transients up to 12 hours. | Ours fresher | | **Self-hosted server uptime**. Hourly poll lag during outage. | Self-resolves | | **Plugin-version compatibility**. Some "WooCommerce subscription" hosts ship custom WC builds; version may report off. | Investigate per-merchant | | **Auto-updates**. Managed-Woo applies updates between WP Admin and our poll; brief mismatch. | Self-resolves | **Cross-connector reconciliation:** | Card | Expected relationship | | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- | | [`stripe.stripe_charge_count`](/nerve-centre/stripe/stripe_charge_count) | Major WC version bumps occasionally introduce checkout regressions; pair to verify post-upgrade payment health. | ***
Same-metric documentation cross-reference WooCommerce-specific. No equivalent on Shopify or BigCommerce (vendors manage core platform versions).
## Known limitations / merchant FAQs **Self-hosted vs managed-Woo, why does WC version vary?** Self-hosted owners delay WC updates while waiting for paid extensions to certify compatibility. Managed-Woo applies sooner. **Status-filter selection, why >2 minor releases?** 1-minor lag is normal for "wait and see" merchants. 2+ means compounded regressions and unfixed checkout bugs. **Refund-object accounting?** WC introduces refund-handling improvements in many minor releases; running 2+ behind may carry refund-flow bugs. **Plugin-induced data shape variance: HPOS migration?** WC 8.0+ introduced High-Performance Order Storage. Stores migrating from 7.x to 8.x must complete a database migration. Skipping the migration leaves orders fragmented. The card detects version, not migration state, contact support if the Vortex IQ engine reports anomalies post-upgrade. **Multi-currency, does it affect this card?** No. **Why does Woo and Stripe disagree?** Stripe does not track WC version, but new WC minors occasionally ship checkout regressions that show up as Stripe payment failures. Pair with [Failed Order Rate](/nerve-centre/kpi-cards/woocommerce/failed-order-rate) after a major bump. **Today is jumpy, why?** Stable; flips on / off with version changes only. **Sync-lag from self-hosted server slowness?** Hourly poll. 1-2 hour delay during outages. **My WC Admin shows the latest version, why is the alert firing?** 1. Verify in `WC → Status` page (the canonical view). 2. Force a "Check again" in `Dashboard → Updates`. 3. If genuinely current, contact support. *** ### Tracked live in Vortex IQ Nerve Centre *WooCommerce Core Version* is one of hundreds of KPI pulses Vortex IQ tracks across WooCommerce and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.