WooCommerce

WooCommerce was originally built by WooThemes (2011) and acquired by Automattic in 2015; it is developed as a free WordPress plugin, not a standalone company product.

First released September 27, 2011 by WooThemes (Mike Jolley and James Koster), forked from the Jigoshop plugin; acquired by Automattic in 2015.

WooCommerce is not a standalone platform: it is a free plugin that turns a self-hosted WordPress.org site into an online store. Every attribute below describes a WooCommerce store running on self-hosted WordPress, since that is the only way WooCommerce runs (no separate WooCommerce.com hosted product).

Core plugin is GPL-licensed and open source; its extensions/themes sold on the WooCommerce Marketplace are commercial add-ons (many are also GPL for the PHP code, per WordPress plugin licensing norms) but are paid products, not the core software.

Core WooCommerce plugin is released under the GNU General Public License v3.0, as declared in its readme/plugin header on the WordPress.org plugin directory.

Editorial synthesis of WooCommerce's own positioning ("Choose any payments, any features, any host") plus its structural role as a WordPress plugin.

The core WooCommerce plugin is free to download and use, with no platform fees or revenue share on the software itself. "Free" does not include hosting, which is required separately (WooCommerce is not hosted).

Same structural pattern as WordPress core: no platform-imposed feature gating since there is no platform tier, only the hosting layer underneath.

No universal vendor trial exists since WooCommerce is a free download, not a subscription product.

Market-typical figure, not a WooCommerce price (the plugin is free). Cheapest widely-used managed-WordPress entry hosting plan with a custom domain: Bluehost Starter at $3.99/mo intro (renews $9.99/mo), the same representative host used for WordPress in this dataset. WooCommerce runs on any such host.

Market-typical figure, not a WooCommerce price. Used WP Engine Startup plan ($30/mo, annual billing) as a representative "popular" managed-WordPress tier; this is the same reference host used for WordPress in this dataset since WooCommerce inherits WordPress hosting economics.

Market-typical figure for WooCommerce-ready shared hosting (low end of the commonly cited $25-$350/mo range for WooCommerce store hosting). The plugin itself is free; this reflects the cheapest realistic hosting tier capable of running a store reliably, before extensions or a payment processor's own transaction fees.

As a self-hosted plugin, WooCommerce has no vendor watermark to remove; any branding present depends entirely on the chosen theme, not WooCommerce itself.

Not applicable to the free plugin itself, but true of the hosting layer virtually every store depends on: e.g., Bluehost Starter renews at $9.99/mo after a $3.99/mo intro rate. WooCommerce Marketplace extensions also auto-renew annually at full price after the first term.

WooCommerce Marketplace extensions (e.g., WooCommerce Subscriptions, Abandoned Cart) carry a stated 30-day money-back guarantee; this is a Marketplace/extension policy, not a policy for the free core plugin (which has no purchase to refund).

Same variability pattern as WordPress core, since WooCommerce is built on it; the extension marketplace adds a second layer of a la carte cost beyond WordPress's plugin ecosystem.

Storefront pages/posts use the WordPress Block Editor (Gutenberg), and Cart/Checkout use native WooCommerce Blocks fully editable in Gutenberg. Product editing itself, however, remains the classic meta-box form UI: WooCommerce's block-based Product Editor beta (introduced 8.9, 2024) is being deprecated starting in version 10.9 (June 2026) and removed in 11.0, with Woo directing stores back to the classic product editor while it builds a new experience on WordPress DataViews/DataForms.

Cart/Checkout Blocks and page content blocks support drag-and-drop reordering in the WordPress block editor, same as any WordPress site; product-specific fields in the classic product editor are form-based, not drag-and-drop.

Page/post content is click-to-edit via the WordPress block editor; Cart and Checkout blocks are editable in place via Gutenberg. Product data fields (price, SKU, inventory) are edited through the classic product editor's form panels, not inline on a live preview.

Inherits WordPress's native post/page revision history and in-editor undo/redo for content pages; products are a custom post type and also get WordPress's native revisions system.

Inherits WordPress core's periodic autosave for posts, pages, and products (all are WordPress post types).

The free official WooCommerce mobile app (iOS/Android, plus watchOS/Wear OS) lets merchants create and publish products, manage orders, take payments via Tap to Pay, and view real-time stats from a phone.

