Hosting WooCommerce. Sklep gotowy po zaznaczeniu jednego pola.

1. A WooCommerce store needs different hosting than a simple business site.

WooCommerce is a plugin, not a standalone platform, but a store built with it behaves like a separate application. It adds database tables for orders, customers, and inventory, queries the database more frequently than a standard business site, and puts more strain on PHP with every cart operation. Hosting that was sufficient for a blog starts to struggle when the same server also has to calculate taxes and track inventory.

On Saplo, you set up a WooCommerce store just like a regular WordPress site, except you select the WooCommerce Store option during installation, which adds the plugin to your fresh WordPress install right away. After that, the main choice is which Box fits your traffic and order volume, since the stack and container isolation are the same as for a simple brochure site.

Each store runs in its own LXC container with a dedicated MySQL database. A traffic spike during a sale or a payment plugin error therefore will not affect other apps on the same Box. This is a different model from shared hosting, where one overloaded store can slow down every site on the same physical server.

2. How much RAM does a WooCommerce store actually need?

A small store with dozens of products and low traffic runs on Box M ($69/year, 2 GB RAM, 30 GB SSD, full SSH access). In practice, this is the minimum sensible plan for a store, because WooCommerce on Box S with 1 GB RAM can already feel tight when several customers are placing orders at the same time.

A store with a larger product catalog, product variants, and steady traffic from ads works better on Box L ($149/year, 6 GB RAM, 60 GB SSD). It adds daily backups with 7-day retention, which is more important for a store handling real transactions than for a simple brochure site with no dynamic data.

Backups are essential for an online store, not a cosmetic extra. The order database changes every day, so having no copy to restore after a disk failure or a failed payment plugin update means losing orders, not just site content. That is why Box L and above include backups in the plan price instead of selling them as a separate add-on.

Seasonal stores, or stores with heavy traffic during sales such as Black Friday and the holidays, can temporarily add RAM or vCPU capacity with hot-add and no container restart. You do not need to migrate to a higher plan for three weeks a year and then move back.

3. Competitors and e-commerce hosting prices

Competitor A does not have a separate plan called WooCommerce, only general WordPress packages (starter plan $10/year, standard plan $34/year, extended plan $76/year, public price lists, as of 2026-10-10). You have to choose the package that best fits the store's needs, without clear guidance on which package is sufficient for real store traffic.

Competitor B takes a similar approach: its WordPress starter plan ($7/year promotional price, 70 GB of storage) is described as sufficient to get a store started, but full performance under heavier traffic requires the professional plan, where the price rises to $245/year after the first year (public price lists, as of 2026-10-10). That is more than three times the cost of Box L on Saplo with similar storage capacity.

Another provider lists WooCommerce hosting as one of its product lines alongside WordPress, PrestaShop and Magento, but no publicly available price list with specific figures was available on the date checked (2026-10-10). A reliable numerical comparison is therefore not possible without inventing a price.

Saplo's pricing is easier to calculate: one Box, one annual price, and no separate cap on the number of products or orders. Resources such as RAM, SSD storage and transfer increase with your plan, rather than requiring a separate e-commerce license added to your hosting.

4. Payments, SSL and transaction security

