WooCommerce Review 2026: Free, But Not Costless
Bottom line
WooCommerce takes no cut of your revenue and lets you use any processor, which on a store of any size outweighs every subscription fee in the category. In exchange you inherit a real systems administration job.
Research-based — not hands-on tested. Our scores are editorial judgements compiled from vendor documentation, published pricing and independent user reports. How we review.
| Type | Open-source e-commerce plugin for WordPress (self-hosted) |
| Best for | Content-led brands already on WordPress, and anyone who needs full control of checkout and data |
| Licence cost | Free — “Download WooCommerce free”; you pay for hosting and extensions |
| Platform transaction fee | None. Use any processor at its own rate, with no platform surcharge |
| You manage | Hosting, updates, security patching, backups, performance, PCI scope |
| Extension model | Marketplace of paid extensions; individual ones run to hundreds per year (e.g. Subscriptions €248/yr) |
| We run one | Yes — this review draws on operating a live WooCommerce store |
TL;DR: WooCommerce describes itself as “the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.” That is a fair summary of both the appeal and the bill. The software is free and takes no cut of your revenue, which on a store of any size is worth more than every subscription fee on this page. In exchange you inherit a systems administration job, and the specific failure modes below are ones we have hit ourselves.
The economics are genuinely different
WooCommerce has no platform transaction fee. You choose a processor and pay its rate, full stop. Set against a hosted platform charging up to 2% for using an external gateway, this is not a marginal saving — on a store processing meaningful volume it is often larger than the entire hosting bill.
It also means you can serve a market whose dominant payment method requires a specific local processor, without paying a penalty for the privilege. For anyone selling across European or Latin American markets, that flexibility is frequently the deciding factor rather than a nice-to-have.
The costs that replace it are hosting, extensions and your own time. Extensions are the one people underestimate — the marketplace is genuinely good, and individual extensions carry real annual prices (Subscriptions is listed at €248/year). Total the ones you actually need before treating “free” as the comparison.
What we have hit running one
We operate a live WooCommerce store, so this section is experience rather than research.
- The session cookie will block your caching. WooCommerce sets a session cookie to track baskets. If that happens on every page view — including your blog and policy pages — you cannot safely cache any of it at the edge, because caching a response carrying a session hands one shopper’s session to the next visitor. Check the response headers for
Set-Cookiebefore designing any caching strategy; that is the real gate, not the CDN configuration. - Personalised pages are structurally uncacheable. Anything rendering a basket count or a country-dependent shipping line is personal by definition. Editorial pages can be fast; the storefront needs those elements moved into the browser first, which is a real project.
- Payment method availability is not a settings question. A method can be enabled everywhere and still never render, because availability is decided by your store currency, the buyer’s country and amount, and the country your payment account is domiciled in. We have had a method that was structurally impossible in our store’s currency while showing as enabled throughout.
- Geo-detecting the customer’s country is worth doing and easy to get wrong. Never assign a country you do not ship to — the checkout can end up with no valid shipping option, and nothing alerts you. Leave unknown visitors unset, and let a manual choice win permanently.
None of these are arguments against WooCommerce. They are the specific shape of the job you are taking on, and all four are invisible in staging.
The publishing advantage nobody costs
Because it is WordPress, the content side is a solved problem. Landing pages, an editorial section, category copy and SEO controls all work the way they do on any WordPress site, and a marketer can ship them without a developer.
For a content-led brand that is a structural advantage, not a convenience. Publishing friction compounds — a workflow requiring a developer to change a paragraph permanently reduces how much a team publishes — and hosted platforms generally treat content as secondary to catalogue. If your acquisition strategy is search and editorial rather than paid, this belongs high in the comparison. See our hosting guide for what to run it on.
Who it suits
- Good fit: content-led brands where search and editorial drive acquisition.
- Good fit: stores with negotiated processing rates or market-specific payment requirements.
- Good fit: anyone who needs unusual checkout logic or genuine ownership of their data.
- Weaker fit: merchants with nobody to own hosting, updates and backups. This is a real job and skipping it ends badly.
- Weaker fit: teams who want a fixed monthly number with no operational variance.
What we cannot tell you from the outside
Your total extension bill and your hosting requirement, both of which depend on catalogue size, traffic and how much you customise. The honest comparison against a hosted platform is (hosting + extensions + maintenance time) versus (subscription + gateway surcharge + app subscriptions) — and it flips direction depending on revenue and payment mix rather than on preference.
Sources: WooCommerce.com product and documentation pages, retrieved July 2026; plus our own operating experience of a live WooCommerce store. Extension prices change — verify current figures before deciding.