Same constraint as WordPress generally: switching WordPress themes can break custom layouts and page-builder content. WooCommerce-specific data (products, orders, customers) is stored independently of the theme and survives a theme switch, but storefront design/layout customizations do not transfer automatically.

Editorial judgment: WooCommerce adds ecommerce-specific complexity (payment gateway setup, tax configuration, shipping zones, extension compatibility, PCI considerations) on top of WordPress's own moderate learning curve. Getting a fully functional, secure store live requires more decisions and technical judgment than a hosted builder or even publishing-only WordPress, even though the plugin install itself is one click.

WooCommerce Marketplace's official themes category page does not publish a running total theme count, and its content is JavaScript-rendered so it cannot be reliably scraped for an exact figure. Unlike WordPress.org's free theme directory (which lists an exact count), WooCommerce-compatible themes are spread across the official Marketplace, WordPress.org (any theme with WooCommerce support), and third-party marketplaces, with no single official aggregate number.

Inherits WordPress's native Font Library (6.5+, block themes) for uploading custom font files directly in the Site Editor, same as any WordPress site running WooCommerce.

Inherits WordPress's full theme/CSS control; WooCommerce templates (product, cart, checkout, shop archive) are standard theme template files/blocks that can be styled and restructured like any other WordPress template.

Inherits WordPress's native "Additional CSS" panel and unrestricted theme/child-theme CSS editing; WooCommerce ships its own stylesheet that can be overridden the same way.

Inherits WordPress's unrestricted custom JavaScript support via theme files, plugins, or code injection for administrators; no WooCommerce-specific restriction.

No native visual animation/interaction builder in WooCommerce or WordPress core; achieved via theme features, plugins, or custom CSS/JS, same as WordPress generally.

Inherits WordPress's theme.json-powered Global Styles (colors, typography, spacing) on block themes; WooCommerce Blocks (Cart, Checkout, product blocks) respect and render within these global styles.

Editorial judgment: full theme/template/CSS access plus the combined WordPress and WooCommerce plugin ecosystems make design flexibility effectively unconstrained for anyone with developer skill or an existing WooCommerce-compatible theme, mirroring WordPress's own rating.

WooCommerce is not itself a hosting service; every store requires separately-provisioned hosting (shared, VPS, managed-WordPress, or self-managed server). WooCommerce.com maintains a partner directory of recommended third-party hosts rather than offering its own hosting product.

Self-hosting is the entire premise of WooCommerce; it only runs as a plugin on a self-hosted WordPress.org installation.

Not included with the plugin itself; depends entirely on the hosting provider chosen. Many WooCommerce-recommended managed hosts bundle a CDN as part of their plan.

Not a plugin feature; depends on the host. Most WooCommerce-recommended hosts include free Let's Encrypt SSL, making it typical in practice even though not guaranteed by WooCommerce itself.

There is no WooCommerce uptime commitment since it is not a hosting service, mirroring WordPress core.

No platform-wide limit exists since WooCommerce runs on infrastructure the store owner chooses.

Not applicable/practical for a WooCommerce store: static-export tools exist for WordPress content pages, but WooCommerce's core functionality (cart, checkout, inventory, customer accounts, payment processing) is inherently dynamic/server-rendered and cannot be reduced to a static export.

May 2026 CrUX data via HTTP Archive CWV Technology Report API, split by device: desktop 38.9% good CWV (142,100/365,748 origins tested), mobile 40.1% (232,597/579,968). Combined pass rate 39.6% (374,697/945,716 origins). Report technology name: 'WooCommerce'.

WooCommerce inherits WordPress core's responsive image sizes/srcset generation but does not do modern-format conversion (WebP/AVIF) or aggressive compression out of the box for product images; that requires a plugin or host-level feature, same limitation as WordPress generally.

Inherits WordPress core's native lazy-loading (loading="lazy" attribute), default since WordPress 5.5, applied to product images along with other content images.

Store owners have full server/application-level caching control, same as any self-hosted WordPress site; WooCommerce-specific care is needed to exclude dynamic pages (cart, checkout, my-account) from page caching, which is a documented configuration step rather than a platform limitation.

Editable via SEO plugins (Yoast, Rank Math) on product, category, and content pages alike, same mechanism as WordPress generally since WooCommerce core has no dedicated meta title/description UI of its own.

