Choosing WooCommerce Hosting: A Checklist

Which hosting suits your store?

Choosing WooCommerce hosting means ensuring that the cart, checkout and order processing work, as well as product pages loading. A store receiving regular orders does not use the same resources as a catalogue that only displays products. A suitable package meets the store's software requirements, leaves room for peak-time transactions and is chosen alongside a recovery plan for order data.

This checklist is for businesses opening a new store and agencies choosing WooCommerce infrastructure for clients. If you already have a store, measure the current environment first. If it has not yet received traffic, do not turn an estimated visitor capacity into a firm package guarantee; prepare a starting plan to review after launch.

Consider WordPress hosting options for standard management needs. If you require a custom service, operating system permissions or a different runtime environment, use the hosting and VPS decision guide. Adding more products alone does not automatically mean you need to move to a server.

Verify version and application compatibility first

WooCommerce's official server recommendations may change with each version. The documentation checked on 18 October 2026, covering WooCommerce 10.8 and later, recommends WordPress 6.9 or later, PHP 8.3 or later, MySQL 8.0 or MariaDB 10.6 or later, HTTPS and a WordPress memory limit of at least 256 MB. Check the documentation for your WooCommerce version together with your plugins' requirements.

The WordPress memory limit and the hosting account's total RAM are different. A limit set for a PHP process does not guarantee that physical memory is reserved for every process simultaneously. Payment, shipping, invoicing, multilingual and product import plugins may also require additional extensions, specific versions or time limits.

1. Open WooCommerce → Status in the dashboard and record the WordPress, PHP and database versions and the memory limit.
2. Compare the versions supported by your active theme and payment, shipping, invoicing and stock integrations using their own documentation.
3. Ask the destination provider about missing PHP extensions, outbound connection requirements and how scheduled jobs run.
4. Try a version change in a restricted-access test copy first. Do not perform bulk updates in production without current file and database backups.

Before sharing a system report, remove internal paths, keys and customer information that may appear in the full report. A summary of versions and dependencies is enough for an initial quote.

Compare actual transactions instead of product counts

Monthly visitor count alone is not a sufficient measure. The same number of visits may be spread over a month or concentrated in a short campaign. Compare packages under the same conditions; alongside CPU/RAM, ask about I/O, concurrency, PHP process limits, storage and backup coverage. Providers do not all present these limits in the same way.

Test cart, checkout and account pages separately from caching

Caching can help product and category pages that show everyone the same content. Cart, checkout and My Account pages are customer-specific. WooCommerce's caching documentation explains how to exclude these pages from general page caching and assess session and cookie behaviour for the system in use.

If your pages use Turkish or custom URLs, excluding only default paths such as /cart/ may not be enough. Check the actual cart, checkout and account URLs. Plugins, the server and the CDN are separate layers; an exclusion in one may not automatically apply in another.

1. Open the test store in two independent browser sessions.
2. Add a product to the cart in the first session; confirm that the empty cart in the second session remains unchanged.
3. Check that changes to quantity, coupons, shipping address and any customer-specific pricing apply to the correct account.
4. Check that checkout and account pages do not show outdated data or another customer's information. Use the payment provider's test mode.
5. After changing a price or stock level, clear the relevant caches; verify that the product page and cart show the current result.

If carts become mixed between sessions, review cache rules and session configuration first. Buying more RAM will not resolve this kind of configuration error.

Include background jobs and order backups in the plan

Order emails, subscription processing and some integrations may use scheduled tasks. Review the count, dates and associated plugins of pending and failed jobs under WooCommerce → Status → Scheduled Actions. The WooCommerce status report documentation explains these records. Not every pending task is an error; distinguish jobs that are not yet due from overdue jobs. Instead of rerunning failed tasks in bulk, assess the cause and the risk of processing the same transaction twice.

Do not limit your backup plan to product images. Orders, stock, customer accounts and payment statuses change. Define how to recover transactions created after the latest backup and reconcile them with payment provider records. If the data-loss window you can accept is shorter than weekly backups allow, you need an additional backup arrangement; use the RPO/RTO questions in the business backup guide.

Prevent external email, payment, stock and ERP connections in a test copy from performing real transactions. Restoring a backup does not reverse a completed transaction in an external payment system.

Example: the product page is fast, so why is checkout slow?

This is an educational example, not a customer performance result. Imagine that the product page loads quickly while checkout keeps waiting. The product page may come from cache, while checkout waits for a response from the database, shipping calculation or payment provider.

The WordPress performance guide explains how to record browser and page measurements. Do not assume that a checkout issue originates in the server, a plugin or an external service without evidence.

Accept the migration only after testing the order workflow

The homepage loading in the new environment does not complete a migration. Prepare an acceptance checklist for product variations, search, cart, coupons, shipping, account login, a test payment, order email and stock updates. Prevent the old and new environments from running the same scheduled job simultaneously.

Define how you will perform the final synchronisation of orders received after the first copy. A planned maintenance window for write operations may be used if needed; that decision depends on how the store operates. The website migration checklist helps you track files, the database, DNS and email in one plan.

Prepare this short store summary for a quote

Store URL and current hosting type:
WordPress / WooCommerce / PHP versions:
Theme and critical payment, shipping and stock integrations:
Busy workflow and observed error / resource limit:
File, database and email usage:
Backup frequency and acceptable data-loss window:
Migration needs and suitable testing / cutover window:
Person or agency responsible for application maintenance:

Do not share customer lists, payment data or passwords in this summary. You can compare WordPress hosting packages or request a scope and quote for your store. Application maintenance, migration, licences and additional backup requirements are defined separately at the quotation stage.