A WooCommerce store must do more than open a product page quickly. It needs to preserve the correct cart, take payment and send the order to the right business systems. A single cached page cannot demonstrate those operations. Select hosting around actual store behaviour and the compatibility of the complete extension stack.
Siteman recommends checking the environment and the full buyer journey first, then deciding whether an InterServer shared account is sufficient or whether additional resources or a separate server environment are needed.
A starting point for checking the environment
| Component | WooCommerce documentation recommendation for 10.8 and later |
|---|---|
| WordPress | Version 6.9 or later |
| PHP | Version 8.3 or later; the document states testing up to 8.4 |
| Database | MySQL 8.0 or later, or MariaDB 10.6 or later |
| HTTPS | Support for encrypted connections |
| WordPress memory limit | At least 256 MB |
Check more than the PHP version label
The table reflects WooCommerce recommendations checked on 3 November 2026. Each payment extension and theme still needs a compatibility check. Record the store, theme, payment, shipping and integration versions, then compare their requirements with the selected account's environment. The WordPress memory limit is an application setting, not all the RAM in the hosting server.
After installation, inspect WooCommerce's system status report to confirm the actual configuration. If a required PHP function or extension is unavailable, ask the provider whether it can be enabled. A product described as WordPress hosting does not by itself establish compatibility with every store configuration.
Keep carts, checkout and accounts dynamic
WooCommerce's guidance excludes Cart, Checkout and My Account from page caching because they contain information specific to the current customer. Check the exclusions across the active plugin, server cache and CDN. A plugin setting is insufficient if another layer continues serving saved copies of those pages.
WooCommerce sessions and cookies also need consideration under the chosen cache's documentation. A useful acceptance test uses two independent browsers with different carts: change quantities, sign in and return from payment. Each customer must see their own state. Faster responses are not an improvement if a saved page contains another session's information.
Background operations also create store workload
Product imports, stock updates, image processing, shipping synchronisation and notifications may run while customers are buying. Observe their duration, errors and resource use in normal and busy periods. Product counts and visit totals do not replace this check.
For example, a hypothetical small store might receive few visits yet run an expensive catalogue import while orders are being completed. In that situation, first review scheduling and data processing rather than automatically buying the largest plan.
Choose Standard, Boost or VPS from the requirement
Shared hosting can be convenient when the required environment is supported, account permissions are sufficient and the store's operations fit the resources. Consider Boost after confirming a particular shared-account limit is being reached. It does not repair an incompatible payment extension or provide root access.
A VPS is a separate decision when system permissions, custom services or a separate stack are needed. Assign administration, backups and maintenance alongside the server. The general WordPress comparison is at WordPress hosting: Standard, Boost or VPS. Shared-resource differences are explained at Standard vs Boost hosting: resources and limits.
Run an acceptance test before launch
- Open a product, select a variation and verify price and availability
- Add items to carts in two independent sessions
- Check shipping, discounts and the final order amount
- Use the payment provider's permitted test mode
- Verify the payment return and resulting order status
- Confirm notifications and order data reach their intended systems
- Repeat the test while a representative import or background job runs
Protect new orders during updates or migration
A test copy must not send real customer emails, charge money or change production stock. Use test credentials and agreed integration modes. Before migration, document where new orders are accepted and how final synchronisation will work.
Standard's product page lists weekly backups. An active shop may need a shorter interval to meet its acceptable loss of new orders. Choose your own backup frequency from the rate of data change, keep a separate copy and test restoring files and the database together. Restoring an old database can bring the website online while losing orders placed after that copy was made.
Agree the product and responsibilities before payment
Prepare the extension list, representative operations, access requirements and recovery plan. This makes it easier to assess the selected environment and decide who will handle application issues. View hosting offers.
Siteman can help match the store's requirements to hosting options: hosting selection
After selecting a platform, retain the configuration and acceptance notes.
Frequently asked questions
Can the whole store be cached for speed?
No. Static assets and some public pages can be cached under the application's rules. Carts, checkout and accounts must preserve the current customer's information. Test two independent sessions as well as measuring response time.
Which plan is guaranteed to handle my catalogue?
Catalogue size does not describe the complete workload. Filters, extensions, imports, simultaneous orders and database requests matter. Select a configuration after testing those operations; a universal product-count promise is not a substitute.
Sources and verification date
Requirements and conditions checked on 3 November 2026. Recheck versions and the selected product before ordering.
WooCommerce requirements: WooCommerce server requirements
WooCommerce caching: WooCommerce cache configuration
The practical checking sequence and hypothetical example are Siteman recommendations.