An off-the-shelf WooCommerce theme makes sense for as long as your store sells the way most stores sell. A simple range, a standard cart, ordinary shipping - then a marketplace theme for a few hundred PLN (Polish market rates) launches in a week and does the job. A custom design starts paying off the moment you begin fighting the theme instead of using it: paying for extra plugins, working around limits, rewriting the look screen by screen.
Below I break both routes down into parts: what you are buying, where the costs hide that the licence price does not show, and how you can tell that the ready-made theme is already costing you more than a design would.
What a WooCommerce store theme is
A WooCommerce store theme is a set of files that decides the look and layout of the store: the homepage, the product list, the product page, the cart and the checkout. WooCommerce itself is the sales engine, and the theme is its bodywork. Swapping the theme does not delete products or orders - those sit in the database and survive every change of appearance.
You will meet three kinds:
- Multipurpose themes - Divi, Astra, Flatsome, Woodmart. One theme, dozens of ready-made variants, hundreds of options in the admin.
- Niche themes - built for one type of store, e.g. furniture or cosmetics. Fewer options, but they look sensible out of the box.
- A custom theme - code written for your store, usually as a child theme of a lightweight base. Only what you actually use.
Off-the-shelf theme versus custom design - a comparison
Below are the differences that genuinely affect cost and sales, not how the store looks in a screenshot:
| What | Off-the-shelf theme | Custom design |
|---|---|---|
| Time to launch | Days, with a complete set of content | Usually a few weeks |
| Entry cost | Theme licence plus setup | Higher one-off |
| Layout changes | Within the theme’s options | Anything, because it is your code |
| Speed | Depends on the theme’s weight and the plugin count | Controlled from day one |
| Vendor dependency | High, licence and updates on their side | None |
| An unusual buying process | Worked around with plugins | Designed in directly |
| Updates | Frequent, sometimes break your changes | Only the engine and plugins |
Neither column is worse in itself. The bad choice is a ready-made theme in a store with an unusual process, or a custom design for a store with twenty products and classic courier delivery.
When an off-the-shelf theme is the right choice
An off-the-shelf theme is the right choice when you sell in a way the theme’s authors anticipated. Specifically:
- Simple products, or ones with one or two options (size, colour) and no configurator
- Standard delivery and payment - courier, parcel locker (in Poland typically InPost Paczkomaty, the self-service pickup boxes most shoppers use), BLIK, bank transfer, card
- One market and one currency at the start
- The budget has to leave room for photos, copy and advertising - because those sell, not the layout
- You want to check quickly whether the store idea holds up and learn from real orders
In that scenario a good ready-made theme plus a proper setup gives you a store a customer will not tell apart from a designed one. There is one condition: you do not ask the theme to do things it was never built for.
When a ready-made theme starts costing more than a design
A ready-made theme starts costing more the moment every change needs another plugin or another workaround. The signals I see most often when a store comes to me for a rebuild:
- Two plugins get added for one feature, because the theme cannot do it alone
- The admin has several dozen active plugins and nobody can say which are needed
- Every theme update reverts the visual fixes, because they were made directly in the files instead of in a child theme
- The cart and checkout look different from the rest of the store, because they are glued together from three sources
- The product page loads noticeably slower on a phone than the homepage
- A simple change to the product page layout is quoted higher than writing it from scratch
There is no fixed time limit here - for some it comes after a year, for others never, because the store still sells in the way the theme anticipated. You can check it yourself: once a year, add up the top-ups for licences, plugins and fixes, then put that figure next to a quote for a rebuild. When the sum starts catching the quote and the store is still standing on somebody else’s code, the ready-made theme has stopped being the cheaper option. If the look is fine and only the way it works hurts, sometimes a refresh without rebuilding the whole store is enough - I check that first, because it is cheaper.
What it really costs
The theme licence is the smallest part of the bill. Theme and plugin prices change several times a year, so treat the below as an order of magnitude to verify at the source on the day you buy:
| Item | Order of magnitude | Note |
|---|---|---|
| Multipurpose theme, annual licence | A few hundred PLN | Some are sold as lifetime |
| Page builder, Pro version | A few hundred PLN a year | Usually required by the theme |
| Additional plugins | From zero to a few hundred PLN a year each | This is what grows fastest |
| Setting up a ready-made theme | Depends on scope | Photos and copy usually on your side |
| A custom design with me | 5,000-10,000 PLN net | Written quote before the start |
| Ongoing technical maintenance | 1,000 / 2,000 / 3,500 PLN net per month | Basic, Pro, Premium |
I went into more detail in the piece on the real cost of WooCommerce plugins and in the calculation of what a WooCommerce store costs.
Why themes are sometimes slow
Multipurpose themes are sometimes slow because they have to cover every scenario at once, including the ones you never use. The theme ships the browser a full set of styles and scripts for all of its modules, and your store uses a handful of them. On top of that comes a page builder, which generates more code than a layout written out directly.
You see the effect on a phone, in Core Web Vitals. It can be brought under control without changing the theme: switching off unused modules, tidying up the plugins, handling images properly and adding caching. I wrote that up in the pieces on Core Web Vitals in WooCommerce and on why a WooCommerce store runs slowly. A custom theme is not fast by magic - it is fast because it contains nothing surplus.
The third route, the one I recommend most often
Most often I recommend the middle option: a lightweight base plus your own child theme, with design applied only where it decides sales. In practice that means three things:
- A lightweight base theme instead of a heavyweight all-in-one, so you do not drag along code you will never use
- A child theme for every modification - that way an update to the base reverts nothing
- Custom code only on the key screens: the product page, the cart, the checkout and anything unusual about your business
The rest of the store, meaning information pages and the blog, can happily sit on ready-made blocks. This costs a fraction of a full design and removes exactly the limits that hurt most later. I described the same decision mechanism for company websites in the piece on an off-the-shelf template versus a made-to-order site.
How to pick a theme you will not regret
If you are going with a ready-made theme anyway, walk through this list before you buy:
- Check the date of the last update and whether the author answers tickets on the support forum
- Open the demo on a phone and click the whole path from the product list to the checkout
- Count how many plugins the demo requires - the more there are, the harder later updates get
- Check digital accessibility: contrast, keyboard operation, form field labels. Accessibility requirements have applied across the EU since June 2025 and cover online sales too, and many themes still do not meet them
- Establish whether the licence is annual or one-off and what happens when it expires
- Plan for a child theme from day one, even if it does not contain a single line at launch
The criteria for picking the base itself I laid out in the piece on which WordPress theme to choose - it is a decision you make once and live with for several years.
How I check this myself
I start with a free diagnosis: I look at the theme, the plugin list, the results on a phone and the customer’s path to payment, and then I say plainly whether in your situation it is cheaper to tidy up what is there or to build anew. Very often it is the first option, and that is the honest answer even when it earns me less.
When it does come out as a build, you get a written quote before the start, with scope and a deadline. Fixed-price projects usually land in the 5,000-10,000 PLN net range, and exactly what falls inside the scope is agreed before signing. I then run the store on as part of optimization, or build it from the ground up as part of ecommerce stores.
Frequently asked questions
Will changing my WooCommerce theme delete my products and orders? No. Products, orders and customers are saved in the database, and the theme is only responsible for the look. What can disappear are appearance settings and page layouts built in the previous theme’s builder, which is why the change is made on a copy, not on a live store.
How much does a good WooCommerce store theme cost? Commercial themes are usually in the order of a few hundred PLN per licence, often renewed annually, plus a page builder and plugins. Price lists change often, so check with the author on the day you buy. The real cost of a store is always licence plus setup plus maintenance, not the theme price alone.
Is a free theme enough for a store? For a simple store, yes, provided it is actively developed and comes from the official WordPress directory. The problems start with an unusual product page and with digital accessibility, because free themes rarely have those areas polished. Never install premium themes from pirated sources - that is the shortest road to an infected store.
How will I know it is time for a custom theme? By the fact that every change in the store needs another plugin or another workaround, and quotes for small fixes go up instead of down. The second signal is a slow product page on a phone that cannot be improved without cutting out half the theme. If both happen at once, put the cost of a rebuild next to the sum of top-ups and fixes from the last year - that comparison settles the decision better than any impression.
Running a store where something does not work the way it should? I build and rebuild WooCommerce stores - from a single fix to reworking the whole sales flow. Tell me what you are dealing with and I will send back a scope and a price.