An online store is not a "page with a cart". It is a sales system that has to run around the clock, handle payments, integrate with your warehouse and never lose the customer at the final step. That is why price ranges are wider and more misleading than for a regular website - and most comparisons online quote only the build price, staying silent about what actually costs money over the following years.
In this article we break down 2026 online store prices into their real parts: what you will actually pay upfront, the hidden costs, when each option pays off, and how to work out whether the investment makes sense for your specific business.
Price ranges in 2026
The market splits into three clear segments today. Each matches a different business stage and scale.
1. Hosted platform ($1,100-3,300 to set up)
Shopify, WooCommerce on a ready theme, or a local SaaS platform. You launch in days, pick a template, upload products and go. It is the fastest and cheapest way to start.
The downside is that you pay in a currency other than the invoice total: in transaction fees, monthly subscription and engine limits you cannot escape without migrating. The store easily ends up looking like thousands of others, and customisation ends where the theme's limits begin.
2. WordPress/WooCommerce with a custom design ($4,200-9,500)
Here you get a custom design on a popular engine. The store looks good and is visually "yours" while the catalogue is moderate and traffic stays below a few thousand visits a day.
The compromise is that every new feature is another plugin, and every plugin is extra code, a security risk and a slowdown. Over time the store "grows over" and loads slower - and in e-commerce, every second of load time is a measurable drop in conversion.
3. Custom headless store (from $13,900)
A frontend written from scratch in Next.js, wired to headless commerce (a separate products, payments and cart engine). It gives full control over the look and speed, copes well with growing traffic and lets you design the purchase path around a premium brand - but it needs a bigger budget and ongoing technical care.
This is for stores where speed and conversion translate into real money: high cart value, heavy traffic, international sales or a configurable product.
Table: what you get for your money
| Segment | Build cost | Yearly cost | Best for |
|---|---|---|---|
| Hosted platform | $1,100-3,300 | subscription + fees | Launch, small catalogue |
| WooCommerce custom | $4,200-9,500 | hosting + plugins + upkeep | Mid store, own brand |
| Headless (Next.js) | from $13,900 | hosting, commerce engine, updates | Premium, scale, export |
What really drives the price
A store's cost is the sum of four things - and they, not the "design" itself, decide the quote.
- Number and complexity of products. Thirty simple products price very differently from 5,000 with variants, sizes and configuration-dependent pricing.
- Integrations. Payments are only the beginning. Inventory, ERP, couriers, invoicing, loyalty systems - each integration is a separate module.
- Performance requirements. A store meant to load in 0.5s under heavy traffic needs a different architecture than a store for a local brand.
- Shopping experience. Whether we design a deliberate buying journey or just a product list with an "add to cart" button.
A premium store selling multi-thousand items needs a completely different checkout than one selling $12 gadgets. The first defends price with experience and trust, the second competes on convenience and speed. Forcing both onto the same template is the most expensive of the "cheap" mistakes.
Hidden costs nobody mentions
The build price is often less than half the total cost of owning a store. Before you decide, also count:
- Platform and payment fees - for example on Shopify's Basic plan with an external payment provider, a 2% transaction fee applies; at $25k monthly turnover that is $6,000 a year. On top of that every payment gateway takes its own fee - whatever the platform, headless stores included.
- Premium plugins - shipping calculators, integrations, optimisations. Cheap individually, together they can add up to thousands a year.
- Maintenance and security - updates, vulnerability patching, backups. A neglected WooCommerce store is an invitation to bots.
- The cost of slow loading - invisible on the invoice but the most painful: abandoned carts, lower Google rankings, fewer orders.
When headless actually pays off
A custom headless store makes sense when you meet at least one condition:
- You sell high-value products where the shopping experience defends the price.
- You have heavy traffic and every percentage point of conversion is real money.
- You are entering foreign markets and need speed and localisation.
- Your product is configurable and needs custom logic.
A live-pricing configurator can cut the path from landing on the site to a finished quote from days to minutes - and raise average order value, because the client configures the options themselves. That is the difference you pay for with custom code - not a "nicer template", but logic that sells.
How to check if it pays off
The simplest return model looks like this: take the price difference between the cheaper and pricier option, then estimate how much the pricier option will lift conversion or average cart. If a store does $50k monthly turnover at 2% conversion, going to 2.5% means a quarter more orders. Work out on margin what that is really worth - and judge honestly whether the pricier option is likely to deliver it.
Divide the extra store cost by the monthly profit from the extra conversion. The result is the payback in months. If it comes out under a year, the pricier option almost always pays off.
Shopify, WooCommerce or headless - how to choose
This question comes up on every project, so let us turn it into a decision rather than a religion. Shopify is the fastest start with the fewest technical worries, but you pay a monthly subscription - plus an extra transaction fee if you use an external payment provider - and customisation ends where the theme's limits begin. WooCommerce gives full control over the look and no sales fees, but every feature is a plugin, and every plugin is a cost, an update and a potential security hole. Headless on Next.js is the investment that pays off at scale: you separate the frontend from the commerce engine, which makes a fast store and full control over the look easier - at the cost of a higher budget and your own upkeep.
The short version: selling a dozen products and testing the market - start with a hosted platform. Building a premium brand or scaling traffic - custom code pays off sooner than you think. We break down the "someone else's engine" versus "code built for you" trade-off in WordPress or custom code.
The mistakes that needlessly raise the cost
Most overpriced stores overpaid for the same reasons. Know them before you sign.
- Buying headless "because it's trendy" with 30 products. At small scale a hosted platform is cheaper and faster to launch - custom code is a scaling tool, not an ornament.
- Ignoring fees in the maths. Run platform and payment fees over three years before calling a platform "cheap".
- Not quoting integrations. Inventory, ERP, couriers and invoicing are separate modules. If the quote does not list them, the hidden cost returns at build time.
- Saving on speed. A slow store loses customers at checkout and rankings in Google - the most expensive "saving", because it is invisible on the invoice.
Store speed is money, not technology
In e-commerce slower loading usually lowers conversion - the customer does not wait, they return to the search results. A fast frontend can win back some abandoned carts, though how many depends on the starting point. We explain why speed matters and how it translates into sales in Core Web Vitals and sales. And if you are still weighing the budget for a company website itself, start with How much does a website cost.
Frequently asked questions
Yes - with a small catalogue and a market to test, it is usually the most sensible start. A custom solution is worth revisiting once scale, fees or the platform's limits start to cost real money - by then you will know what the store needs.
How much does it cost to maintain a store per year? For a hosted platform: subscription plus fees. For WooCommerce: hosting, plugins and technical upkeep. For headless: hosting, the commerce engine (a licence or running your own) and framework security updates - fewer random patches than with plugins, but not zero.
Is a custom store hard to manage? No. You edit content and products in a panel just like on a hosted platform. The difference is under the hood, not in daily use.
How long does building an online store take? A hosted platform: a few days to two weeks. WooCommerce with a custom design: usually 4-8 weeks. A custom headless store with integrations: usually from 10 weeks up, depending on the number of products and system connections.
Can I move from Shopify to custom code later? Yes, but migration has a cost - products, URLs and order history must move without losing Google rankings. Sometimes it is cheaper to build the target solution from the start than to pay twice.
An online store is an investment, not a cost - but only when someone designed it to earn and worked the numbers with you before issuing the invoice. To estimate your case, run the project in the calculator or write to us for a concrete quote.