WooCommerce Hosting Requirements: Compatibility, Checkout and Capacity
Official documentation checked October 5, 2026. Provider requirements are sourced below; planning checks and recommendations are HRL analysis. We have not performed hands-on hosting, checkout or extension tests for this guide.
A “WooCommerce ready” label should lead to a specification, not end the investigation. First establish that the server supports the software and extensions you intend to run. Then establish that the plan can handle the store’s dynamic work and that someone is responsible when checkout stops working.
This guide covers the technical purchase checks. Our WooCommerce pricing guide covers the budget, and the ecommerce hosting shortlist provides candidates to investigate. Neither a starting price nor a fast homepage proves store capacity.
Current published server requirements
The official server recommendations, checked October 5, 2026, state that the document applies to WooCommerce 10.8 and later. Match this version scope to your intended installation and recheck the source before changing an existing environment.
| Component | Published specification | What to ask the host |
|---|---|---|
| WordPress | 6.9 or greater | Which version is supported on this plan? |
| PHP | 8.3 or greater; tested through 8.4 | Can we select and test a supported version? |
| Database | MySQL 8.0+ or MariaDB 10.6+ | Which engine and version will the store use? |
| HTTPS | Support required | How are certificates installed and renewed? |
| WordPress memory | 256 MB or greater | What effective limit does WordPress actually receive? |
The documentation also lists optional components needed by some integrations. Check the requirements of your payment, shipping and other extensions, then inspect the WooCommerce System Status report. Do not assume the core baseline covers every dependency.
Also compare the current WordPress recommendations: on October 5, 2026, WordPress recommends MariaDB 10.11+ or MySQL 8.0+. Its MariaDB recommendation is higher than the WooCommerce document above. Ask the host to satisfy the current recommendations for WordPress and all selected extensions together.
Our memory limits guide explains effective PHP settings, WordPress requests and server capacity. Check PHP worker concurrency alongside the memory available to individual tasks.
WordPress memory is not the server’s total RAM
The WordPress memory limit is a limit available to the application; it is not a statement that the entire store needs only 256 MB of machine memory. A plan also has other workloads and resource constraints. Ask for PHP worker or process limits, CPU restrictions, database limits and the behavior when an allowance is exceeded.
HRL does not prescribe a universal RAM or visitor threshold here. Catalogue shape, theme, extensions, concurrent shoppers and scheduled work change the workload. Use the hosting resource-limit guide to translate the host’s answer into a usable specification.
Check dynamic checkout, not only cached pages
WooCommerce’s caching documentation describes exclusions for cart, checkout and account pages, along with session-related behavior. Ask how those rules apply across the host cache, WordPress caching plugin and CDN. Configure for your actual URLs and extensions.
HRL recommends testing two independent shopper sessions, cart changes and the selected payment workflow. Watch for stale totals, lost cart contents or one session receiving another session’s state. A high cache-hit rate is useful only when the cached response is appropriate.
Read page cache, CDN and object cache for the different jobs those layers perform. More caching is not an acceptance test for a working transaction.
Check database size, import and connection limits alongside file-count capacity. Ask which constraints apply to the exact plan and how they affect growth, staging and restores.
Use the test-order checklist to verify the selling workflow. Check outgoing webhook delivery separately when an external system depends on store events.
Require a safe change and recovery route
WooCommerce’s update guide recommends current backups and staging checks before production updates. Ask whether staging is included, how it is isolated, and how updates reach production without replacing newer trading records.
Get a specific answer about backup coverage, frequency, retention and restores. Our WooCommerce order-recovery guide explains why a database rollback can affect newer orders. The staging guide covers deployment boundaries.
Turn the baseline into a host acceptance request
Send the host the intended software versions and required extensions, then request the effective environment and resource scope for the named plan. Ask how a staging test and recovery would be performed. Meeting published version requirements establishes a baseline; it does not establish checkout capacity under your workload. Use worker evidence and representative store tests for that separate question.
Ask who owns the failure
Write down whether support handles server faults, WordPress problems, payment integration issues and extension conflicts. “Managed” is a service description that needs a scope. Identify the contact for each dependency and what evidence they need, such as a status report or error log.
Before buying, request the named plan’s compatibility details, resource limits, renewal invoice, staging terms and recovery scope. After setup, use the WooCommerce launch checklist to prove the store workflow and keep extension updates and renewal access assigned to an owner.
See our review methodology and affiliate disclosure. Official links are direct. Verify your exact plan, software versions and service terms before purchase or deployment.