I built WooCommerce stores for ten years. I'm building a live chat plugin for WooCommerce — woobchat, currently in beta. I know the WooCommerce plugin ecosystem from the inside. And in 2026, I plan most new e-commerce builds on a different stack — here's why.
This isn't a hate piece. WooCommerce solved a real problem for over a decade. But the world it was designed for — PHP/MySQL LAMP stacks, jQuery storefronts, slow mobile internet — is not the world your store competes in now. Here's what changed, and what the right replacement looks like.
What WooCommerce still does well
Credit first, criticism after:
- Open source, self-hosted from day one. No vendor controls your data.
- Massive plugin ecosystem. Almost any feature exists as a plugin.
- Familiar admin for non-technical owners. WordPress backend is widely known.
- Cheap to start. A €5/month shared host plus free plugins gets you a working store.
- Content + commerce in one place. Blog and store share the same CMS.
If those four things describe your priorities and your store does €10–€30k/year, WooCommerce remains a reasonable choice.
The five structural problems in 2026
Where WooCommerce breaks down today:
1. Plugin hell is a tax, not a feature. A typical mid-size WooCommerce store runs 30+ plugins. Each plugin is a security risk, an update risk, and a performance cost. Mid-size WooCommerce stores routinely pay €150–€300/month in plugin subscriptions for features that ship native in modern alternatives. The "free" platform has the highest hidden tax of any option.
2. Lighthouse scores around 55 on mobile. WooCommerce's runtime architecture — PHP per-request rendering, jQuery storefront, theme + plugin asset chain — fights against Core Web Vitals. You can tune it (caching plugins, CDN, lazy-load) but you hit a ceiling around 75 before structural changes are needed.
3. Security plugins are a recurring cost. Wordfence, Sucuri, or iThemes Security aren't optional anymore — and they aren't cheap at scale. Add managed hosting that does some of this for you (Kinsta, WP Engine) and you're at €40+/month before any store features.
4. Headless support is bolted on. WooCommerce has a REST API, but the data model and the admin assume a coupled front-end. Going headless on WooCommerce means working around it, not with it.
5. Updates are dangerous. WordPress core, WooCommerce, theme, and 30+ plugins all update independently. Every quarter something breaks. Emergency fix invoices after plugin/WooCommerce version conflicts are a normal part of running a WooCommerce store at scale. That's not the platform's fault — it's the architecture's consequence.
What's the actual alternative
The honest answer in 2026: headless commerce on a Node.js backend with a Next.js storefront. The leading open-source option for this is Medusa.js v2.
It's the same architectural principle as Shopify Hydrogen — split the storefront (React/Next.js) from the commerce engine (Medusa) — but without the SaaS lock-in. You own the database, the code, and the hosting choice.
What changes structurally:
- Storefront is static or ISR-cached. Pages render once, serve from CDN. No PHP per request.
- The admin runs separately as its own service. It's not in the customer's request path.
- Plugins are code, not configuration. When you need a feature, you write or install a Node module — it doesn't slow down the storefront.
- Multi-currency, multi-language, multi-region are native to the data model, not retrofitted via plugins.
The cost: higher initial development effort, lower ongoing maintenance. A WooCommerce migration starts around €1,200 from a working baseline. Here's the migration playbook →
Side-by-side: real numbers
The Lighthouse and TTFB figures are typical production values, not best-case demos. For the deeper performance story see How to get 90+ on PageSpeed Insights →
When NOT to migrate
Honest disclaimers — migration isn't right for everyone:
- Revenue under €20k/year. The build cost won't pay back within a reasonable horizon.
- Content-first sites with a small store. If your blog is the main product, WordPress + WooCommerce still earns its place.
- You have no developer relationship. Headless requires either a partner or in-house dev for non-trivial changes. WooCommerce has a much larger pool of cheap freelancers.
- You ship in 2 weeks or less. Migration projects take 3–6 weeks done correctly. If your launch deadline is tight, stay where you are and migrate later.
Who should migrate now
- Stores doing €30k+/year where page speed measurably affects conversion.
- Stores running paid ads where slow pages inflate CPA.
- Stores planning multi-region or multi-language expansion.
- Stores that have outgrown a single developer's ability to maintain plugins.
- Anyone whose WooCommerce has had two or more emergency outages this year.
If two or more of these describe you, the math points to headless. The next step is the migration plan →
What migration actually looks like
A typical WooCommerce-to-Medusa migration:
- Week 1 — Audit and SEO map. Catalogue export, URL inventory, redirect map, schema audit.
- Week 2–3 — Build the Medusa baseline. Import products, customers, orders. Configure regions, currencies, taxes.
- Week 3–4 — Build the Next.js storefront. Restore theme look and feel (or rebuild from Figma), rebuild custom flows, restore content pages.
- Week 4–5 — Analytics, ads, tracking. GA4 + Meta CAPI server-side, GMC feed, schema, hreflang. Preserve attribution history where possible.
- Week 5–6 — Cutover. 301 redirect map deployed, DNS switch, staged customer notification.
Cost starts at €1,200 for sub-200-SKU stores; scales with catalogue complexity and custom flows.
FAQ
Will I lose SEO rankings during migration? With a proper 301 map and preserved URL structure, no. Most clients see rankings recover within 2–4 weeks, and many see lift because of the speed improvement.
Can I keep my WordPress blog separately? Yes. WordPress can stay as a sub-path (e.g. /blog) or a sub-domain alongside the Medusa storefront. Many clients keep their content authoring workflow exactly as-is.
What about my WooCommerce subscriptions, bookings, or B2B plugins? These need re-implementation, not direct migration. Most have direct equivalents in Medusa or can be built in a few days each. Budget €500–€1,500 per significant flow depending on complexity.
Is Medusa.js production-ready in 2026? Yes. Medusa v2 has been generally available for over a year, has paying customers running real stores, and is actively maintained by a well-funded team.
Why not Shopify Hydrogen? Hydrogen is excellent technology with the same architectural advantages — but it still locks you into Shopify's commerce engine and pricing model. The Shopify cost analysis still applies. Here's the breakdown →
Next steps
If you're running a WooCommerce store doing more than €30k/year and the points above describe your reality, the move is worth modelling. Send a one-line brief → and I'll come back within 24 hours with a fixed migration quote — usually between €1,200 and €3,000 depending on catalogue and custom flows.