WooCommerce is an extension for WordPress that turns an existing website into a shop. That is essentially the whole idea — and also why the answer to "is it worth it?" depends so heavily on what you already run today and who will look after it tomorrow.
We build with WordPress and WooCommerce. Please read this with that in mind. Which is why you will not find a list of other systems’ shortcomings here, but an attempt to tie the decision to criteria you can check yourself — including when the answer turns out to be against building a shop at all.
When WooCommerce is the right fit
There are four situations in which the decision is usually clear cut:
- You already run your website on WordPress and update content there regularly
- You want to own the shop, the orders and the customer data rather than rent them
- Your catalogue is small to mid-sized and changes at a manageable pace
- You do not want to hand a share of revenue to a shop platform
The common thread is ownership. The shop runs on hosting you choose, order and customer data sit in your own database, and you can change service providers without losing the shop. That is not an abstract benefit — it is the difference between moving house and starting over.
When WooCommerce is the wrong fit
The other direction is just as clear. If any one of these three applies, we advise against it:
- You want nothing to do with maintenance — neither yourself nor through a provider
- You sell across several channels at once, such as marketplaces, social platforms and a physical shop, and need stock levels that stay correct everywhere simultaneously
- Nobody has been named as responsible for updates and backups
The first and third points look different but amount to the same thing. A self-hosted shop is software that belongs to you — and software that belongs to nobody does not get maintained. That is where most small shops actually fail: not at launch, but in month fourteen, when nobody has looked at it for half a year.
Six criteria you can decide this on yourself
The platform question is usually argued as a matter of belief. It can be answered quite soberly against requirements instead. Work through the table below row by row and note which column applies to you. If one column clearly dominates, you have your answer.
| Requirement | Points towards WooCommerce | Points towards a hosted solution |
|---|---|---|
| Existing website | You already run WordPress and maintain content there yourself | You are starting without a website, or on a different system |
| Responsibility for updates | A named person or provider is in place for it | Nobody should have to deal with updates, backups and server upkeep |
| Catalogue | Manageable catalogue with its own rules for variants, tiers or collection | Very large or constantly changing catalogue with largely uniform logic |
| Sales channels | You sell essentially through your own website | You sell through marketplaces, social platforms and a till at the same time |
| Fee model | The shop software itself takes no share of revenue; payment providers bill separately | A provider fee model whose terms you check in advance |
| Data and ownership | Orders and customer data sit in your own database | Data sits with the provider; access runs through their export |
What a shop requires legally that a brochure site does not
This is the part small shops underestimate most often. As soon as you sell to consumers in Germany, obligations arrive that a plain company website does not carry. They are not formalities at the edges — they are part of the checkout itself.
- A right-of-withdrawal notice and model withdrawal form, reachable and sent to the customer
- Terms and conditions that match your catalogue and the regions you ship to
- An Impressum that meets the requirements for a commercial website
- A privacy policy that covers ordering, payment and shipping — not just the contact form
- Price information under the German price indication rules: total price, VAT notice, shipping costs and, where applicable, the unit price
- An order button that states unambiguously that the order carries an obligation to pay
Technically that is our job: the texts have to appear at the right point in checkout, be sent along with the purchase, and must not disappear into a subpage nobody sees. In substance it is a lawyer’s job. That is why we do not use texts pieced together from the internet, and do not recommend it to anyone — with shop texts that is the single most common reason for a warning letter.
The ongoing cost that rarely gets planned for
A self-hosted shop is not a piece of furniture you set down once. It is a small operation, and it carries a baseline of work. That work exists whether you plan for it or not:
- Keeping the WordPress core, WooCommerce, the theme and every extension up to date
- Moving with the hosting PHP version when the old one reaches end of life
- Backups that somebody has restored at least once as a test — an untested backup is an assumption, not a safety net
- A real test order through to payment confirmation after every larger update
- Payment and shipping extensions, which follow update cycles of their own
- An eye on checkout itself: a shop can look perfectly fine and have failed to complete a payment for days
We deliberately give no figures here. What hosting, extensions and payment processing cost varies so much by provider, catalogue and turnover that any range would imply more than it explains. What can be said: this work does not go away. The one mistake that reliably gets expensive is assigning it to nobody.
A useful test before you start: write a name on a piece of paper. Who checks, on the first Monday of the month, whether updates are due, whether the last backup genuinely exists, and whether a test order goes through? If there is no name, the shop is not ready to be decided on — regardless of the system it would be built with.
The honest edge case: five products
The uncomfortable part first. If you have five products and sell one of them occasionally, a shop may be the wrong answer to a right question.
A shop is a system made of a basket, checkout, order management, shipping rules, tax rates and mandatory legal texts. All of it has to be operated — including in the months when nothing sells. A very good product page with clear photos, an honest description, a visible total price including shipping and a payment link can sell more in that situation than a shop nobody maintains. It has fewer moving parts, and fewer moving parts break less often.
One point that often gets lost here: the legal obligations of selling to consumers do not disappear. A payment link is a sale too. The difference lies in technical effort and maintenance, not in the legal position. And if turnover grows, moving to a proper shop later becomes a decision backed by numbers rather than a bet.
How we price a shop project
For websites we publish fixed prices. For shops we do not, and there is a factual reason: two shops with the same number of products can differ several times over in effort, depending on what sits behind the sale. A price quoted before that is clarified is a guess.
So before any quote we clarify the same points:
- How many products, and do they have variants such as size, colour or quantity?
- How are prices formed — fixed, tiered, with a unit price, with different tax rates?
- Which payment methods should be available, and through which provider?
- How does shipping work: flat rate, weight, zones, collection in person, abroad?
- Is there an existing shop or inventory system whose data has to be migrated?
- Who maintains the shop after launch, and who is responsible for updates and backups?
Only once those six answers exist is a price more than a number. You then get it fixed before the work starts, and you receive every login at the end — hosting, shop, payment provider, Search Console. The shop is yours, technically as well.
Our published packages, Standard (€1,250) and Pro (€2,100), are website packages. A shop is quoted separately from them and is not calculated as a surcharge on top. The first conversation costs nothing, and it is explicitly allowed to end with "you do not need a shop yet" if that is the honest answer.
Frequently asked questions about WooCommerce for small shops
We publish no price for this, because the effort depends mainly on variants, shipping rules, payment methods and any data migration — not on the number of products. We clarify those points in the free first consultation and then quote a fixed price before the work begins. Anyone who names a figure without that clarification is guessing.
For day-to-day operation, yes: adding products, changing prices and processing orders can be learned in a short handover session. For the initial setup, less so, because that is where tax rates, shipping rules and the placement of mandatory legal texts are decided. Getting those right once is considerably cheaper than correcting them later.
We deliberately avoid naming a figure, because without context it would be worthless. In practice the size is limited by hosting and by how the catalogue is built, not by a fixed ceiling in the software. For small and mid-sized catalogues it is a non-issue; if the catalogue gets very large, the question belongs before the project starts.
Structurally, three things: with WooCommerce the installation belongs to you, with a hosted solution you rent the operation of it. Maintenance sits with you or your provider in one case and with the platform in the other. And the fee model differs — always check the terms with the specific provider rather than relying on general statements.
Not necessarily to run it, but usually to set it up. What matters is less who builds the shop than who takes responsibility afterwards for updates, backups and a regular test order. If you want to take that on yourself, we set the shop up so that doing so is realistic.
Free consultation
We look at your website up front and show you the biggest levers for more enquiries.