Native permalink/slug editing for products (a WordPress custom post type) as well as pages and posts.

Materially more flexible than closed ecommerce platforms like Shopify, which force permanent /products/ and /collections/ prefixes.

No native redirect manager in WooCommerce or WordPress core; requires a plugin (e.g., Redirection) or server-level configuration, same as WordPress generally.

Inherits WordPress core's self-referencing canonical tag output on all singular content, including WooCommerce product pages; SEO plugins allow per-page overrides.

Inherits WordPress core's virtual robots.txt, editable via the Settings > Reading toggle and the robots_txt filter hook, or overridden entirely with a physical robots.txt file.

WooCommerce products are a standard WordPress custom post type, so they are automatically included in WordPress core's native XML sitemap (/wp-sitemap.xml, default since WordPress 5.5). A known core limitation: products marked "hidden" in WooCommerce's catalog visibility setting can still appear in the sitemap unless an SEO plugin (Yoast, Rank Math) is used for finer WooCommerce-aware control.

WooCommerce core automatically outputs Product schema.org JSON-LD (name, image, SKU, price/currency, availability, URL) on every single product page via the woocommerce_structured_data_product hook, no plugin required. Limited to single product pages, not category/archive pages; richer schema types are commonly layered on with an SEO plugin.

No native hreflang support in WooCommerce or WordPress core; requires a multilingual plugin. WPML's WooCommerce Multilingual & Multicurrency (WCML) is the dominant option (100,000+ active WooCommerce sites) and generates hreflang tags automatically once installed, translating products, variations, cart, checkout, and emails.

Not in bare WooCommerce core, but universally available via SEO plugins (Yoast, Rank Math) that ship Open Graph/Twitter Card control for product and content pages alike, same mechanism as WordPress generally.

Achievable per product/page via an SEO plugin (Yoast, Rank Math), which is near-universal on production WooCommerce sites; WordPress core only offers a site-wide "discourage search engines" toggle, not true per-page noindex, same limitation as WordPress generally.

Native alt text field in the Media Library and block editor's image block, applicable to product images the same as any other media; the native CSV product importer notably does not support setting alt text in bulk, requiring manual entry or a plugin for that specific workflow.

Full WordPress Posts functionality is available on every WooCommerce install since WooCommerce is a plugin added to WordPress, not a replacement for it; giving WooCommerce stores the same native blogging capability as any WordPress site.

Inherits WordPress's native register_post_type() API for custom post types/taxonomies; WooCommerce itself registers "Product" as a custom post type with custom taxonomies (category, tag, attributes) using this same native mechanism.

Products have native category, tag, and custom attribute taxonomies; blog posts retain WordPress's native categories/tags; both are fully hierarchical/native taxonomies, not a plugin add-on.

Inherits WordPress's native "Publish" date/time scheduling, applicable to products as well as posts and pages.

Products are a WordPress post type and inherit native revisions (restorable diff/compare history) the same as posts and pages.

Inherits WordPress's native role system (Administrator, Editor, Author, Contributor, Subscriber) plus WooCommerce-specific "Shop Manager" role, supporting multi-author/multi-staff workflows out of the box.

Inherits WordPress core's native RSS/Atom feeds for posts, categories, and tags; no WooCommerce-specific product RSS feed is generated by default.

WooCommerce ships its own REST API (built on top of the WordPress REST API) with full read-write access to products, orders, customers, coupons, and shipping zones; a separate unauthenticated Store API serves customer-facing cart/checkout functionality.

Ecommerce is WooCommerce's entire purpose; scored as "native" within the scope of this listing (a WooCommerce-powered store), though structurally it is itself a plugin added onto WordPress rather than a built-in CMS feature.

Unlike hosted ecommerce platforms with plan-based product/variant caps, there is no WooCommerce-imposed limit.

No WooCommerce-imposed transaction cut regardless of which payment gateway is used, unlike platforms that charge extra for not using their in-house processor.

Among the widest gateway choices of any platform compared, consistent with WooCommerce's plugin-based architecture.

Native support for downloadable/virtual products in core WooCommerce, no extension required.

Requires the paid official WooCommerce Subscriptions extension ($279/yr for 1 year, or $446.40/2yr with 20% multi-year discount), not included in free WooCommerce core; supports weekly/monthly/annual billing, 25+ gateways for automatic recurring charges, customer self-management, and failed-payment recovery.

