WooCommerce
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Automattic Inc. · woocommerce.com
Compare with Shopify → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
WooCommerce at a glance
- Vendor
- Automattic Inc.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Oct 2026
- Panel verdict
- The AI panel rates WooCommerce 3/5, the mean of 6 judges. WooCommerce is Automattic Inc.'s open-source shop platform for WordPress. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
WooCommerce is Automattic Inc.'s open-source shop platform for WordPress. The bench's strongest scores are pricing transparency and data control and exit: a free core with no monthly subscription, extensions at $29 – $299/year per extension, hosting at $25 – $350/month for most stores, WooPayments at ~2.50-2.90% + 30¢ per transaction, 0 % revenue share, and a documented import/export suite that moves products, orders, customers and images in CSV or XML with no hard record limit. Sovereignty is the weakest area, where scores cluster at 3: Dublin entities are named for residents of the Designated Countries, standard contractual clauses cover transfers outside the EEA and the UK, Automattic Inc. of San Francisco is controller for everyone else, and we found no public information on hosting location, a data-processing agreement or subprocessors. Tax and legal scores 3-4 — automated rates for supported countries, but the German B2B chain is unproven — and catalog and checkout scores 4-5 on unlimited variants and multiple gateways. No disagreements were flagged.
Speaks for it
- Free core with no monthly subscription, unlimited products, orders and APIs, and 0 % revenue share
- Published à la carte pricing — extensions $29 – $299/year per extension, hosting $25 – $350/month for most stores, WooPayments ~2.50-2.90% + 30¢ per transaction
- Documented exit via CSV or XML export of products, orders, customers, subscriptions and images with no hard record limit, plus Shopify CSV import
- Fulfilment system with partial fulfilments, an automatically calculated 'Partially Fulfilled' order status, 70+ international shipping providers and USPS/DHL label printing
- Open-source WordPress plugin downloadable from WordPress.org, runnable on any host, with a marketplace of hundreds of extensions and themes
Held against it
- Sovereignty scores cluster at 3, with no public information found on hosting location, a data-processing agreement or the subprocessor chain
- No public information found on German payment methods such as PayPal, invoice or direct debit, or on guest checkout
- No public information found on VAT ID validation, reverse charge, OSS reporting or the German checkout-legal requirements
- No public information found on returns and refund handling in the system or maintained ERP and accounting interfaces such as DATEV
- Captured pages give different figures for the same extension (44 € and 45 €; 116 € and 117 €)
Best for
- You want to own your stack: an open-source platform on your own WordPress, with a documented export path for products, orders and customers
- You are migrating from Shopify and need your product CSV accepted as-is
- You ship through major carriers and need partial fulfilments, tracking emails and USPS/DHL labels in the core workflow
- You want costs you can compute before committing — a free core, à la carte extensions and 0 % revenue share
Avoid if
- Your procurement requires a European controller and a documented subprocessor chain — outside the Designated Countries the controller is Automattic Inc. of San Francisco, and transfers outside the EEA and the UK rely on standard contractual clauses
- You sell B2B in Germany and need VAT ID validation, reverse charge and invoicing proven — the pages show automated rates for supported countries and role-based net display via a paid third-party extension
- You need German consumer checkout conversion in the core — the documented conversion aids, such as skip cart and direct checkout, arrive as paid third-party extensions
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 2 of 5 |
| Tax & German legal correctness | 2 of 5 |
| Extensibility & developer surface | 3 of 5 |
| Order operations & back office | 3 of 5 |
| Data ownership & exit | 4 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 4 of 5 |
Catalogue & checkout
Show reasoningHide reasoning
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and buy-now-pay-later where offered.
10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.
The Merchant
The checkout is genuinely mine to change — the pricing page says "Customize your checkout without forced upgrades", the platform runs cart and checkout blocks, and a direct-checkout extension lets customers skip the cart with the button shown or hidden per product, category, tag and customer role — alongside unlimited product variants and coupons as core data. I found no public information on the payment methods German shoppers expect (PayPal, invoice, direct debit) through named providers on the product pages, nor on guest checkout, abandoned-cart recovery or rule-based promotions, and those are the conversion levers I actually sell with. 2 5 2 5 12
The B2B Seller
The captured pages show a catalogue with unlimited products and unlimited variants, a checkout that can be customised without forced upgrades and run through multiple payment gateways at no extra platform cost, plus conversion add-ons such as a skip-cart direct checkout. We found no public information on guest checkout, vouchers, or named providers for the payment methods German buyers expect — PayPal, invoice, direct debit — so it sits a step above a basic catalogue-and-checkout and clearly short of trade-grade pricing rules. 2 2 5
The Developer
The platform documents unlimited products and unlimited variants, coupons in the data model, and multiple payment gateways with a checkout customisable without forced upgrades, plus cart and checkout blocks compatibility and a marketplace of checkout features. That clears the basic catalogue-and-payment level and moves toward the variants-and-vouchers level. We found no public information on guest checkout or on German payment methods such as PayPal, invoice or direct debit being included. 2 2 5 5 12
The Operations Lead
Unlimited products and unlimited variants plus coupons come with a checkout the merchant can customise without forced upgrades and run with multiple gateways, and the marketplace sells a skip-cart direct-checkout conversion extension. But I found no public information on payment methods German buyers expect such as PayPal, invoice or direct debit through named providers, and nothing on guest checkout or abandoned-cart recovery. 2 2 12 5
The Data Protection Officer
The checkout is real and shapeable: unlimited product variants, coupons and subscriptions in the data model, several gateways with WooPayments named at ~2.50-2.90% + 30¢, plus skip-cart, direct checkout and cart & checkout blocks as conversion aids. We found no public information on the payment methods German buyers expect (PayPal, invoice, direct debit) or on abandoned-cart recovery. From my desk, 'pick your processor' is welcome control over the checkout, but it also means the payment-routing chain sits outside this documentation. 2 2 5 5 12
The Skeptic
Variants are documented with 'Unlimited' limits and coupons run through the platform's data model, and payment runs through named processing — WooPayments at published rates — with the vendor stating merchants can 'Run multiple gateways'. We found no public information on guest checkout, on the payment methods German buyers expect such as PayPal, invoice or direct debit, or on tiered, customer-group or rule-based pricing; the conversion features we do see, skip cart and direct checkout, arrive as a paid third-party extension. 2 2 12 5
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.
10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.
The Merchant
Automated tax calculation for supported countries, with a named extension that switches prices inclusive, exclusive or both per user role across product, shop, cart and checkout pages — plus percentage tax display and a country tax preview bar — covers the VAT display basics a German shop needs. I found no public information on VAT ID validation or reverse charge for B2B, OSS reporting, invoicing or e-invoicing, or the German checkout requirements such as order button wording, withdrawal policy and price indications, so legal correctness beyond tax display rests with the merchant. 6 7 7 7
The B2B Seller
WooCommerce Tax automates tax rates for supported countries, and a marketplace extension switches prices between inclusive and exclusive of taxes per user role on product, shop, cart and checkout pages — the net display my trade customers demand, though through a third-party extension rather than the core platform. We found no public information on VAT-ID validation, reverse charge, OSS, invoices issued from orders, or the German checkout requirements, so the B2B chain is unproven on these pages. 6 7
The Developer
Tax rates are set up automatically for supported countries through WooCommerce Tax with no manual rate tables, and a named extension controls gross, net or both price display per user role across product, shop, cart and checkout pages. We found no public information on VAT ID validation, B2B reverse charge, invoicing from orders, or the German checkout requirements such as order button wording, withdrawal policy and price indications. 6 7 7
The Operations Lead
Automated tax calculation for supported countries with rates set up automatically, and gross or net price display per user role on product, shop, cart and checkout pages, is real destination-country VAT with per-group display. I found no public information on VAT ID validation or reverse charge, OSS reporting, invoicing and e-invoicing, or the German checkout requirements such as order button wording and the withdrawal policy. 6 7 7
The Data Protection Officer
Tax rates are automated for supported countries via WooCommerce Tax — set up automatically, no manual entry — and price display switches between including and excluding tax per user role on product, shop, cart and checkout pages, though both prices at once is not available for the cart total. We found no public information on VAT ID validation, reverse charge, OSS, invoicing with XRechnung or ZUGFeRD, or the German checkout-legal requirements. Before I could defend this in a complaint, I would need the supported-country list and the invoicing story in writing. 6 7 7
The Skeptic
Automated tax calculation is documented — 'tax rates are set up automatically; no need to enter them manually' for supported countries — and gross or net display, even per user role, is handled by a named third-party extension that itself concedes showing both prices is 'not available for the cart total'. We found no public information on B2B reverse charge, VAT ID validation, OSS reporting, invoices issued from orders, or the German checkout requirements of order-button wording, withdrawal policy and price indication. 6 7 7
Extensibility & developer surface
Show reasoningHide reasoning
How this is scored
Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.
0 — A closed shop builder: no themes to edit, no apps or plugins and no API.
3 — Themes adjustable in an editor and a set of apps or plugins to add features.
5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.
8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development environments, version control for themes, and documented rate limits.
10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.
The Merchant
This is an open-source plugin the merchant downloads from WordPress.org and runs on their own WordPress, with hundreds of extensions and themes through a marketplace that runs vulnerability and best-practice checks, developer resources, unlimited APIs, and even a documented API on the fulfilments system. I found no public information on webhooks for order events, a headless storefront API or documented rate limits, so the code can be owned while the documented platform surface stays modest. 6 11 1 2
The B2B Seller
This is an open-source WordPress platform with a marketplace of hundreds of extensions and themes, developer resources, unlimited APIs, and a plugin model third parties demonstrably extend — the captures show plugins adding fulfilment statuses and third-party metadata riding along in imports. We found no public information on webhooks, a headless storefront API, or theme code access, which keeps a genuinely strong ecosystem at the middle of the scale. 1 2 12 11
The Developer
This is a plugin ecosystem in the real sense: an open-source WordPress platform free to download, hundreds of extensions and themes, extensions installed as code through the Plugins screen with declared platform and PHP versions, and third-party plugins demonstrably extending core behaviour such as fulfilment statuses. What keeps me from scoring higher is silence on the developer tooling I judge by — we found no public information on theme template code access, webhooks, headless storefront APIs, staging environments, version control for themes, or a dependency model between plugins. 1 2 1 7 11
The Operations Lead
A free, open-source WordPress platform with a marketplace of hundreds of extensions and themes, unlimited APIs, developer resources, and third-party plugins that extend even core systems like fulfilment statuses — customizations that stay yours, source downloadable from WordPress.org. I found no public information on webhooks for order events, a headless storefront API, staging environments or documented rate limits. 2 1 2 11
The Data Protection Officer
This is an open-source platform on the merchant's own WordPress — free, with any host, any payments, any features and unlimited APIs in the core — plus a marketplace of hundreds of trusted extensions and themes, and customisations the merchant keeps. That is more shaping freedom than a closed builder gives. Still, we found no public information on headless storefront APIs, staging environments, theme version control or documented rate limits on the captured pages. 2 1 2 1 1
The Skeptic
The core is open source on WordPress, hostable on 'any host', with an API included in the free core, developer resources, a marketplace of 'hundreds of trusted extensions and themes', and third-party plugins documented as extending even the fulfilment statuses. We found no public information on webhooks for order events, a headless storefront API, staging environments or documented rate limits, so the developer surface beyond the plugin ecosystem is not established on the captured pages. 2 1 1 11
Order operations & back office
Show reasoningHide reasoning
How this is scored
What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
0 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.
3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.
5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.
8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).
10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.
The Merchant
The fulfilment system is real back office: partial fulfilments with an automatically calculated "Partially Fulfilled" order status, notification emails carrying tracking numbers and carriers, 70-plus shipping providers including UPS, FedEx, DHL and USPS, ready-to-print USPS and DHL labels, and scheduled import and export jobs via FTP. The captured pages state that live rates in the cart require a further extension and that labels cannot be generated for Canada Post at this time, and I found no public information on multi-location stock or maintained interfaces to ERP and accounting systems such as DATEV. 6 11 10 13
The B2B Seller
Fulfilment is properly worked: partial fulfilments with an automatically calculated order status, customer emails with tracking numbers and carriers, label printing for USPS and DHL, support for 70+ providers including UPS, FedEx and DHL, and an API for shipping integrations. We found no public information on stock and warehouse management, returns and refunds, or maintained ERP and accounting interfaces such as DATEV, which holds it back from the top level. 11 6 13
The Developer
The fulfilment system documents item-level tracking with an automatically calculated partially-fulfilled order status, email notifications with tracking numbers, more than 70 shipping providers including UPS, FedEx, DHL and USPS, and ready-to-print USPS and DHL labels. We found no public information on returns or refund processing in the system, multi-warehouse stock, marketplace order intake, or maintained ERP and accounting connections such as DATEV. 11 6 10
The Operations Lead
The fulfilments system is what I want to see: it tracks which items in an order have shipped, supports partial fulfillments with an automatic 'Partially Fulfilled' order status, emails customers tracking numbers, names 70+ carriers including UPS, FedEx, DHL and USPS, and prints ready-to-print labels for USPS and DHL. But it stops there — I found no public information on returns or refund handling in the system (partial refunds above all), multi-warehouse stock, multi-channel order intake, or maintained ERP and accounting interfaces such as DATEV. 11 6 10
The Data Protection Officer
The fulfilment system tracks which items in an order have shipped, supports partial fulfilments with an automatically calculated order status, sends customers status emails with tracking numbers, auto-detects the carrier from the tracking number, and names 70+ providers including UPS, FedEx, DHL and USPS, with ready-to-print labels for USPS and DHL and an API for shipping tools. Live shipping rates at checkout require a further extension, and we found no public information on multi-warehouse stock, marketplace order intake, or maintained interfaces to ERP and accounting systems such as DATEV. 11 6 10
The Skeptic
After checkout there is a real fulfilment system: partial fulfilments with an automatically calculated 'Partially Fulfilled' status, notification emails carrying tracking numbers, support for '70+ international shipping providers', and label printing for USPS and DHL — though the pages state live rates at checkout require further extensions and that labels 'cannot be generated for Canada Post at this time'. We found no public information on stock management, returns and refund handling in the system, or maintained interfaces to ERP and accounting systems such as DATEV. 11 6 13
Data ownership & exit
Show reasoningHide reasoning
How this is scored
Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.
0 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.
3 — CSV export of products and customers, or of orders, from the admin.
5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.
8 — Full-fidelity export including media and order documents, a documented migration path in and out, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.
10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.
The Merchant
Exit and entry are both documented: a named import and export suite moves products, orders, customers, coupons, subscriptions, reviews and images in CSV or XML with no hard record limit, accepts a Shopify product export as-is, recommends a migration order, and links parent and renewal subscriptions while IDs change. With the open-source core, "Choose any payments, any features, any host" and no revenue share, ownership is structural rather than promised; I found no public information on a contractual data-return guarantee on cancellation. 3 13 2 1 12 12
The B2B Seller
Everything a merchant needs to leave is exportable: products, orders, customers, coupons, subscriptions, images and third-party metadata in CSV or XML with no hard record limit, a documented migration sequence, and Shopify imports as the way in; the platform is open-source and the pages say to choose any payments, any features, any host. This is ownership by structure rather than promise, though we found no public information on exporting order documents such as invoices or on contractual data return. 12 13 2 12
The Developer
Exit is documented in practice rather than only promised: CSV and XML export of products, orders, customers, coupons, subscriptions and reviews including images and third-party metadata, a recommended whole-store migration sequence, Shopify CSV import for the way in, and scheduled FTP and SFTP jobs. The platform is open source with a choice of any host, zero revenue share and costs tied to infrastructure rather than sales volume, so leaving is not metered by volume. We found no public information on database-level access or a contractual data-return commitment. 12 12 13 2 1
The Operations Lead
Migration in and out is documented — a recommended import sequence from customer to order, Shopify CSV import coming in, and CSV or XML export of products, orders, coupons, subscriptions, customers and reviews including images and third-party metadata — on an open-source platform the merchant can host anywhere, with no hard record limit. I found no public information on exporting order documents such as invoices, or on data return or deletion when a subscription ends. 13 13 12 2
The Data Protection Officer
Ownership is close to structural: an open-source platform, free to download and runnable on any host, so the catalogue, customers and order history live in the merchant's own installation. Import and export covers products, orders, customers, subscriptions and reviews via CSV or XML, including custom and hidden metadata, third-party plugin data and product images, over FTP/SFTP on schedules with no hard record limit and zero revenue share; a Shopify CSV import and a documented migration sequence give the path in, full export the path out. We found no public information on database-level access or contractual data-return terms. 2 1 1 12 12 12 13
The Skeptic
Exit is documented in unusual depth through the paid Import Export Suite: products, orders, customers, subscriptions, images and third-party metadata in CSV or XML, roughly sixty order fields including refund items and order notes, a migration path in from Shopify CSV and out store-to-store with a recommended sequence, and no hard record limit — all on an open-source core the merchant can host anywhere. Leaving costs a flat annual licence for the tooling rather than metered extraction; we found no public information on exporting generated order documents such as invoices, and cancellation is addressed only at account level, with some information retained for legal obligations. 12 13 2 3
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.
The Merchant
The privacy policy names WooCommerce Ireland Ltd. at Grand Canal Dock, Dublin as the controller for Woo services for residents of the Designated Countries, with European Commission approved standard contractual clauses covering transfers outside the EEA — one European element proven. Data residency, hosting options and any data processing agreement are unknown on the captured pages, so the rest of the chain, including subprocessors in the checkout path, is unstated. 3
The B2B Seller
The privacy policy names WooCommerce Ireland Ltd. in Dublin as controller for Woo services for residents of the Designated Countries, while the US parent Automattic Inc. in San Francisco controls everything else, and standard contractual clauses govern transfers out of the EEA. Hosting, data residency, the DPA and the subprocessor chain are not established on the captured pages, so exactly one European element is proven and the rest stays open — for EU buyers that is a question the vendor should answer in writing. 3
The Developer
One European element is proven: residents of the Designated Countries contract with WooCommerce Ireland Ltd. in Dublin for Woo services, and transfers outside the EEA or UK are covered by standard contractual clauses; the controller for everyone else is Automattic Inc. in San Francisco. We found no public information on where customer and order data are hosted for the vendor's own services, the subprocessor chain, or a published data processing agreement, so only the one proven element counts. 3 1
The Operations Lead
The privacy policy names WooCommerce Ireland Ltd. in Dublin as controller for residents of the Designated Countries, with standard contractual clauses for transfers outside the EEA/UK — one European element proven. Everything else is unstated: I found no public information on data residency, hosting options, a DPA or subprocessor locations, and residents outside the Designated Countries contract with Automattic Inc. of San Francisco. 3
The Data Protection Officer
Two Dublin entities are named for residents of the Designated Countries — WooCommerce Ireland Ltd. and Aut O'Mattic A8C Ireland Ltd. — and transfers out of the EEA run on European Commission approved standard contractual clauses, while the default controller for everyone else is Automattic Inc. in San Francisco. That is one European element proven with the rest of the chain unstated: we found no public information on where hosting sits, no published data-processing agreement, and no subprocessor list telling me where the CDN, analytics and payment routing in the checkout actually process. For a checkout this full of third parties, that silence is the whole story of the score. 3
The Skeptic
The privacy policy names WooCommerce Ireland Ltd. and Aut O'Mattic A8C Ireland Ltd. in Dublin as controllers for residents of the Designated Countries — one proven European element — while the vendor is Automattic Inc. of San Francisco, and the same policy relies on standard contractual clauses for transfers outside the EEA and the UK. We found no public information confirming where shop and order data is hosted, on a published data-processing agreement, or on the subprocessor chain in the checkout path. 3
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier.
5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.
8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.
10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.
The Merchant
Pricing is laid out unusually plainly for an open-source platform: the core is free with no monthly subscription, extensions are "à la carte $29 – $299/year per extension", hosting is "Choose your provider $25 – $350/month for most stores", WooPayments runs "~2.50-2.90% + 30¢ per transaction", revenue share is "None", and neither third-party gateways nor localized selling carry an extra fee, with named extensions priced in euros and the billing period stated. Hosting is a range that "scales with traffic and performance needs", VAT treatment appears only in embedded product data, and the captured pages give different figures for the same extension (44 € and 45 €; 116 € and 117 €), so the true annual figure is computable only as a range. 2 12 5 2 12
The B2B Seller
The pricing page is unusually honest: the core is free with no monthly subscription, extensions are à la carte at $29 – $299/year per extension, hosting runs $25 – $350/month from a provider of the merchant's choosing, WooPayments charges ~2.50-2.90% + 30¢ per transaction with no extra fee for another processor, and revenue share is zero — a merchant can compute a year's cost almost to the euro. Extension prices are listed in EUR with the billing period stated and shown net of VAT, which is how trade buyers want it; only the hosting and processing ranges keep it from complete computability. 2 2 5 12
The Developer
The pricing pages make an annual cost largely computable: core is free with unlimited products, orders and APIs, extensions run $29 – $299/year, hosting $25 – $350/month, revenue share is none and there are no tiers, and payment processing is stated at ~2.50-2.90% + 30¢ per transaction with WooPayments with no additional fee for using a third-party processor. Individual extension prices are public with one-year and two-year terms, a 30-day money-back guarantee, and VAT shown as excluded in the product pricing data. Hosting cost still scales with traffic, which is what keeps full computability out of reach. 2 2 12
The Operations Lead
The pricing pages are straight with a merchant: the core is free with no monthly subscription, hosting is "$25 – $350/month for most stores", extensions are à la carte "$29 – $299/year", WooPayments charges "~2.50-2.90% + 30¢ per transaction", there is 0 % revenue share and no additional fee for a third-party payment solution — so the annual cost structure is computable from public pages, with unlimited products and orders stated. Individual extensions carry public prices with billing periods and a 30-day money-back guarantee, though the captured pages give different figures for the same extension on different dates (44 € and 45 €; 116 € and 117 €), and VAT treatment appears only in product data rather than as a stated policy. 2 2 12 5
The Data Protection Officer
A merchant can compute the real cost from public pages: 'Core platform: WooCommerce Free, with no monthly subscription', extensions 'à la carte $29 – $299/year per extension', hosting '$25 – $350/month for most stores', WooPayments at '~2.50-2.90% + 30¢ per transaction', '0 % revenue share' and no extra fee for third-party payment solutions, with concrete annual prices such as 45 € and 117 € and 1-year or 2-year billing periods plus a 30-day money-back guarantee on product pages. Unlimited products, orders and APIs remove volume limits from the maths, and the structured offer data marks VAT as excluded. The softness is that hosting is published only as a range and support beyond the free tier is not priced. 2 2 5 12 5
The Skeptic
A rare case where the headline is close to the invoice: the core is stated as free with 'no monthly subscription', revenue share is '0 %', WooPayments rates are published at '~2.50-2.90% + 30¢ per transaction', extensions are listed at $29 – $299/year per extension, hosting is honestly ranged at $25 – $350/month with the admission that it 'scales with traffic', and marketplace prices are marked as excluding VAT with billing periods stated. Full computability still eludes the buyer — hosting and the processor mix are open variables — and the captured pages give different figures for the same plan, 116 € and 117 € for one year of the import/export suite, which a buyer should reconcile. 2 2 12 12
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Not determined
unverified
Why unverified?The vendor's pages name a local subsidiary and do not state the parent's seat. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source |
Open source (copyleft)
unverified
Why unverified?The GPL claim covers 'the vast majority' of Automattic's work collectively rather than naming WooCommerce's licence specifically, and the WooCommerce pages say only 'open-source' without naming a licence. |
1/1 pts | 3 Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about WooCommerce
Is WooCommerce European?
No. whats-best.ai classifies WooCommerce as Rest of world.
Where does WooCommerce store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does WooCommerce have a free plan?
Yes. WooCommerce has a free plan, per the vendor’s page captured 1 Oct 2026.
What are the best alternatives to WooCommerce?
As of 18 Nov 2026, the panel rates JTL-Shop (3.5/5), Saleor (3/5) and Shopware (3/5) highest among the other 28 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is JTL-Shop (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: WooCommerce alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Open source. The GPL claim covers 'the vast majority' of Automattic's work collectively rather than naming WooCommerce's licence specifically, and the WooCommerce pages say only 'open-source' without naming a licence.
- Weak sourcing — Legal entity. The vendor's pages name a local subsidiary and do not state the parent's seat.
- Weak sourcing — Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 255 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 47 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage woocommerce.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 19 Oct 2026 Details →
- 2 Pricing woocommerce.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 3 Privacy policy automattic.com Checked 16 Nov 2026 Details →
- 4 Catalogue & checkout — found from sitemap woocommerce.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026, 1 Oct 2026 Details →
- 5 Catalogue & checkout — found from sitemap woocommerce.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026, 1 Oct 2026 Details →
- 6 Tax & German legal correctness — found from sitemap woocommerce.com Checked 16 Nov 2026 Details →
- 7 Tax & German legal correctness — found from sitemap woocommerce.com Checked 16 Nov 2026 +2 earlier captures: 19 Oct 2026, 1 Oct 2026 Details →
- 8 Extensibility & developer surface — found from sitemap developer.woocommerce.com Checked 16 Nov 2026 Details →
- 9 Extensibility & developer surface — found from sitemap developer.woocommerce.com Checked 16 Nov 2026 Details →
- 10 Order operations & back office — found from sitemap woocommerce.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026, 1 Oct 2026 Details →
- 11 Order operations & back office — found from sitemap woocommerce.com Checked 16 Nov 2026 Details →
- 12 Data ownership & exit — found from sitemap woocommerce.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026, 1 Oct 2026 Details →
- 13 Data ownership & exit — found from sitemap woocommerce.com Checked 16 Nov 2026 +2 earlier captures: 19 Oct 2026, 1 Oct 2026 Details →