# WooCommerce Hosting Requirements for a Growing Store

- Link: https://offshorehosting.pk/woocommerce-hosting-requirements-for-a-growing-store/
- Published: 2026-10-25T10:31:00+00:00
- Author: admin

# WooCommerce Hosting Requirements for a Growing Store

A WooCommerce store is not a blog with a shop attached. Every product page, cart,
search and checkout is generated dynamically, per visitor, from the database — and
that changes what the server has to do. A host that runs a brochure site happily
can struggle with a store doing real order volume, and the symptoms look like a 
WooCommerce problem when they are really a hosting problem.

This guide sets out the requirements that matter in 2026, how they change as a store
grows, and how to tell when it is time to move up.

## The official baseline

WooCommerce publishes server requirements that are the floor, not the target. As
of October 2026, for WooCommerce 10.8 and later, the recommendations are:

 * **WordPress:** 6.9 or greater
 * **PHP:** 8.3 or greater (WooCommerce is tested up to PHP 8.4)
 * **MySQL:** 8.0 or greater, or MariaDB 10.6 or greater
 * **WordPress memory limit:** 256 MB or greater
 * **HTTPS:** required for checkout security
 * **Permalinks:** set to anything other than the default “Plain” option

The WordPress.org plugin listing states lower minimums — PHP 7.4 or greater, MySQL
5.5.5 or MariaDB 10.1 or greater — but those are legacy floors. PHP 7.4 reached 
end of life years ago and no longer receives security fixes. Running a store that
takes payments on an end-of-life PHP version is a risk, not a saving. The WordPress
project’s own requirements page has likewise moved to PHP 8.3 or greater, with MariaDB
10.11+ or MySQL 8.0+, and HTTPS required for every install.

The gap between “will run” and “is supported” is the whole point: a store on old
software works fine, passes no visible test, and runs on software nobody is patching
any more.

## Why a store needs more than a blog

A blog, once cached, serves mostly static HTML. Ten visitors or ten thousand, the
server delivers the same cached file and load stays predictable. WooCommerce is 
different in four ways:

 1. **Cart and checkout are per-visitor and cannot be shared.** Each shopper’s cart,
    totals and tax calculation are unique, so those pages must be generated live by
    PHP on every request.
 2. **Stock is live.** Product availability changes with every order, so product pages
    cannot be cached as aggressively as blog posts.
 3. **Search and filtering hit the database.** Faceted search, sorting and filtering
    are database queries, and they get slower as the catalogue grows.
 4. **Payment processing needs live PHP execution.** Every checkout runs PHP, calls
    the payment gateway, and writes an order — there is no cached shortcut.

That is why a store’s hosting needs scale with orders and catalogue size, not just
with page views. A store with 50 products and 20 orders a day has very different
needs from one with 5,000 products and 500 orders a day, even if their traffic looks
similar.

## The stack, piece by piece

### PHP version and workers

Use PHP 8.3 or 8.4, tested on staging first — WooCommerce is tested up to PHP 8.4,
so do not move to a newer PHP version on a live store until you have run a full 
checkout on staging. PHP workers matter as much as the version: each simultaneous
PHP request needs a worker, and a plan with too few workers queues checkouts during
a sale. Ask your host how many PHP workers your plan includes, and what happens 
when they are exhausted. That number is rarely on the sales page and it decides 
how your store behaves under load.

### Memory

256 MB is the minimum WordPress memory limit; larger stores should treat 512 MB 
as the practical starting point, particularly with several plugins, a page builder,
or a large catalogue. Memory exhaustion shows up as white screens and failed checkouts
at the worst moments. Confirm both the PHP memory limit and the server’s total RAM—
they are different numbers, and both matter.

### Database

