BSc (Hons) Software Engineering, Liverpool John Moores University. Has shipped Shopify migrations, custom POS systems, and AI automation builds for ecommerce and regulated-retail clients.
In this article
Not 'which is better' but 'what does your catalog and content roadmap actually require.' This is the question that changes everything. Most platform debates start from architecture preference — someone read a blog post about headless, or a competitor just launched on a composable stack, and now it sounds like the obvious move. But the honest starting point is simpler: what are the three things your current platform can't do that your roadmap needs in the next 18 months?
That question usually has a short answer. And in most cases, Shopify Plus can do it — custom checkout logic via Checkout Extensibility, metafield-driven merchandising, international markets with Shopify Markets, subscription apps that actually work. The cases where headless genuinely wins are more specific than the hype suggests, and identifying them early saves a significant amount of money.
We ask clients to sketch the customer journey end to end: how a shopper discovers a product, how they navigate the catalog, what the checkout needs to do, and what happens after purchase. If that journey fits inside what Shopify Plus handles natively, the answer is almost always Shopify Plus. If it doesn't — and there are real, legitimate cases where it doesn't — then the headless conversation is worth having.
Beyond the build: ongoing hosting, API costs, and the ecommerce engineering hours a Shopify Plus theme doesn't need. A headless Shopify build starts at roughly 2–3x the cost of a Shopify Plus theme build for the same catalog, and that's before you account for the ongoing maintenance delta.
A Shopify Plus theme build on a well-structured Prestige or Dawn base typically takes 6–10 weeks and produces a codebase any Liquid-literate developer can maintain. A headless build — Next.js or Remix frontend, Shopify Storefront API, a CDN layer, a separate CMS if content is the driver — takes 14–22 weeks for the same catalog and requires frontend engineers with both ecommerce and React expertise to maintain it. The CDN and hosting costs for a headless stack are real: $200–800/month depending on traffic, compared to Shopify's included CDN.
The more significant hidden cost is ongoing iteration. When a merchandiser wants to change a collection layout or test a new PDP format on a Shopify Plus store, a junior developer or a trained merchandiser can do it in an afternoon. On a headless stack, the same change often requires a frontend deploy. The operational overhead compounds over 12 months in a way that the initial build estimate doesn't capture.
None of this means headless is wrong. It means the business case needs to be real, not architectural preference. When the case is real — content and commerce sharing a design system, a checkout flow that Shopify's extensibility genuinely can't handle, app-like product configurators — the additional investment pays back. When it's not, you're paying a premium for infrastructure the roadmap doesn't need.
Catalog complexity is moderate, the team wants to self-manage merchandising, and time-to-launch matters more than architectural flexibility. The threshold where Shopify Plus wins is broader than most headless advocates admit.
Shopify Plus wins when: your merchandising team needs to make changes without engineering involvement, your checkout requirements fit inside Shopify Checkout Extensibility (which now covers a genuinely large surface area including post-purchase upsells, custom shipping logic, and payment customisation), your SEO strategy is straightforward enough that Shopify's built-in SEO tooling handles it, and your content cadence doesn't require a separate headless CMS.
It also wins on timeline. If you need to be live in 8–12 weeks — a common reality for brands launching a new product line, entering a new market, or replacing a broken legacy platform — Shopify Plus is achievable. A headless build at the same quality level almost certainly isn't.
The brands we've built for that are happiest on Shopify Plus are the ones where the storefront is the product. They want to iterate fast on merchandising, test new collection structures, run frequent promotions, and have their team own the day-to-day store management. Shopify Plus is designed for exactly this, and it does it well.
Content and commerce need to share a design system, or the roadmap includes non-standard checkout or app-like features. These are the conditions that genuinely justify the investment.
Headless wins when your content operation and your commerce operation need to feel like the same product rather than two adjacent things. A brand that publishes editorial content — recipes, guides, stories — alongside a product catalog, where the two need to share layout and navigation, often benefits from a headless CMS (Sanity, Contentful, or similar) that serves both surfaces. Shopify's native blogging is functional but limited, and it doesn't give you the content modeling flexibility that an editorial team at scale actually needs.
Headless also wins when the checkout flow is genuinely non-standard. Configured products with real-time pricing, B2B workflows with account-level pricing and approval chains, multi-currency checkout with per-region compliance logic — these sometimes push past what Checkout Extensibility can do. When they do, a custom storefront built headless is warranted.
Finally, headless wins when you need a single frontend to serve multiple backend sources. A brand operating a Shopify storefront, a subscription platform, and a digital product marketplace, all surfaced through a single design system, is a real use case that headless handles better than a monolithic platform.
What actually breaks when you move platforms, and how to budget for it honestly. Platform migrations are almost always underestimated because the visible cost is the build and the hidden cost is everything that doesn't migrate cleanly.
SEO equity is the most expensive thing to lose and the easiest to underestimate. Every URL that changes needs a 301 redirect. Every collection, product, and blog post URL that was ranking needs to be mapped to its new equivalent before DNS is touched. We've seen migrations where this mapping work takes longer than the build itself — a 3,000-SKU catalog with 8 years of indexed URLs is not a quick CSV import.
Customer accounts are the second hidden cost. Passwords cannot be migrated between platforms — it's a security constraint, not a choice. A migration to a new platform means every existing customer gets a password-reset email at launch. How you communicate that, and how the reset flow is designed, affects whether customers reconnect with their accounts or abandon them.
Third-party integrations are the third. A Klaviyo integration that worked perfectly on Magento needs to be reconfigured for Shopify. Your loyalty app may not have a direct Shopify equivalent. Your B2B pricing rules that lived in a custom plugin need to be replicated using Shopify's native B2B tools or rebuilt from scratch.
Budgeting for a platform migration honestly means adding 30–50% to the build estimate for data migration, redirect mapping, integration rebuilds, and the QA work to verify nothing was lost. The teams that do this properly launch smoothly. The teams that don't learn the hard way at go-live.
A Shopify Plus theme build — custom design, full merchandising configuration, and launch support — typically lands between $15,000 and $40,000 depending on catalog complexity, custom functionality requirements, and the number of third-party integrations. A headless build on the same brief starts at roughly 2–3x that range.
Most Shopify Plus builds land between 6 and 12 weeks from kick-off to launch. A headless build on the same brief typically takes 14–22 weeks. Timeline is one of the most common reasons clients choose Shopify Plus over headless when both options are technically viable.
Yes, but it requires careful preparation. Every URL that changes needs a 301 redirect mapped before DNS cutover. Product, collection, and blog post URLs all need to be audited against your current Google Search Console data. Done correctly, most of the SEO equity transfers. Done incorrectly, you can lose months of ranking work overnight.
Checkout Extensibility is Shopify's framework for customising the checkout experience without touching the core checkout code. It covers post-purchase upsells, custom shipping logic, payment method customisation, and branded checkout UI. As of 2024, it replaces the older checkout.liquid approach and covers the majority of custom checkout requirements without needing a headless build.
A headless Shopify build — Next.js or Remix frontend connected to the Shopify Storefront API — typically costs $40,000 to $120,000 depending on catalog complexity, custom checkout requirements, and CMS integrations. This is 2–3× the cost of a Shopify Plus theme build on the same brief. Ongoing hosting and CDN costs for a headless stack run $200–800/month, compared to Shopify's included CDN.
A Shopify Plus custom theme build typically costs $15,000–$40,000 and takes 6–12 weeks. A headless build on the same brief costs $40,000–$120,000 and takes 14–24 weeks. The ongoing maintenance cost of headless is also higher — changes require frontend developers rather than Shopify-trained merchandisers. The headless investment is justified when the roadmap genuinely requires it; for most brands, Shopify Plus covers the requirements at a fraction of the cost.
Work with us
We build Shopify stores, custom software, and AI tools for ecommerce brands — remote, worldwide.
Related reading
What actually breaks when you migrate a Shopify store, and the honest range for how long checkout realistically stays down during cutover.
Read moreA plain-English breakdown of when each platform wins — and the specific signals in your roadmap that should push you toward one over the others.
Read more