← Blog

WooCommerce hosting: the 7-point checklist before you pick a host

July 9, 2026

A store is not a blog with a cart plugin. It has sessions, money and inventory — which means hosting failures cost orders, not just page views. Seven things to check before you put a WooCommerce store on any host, with a way to test each one.

1. 1
   1 · Checkout must bypass the cache — always

   Full-page caching makes product pages fast, but a cached cart or checkout shows customers stale totals or someone else's session. Test: add a product to the cart in two browsers and watch for bleed-through. On a store-aware host the bypass rules are built in, not something you configure.
2. 2
   2 · A crashed plugin can't be allowed to keep checkout down

   The most common store outage is a plugin update throwing a PHP fatal. The question is recovery time: hours (you notice, you file a ticket) or seconds (the platform deactivates the crashing plugin and verifies checkout is back). Ask your host which one they are.
3. 3
   3 · Deployments must respect live orders

   Pushing a staging copy to production hours after cloning can silently overwrite every order placed in between. Test: ask the host what happens to orders placed after staging was cloned. Most can't answer. Ours refuses to overwrite them and shows you the exact at-risk count.
4. 4
   4 · A sales spike can't move the bill (or throttle the store)

   Visit-metered hosts bill your best day as overage; CPU-metered hosts throttle it. Both are exactly wrong for commerce. Price the plan at your best expected month, not your average one — or pick flat pricing and stop doing that math.
5. 5
   5 · Object cache for sessions and carts

   WooCommerce hits the database hard for sessions, carts and product queries. A Redis object cache is the difference between a store that holds up under concurrency and one that dies at 40 simultaneous carts. It should be included and pre-wired.
6. 6
   6 · Backups that capture orders consistently

   Files-only backups lose orders; database-only backups lose media. You want both, captured together, off-site, with one-click restore — and the restore itself should snapshot first, because restoring over this morning's orders is its own disaster.
7. 7
   7 · PHP current, with a rollback

   Stores run heavy plugin stacks that don't all update at once. You want current PHP (8.1–8.5) switchable per site, health-checked, with automatic rollback if the store doesn't come up clean — so staying fast never risks staying up.

← All posts