WooCommerce has a reputation in some circles for not scaling. In my experience, that reputation is mostly undeserved. I’ve worked with WooCommerce stores carrying tens of thousands of products and processing large daily order volumes. What separates the ones that run smoothly from the ones that struggle isn’t WooCommerce itself. It’s how they’re configured, what’s installed on them and the infrastructure underneath.
Small stores can get away with a lot. Cheap hosting, dozens of plugins and no caching strategy might be fine at a few hundred products. As catalogues and order volumes grow, those shortcuts turn into slow category pages, sluggish admin screens, checkout timeouts and failed background jobs.
Here’s how I approach scaling WooCommerce.
Know where the pressure comes from
Large stores face pressure in several places at once:
- Catalogue size: thousands of products and variations make queries, imports and searches heavier.
- Order volume: more orders mean more database writes, more emails and more background tasks.
- Concurrent customers: many people browsing, searching and checking out at the same time.
- Admin activity: staff processing orders, editing products and running reports.
- Integrations: inventory sync, ERP connections, marketplace feeds and accounting exports.
Each needs a different solution, so measure before changing anything. Query Monitor, the PHP-FPM slow log, database slow query logs and application performance monitoring tools show where time is actually spent.
Use High-Performance Order Storage
Historically, WooCommerce stored orders as posts in the wp_posts table, with order details spread across wp_postmeta. On large stores, this made order queries slow and bloated the postmeta table.
High-Performance Order Storage, known as HPOS, stores orders in dedicated tables designed for order data. Order queries become faster and more efficient, and the posts tables are no longer burdened with order data. HPOS has been the default for new stores since WooCommerce 8.2.
Older stores may still be using legacy storage. Check under WooCommerce, then Settings, then Advanced, then Features. Before switching:
- Confirm every plugin that touches orders is compatible. WooCommerce shows warnings for incompatible plugins.
- Enable compatibility mode, which keeps both storage systems in sync during the transition.
- Test thoroughly on staging, including order creation, refunds, reports and integrations.
- Switch to HPOS as the authoritative storage, then disable sync once you’re confident.
For large stores, the migration itself can take time, so plan it for a quiet period.
Add a persistent object cache
A persistent object cache, usually Redis, stores the results of database queries and computed data in memory between requests. On a large WooCommerce store, it’s one of the most impactful changes you can make, especially for the parts that can’t be page cached: cart, checkout, My Account and the admin.
Make sure Redis has enough memory for your store, and monitor its eviction rate. If Redis constantly evicts data because memory is full, you lose much of the benefit.
Page caching for catalogue pages
Category, product and content pages can be page cached for anonymous visitors, as long as caching bypasses visitors with items in their cart and logged-in customers. WooCommerce sets cookies when a customer adds something to the cart; your caching layer should bypass the cache when those cookies are present.
Cart fragments, the AJAX request that updates the mini cart, can undermine caching and add load. On large stores, review whether cart fragments run on every page, and limit them where possible.
Make product search fast and useful
Default WordPress search uses simple database queries that get slow and return poor results on large catalogues. They don’t handle typos, synonyms or relevance well, and searching product attributes and SKUs is limited.
For large stores, a dedicated search engine makes a huge difference. Options include Elasticsearch or OpenSearch-based solutions and hosted search services. They offer:
- Fast results even across tens of thousands of products.
- Relevance ranking, typo tolerance and synonyms.
- Faceted filtering by attributes, price and categories.
- Reduced load on your database.
Customers who search are often your most motivated buyers. Fast, accurate search directly affects revenue.
Optimise layered navigation and filters
Filtering by attributes like size, colour and brand generates complex queries. On large catalogues, filter plugins can become a major performance bottleneck, especially if they calculate counts for every filter option on every page load.
Choose filter solutions built for scale, which often use their own index tables or a search engine. Cache filter results where possible, and block search engines from crawling endless filter combinations.
Database health
Large stores accumulate database clutter quickly:
- Action Scheduler tables can grow to millions of rows of completed and failed actions.
- Sessions for guest carts are stored in a WooCommerce sessions table.
- Transients for product data and caches.
- Postmeta for products, especially with many custom fields or variation attributes.
- Logs from plugins and integrations.
Review table sizes regularly, investigate unusual growth and clean up safely. Make sure the database has enough memory, particularly the InnoDB buffer pool, so frequently used data stays in memory.
Indexing improvements for postmeta and other tables can help large stores significantly. Plugins exist that add better indexes safely, and on your own infrastructure, a database specialist can tune indexes for your workload.
Background jobs and Action Scheduler
Large stores rely heavily on background processing: sending emails, syncing inventory, processing webhooks, renewing subscriptions and generating reports. WooCommerce uses Action Scheduler for most of this.
To keep it healthy:
- Run WP-Cron from a real system cron, so background tasks run reliably.
- Run Action Scheduler more aggressively on busy stores, for example with a dedicated cron job using WP-CLI:
- Monitor the queue for growing backlogs and failed actions.
- Investigate failures. A failing integration can generate thousands of failed actions and hide a real business problem.
Imports, exports and integrations
Product imports and stock syncs are frequent sources of performance problems on large stores. Updating thousands of products through slow, one-at-a-time processes during busy hours can bring the site to its knees.
- Schedule large imports for quiet hours.
- Use tools that batch updates efficiently.
- Prefer WP-CLI or background processing for big jobs, rather than browser-based imports that time out.
- Only update products that changed, rather than reimporting everything.
- Monitor integrations for errors and retries that pile up.
Admin performance
Store staff spend hours in the admin, and slow admin screens waste their time. Common causes include:
- Plugins adding heavy columns or widgets to order and product list screens.
- Dashboard widgets running expensive queries.
- Reports calculated on every page load.
- Lack of an object cache.
Remove unnecessary admin widgets and columns, use HPOS for faster order screens and make sure WooCommerce Analytics data is processed in the background. The WP Admin Heartbeat API can also add load when many staff have the admin open; limiting its frequency can help.
Checkout under load
Checkout is the most important path and the hardest to cache. Under heavy load, especially during sales:
- Keep checkout lean, with minimal scripts and plugins.
- Make sure payment gateway webhooks are processed quickly.
- Cache external shipping rate calls where possible.
- Test checkout under realistic load before big sales events.
Load testing tools let you simulate many concurrent shoppers, revealing bottlenecks before real customers find them.
Hosting for scale
At some point, a single small server isn’t enough. Options for scaling include:
- A larger server with more CPU and memory, often the simplest first step.
- Separating the database onto its own server or a managed database service.
- Dedicated Redis instances.
- Multiple web servers behind a load balancer, with shared file storage or offloaded media.
- Managed WooCommerce hosting designed for large stores.
Scaling horizontally adds complexity: sessions, file uploads and caches need to work across servers. Make sure your team or provider has experience with it.
Plugin discipline
The biggest performance problems on large stores often come from plugins that work fine on small stores but don’t scale. Before adding a plugin to a large store, test it with realistic data volumes. Remove plugins that aren’t essential. Every plugin adds code that runs on every request.
Frequently asked questions
Can WooCommerce handle 100,000 products?
Yes, with the right setup: HPOS, a persistent object cache, a dedicated search solution, efficient filters, well-tuned hosting and careful plugin choices. Default setups on budget hosting won’t cope.
What’s the single biggest improvement for a large store?
It depends on the bottleneck, but a persistent object cache and HPOS often deliver the biggest gains for dynamic pages and admin screens. For catalogue browsing, search and filtering solutions built for scale make a large difference.
Should I move to a headless setup for performance?
Rarely necessary. Most performance problems can be solved within a traditional WooCommerce setup. Headless adds significant complexity and should be chosen for other reasons, like multichannel needs.
How do I prepare for a big sale?
Load test checkout, make sure caching and Redis are configured, scale hosting temporarily if needed, avoid deploying changes right before the sale and monitor closely during it.
Final thoughts
WooCommerce can scale to large catalogues and high order volumes, but scaling doesn’t happen by accident. Move to HPOS, add a persistent object cache, use search and filtering built for scale, keep background jobs and the database healthy, handle imports carefully and choose hosting that matches your growth. Measure before you change, test with realistic data and your store will grow without slowing down.




