WooCommerce hosting has to do more than keep a website online. It has to keep carts, logins and checkouts working while your catalog, orders and traffic grow. Hosting that is fine for a blog often struggles once a store gets a few hundred visitors an hour, because the pages that make money cannot be cached the same way.
This guide covers eight requirements to check before you choose a WooCommerce hosting plan. It is written for store owners and the developers who build for them. Along the way you will see the official WooCommerce server requirements and what each one means for your store.
Why WooCommerce hosting needs different specs
A static blog post can be cached once and served to thousands of visitors. A cart cannot. Every cart, checkout and account page is built for one person, so each request reaches PHP and the database.
That is why store speed depends on server resources more than most WordPress sites do. Slow checkout pages lose sales, and they tend to fail at the exact moment traffic peaks, such as a promotion or holiday sale.
The best WooCommerce hosting is built around that fact. It gives checkout traffic its own capacity, caches what can be cached and leaves dynamic pages alone.
1. Current PHP and database versions
Start with the official WooCommerce server requirements. The WooCommerce documentation lists PHP 8.3 or greater (tested up to PHP 8.4), MySQL 8.0 or later or MariaDB 10.6 or later, and WordPress 6.9 or later. It also calls for HTTPS.
The same page notes that older PHP 7.4 and MySQL 5.6 setups still work but have reached end of life and may expose your store to security vulnerabilities. Choose a host that lets you pick a current PHP version per site, and test a new version on staging before you switch live.
2. Enough memory for WordPress
WooCommerce recommends at least 256 MB of WordPress memory. Stores with many plugins, large catalogs or heavy reports need more.
Ask the host what memory limit applies per PHP process, and whether you can raise it. A low limit shows up as white screens, failed imports and admin pages that time out when you edit a large product.
3. PHP workers reserved for checkout
A PHP worker handles one uncached request at a time. If your plan has four workers and five shoppers hit checkout in the same second, the fifth waits. When enough people wait, the site feels broken.
This is the most overlooked spec in WooCommerce hosting plans. Our WP Growth plan includes 4 PHP workers, our Commerce plan reserves 6 for checkout, and Commerce Scale reserves 10.
When you compare hosts, ask for the worker count in writing. If a provider only promises “unlimited” resources, ask what happens at the limit.
4. Object caching for carts and sessions
An object cache such as Redis stores the results of repeated database queries in memory. It speeds up the pages that page caching cannot help, including carts, sessions and account areas.
Our plans run a Redis object cache for carts and sessions. For a store, this is closer to a requirement than a bonus feature.
5. Cache rules that leave cart and checkout alone
Server-level caching is great for category pages and product pages. It must never serve one customer’s cart to another. A good host excludes cart, checkout and my account pages from page caching and handles cookies correctly.
Ask how the cache decides what to skip, and whether it has been tested with WooCommerce specifically. Managed WooCommerce hosting should handle this setting without you touching a plugin.
6. HTTPS and a clear PCI responsibility line
Every store needs HTTPS, and WooCommerce lists it as a requirement. Beyond that, payment security is a shared job. The host provides a hardened, firewalled environment with encryption and access control. Your payment gateway and your own configuration handle card data.
Be wary of any host that promises PCI compliance for you without qualification. Ask what the host covers, what you cover and what your payment processor covers. Our plans let you keep the processor you already use.
7. Staging with selective publish-back
A staging site lets you test plugin updates, theme changes and PHP upgrades before customers see them. For a store, one detail matters most: what happens when you publish staging back to live.
If publishing overwrites the live database, you can erase orders placed while you were testing. Look for staging that lets you push selected files or tables rather than the whole database. Our staging supports selective publish-back for exactly this reason.
8. Backups with real retention and no surprise fees
Store data changes every minute. A weekly backup means a week of orders at risk. Look for daily backups with enough history to catch a problem that went unnoticed for days.
Our Commerce plans keep daily backups for 30 days, and WP Growth keeps 14 days. Restore should be self-service, and the host should not bill overage fees when a good month brings extra traffic. We do not bill by visitor.
What WooCommerce hosting plans cost
WooCommerce hosting plans cost more than basic WordPress plans, because the resources behind them are bigger. For reference, our annual prices are $59 per month for WP Growth (150,000 visits), $109 for Commerce (200,000 visits) and $179 for Commerce Scale (500,000 visits).
Cost per 1,000 visits is a fair way to compare. Commerce costs more per visit than WP Growth because it reserves workers for checkout and keeps backups longer. Commerce Scale brings the figure back down by spreading a larger server across more traffic.
The plan price is not the full cost of running a store. Budget for payment fees, premium extensions, shipping tools and email. Our e-commerce development team can help you scope the build as well as the hosting.
Managed WooCommerce hosting or a VPS?
A VPS gives you more raw power for the money, but you manage the server. That includes security patches, caching rules, backups and PHP tuning. It makes sense when you have a developer or an operations team.
Managed WooCommerce hosting hands those jobs to the provider. For most small and mid-sized stores, the time saved is worth the extra cost. You can read about the broader trade-offs in our guide to managed WordPress hosting.
The best WooCommerce hosting for different store sizes
There is no single best WooCommerce hosting plan, because stores differ so much. A rough match by size helps you aim at the right tier.
A new store with a small catalog and a few orders a day can start on a plan like WP Growth. It has enough PHP workers for light checkout traffic, and you can upgrade as orders increase.
A store with steady daily orders, email campaigns and a larger catalog belongs on a plan that reserves workers for checkout. Our Commerce plan does that job, which reserves 6 workers and adds a Pro CDN.
A store that runs big promotions or serves a large audience needs headroom. Commerce Scale adds 10 reserved workers, 100 GB of storage and room for 500,000 visits per month. If your needs sit outside those tiers, a custom plan is available.
Whatever tier you pick, plan for the busiest week of the year, not the average one. A plan that is fine in March can struggle in November.
Common mistakes when choosing WooCommerce hosting plans
A few errors come up again and again when store owners pick WooCommerce hosting plans. Avoiding them saves money and stress.
The first is picking a plan by visit limit alone. Visits tell you little about how many people check out at once, so ask about workers as well. The second is testing only the home page. Your checkout, your search and your account pages are the slow ones.
The third is skipping staging. Updating a payment plugin on a live store is how checkouts break at the worst time. The fourth is ignoring backup retention until an incident. Many store owners discover too late that their backup history only covers a few days.
The last mistake is trusting “unlimited” claims. Every server has limits. A provider that states them plainly is easier to plan around than one that hides them.
How to load test before you launch or run a sale
You do not need fancy tools to learn whether your hosting can cope. Add a few products to a cart, run through checkout in a test mode and watch how long each step takes. Then repeat from a second device at the same time.
For a deeper test, use a free load testing service to send simulated visitors to your product and cart pages. Increase the number slowly and note where response times climb. That point tells you how much headroom your WooCommerce hosting has.
Tell your host before a big sale. A good provider can check that your plan has the capacity and suggest changes in advance. It is much easier to add workers beforehand than during an outage.
A short checklist before you pick
- PHP 8.3 or newer, with a version selector per site
- At least 256 MB of WordPress memory, with room to raise it
- A stated number of PHP workers, with some reserved for checkout
- Redis or similar object caching
- Cache exclusions for cart, checkout and account pages
- Staging with selective publish-back
- Daily backups with at least 14 days of history
- No per-visitor overage charges
Ready to compare? Our WooCommerce hosting page lists the plans in full, and our team can size one for your catalog and traffic.
WooCommerce hosting FAQ
What are the WooCommerce server requirements?
The WooCommerce documentation lists PHP 8.3 or greater, MySQL 8.0 or later or MariaDB 10.6 or later, WordPress 6.9 or later, HTTPS and at least 256 MB of WordPress memory.
Do I need special hosting for WooCommerce?
Not required, but it helps. Stores need more PHP capacity, object caching and careful cache rules than a simple blog does, and good WooCommerce hosting plans include those by default.
How many PHP workers does a WooCommerce store need?
It depends on how many shoppers check out at the same time. A small store may get by with four. A store that runs promotions needs more, and some of those workers should be reserved for checkout.
Is managed WooCommerce hosting worth it?
For stores that earn money every day, usually yes. You pay for caching tuned to WooCommerce, backups, security monitoring and staff who understand store problems.
Can I move my existing store to a new host without losing orders?
Yes, if you plan the cutover. Freeze changes briefly, copy the store, test checkout on the new server and then switch DNS. We migrate stores for free, and a person handles it.
Sources
- WooCommerce documentation, server requirements
- Liberation Technology Services WooCommerce hosting plans
Related reading: WordPress hosting, secure WordPress hosting and WordPress hosting cost.