WooCommerce doesn’t cap your products or orders, and you choose the hosting, so few stores ever hit a WooCommerce limit. What they outgrow is the back office around the store, and the work of keeping a stack of plugins running. That’s usually when someone starts looking for a WooCommerce ERP.
Does a WooCommerce store need an ERP? Only when the business can’t answer basic questions without a spreadsheet, or keeping the store and your other systems in step has become someone’s job.
We implement Odoo, and we’ve moved a store from WooCommerce to Odoo, so we benefit if you switch. Most of what follows is about how to tell you don’t need to.
Key takeaways
- WooCommerce’s limits are mostly yours to set. Hosting, plugins and whoever maintains them decide how far it goes.
- Hosting and plugins are the cheap part. In an agency partner’s example on WooCommerce’s pricing page, a $2M store spends $600 a year on them and $35,000 a year on maintenance.
- A slow store often isn’t a reason to leave. Hosting, caching and WooCommerce’s newer order storage fix most of it.
- What breaks first is a question you can’t answer, like what an order really cost you, or which system has the right stock.
- There are three answers, not two. Stay as you are, keep WooCommerce and put an ERP behind it, or move the store and the back office together.
What WooCommerce actually costs and limits
Search “WooCommerce limitations” and you’ll find product counts and server specs. Here’s what WooCommerce publishes itself.
| Item | What WooCommerce says |
|---|---|
| Core plugin | Free, no platform fee, no revenue share (pricing page) |
| Products and orders | Unlimited (pricing page) |
| Hosting | $25 to $350 a month for most stores (pricing page) |
| Extensions | $29 to $299 a year each (pricing page) |
| Official support | Latest core release and the one before it (support policy) |
| Release pace | Roughly monthly (releases) |
| Variable products | Dropdowns become static above 30 variations (docs) |
The same pricing page carries cost examples from one of WooCommerce’s agency partners. Their $2M boutique brand costs about $139,000 in year one and about $89,500 a year after that. Hosting is $300 a year of it, and premium plugins another $300. The rest is development, maintenance, third-party services and payment fees, with maintenance at $35,000 a year once the store is built.
So the software is close to free. The people who build and maintain it are not.
Why limits are the wrong test
A limit tells you when a record can’t be created. It tells you nothing about whether your business can answer its own questions, or how much of someone’s week goes into keeping the store up.
WooCommerce is a plugin on WordPress, and every feature you add is another plugin with its own update schedule. Core ships about once a month. Fall two releases behind and you’re outside official support. Fall behind on plugins and you carry the risk yourself: Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 91% of them in plugins, and 46% had no fix by the time they were disclosed.
WooCommerce isn’t fragile because of this. But someone in your business owns update day, and it’s worth knowing who, and how much of their week it takes.
What breaks first behind a WooCommerce store
The general warning signs of needing an ERP are covered in our piece on when a store needs one. These are the ones we see behind WooCommerce stores in particular.
You can’t say what an order cost you. WooCommerce knows the sale. Your supplier invoice, the freight in and the returns live somewhere else. If landed cost needs a spreadsheet, every margin decision depends on a join someone does by hand.
Purchasing happens in email. WooCommerce is built to take orders from customers, not to place them with suppliers. So lead times and backorders sit in an inbox until the person who knows them is away.
Two systems disagree, and the team knows which one lies. Stock in WooCommerce says one thing and the accounting or inventory plugin says another. Your staff have quietly learned which to trust.
Keeping the systems in step has become a job. That’s the clearest signal. A UK company advertised a Webshop & ERP Coordinator role at about £31,000, splitting the week roughly evenly between keeping its WooCommerce shop accurate and working in Odoo. When running two systems side by side needs its own salary, that’s a strong sign you’ve outgrown the setup.
What looks like outgrowing WooCommerce but isn’t
A slow site. Usually hosting, caching or a heavy theme. If your store is older, also check how it stores orders. WooCommerce used to keep orders in WordPress’s general posts tables. Since version 8.2 in October 2023, High-Performance Order Storage puts them in their own tables, and it’s the default for new stores. Older stores have to switch it on, and any incompatible plugin blocks the switch. So advice that blames slow admin screens on orders sitting in the posts table applies to older stores that haven’t switched.
Lots of plugins. Plenty of plugins that agree with each other are a working stack. Two that hold the same stock figure and disagree are a problem, whatever the count.
A missing feature. If one extension fixes it, buy the extension.
A revenue milestone. A $10M single-channel store with simple shipping can be fine. A $3M store selling retail and trade, with freight, may not be.
Being told you have. Most pages on this topic are written by someone selling the exit, whether that’s another storefront or an ERP. That includes this one, so test our advice against the three questions further down.
The one constraint that does bite: configurable products
Products built from parts are where WooCommerce strains first, at any size. Two examples from its own docs. Product Bundles can’t contain other bundles, so a kit inside a kit needs the separate Composite Products extension. And once a product passes 30 variations, its storefront dropdowns become static.
Our client’s gate and hardware kits ran on WooCommerce with a custom configurator and a growing set of extensions. It worked well at first. As sales and the range grew, keeping plugins compatible, paying their subscriptions and hand-quoting freight got harder to keep up with. We rebuilt the configurator as an Odoo module, which we cover in when a product configurator is worth building and the case for phantom BOMs.
That’s an architectural reason to move. If your products are assembled or configured, the configurator belongs in the system that knows your bill of materials and your stock.
Should you keep WooCommerce, add an ERP, or move to Odoo?
Answer three questions honestly.
- Can you state the landed cost of your best seller right now, without a spreadsheet?
- When stock disagrees between two systems, does someone have to decide which is right?
- Is keeping the store, its plugins and your other systems in step part of somebody’s job?
If all three answers are comfortable, stay where you are. Spend the money on better hosting or a reliable maintenance plan instead.
If they aren’t, you have two real options.
Keep WooCommerce and put an ERP behind it
This is the smaller project, and it’s the right one when the storefront works and the back office doesn’t. You keep your theme, your content and your SEO, and the ERP takes over stock, purchasing and accounting.
The cost is the connector between them. You now run two systems and a sync, and someone has to decide which system owns each piece of data and watch the sync log when it fails. If Odoo is the ERP, connectors exist on both sides, as Odoo modules such as this one on the Odoo Apps store and as WordPress plugins. Odoo-side modules need Odoo.sh or your own server, because Odoo Online doesn’t run custom or App Store modules. At least one WooCommerce-side plugin connects to Odoo Online through its own hosted service. Check which side a connector lives on before you choose your Odoo plan.
Move from WooCommerce to Odoo, store and back office together
This makes sense when the storefront itself is part of the problem: configurable products, trade and retail pricing on the same catalog, or a plugin stack that takes more upkeep than it’s worth. There’s no sync to babysit afterwards, because the store and the stock are the same system.
That’s the move our client made. Products, descriptions, manuals and videos all came across. None of it came across by itself, though. We wrote a parser to carry the old HTML product content into Odoo, rebuilt the configurator as a module, and moved trade pricing into Odoo’s pricelists. Every plugin you run is a feature someone has to rebuild or replace, so list them before you price the move.
We measured the result with Largest Contentful Paint, Google’s page-load metric. On desktop, pages that had taken over four seconds came in under 2.5. On mobile, half the pages had been slower than 2.5 seconds; afterwards 99% were faster. Freight quotes that took up to a day became instant at checkout. The full story is in our WooCommerce to Odoo migration case study and the wider ERP integration case study, with the freight work in automating freight quoting with Odoo.
Moving the storefront puts your search rankings at risk, so plan redirects before anything else. We cover that in preventing traffic loss during a migration, and deciding which system owns what in replatforming when the ERP is the real move.
For budgets, see what an Odoo ecommerce implementation actually costs. On Shopify instead? The same test is in have you outgrown Shopify?
Frequently asked questions
How do I know if I’ve outgrown WooCommerce?
Look at the questions you can’t answer, not at limits. If landed cost needs a spreadsheet, purchasing lives in email, your team knows which system’s stock to distrust, or keeping the systems in step is part of someone’s job, you’ve outgrown your back office. WooCommerce itself doesn’t cap products or orders.
Does a WooCommerce store need an ERP?
Only when the back office stops coping. WooCommerce takes customer orders; purchasing, landed cost and accounting usually live elsewhere, in plugins, spreadsheets or an ERP. In our experience a single-channel store with simple shipping can run for a long time without one.
Should I keep WooCommerce and add Odoo, or move everything to Odoo?
Keep WooCommerce if the storefront works and only the back office hurts. It’s the smaller project, but you’ll run a sync between two systems. Move both if the storefront is part of the problem, for example configurable products or trade pricing held together by plugins.
Is WooCommerce slow with lots of orders?
Usually not because of WooCommerce itself. Since version 8.2 in October 2023, new stores keep orders in dedicated tables by default. Older stores have to switch this on, and incompatible plugins can block it. Most slow stores come down to hosting, caching or plugins.
Can WooCommerce connect to Odoo Online?
It depends on where the connector runs. Odoo Online doesn’t run custom or third-party Odoo modules, so Odoo-side connectors need Odoo.sh or your own server. At least one WooCommerce-side plugin connects to Odoo Online through its own hosted service. Check before choosing your Odoo plan.
Not sure which of the three fits?
Send us your answers to the three questions and a list of the plugins you run. We’ll tell you whether to stay, add an ERP, or move, and why.
Talk to us about your WooCommerce setup →
About the author
Nguyen Tran is the founder of Ministers.io. He has worked on Odoo ERP implementations across ecommerce, retail, manufacturing, and maintenance, repair and operations (MRO), delivering five directly and advising on more than twenty.
