How much does an online store cost?
"It depends" is the honest answer — and also completely useless. When a client asks about the cost of an online store, they usually have a number in mind. The problem is that a $500 store and a $50,000 store are both technically "online stores" — just like a beat-up hatchback and a Porsche are both technically "cars".
The difference lies in scale, degree of customisation, integrations, performance, and the business processes the store needs to support. A store selling 50 products locally has completely different requirements than a B2B platform handling 10,000 SKUs, multiple warehouses, and ERP integration.
The biggest mistake is choosing technology based on where your business is today instead of where it will be in 2 years. I've seen dozens of projects where the client chose the cheapest solution — and 18 months later paid twice as much to rewrite everything from scratch. This article is here to help you avoid that.
What actually drives the cost of an online store?
This isn't a feature checklist. It's a layered problem — and every layer has a price tag.
Two stores can look nearly identical visually and differ in budget by 10x. Why? Because one has a simple cart, and the other handles contract pricing for B2B clients, dynamic discounts, warehouse system integration, and automatic invoice generation. Visually — similar. Technically — completely different software.
Here are the layers that genuinely drive cost:
- Business logic — standard cart, or custom pricing rules, discount tiers, subscriptions, B2B?
- Integrations — ERP, WMS, payment processors, shipping carriers, marketing automation, CRM?
- Catalogue scale — 50 products or 50,000? Variants, attributes, filters, search?
- Traffic and performance — does the store need to handle Black Friday with 10,000 concurrent sessions?
- Checkout UX — standard flow, or multi-step with conditional logic, business addresses, split payment?
- SEO and automation — do you need advanced URL structures, dynamic meta tags, automated sitemaps, schema markup?
- External systems — how many systems need to talk to each other, and how often do they need to sync?
Only when you understand these layers can you have a meaningful conversation about budget. Without that — every quote is a shot in the dark.
Shopify — fast to launch, but with real limitations
Shopify is probably the most well-known ecommerce platform in the world — and it's good for concrete reasons. Let's start with the strengths, because there are genuinely many.
What Shopify does well
- Fast deployment — a store can be live in days, not weeks.
- Stability and security — hosting, SSL certificates, security updates — all included in the price.
- Ready-made ecosystem — thousands of apps, themes, integrations. Most needs can be met without writing code.
- Ease of use — the admin panel is intuitive even for non-technical users.
Where Shopify hurts
- Transaction fees — if you don't use Shopify Payments (unavailable in many markets), you pay an additional fee on every transaction. At high volumes, this adds up fast.
- Vendor lock-in — you're on Shopify's platform. Migration is possible, but costly and painful.
- Limited customisation — Liquid (Shopify's templating language) has its limits. Non-standard business logic can be difficult or impossible to implement.
- App costs compound — every additional feature is another app at $20–100/month. With 10 apps, this becomes a serious budget line.
Real Shopify costs
- Small store implementation: $1,500–4,000
- Monthly platform + app costs: $150–800+
- At scale: app costs can reach absurd amounts
For many businesses, Shopify is an excellent choice. Especially if you're starting out, have a simple business model, and want to focus on selling rather than technology. There's no point building a rocket when you need a bicycle.
WooCommerce — cheap to start, chaotic at scale
WooCommerce is the undisputed king of the SMB ecommerce market in many countries. If you talk to a freelance developer about building a store, there's a good chance they'll suggest WooCommerce. And often, they're right.
Why WooCommerce is so popular
- Cheap to start — WooCommerce itself is free. You pay for hosting, a theme, and optional plugins.
- Massive plugin ecosystem — virtually any feature can be added via a plugin. The ecosystem is enormous.
- Easy to find developers — the market is full of WordPress and WooCommerce specialists.
- Local integrations — local payment gateways, shipping providers, and marketplace connectors typically work out of the box.
Where WooCommerce starts to hurt
- Performance under heavy traffic — WordPress + WooCommerce + 20 plugins is not an architecture built for thousands of concurrent sessions.
- Plugin hell — the more plugins, the greater the risk of conflicts, security issues, and instability.
- Technical debt — WooCommerce stores tend to accumulate technical debt. After 2–3 years, maintenance becomes increasingly expensive.
I've seen stores where updating a single plugin could blow up the entire checkout. That's not an edge case — that's the reality of WooCommerce with a large number of dependencies. Not because WooCommerce is bad, but because the plugin ecosystem isn't designed with consistency in mind.
Real WooCommerce costs
- Simple WooCommerce store: $800–4,000
- More custom project: $4,000–12,000+
- Hosting and maintenance: $50–300/month
Headless commerce / Medusa.js — when does it start making sense?
Headless commerce starts making sense when your business outgrows off-the-shelf solutions. Not because it's trendy. Not because it sounds technical. But because some problems simply don't have solutions within ready-made platforms.
What is headless commerce?
In the traditional approach (Shopify, WooCommerce), the frontend and backend are tightly coupled. Headless means separating these layers: the frontend (what the user sees), the ecommerce backend (logic, orders, products), and external systems all communicate via API.
What does this mean in practice?
- Full frontend control — you can build any UX without constraints imposed by the platform.
- Better performance — Next.js, Astro, Remix — modern frontend frameworks deliver Core Web Vitals that monolithic platforms can't match.
- Any integration — you're not limited to one platform's ecosystem. You integrate exactly what you need.
- Easier scaling — each layer scales independently.
Medusa.js — open-source ecommerce for demanding projects
Medusa.js is an open-source ecommerce engine written in Node.js/TypeScript. It's not another website builder — it's a platform for engineers who want full control over business logic.
What sets Medusa apart?
- Zero transaction fees — you only pay for hosting and your own development. (apart form payment provider on terminal which is obious even in your next door 7eleven).
- Full customisation — you can modify absolutely every aspect of the ecommerce logic.
- Modularity — use only the modules you need. You can replace any component with your own implementation.
- Modern stack — TypeScript, REST API, webhooks, workflows — architecture that any good engineer understands.
Medusa excels at: custom pricing modules, marketplaces, ERP integrations, complex order workflows, B2B logic, multi-vendor, advanced fulfillment. This is the moment when you stop looking for a website developer — and start looking for an ecommerce engineer.
How much does a custom online store cost?
Custom ecommerce is not a landing page with a form. It is software engineering — and it should be priced like software engineering.
If you need: a custom checkout, your own architecture, APIs, integrations with multiple systems, process automation, roles and permissions, marketplace logic, inventory management, ERP sync, multiple payment methods, advanced fulfillment — that is software engineering. And it should be priced accordingly.
Indicative price ranges
- Simple ecommerce (Shopify/WooCommerce, standard features): $1,500–4,000
- Custom ecommerce (own logic, integrations, custom UX): $4,000–12,000+
- Advanced headless / marketplace / B2B: $12,000+
The client isn't buying 200 hours of React. They're buying a system that won't collapse when the business scales. They're buying flexibility, freedom from platform constraints, and the ability to grow the store alongside the company. That's the value worth communicating — and worth paying for.
The hidden costs of ecommerce
This is the section most agencies won't show you in their proposal. But they should. Because hidden costs can completely change the economics of a project.
- Payment processing fees — Stripe, PayPal, and others charge 1.4–2.9% + a fixed fee per transaction. At $100,000/month in revenue, that's $1,400–2,900 every month.
- Shopify fees — plan cost + transaction fees (if not using Shopify Payments) + apps.
- App and plugin costs — every additional feature is another subscription. It's easy to reach $300–800/month.
- ERP and inventory management — licences, configuration, integration, maintenance.
- Hosting and infrastructure — from $15/month (shared hosting) to thousands (dedicated servers, CDN, load balancing).
- Maintenance and development — bug fixes, updates, new features. A store is a living organism, not a one-time project.
- SEO, product photography, copywriting — without good content and SEO, the store won't be visible. These are separate budgets.
- Marketing and advertising — Google Ads, Meta Ads, email marketing. Without traffic, the store doesn't sell.
The most expensive online store is usually the one that needs to be rewritten after a year. Saving money at the start often means paying double 12–18 months later. It's worth factoring this in when choosing your technology.
Which solution makes sense — and when?
Instead of saying "it depends" — here's a concrete breakdown of who each solution is for.
Shopify — best for:
- Fast launch with limited development budget
- Small team without technical resources
- Simple business model (B2C, standard cart)
- Selling primarily in markets where Shopify Payments is available
WooCommerce — best for:
- Small to medium store with a limited budget
- Important local integrations (payment gateways, shipping, marketplaces)
- Already in the WordPress ecosystem
- Not planning rapid traffic growth in the short term
Headless / Medusa.js — best for:
- Custom business processes that no off-the-shelf platform can handle
- Scaling, high traffic, serious performance requirements
- Marketplace, multi-vendor, B2B, subscriptions
- Complex integrations with ERP, WMS, external systems
- Long-term development with an in-house team or a dedicated technical partner
- Full control over architecture
- Low hosting cots. The biggest cost is development itself, but it gives back thanks to ownership over architectire and lower costs of hosting and commisions.
Not sure which solution to choose?
That's completely normal — choosing ecommerce technology is one of the most important decisions you'll make for your business. The wrong choice costs not just money, but time and energy.
If you're not sure which solution makes sense for your business, I can help you choose an architecture based on where your company will be in 2–3 years — not just what's cheapest today.
The goal isn't to sell you the most expensive solution. It's to make sure you don't have to pay twice in a year. If you have a specific project or questions — reach out. Happy to talk it through.
What do I personally recommend?
If you don’t have an issue with spending a larger budget and want to launch as quickly as possible, go with solutions like Shopify or WooCommerce.
If you want full control and flexibility — even at the cost of a longer development process — go with Medusa.js. I’m a strong advocate of freedom and lack of limitations, which is why for my e-commerce projects I choose Medusa.js as the foundation.