MySQL 8.0+ or MariaDB 10.6+ is the recommendation, and the database is usually the
first bottleneck in a growing store. Slow queries, missing indexes and an un-tuned
database hurt more than a slow CPU. Keep the database on fast storage — NVMe makes
a measurable difference here — and make sure object caching is available. WooCommerce
explicitly recommends object caching via Redis or Memcached, and for a growing store
it is close to essential: it caches database query results so repeated queries do
not hit the disk every time. See [NVMe vs SSD Storage for Hosting Workloads](https://offshorehosting.pk/blog/nvme-vs-ssd-storage-for-hosting-workloads/)
for the storage side of this decision.

### Storage and I/O

Disk space needs room for products, media, backups and updates — and for growth.
More important than raw gigabytes is I/O speed: a store’s database does many small
random reads and writes, which is exactly where NVMe outperforms SATA SSD. If your
host offers a choice, take NVMe for a store, and check that backups are not stored
on the same disk as the live data.

### HTTPS and security

HTTPS is required, not optional, for checkout. Beyond the certificate itself, a 
store needs a firewall, malware scanning, and a host that patches the server promptly.
Payment security is covered in detail in [How to Keep WooCommerce Checkout Fast](https://offshorehosting.pk/blog/how-to-keep-woocommerce-checkout-fast/)
and in the PCI DSS section of that guide — the short version is: never store raw
card numbers, use a tokenised gateway, and keep your software updated.

### Caching — done correctly

Caching helps a store, but only if it is configured to exclude the pages that must
stay dynamic: cart, checkout, and account pages. A cache that serves one shopper’s
cart to another is worse than no cache at all. Page caching for product and category
pages, object caching for the database, and a CDN for static assets is the standard
combination. Confirm with your host that WooCommerce-aware caching is configured,
not generic WordPress caching.

## Sizing by stage of growth

  |  Stage |  Typical profile |  Hosting that usually fits |  
   |  Starting out |  Under 100 products, a few orders a day |  Quality shared or small VPS, PHP 8.3+, 256 MB memory, NVMe if available |  
 |  Growing |  Hundreds of products, tens of orders a day, traffic spikes at sales |  VPS with dedicated CPU/RAM, Redis object cache, 512 MB memory, CDN |  
 |  Established |  Thousands of products, hundreds of orders a day, regular campaigns |  Larger VPS or dedicated server, tuned database, separate staging, monitored workers and I/O |  
 |  High volume |  Sustained high concurrency, seasonal peaks |  Dedicated resources, load testing before campaigns, database tuning, and a documented scaling plan |

These are starting points, not prescriptions. The right size is the one that keeps
checkout fast at your peak, not your average — measure at peak, and test before 
a sale rather than during it.

## Signs you have outgrown your hosting

 * Checkout slows or times out during sales, while the site is fine at quiet times.
 * “Allowed memory size exhausted” errors, or 503 errors when traffic rises.
 * The host tells you that you are hitting CPU, worker, or I/O limits.
 * Backups take so long they overlap with trading hours.
 * You cannot enable Redis, cannot change the PHP version, or cannot get a staging
   environment.

Any one of these is a reason to talk to your host about the next plan — or to a 
different host. Do not wait for a failed sale to force the conversation.

## Before you move or upgrade

 1. **Back up everything** — files and database — and verify the backup. See [How to Plan Backups for an Online Store](https://offshorehosting.pk/blog/how-to-plan-backups-for-an-online-store/).
 2. **Set up staging** on the new environment and run a full test: browse, search, 
    add to cart, check out, refund, and test emails.
 3. **Check PHP compatibility** of every plugin on the new PHP version before going
    live.
 4. **Plan the move for a low-traffic window**, and keep the old site available until
    the new one is proven. See [How to Migrate an E-commerce Store with Less Downtime](https://offshorehosting.pk/blog/how-to-migrate-an-ecommerce-store-with-less-downtime/).

## The bottom line

A growing WooCommerce store needs PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6 or
newer, at least 256 MB of WordPress memory (512 MB in practice for larger stores),
HTTPS, fast NVMe storage, and object caching — on a plan with enough PHP workers
and RAM for your peak, not your average. Meet that baseline, monitor checkout at
peak times, and upgrade when the evidence says so rather than when a sale fails.

For hosting built around those requirements, see our [WooCommerce hosting](https://offshorehosting.pk/ecommerce-hosting/)
plans. [TO BE CONFIRMED: Offshore Hosting WooCommerce plan specifications — PHP 
versions, memory limits, object caching, and staging availability.]

## Sources

 * WordPress.org — WooCommerce plugin (minimum requirements): https://wordpress.
   org/plugins/woocommerce/
 * DevDiggers — Can I Use WooCommerce Without WordPress (requirements summary, October
   2026): https://devdiggers.com/woocommerce-without-wordpress/
 * AHosting — WooCommerce Hosting from $3.79/mo: What Your Store Needs: https://
   www.ahosting.net/blog/woocommerce-hosting-2026/
 * WPFactory — How to Set Up WooCommerce on WordPress in 2026: Complete Beginner
   Guide: https://wpfactory.com/blog/how-to-set-up-woocommerce-on-wordpress/
 * NexonHost — WordPress Hosting Requirements and When to Upgrade: https://nexonhost.
   com/wordpress-hosting-requirements

## Sources

 * https://wordpress.org/plugins/woocommerce/
 * https://devdiggers.com/woocommerce-without-wordpress/
 * https://www.ahosting.net/blog/woocommerce-hosting-2026/
 * https://wpfactory.com/blog/how-to-set-up-woocommerce-on-wordpress/
 * https://nexonhost.com/wordpress-hosting-requirements