Not native to WooCommerce core; requires a currency-switcher extension. Representative official Marketplace option (TIV Multi-Currency) runs $149/yr for 1 year ($238.40/2yr with discount); WooPayments and other plugins offer alternative multi-currency approaches.

Via the free, official Square for WooCommerce extension (Woo's named preferred POS partner as of May 2025), syncing inventory/catalog/orders between the online store and in-person Square POS hardware; available in US, Canada, Australia, Japan, Ireland, France, Spain, and the UK. Transaction fees are Square's standard per-country card-processing rates, not a separate WooCommerce fee.

Not tracked by WooCommerce core by default; requires a plugin. Representative official Marketplace option (Abandoned Cart) runs $49/yr for 1 year ($78.40/2yr with discount) and includes automated email reminders, discount coupons, and optional SMS via Twilio.

Baseline tools are native; live-rate shipping and advanced automated tax filing are extension-gated, though core automated tax calculation is free via WooCommerce Tax.

Native WordPress Exporter (WXR) covers posts/pages/comments/terms; WooCommerce adds its own native Product CSV Importer/Exporter (Products > All Products > Export) covering products, attributes, categories, and inventory data. Between the two, all store content and catalog data is natively exportable without a plugin.

Two separate native export mechanisms (WXR for content, CSV for catalog) rather than one unified export, reflecting WooCommerce's layering on top of WordPress.

Because the store owner has full source-code and database access on self-hosted infrastructure, the entire site including theme, WooCommerce configuration, and database can be migrated wholesale to any other host running PHP/MySQL, same as WordPress generally.

No domain lock-in; inherits WordPress's standard domain portability since WooCommerce runs on self-hosted WordPress.

Definitionally portable; a WooCommerce store can run on any host supporting PHP and MySQL/MariaDB, the same as WordPress.org software generally, since WooCommerce is just a plugin on top of it.

The native WooCommerce REST API (built on the WordPress REST API) exposes full read/write access to products, orders, customers, coupons, and shipping zones, with authentication for write operations; WordPress's own REST API and WP-CLI provide additional full-fidelity access.

Editorial judgment: self-hosted, GPL-licensed, standard PHP/MySQL stack with full database/file access and native export tools for both content (WXR) and catalog data (CSV) makes lock-in risk low, mirroring WordPress. The main risk vector is accumulated paid-extension dependencies (e.g., a store built around WooCommerce Subscriptions) rather than the core platform itself, which is a notch higher than plain WordPress content sites but still low relative to closed SaaS ecommerce platforms.

WooCommerce's own curated Marketplace is far smaller than WordPress's overall plugin count, but any general WordPress plugin can also extend a WooCommerce store, giving effectively the same ecosystem depth as WordPress itself.

Native WooCommerce REST API (v3, built on the WordPress REST API) plus a separate unauthenticated Store API for customer-facing cart/checkout integrations.

Native webhook system configurable via wp-admin or the REST API, covering order/product/customer/coupon topics; payloads are HMAC-SHA256 signed, with automatic disabling after 5 consecutive delivery failures.

Unrestricted custom code embedding via theme files, plugins, code blocks, or header/footer injection, same as WordPress generally; no WooCommerce-specific gating.

Requirements per the current WordPress.org plugin listing (version 10.9.4 as of July 2026).

Full WP-CLI support inherited from WordPress, plus WooCommerce-specific WP-CLI commands (wc product, wc order, wc shop_coupon, etc.) documented in WooCommerce's own developer docs.

WooCommerce has dedicated Zapier support for order/customer/product events (triggers and actions), and Make.com connects via the REST API; same integration path noted for WordPress generally but with WooCommerce-specific triggers.

WooCommerce's extensibility model is plugin-based like WordPress, but it curates a stronger set of first-party commerce integrations (payments, shipping, tax) than bare WordPress core does.

No first-party AI store/site generation feature from WooCommerce or Automattic as of July 2026; WordPress 7.0's AI Client/Abilities API provides infrastructure other plugins can build on, but WooCommerce itself has not shipped a store-generation feature on it. AI store-building tools exist only as third-party plugins.

No first-party WooCommerce AI writing assistant for product descriptions as of July 2026 (unlike Shopify Magic's native Writer tool). AI product-description generation is available only via third-party plugins on the WordPress.org/Marketplace ecosystem (e.g., AI Product Tools, AI Content Generator for WooCommerce), which connect to external AI providers and are not built or maintained by Automattic/WooCommerce.

No first-party WooCommerce AI image generation/editing feature as of July 2026. Third-party plugins provide this (e.g., product image generation via connected OpenAI/Gemini accounts), but it is not a built-in WooCommerce capability.

No first-party WooCommerce AI SEO assistance as of July 2026; SEO plugins (Yoast, Rank Math) that have added AI features serve this role for WooCommerce sites the same as for WordPress generally, and the official "AI Product Recommendations" Marketplace extension (a paid, OpenAI-key-based third-party-style listing) adds an AI shopping assistant and product recommendations rather than SEO assistance specifically.

This is an architecturally significant gap versus Shopify/Wix, which bundle first-party AI directly into the core product.

Inherits WordPress's native capability-based role system and adds a WooCommerce-specific "Shop Manager" role (full store management access without full site-admin rights), plus dozens of individually assignable capabilities.

Inherits WordPress core's native post-locking (prevents two users editing the same post/product simultaneously, shows a "someone else is editing" notice) rather than true real-time simultaneous co-editing.

Inherits WordPress core's basic "Pending Review" status; structured multi-step editorial/product approval workflows require a plugin (e.g., PublishPress, Edit Flow), same as WordPress generally.

Inherits WordPress core's native content Preview; a true staging environment (full store clone for testing, including orders/inventory) is not a core WooCommerce feature and requires a hosting-provider tool (e.g., WP Engine, Kinsta one-click staging) or a plugin (WP Staging).

No native in-editor commenting/annotation on drafts or products; inherits the same gap as WordPress core (Gutenberg Phase 3 collaboration work is on the roadmap but not shipped).

No native audit/activity log of admin or store actions in WooCommerce or WordPress core; requires a plugin (e.g., WP Activity Log, Simple History) or host-level logging.

Support model mirrors WordPress's split between free community support and paid-product support, but WooCommerce adds its own Marketplace Helpdesk tier for extension/theme purchasers.

WooCommerce's official support policy makes no 24/7 availability claim for its Helpdesk (chat/email only); free-plugin users rely on volunteer community forums with no guaranteed response time at all.

Editorial judgment: woocommerce.com/document and developer.woocommerce.com provide extensive, actively maintained official documentation (merchant guides, developer handbooks, REST API reference, extension docs) on top of WordPress's own extensive documentation, backed by an active developer blog with detailed per-release notes (e.g., documented, dated deprecation notices for the Product Editor beta).

Active-install and market-share figures are WooCommerce's/WordPress.org's own published numbers; the 43% WordPress web-share figure is a third-party (W3Techs) statistic, treat as approximate.

Same structural pattern as WordPress: the plugin's own security posture depends on the chosen host, the payment gateway, and the site owner's practices, not a WooCommerce-issued certification.

No automatic backups in WooCommerce or WordPress core; requires a plugin (e.g., UpdraftPlus, which explicitly supports WooCommerce order/customer/product data and offers selective database table restoration) or a host-provided backup feature. WooCommerce's transactional data (orders, inventory) changing minute-to-minute makes backup frequency a more acute concern than for a static content site, per third-party guidance, but this remains a plugin/host responsibility, not a native WooCommerce feature.

No WooCommerce-specific accessibility tooling beyond what WordPress core and standard theme conventions already provide.

WordPress core ships translated in 70+ languages (admin UI) and WooCommerce itself is localized into 71 locales per its own plugin listing, but multi-language store content (products, cart, checkout translated per-language) is not native; requires a plugin, dominantly WPML's WooCommerce Multilingual & Multicurrency (WCML) add-on, used by 100,000+ WooCommerce sites.

Not native to WooCommerce core, but standard once WCML (WPML's WooCommerce add-on) is installed; provides a structured translation-management workflow for products, variations, cart, checkout, emails, and reviews, including AI-assisted translation.

Not native to WooCommerce core; WCML automatically generates hreflang tags and per-locale URL structures once installed, and integrates with major SEO plugins, mirroring the WordPress-wide pattern (WPML/Polylang).

Inherits WordPress core's native RTL (right-to-left) language support built into core and the block editor; theme-level RTL stylesheet support (rtl.css) is a documented core convention that WooCommerce-compatible themes follow.