Every Box includes a free SSL certificate (Let's Encrypt) that is activated automatically when you connect a domain. This is a requirement of practically every payment gateway integrated with WooCommerce (Przelewy24, Stripe, PayU), so the store is ready to accept payments without additional SSL configuration.

LXC isolation means that customer and order data from one store is separated from other applications on the Box at the filesystem and process levels, not just through permissions within the same WordPress installation. This matters during security audits and GDPR compliance involving the personal data of the store's customers.

Starting with Box M, full SSH access with sudo lets you manually configure WooCommerce cron jobs, such as cart cleanup and inventory syncing with an external system. Larger stores often need this in addition to the standard WordPress dashboard.

5. Who it is for

For a small, one-person business just starting with its first products, Box M is a safe starting point. It provides enough RAM for WooCommerce without overpaying for resources the store does not need yet.

For a store with steady traffic and real revenue, Box L closes the gaps, adding backups, more RAM and more SSD storage, without forcing you to switch to a separate, more expensive product designed specifically for e-commerce, as some competitors do.

For an agency managing several client stores, one Box L or Box XL with a separate container for each store provides full isolation between clients under one shared annual invoice, instead of requiring you to manage several separate hosting accounts.

6. Ordering and your first days with a WooCommerce store

You set up a WooCommerce store just like regular WordPress, selecting the WooCommerce Store option during installation. Your Box container is created as soon as your account is activated, so SSH access (from Box M upward) is ready before you add your first product.

After installation, the WooCommerce setup wizard for currency, payment methods and shipping works exactly as it does on any other host. Saplo does not modify the plugin itself, but provides a server environment ready for it to run.

Connecting a payment gateway (Przelewy24, Stripe, PayU) requires an active SSL certificate, which is activated automatically when you connect a domain. The store can therefore start accepting payments as soon as you configure the gateway in the WooCommerce panel.

Importing an existing product catalog from another store, either from CSV or through a full database migration, is included in the free migration service if you are moving from another host. You do not need to enter every product manually.

During the first few weeks, use the time to monitor RAM usage under real traffic. This lets you assess whether your chosen Box has enough headroom before traffic increases during your first advertising or seasonal sale campaign.

7. What to avoid when hosting an online store

Underestimating RAM from the start and treating Box S as sufficient for a store, even though WooCommerce needs substantially more memory than a simple brochure site when several customers have carts open at once.

Running a store with real transactions without backups. After a failure, this means losing orders and customers, not just site content as with a simple blog that does not handle dynamic data.

Failing to plan for seasonal traffic spikes such as Black Friday and the holidays, which leaves you making a rushed migration at the worst possible moment instead of calmly adding RAM in advance through the hot-add feature.

Ignoring cache performance when using many plugins at once. A store with numerous add-ons, such as reviews, discounts and loyalty programs, multiplies the number of database queries on every product page view.

Assuming a store with an order database is as easy to migrate as a simple brochure site, even though transactional data needs to be transferred carefully to make sure no orders are lost in the process.

8. Store performance under heavy traffic

With real advertising traffic, WooCommerce can generate far more database queries than a simple brochure site. Every customer visit checks stock levels, discounted prices, and cart contents, even if the customer ultimately buys nothing. This type of load, rather than the number of visits alone, puts the most strain on the store's server.

On Saplo, each store runs in a separate LXC container with RAM allocated from the Box. A traffic spike in one store therefore does not take resources away from other apps on the same account. It can, however, require more memory than the starter plan anticipated, especially when a promotion and heavy ad traffic happen at the same time.

Object caching and page caching, such as cache plugins that work with WooCommerce, reduce database queries when pages are viewed repeatedly. The cart and checkout page, however, cannot be fully cached because they must display the current, personalized state for each customer.

If you're planning a major marketing campaign, such as Black Friday or a new collection launch, test your store's performance in advance by simulating traffic. That's better than discovering your resource limits on your busiest day, when there's no time to respond.

The hot-add RAM add-on lets you temporarily increase resources for a campaign without permanently moving to a higher plan. For stores with clear seasonal peaks, such as holidays or sales, this is cheaper than keeping maximum resources allocated all year.

Monitoring resource usage in the Saplo dashboard during and after the campaign helps you determine whether the temporary increase was enough or whether the store is growing steadily and should move to a higher Box for longer, rather than adding resources ad hoc for each promotion.

9. Support for WooCommerce-specific issues

An online store has a different risk profile from a simple brochure site. A payment integration problem or tax calculation error during checkout directly affects your revenue, not just the site's appearance, so response time can be critical to the store owner.

The Saplo team helps customers with common infrastructure issues, including server availability, SSL configuration, and container performance. Configuring WooCommerce itself, its plugins, and payment integrations remains the responsibility of the store owner or their hired developer, just as it does with any other WordPress host.

This distinction matters when choosing a host for your store. You should know where the infrastructure provider's responsibility ends, covering the server, SSL, and backups, and where responsibility for the store configuration begins, so you know who to contact for help if something goes wrong.

The Saplo documentation explains common infrastructure tasks for your store, such as adding RAM before a campaign or setting up a backup before a major update. For store owners without an in-house technical team, it's a practical reference for day-to-day store management.

For stores with seasonal traffic increases, contacting Saplo support before a planned campaign, for example about a temporary RAM increase, is wiser than waiting until your store starts slowing down under real customer traffic.

10. Return on investment in hosting your own store

For a store with steady, substantial traffic, hosting costs quickly become secondary to the value of orders lost during downtime or slowdowns during a peak shopping period. Treat a plan with enough resource headroom as an investment in revenue stability, not just a cost to minimize. A store that loses even a few percent of conversions because the checkout page loads slowly will lose far more than the annual price difference between Box M and Box L.

Comparing the cost of Box L ($149/year) with the cost of losing a single larger order during the sale season shows that the price difference between plans is usually small compared with the real business risk of underestimating server resources during the store's most important period of the year.