Traditional ecommerce — Shopify, WooCommerce as a monolith, BigCommerce — is faster to launch and cheaper to start. Headless ecommerce is faster at runtime and more flexible long-term. Neither is universally better. The right answer depends on your GMV, your development budget, and how much your current platform is actually limiting you.
What “Traditional” Ecommerce Actually Means
Traditional ecommerce means your frontend and backend run on the same platform. Shopify renders your product pages. WooCommerce generates your checkout. The theme, the cart, the payment processing — all managed by one system, often through a visual editor or theme files.
The advantages are real. You can launch a Shopify store in a day. WooCommerce has 59,000+ plugins. The documentation is extensive, the developer pool is massive, and the monthly costs are predictable.
The limitation is equally real. You are constrained by what the platform allows. Every custom feature has to work within Shopify’s Liquid templating system or WooCommerce’s hook architecture. Performance is bounded by what the monolith can deliver — and on Shopify in particular, you cannot optimize the server-side rendering layer because you do not control it.
What Headless Ecommerce Actually Means
Headless ecommerce means your backend (product data, cart, orders, checkout) runs separately from your frontend (the website the customer sees). The two talk via API. You build your frontend in whatever framework you want — Next.js, Nuxt, Remix — and call the backend API to get product data, add items to cart, and process orders.
The performance advantage is significant. A Next.js storefront with static generation and edge caching can serve product pages in under 200ms globally. A Shopify storefront on Liquid typically delivers 800ms–2,500ms Time to First Byte on a cold server, depending on theme complexity and app overhead.
That performance gap has a revenue impact. Google’s data points to a 32% increase in bounce rate when page load time goes from 1 second to 3 seconds. At $2M GMV, a 10% conversion improvement from faster pages represents $200,000 in additional revenue per year — enough to fund a significant headless build.
We explain the full architecture in our post on headless commerce explained.
The Real Cost Difference
This is where most headless comparisons get dishonest. They compare Shopify’s monthly fee to zero and declare headless the winner. That ignores build cost.
Traditional ecommerce costs
- Shopify Basic to Advanced: $39–$399/month ($468–$4,788/year)
- Shopify Plus: $2,300/month ($27,600/year)
- WooCommerce hosting: $100–$500/month for production-grade hosting
- Theme + plugins: $500–$5,000 one-time, plus annual renewals
- Custom development: $5,000–$30,000 for meaningful customization
A fully customized WooCommerce store might cost $15,000–$40,000 to build and $2,000–$6,000/year to maintain.
Headless ecommerce costs
- Platform licensing (Medusa, open-source): $0. Vendure: $0. Saleor: $0.
- Hosting: $200–$800/month for API backend + CDN + frontend hosting
- Build cost: $40,000–$120,000 for a full headless build with custom storefront
- Ongoing development: $15,000–$50,000/year for feature work and maintenance
The break-even point for headless vs a well-built WooCommerce monolith is typically around $800K–$2M in annual GMV — where platform fees and performance losses from traditional architecture start to exceed the amortized cost of the headless build.
Below that threshold, traditional ecommerce is usually the right financial decision. Above it, the math often flips.
For a detailed look at what Shopify costs at scale, see our post on the true cost of Shopify at scale.
Performance: What the Numbers Look Like
The Core Web Vitals gap between headless and traditional is measurable.
A well-built Next.js headless storefront on Vercel or Netlify Edge typically achieves:
- LCP (Largest Contentful Paint): 1.2–2.0 seconds
- FID / INP: under 100ms
- CLS: under 0.05
A standard Shopify store with a premium theme and 8–12 apps commonly shows:
- LCP: 3.5–6.0 seconds
- FID / INP: 150–300ms
- CLS: 0.1–0.25 (apps injecting content cause layout shift)
The performance gap is not theoretical. It is measurable in Google Search Console, and it affects both organic rankings and paid conversion rates.
That said, a badly-built headless storefront can perform worse than a well-optimized Shopify theme. Headless architecture enables better performance — it does not guarantee it. The implementation matters.
When Traditional Ecommerce Is the Right Call
Traditional ecommerce is the right choice when you are launching a new store and need to validate product-market fit before spending $60,000 on a headless build. It is right when your GMV is under $500,000 and the platform fee is a manageable percentage of revenue. It is right when your team has no developer, and you need to make store changes through a visual editor without writing code.
WooCommerce in particular has a compelling ownership argument even in its traditional form. You own the code, the database, and the hosting. There are no transaction fees. Plugin costs are mostly one-time. A hand-coded WooCommerce build from a capable agency — not a page builder shop — can perform and convert at a level that does not require headless architecture to justify. We build those through our WooCommerce development service.
Traditional ecommerce is also the right call when your product catalog and store logic are straightforward. If you sell 50 products with standard variants and no complex pricing rules, headless architecture adds cost and complexity without solving a real problem.
When Headless Ecommerce Is the Right Call
Headless makes sense when performance is a genuine business constraint — when you have analytics showing that page speed is causing meaningful drop-off, and a traditional platform cannot fix it. It makes sense when you are selling across multiple channels (web, mobile app, kiosk, B2B portal) and you need one commerce backend serving all of them via API.
It makes sense when your store logic has outgrown what a plugin can handle: custom pricing engines, subscription tiers with complex upgrade paths, multi-warehouse fulfillment with real-time inventory allocation. These scenarios require a composable backend that a monolith was not designed to handle cleanly.
It also makes sense at high GMV simply because platform fees become a significant cost. At $5M GMV on Shopify Plus ($2,300/month plus 0.6% transaction fee), you are spending $27,600/year in platform fees plus $30,000/year in transaction fees — $57,600/year that a self-hosted headless build eliminates. That ROI math is easy.
For a deeper look at where Medusa.js fits in this decision, see our post on Medusa.js for growing ecommerce.
The Team Size Factor
Headless ecommerce requires a developer. Not permanently on payroll, but available. Someone who can push updates to the storefront, handle dependency upgrades, monitor the API backend, and debug issues when they appear.
Traditional ecommerce platforms are specifically designed to let non-developers manage the store day-to-day. A Shopify merchant can add products, update banners, run promotions, and change shipping rates without touching code. A WooCommerce store with a well-built admin UI is nearly as accessible.
A headless store requires developer involvement for anything beyond content updates. That changes the staffing math. If your business does not have a developer and cannot afford one on retainer ($1,500–$4,000/month for a reliable agency relationship), traditional ecommerce is genuinely more appropriate — not because it is technically better, but because it fits your operational reality.
The Hybrid Option: Headless-Adjacent Builds
There is a middle path that some businesses get value from: keeping WooCommerce as the commerce backend but decoupling the frontend into a high-performance custom theme — not a page builder, but hand-coded PHP, minimal JavaScript, and aggressive server-side caching.
This approach delivers Core Web Vitals scores in the 85–95 range on mobile, eliminates plugin bloat, and costs $15,000–$35,000 to build. It is not technically headless (the frontend and backend still share a server), but it eliminates most of the performance problems that drive businesses toward headless in the first place.
For businesses in the $300,000–$1.5M GMV range, this is often the highest-ROI option. You get meaningful performance improvement without the full infrastructure overhead of a headless build.
Making the Decision
The question to ask is not “is headless better?” It is “what problem am I actually trying to solve?”
If the answer is “I need to launch quickly and keep costs low,” traditional wins. If the answer is “my site is slow and Shopify won’t let me fix it,” headless wins. If the answer is “my platform fees are eating my margin at scale,” headless wins. If the answer is “I want to sell on web, app, and B2B portal from one backend,” headless wins. If the answer is “I’ve heard headless is modern and I want to be modern,” you are not ready for headless.
View our fixed-price packages to understand what a custom build costs before you commit.
Frequently Asked Questions
What is the main difference between headless and traditional ecommerce? In traditional ecommerce, one platform handles both the backend (products, orders, cart) and the frontend (what customers see). In headless, these are separated — the backend exposes an API, and you build the frontend independently. The separation gives you more control over performance and frontend experience, at the cost of added complexity and build time.
Is headless ecommerce worth it for a small business? Usually not. For stores doing under $500,000 GMV, the development cost of a headless build ($40,000–$120,000) is difficult to justify. A hand-coded WooCommerce store delivers strong performance at a fraction of that cost. Revisit headless when platform limitations or fees become a real constraint.
How much faster is a headless storefront compared to Shopify? A well-built Next.js headless storefront typically achieves LCP of 1.2–2.0 seconds. A standard Shopify theme with multiple apps often lands at 3.5–6.0 seconds LCP. That gap narrows if you strip down the Shopify theme aggressively and remove unnecessary apps, but the architectural ceiling is lower.
Can I run headless ecommerce without a developer? No. Headless requires developer involvement for anything beyond content updates. If your business cannot support ongoing developer access (internal or agency), headless architecture creates a fragile situation where normal store changes become blocked. Traditional ecommerce platforms are explicitly designed for non-developer management.
What headless commerce platforms should I consider? Medusa.js is the strongest open-source option for mid-market businesses. It is free to use, built on Node.js, and actively maintained. Alternatives include Vendure, Saleor (Python-based), and commercetools (enterprise, $50,000–$150,000/year). We compare these in our open-source headless commerce comparison.
Does headless ecommerce hurt SEO? Not if it is built correctly. A Next.js storefront with server-side rendering or static generation produces fully crawlable HTML. The performance improvements from headless architecture typically help SEO. The risk is client-side-only rendering (JavaScript-rendered pages that Google struggles to index) — but that is an implementation problem, not an architecture problem.
How long does a headless ecommerce build take? A full headless build — API backend configured, custom Next.js storefront, payment integration, deployment pipeline — typically takes 10–20 weeks depending on complexity. A traditional WooCommerce build runs 6–12 weeks. That time-to-market difference matters if you are trying to launch quickly.
The decision is not ideological. Headless architecture is not inherently superior — it is a tool with a specific cost-benefit profile. Use it when the benefits justify the cost. Use traditional ecommerce when they do not. If you are not sure, a well-built WooCommerce store is a defensible starting point that you can migrate off when the business warrants it.
See our WooCommerce development service or go straight to fixed-price packages to understand the scope and cost of a proper build.