WooCommerce hosting requirements: what to check before you buy

You do not need a plan named “WooCommerce hosting” just to run a WooCommerce shop. Your existing WordPress hosting may fit if it supports the required software, handles customer-specific pages correctly, and gives you a workable recovery and support arrangement. Check those details before changing plans.

This guide is for someone planning or running a modest shop who can read a hosting plan or ask its support team for help. Have your plan name and a list of essential shop features ready: ordinary products, subscriptions or bookings, for example. You will finish with a decision to keep the plan, resolve an unanswered question, or compare an alternative against a specific gap. Installation, migration and payment setup come afterward.

Check the software versions first

WooCommerce adds shop features to WordPress. PHP is the software that runs WordPress code; MySQL or MariaDB stores the site’s database. A host saying “supports WordPress” does not tell you which versions are available on your account.

The checks below were reviewed on 24 September 2026. The current WooCommerce plugin listing identifies version 11.1.2 and requires WordPress 7.0 or later and PHP 7.4 or later. The PHP figure is a compatibility minimum, not the target for buying new hosting.

Use the WooCommerce server recommendations together with the WordPress hosting recommendations to ask for this baseline:

The official pages do not give identical older-version floors. The server guide describes WooCommerce 10.8 and later with WordPress 6.9+, while the current plugin listing requires 7.0+; their legacy database figures also differ. For a new plan, use the recommended database versions above and check the exact plugin release. Both projects warn about security risks from older, end-of-life environments: “can run” is not a reason to buy an obsolete stack.

An extension is an additional plugin supplying a shop feature. Give the host the names of your required extensions, especially payment, shipping, subscription and booking integrations, and check their own requirements. Meeting the core WooCommerce baseline does not establish that every extension will work.

If WooCommerce is already installed, open WooCommerce → Status in the WordPress dashboard. Its System Status report lists installed versions, memory and server information. Compare those values with the table. If you cannot access the dashboard, ask the person maintaining the site for these specific values. If the shop does not exist yet, ask the host to confirm them for the exact plan before ordering.

Record mismatches as questions for the host. A newer version may already be available on the account; changing it needs compatibility checks and a backup, so this comparison is not an instruction to change the live shop’s settings.

Make sure checkout and account pages stay personal

Page caching saves a response so it can be reused instead of rebuilt for every visit. That can help a public catalog, but a customer’s cart and account must show that customer’s information.

WooCommerce’s caching guidance says to exclude Cart, Checkout and My Account pages from the cache. Some integrations do this automatically. The guide also describes cart cookies and customer sessions, and notes that details depend on the caching system.

Ask the host which caching systems apply to your site, including any host cache or content delivery network, and how they handle signed-in customers, active carts and your actual page addresses. A cache plugin’s setting alone does not establish what another caching layer does. If you use custom checkout or account pages, include those in the question.

The useful answer is confirmation of the exclusions and someone responsible for investigating incorrect cart or account behavior. “We have caching” does not answer it. A fast public product page also cannot show how checkout behaves when several customers use it at once.

Choose a recovery arrangement that fits orders

A full recovery needs both site files and the database; WordPress explains the two parts of a backup. WooCommerce’s database contains products and orders, so backup timing matters to a shop.

For example, restoring yesterday’s database can discard orders recorded since that copy. Decide how much recent order information you could reconstruct, then ask:

• How often is the database backed up, how long are copies kept, and can I obtain a usable copy outside the hosting account?
• Who performs a restore, what does it cost, and what recovery time does the service actually commit to?
• How are orders received after the chosen backup handled during recovery?
• Can we check a restored copy separately before replacing the live shop?

Staging is a separate copy for checking changes. WooCommerce recommends backups and staging checks before updates. Ask whether your plan includes staging and who checks the shop after a change. Also ask how changes are transferred without replacing current orders with an older staging database. The availability of a staging button does not answer that question.

You can keep a plan whose backup service is basic if another suitable recovery arrangement already covers the shop. What matters is an understood process with someone responsible for it.

Confirm limits and support before paying more

Ask for the plan’s storage and processing limits, what happens when a limit is reached, and whether support can investigate slow cart or checkout requests. A monthly visitor allowance does not establish how many simultaneous purchases your particular combination of theme and extensions can handle. There is no traffic-capacity guarantee in the software table above.

Explain any known symptoms with their time and location: for example, “Checkout is slow while the public product page loads normally.” Let the host or maintainer identify the cause before treating an upgrade as the fix.

Separate hosting support from software maintenance. Ask who handles WordPress and extension updates, who investigates a broken checkout, and when you must contact an extension developer. Also identify who investigates missing order emails or failed background tasks. The WooCommerce Status documentation describes logs and scheduled actions, which can help the responsible person investigate; access to those tools does not mean the host performs that work.

A WooCommerce-branded plan is worth considering when its written scope solves one of these needs. Verify the exact tier, included work and extra charges. The label alone proves neither extension compatibility nor a recovery service.

Turn the answers into a decision

Mark each required area—software, caching, recovery, limits and support—as confirmed, covered separately, or unanswered. For the unanswered items, adapt this message to your current or candidate host:

I run or plan a WooCommerce shop on [plan name], using [essential extensions]. Please confirm the available WordPress, PHP and database versions, WordPress memory limit and HTTPS renewal. How does your caching exclude our cart, checkout and customer account pages? What are the database backup frequency, retention and restore arrangements, including recent orders? Please identify the plan limits, who investigates checkout or order-email failures, and any required extras.

Keep the current plan when the requirements are covered and maintenance has an owner. Resolve unknowns when the documentation or reply is incomplete. Compare another plan when you can name a gap the current arrangement cannot reasonably cover, such as an obsolete software environment or unsuitable recovery process.

For that comparison, get the full renewal price and required extras over the same billing period, including backup or maintenance services you would still need. Your decision is complete when you can say what the chosen arrangement provides, who handles the remaining work, and which questions must be resolved before the shop goes live.

Sources and useful links

• WooCommerce plugin listing — check the current release and its WordPress/PHP compatibility minimums before choosing versions.
• WooCommerce server recommendations — review the recommended environment, memory setting and extension-dependent components.
• WordPress hosting requirements — cross-check WordPress’s PHP, database and HTTPS recommendations.
• WooCommerce caching guidance — give the cache maintainer the official exclusions for cart, checkout and account pages.
• WooCommerce System Status report — locate installed versions and diagnostic information in an existing shop.
• WordPress backups — understand why both files and the database belong in a recovery plan.
• Updating WooCommerce — review the preparation and shop checks to assign to whoever maintains your store.