Key takeaways
- WooCommerce hosting is WordPress hosting with a store on it. It is not a private server.
- A brochure with hours and a contact form does not need a cart.
- On our cards the WooCommerce Basic plan and the WordPress Basic plan share the same intro and the same renewal. Busy checkout needs more performance, not the Woo label alone.
People hear WooCommerce and shop for a special box. They do not need one. WooCommerce is a WordPress plugin that adds products, a cart, and checkout. The hosting aisle named after it is still WordPress hosting, tuned so the cart is not treated like a blog post.
If nobody can buy anything on the site, you are in the wrong aisle.
| Brochure WordPress | WooCommerce hosting | |
|---|---|---|
| What the site does | Services, hours, a contact form | Products, cart, checkout, orders |
| Extra work | Pages and the form | Inventory, tax, shipping, payment plugins |
| Our Basic intro, then renewal | $2.99, then $7.99 | $2.99, then $7.99 |
A contact form is not a checkout.
What WooCommerce hosting actually is
On WooCommerce hosting you still get WordPress. You also get the store layer: a catalog, a cart that has to stay personal to the shopper, and a checkout that talks to a payment processor. That is heavier than a five-page plumber site, even if the homepage looks the same.
It is not a different data center. It is not a staffed warehouse. The files still live on shared US infrastructure. Support is still tickets and email, a person in Connecticut, not someone watching the cart at 3:00 AM.
We print intro and renewal on the card. The WooCommerce Basic plan starts at $2.99 a month and renews at $7.99. That matches the WordPress Basic plan on WordPress hosting. If you compare those second numbers and they are identical, you are not buying a bigger machine by picking the store label. You are buying the store toolkit. We already argued the teaser problem in compare hosting on the renewal price, not the intro rate.
A brochure site does not need a cart
Most Connecticut shops that call us do not sell SKUs. They sell jobs. A landscaper in West Hartford or a plumber who lives on Google Business Profile needs the site to load, show the work, and send the form. Square on a phone, an invoice, or “call for pricing” is the checkout. Putting WooCommerce on that site adds admin screens you will ignore and plugins you will not update.
Stay on a regular WordPress plan when the money happens off the page. A booking tool that only emails the office is still a form. A “buy now” button that is really a tel: link is still a brochure. You do not owe the internet a cart because a theme demo had one.
If updates are the part you will not do, that is the managed aisle, not the store aisle. We covered the labor split in what managed WordPress hosting is for.
What a store asks of the server
A brochure page can be cached and served to everyone. A cart cannot. Two customers cannot share a cart. Checkout has to hit the database for stock, tax, and the order. That is why a host that looks fine on a homepage test can still choke when three people try to pay at once.
WooCommerce’s own server recommendations for current versions (10.8 and later) ask for WordPress 6.9 or newer, PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6, HTTPS, and a WordPress memory limit of 256 MB. They still admit older PHP 7.4 stacks can boot the plugin. Those older PHP lines are past official end of life, which is a polite way of saying you are borrowing time. Read it on WooCommerce’s server recommendations, not on a ranking blog.
A quiet catalog of twenty products can live on a modest plan. A holiday sale, a pile of extra store plugins, or checkout that also talks to shipping APIs is when the cheap tile lies. Step up performance on the plan you actually run. Do not assume the word WooCommerce on the invoice did that for you.
Card numbers should not sit on your server
If checkout uses a processor such as Stripe with hosted fields, card data is supposed to stay with them. You still need HTTPS on the site. That is not a PCI audit, and we are not your assessor. Ask the processor what their setup actually requires.
When the Woo aisle is the right call
Use WooCommerce hosting when people pay on your domain and the order has to live next to the rest of the WordPress site. You already write in WordPress. You want the catalog, the blog, and the receipt in one login. You are willing to own inventory, tax, and shipping rules, or you pay someone who will.
A farm stand that started on Instagram and now needs stock and pickup windows belongs here. So does a shop that outgrew “DM to buy.” The test is simple. If the site going down on a Saturday costs you orders, not just pride, you are running a store. Treat it like one, including a staging copy before you touch checkout. That why is in what a WordPress staging site is for.
When you should stay on WordPress
Keep the brochure plan when there is no catalog, no cart, and no card form on your domain. Adding WooCommerce “in case we sell merch later” is how sites collect abandoned plugins. Later can wait until there is a product and a payment method.
Some owners pick a hosted store elsewhere and keep WordPress for the story. That can be honest. You rent their checkout. You still need hosting for the WordPress half. Do not run two half-stores and wonder which URL Google should trust.
If you already know you will never log into wp-admin, managed WordPress is the closer match than a store plan you will not stock.
What you still do yourself
Nobody at the host is going to write product descriptions or set Connecticut sales tax. Premium theme and payment-plugin licenses stay on the business, not on a freelancer’s personal account. Staging still matters. Backups still matter. Managed WordPress, if you buy it, is who clicks Update. It is not a merchandiser.
Ask a host, in writing, whether cart and checkout are excluded from full-page cache, whether HTTPS is on the plan, and what the renewal is after the intro. If they only talk about unlimited this and unlimited that, you already have our other post. For the store question, you want to know who owns a failed checkout on a Friday.
If the site takes money on the domain, start on WooCommerce hosting. If it only needs pages and a form, stay on WordPress hosting. For one domain, open a ticket from the client area and say whether anyone can currently pay on the site. That is enough.
