WooCommerce is WordPress plus a lot of PHP and a busier MySQL database. It can run on WPHost because WPHost is PHP 8.4 + MySQL hosting. That sentence is where honesty starts — and where a lot of “WooCommerce hosting” marketing ends.

We will not sell you a checkout SLA, a PCI compliance product, or Elasticsearch. High-volume or highly regulated stores should evaluate those needs before migrating. Small catalogs with standard gateways often work fine. Know which store you are.

What “WooCommerce hosting” must provide

  • PHP current enough for modern Woo and WordPress (we run 8.4)
  • MySQL with room for orders, products, and autoloaded options that grow messy
  • HTTPS everywhere (preview immediately; custom-domain cert after DNS)
  • Enough disk for product images
  • A way to schedule tasks (Pro+ cron beats lonely wp-cron on quiet stores)

Optional but wise: staging on Pro+ to test gateway and plugin updates. Copy the database yourself if you need production products on staging — staging.

Small store versus enterprise

Fits the honest small-store profile

  • Dozens to low hundreds of SKUs
  • Simple shipping rules
  • Stripe/PayPal-style gateways with hosted fields
  • Traffic in the “busy boutique,” not flash-sale arena
  • Owner or freelancers who can update plugins carefully

Needs a harder look elsewhere (or serious architecture)

  • Large catalog search requiring Elasticsearch / specialized search
  • Contractual uptime on checkout
  • Complex ERP sync as a core dependency
  • PCI scope you expected the host to absorb as a packaged compliance product
  • Multisite network of storefronts with exotic caching

WPHost plans are capacity plans: Starter $9 (1 site, 2 GB), Pro $30 (3 sites, 10 GB, staging), Scale $65 (10 / 30 GB), Business $130 (30 / 100 GB, teams). A store with huge image assets graduates storage quickly — image-heavy.

Install and runtime notes

There is no one-click WooCommerce stack installer here. Install WordPress via zip — first host — then install WooCommerce from wp-admin like any plugin. We do not auto-update Woo or payment plugins; you do.

After domain attach, force HTTPS URLs in WordPress settings so checkout cookies behave — custom domain. Mixed http/https on stores is self-inflicted pain.

Cron, queues, and emails

WooCommerce expects scheduled events: held stock, emails, subscription tasks if you use them. On Pro+, prefer real cron so overnight orders still process when nobody visits the site — managed features.

Transactional email: WPHost does not include email hosting. Configure SMTP toward a provider with decent deliverability. “Orders emails went to spam after migrate” is usually mail reputation, not PHP.

Caching: the store footgun

Page caches must bypass cart, checkout, my-account, and typically any cookie that marks a session. Blind “cache everything” will show customer A the cart of customer B — a support nightmare and a trust killer. Test on staging. See also membership parallels — membership.

We do not operate a proprietary Woo-aware cache appliance. Use a plugin you understand — fast hosting.

Payments and PCI honesty

Using Stripe, PayPal, and similar with hosted payment fields keeps much sensitive card data off your origin. That helps. It does not mean WPHost is “PCI certified WooCommerce hosting” as a product claim. Your organization still owns compliance choices, plugins that touch data, and policies. If a procurement form demands a host-side PCI package, we are the wrong checkbox.

Backups for orders

Orders are database rows. Deploy history restores files, not order history. Daily (or better) DB backups via UpdraftPlus or similar are mandatory for stores — SSL and backups. Before Woo or gateway updates, take a manual backup. Staging first.

Extensions and bloat

Every extension is another plugin to update and another query pattern. Prefer official or well-maintained payment/shipping plugins. Delete the five shipping plugins you installed “just to try.” Autoloaded options bloat makes admin and front slow — performance is often data hygiene, not a plan upgrade.

Freelancers and agencies shipping Woo

Count sites against plan limits. Do not promise clients enterprise search or checkout SLAs we do not offer. Document the stack. Teams on Business help — agencies, freelancers. GitHub is per-person; zip deploys remain common for WP shops.

When not to use WPHost for commerce

  • You need concierge plugin updates under contract
  • You need Elasticsearch as a host feature
  • You need a legally framed checkout SLA
  • You expected Softaculous + cPanel + inbox + CDN in one coupon

For brochure SMBs with a tiny catalog, stay; for enterprise RFPs, leave early — small business, pillar.

Catalog hygiene that feels like “faster hosting”

Delete draft products you will never publish. Compress product images before upload. Avoid giant variable-product attribute explosions if a simpler product type works. Woo admin slowness is often data shape, not PHP version — though PHP 8.4 still helps — fast.

Run a staging test of checkout after every Woo minor that touches payment or cart templates. Gateway plugins update on their own cadence; we will not auto-merge them into production for you.

Taxes, shipping, and “the host broke checkout”

Most “hosting broke checkout” tickets are tax plugin conflicts, shipping zone misconfiguration, or cache serving a stale cart fragment. Checklist before opening a runtime ticket: reproduce with cache purged, staging vs production, gateway in live vs test mode, browser without aggressive extensions. Logs help when PHP fatals; they will not fix a missing shipping class.

Multichannel and inventory

Syncing Woo to marketplaces adds plugins and cron. Prefer Pro+ cron. Expect conflicts; stage them. WPHost remains the origin web store, not your ERP.

Inventory during launch week

Do not start a flash sale the same afternoon you flip DNS. Stabilize HTTPS, cache bypasses, and email first — how to launch. Then advertise. Your future self, reading logs at midnight, will agree.

Keep a written rollback: previous Woo plugin versions and a morning database backup ready if checkout fatals after an update.

WooCommerce can run — read the limits twice

WPHost will run WooCommerce as PHP on MySQL with HTTPS. That is necessary and not sufficient for a fantasy enterprise store. There is no checkout SLA, no PCI compliance product, and no Elasticsearch bundle. Use gateway-hosted payment fields to shrink PCI scope. Test checkout on staging with a database copy (Pro+) before theme updates.

Cron matters for subscriptions and held stock — Pro+ real cron beats hoping for traffic. Cache plugins must exclude cart, checkout, and account. Deploy history restores files after a bad plugin zip; order tables live in MySQL — back them up separately — SSL and backups.

Install path for a small catalog

Zip-install WordPress, add Woo, configure currency and shipping, connect Stripe/PayPal-class gateways, send a test order on preview, then attach the domain. We do not auto-update Woo or extensions. Email receipts need SMTP — no email hosting here. Plans: Starter $9 may fit tiny catalogs; Pro $30 is the sensible floor once money moves. Trial ~1 day.

Reconcile a test order end-to-end (cart, pay, email, thank-you) on the custom domain before opening the gates.

FAQ

Can WooCommerce run on Starter?

Technically yes if one site and 2 GB suffice. Many stores want Pro for staging and cron. Disk fills with product images fast.

Do you support Woo subscriptions / memberships?

As PHP plugins, they can run. Operational care (cron, cache, backups) is yours. No specialty SLA.

Is Elasticsearch available?

No. Large catalog search is a reason to evaluate other stacks.

Will you guarantee checkout uptime?

No checkout SLA. We aim at solid infrastructure; we do not sell commerce guarantees.

Do you auto-update WooCommerce?

No. Update in wp-admin after backups (and staging when you have it).