Shopify Plus vs Headless vs Custom: Which Should You Build On?

For most brands doing $10M+ online, Shopify Plus on a custom Online Store 2.0 theme is the right default. Go headless when a specific requirement can't be met with themes and apps, and you have engineers to own a frontend for years. Go fully custom or composable only when the business model itself doesn't fit a SaaS platform.

That's the short version. This guide covers what each option really involves, what it costs to run, who has to run it, and the migration risks that decide whether the move pays off. It draws on platform documentation and on replatforms DYODE has shipped in both directions, including taking a brand off headless.

What is the difference between Shopify Plus, headless and custom?

All three are ways to split responsibility between a platform and your team. On Shopify Plus with a theme, Shopify runs the backend and the storefront. Headless keeps Shopify's backend but you build and host the frontend. Custom or composable means you assemble the backend from separate services, then build the frontend too.

Shopify Plus on a theme (Liquid and Online Store 2.0)

The storefront is a Shopify theme written in Liquid. In Online Store 2.0 architecture, JSON templates act as a wrapper for sections, and sections and blocks are reusable modules merchants add, remove and reorder in the theme editor. Apps plug in through theme app extensions (app blocks and app embeds) without anyone editing theme code. A custom theme is still custom: your design, your components, your code, on Shopify's hosting and checkout.

Headless Shopify (Hydrogen, Oxygen or your own frontend)

Shopify describes headless as separating the storefront's frontend from its backend: "You build the frontend, and Shopify's APIs handle the commerce underneath." The Storefront API is GraphQL, and checkout is still Shopify's. You have two routes. Hydrogen, Shopify's headless toolkit, now works inside the framework you already use, including React Router, Next.js, Nuxt, SvelteKit and Astro. Or you skip the toolkit and call the APIs from any stack. Hosting is your choice: Oxygen, Shopify's edge hosting for Hydrogen storefronts, is available at no extra charge on paid Shopify plans, and Shopify says Hydrogen also runs on Vercel, Cloudflare or your own Node server.

Custom or composable (commercetools and similar)

commercetools defines composable commerce as breaking the whole commerce stack into modular components and plugging in "best-of-breed building blocks like cart, checkout and payments." You pick the commerce engine, CMS, search, payments and frontend separately, then integrate them. Fully custom (your own commerce backend) is the far end of the same spectrum.

How much does each option cost to run?

Shopify Plus starts at $2,300 a month on a 3-year term or $2,500 on a 1-year term, with a variable platform fee for more complex, higher-volume businesses. Headless adds the cost of building and running your own frontend on top of that. Composable platforms quote privately, and you pay for every other service you assemble.

The platform fee is rarely the number that decides this. What matters is the engineering you sign up to carry:

• Plus on a theme: the Plus fee covers the main store and 9 expansion stores, hosting and checkout. Your ongoing cost is theme development, apps and optimization.
• Headless Shopify: the same Plus fee, plus a frontend codebase you build, host and maintain. Shopify's own documentation says plainly that "a headless storefront costs more to build and run than a theme" and needs dedicated developer maintenance.
• Composable: commercetools doesn't publish prices; it uses an order-based model quoted by sales. Add separate contracts for CMS, search and anything else you compose, plus the integration work to make them behave as one store.

We won't quote a build budget in a guide. Real numbers depend on catalog, integrations and design scope, and a strategy audit is where we size them for a specific business.

Who has to run the site after launch?

On a theme, marketers and merchandisers run day-to-day changes in the theme editor. Headless moves most changes to developers unless you add a headless CMS. Composable needs a permanent engineering team that owns integrations between every service. Pick the option your team can operate in year three, not the one that demos best.

This is the trade-off most replatform decks skip. Every layer you take ownership of is a layer someone has to upgrade, monitor and debug when a promo breaks at 6 a.m. on launch day. If your E-Commerce team is three marketers and a contract developer, a headless or composable build turns every homepage change into a ticket.

When does Shopify Plus on a theme win?

Plus on a custom theme wins when your requirements fit inside Shopify's checkout, apps and APIs, which covers most DTC and a lot of B2B. You get Shopify-run hosting and checkout, an editor your team can use without developers, and the full app ecosystem. Customization comes from your theme code, Shopify Functions and custom apps.

It is also the option that stays cheapest to change. Plus includes built-in B2B tools, Shopify Functions and checkout customization, so plenty of "we need custom" requirements turn out to be a Function or a custom Shopify app, not a new architecture.

When is headless Shopify worth it?

Headless is worth it when you have a concrete experience a theme can't deliver and engineers who will own the frontend long-term. Shopify's own list includes storefronts existing tools can't support, a stack that doesn't use Liquid, commerce embedded in existing infrastructure, or a CMS-driven storefront. "It's faster" or "it's modern" alone isn't a reason.

Good fits we see: a brand whose site is mostly editorial content already managed in another CMS, commerce inside an existing app or web platform, or a product experience (configurators, heavy interactivity) that fights the theme model. In each case the requirement is specific and the brand has engineering capacity that doesn't disappear after launch.

When does a custom or composable build win?

Composable wins when your commerce model doesn't fit a SaaS platform's assumptions and you can fund a permanent engineering team to own it. Think global enterprises with unusual catalog, pricing or order logic across many brands and channels, where replacing individual services independently is worth the integration overhead.

If that isn't you, composable is an expensive way to rebuild what Shopify Plus includes. Our Shopify Plus vs commercetools comparison walks through the trade-offs feature by feature.

Shopify Plus vs headless vs custom: a decision guide

Match your situation to the line that fits. If two fit, take the simpler option.

• Your team edits the site daily without developers: Shopify Plus on a theme.
• Requirements fit Shopify checkout, apps and Functions: Shopify Plus on a theme.
• Wholesale and DTC from one backend: Shopify Plus on a theme, using its built-in B2B tools.
• A storefront experience a theme genuinely can't deliver, with in-house engineers: headless Shopify (Hydrogen on Oxygen or Vercel, or your own stack).
• Content lives in another CMS or app and commerce has to sit inside it: headless Shopify.
• Several brands or franchise storefronts on one shared backend: Shopify Plus expansion stores, or a multi-storefront platform such as BigCommerce.
• Commerce logic no SaaS platform models, with a permanent engineering team and budget: composable (commercetools or similar).
• You're on headless or a legacy enterprise platform and the team can't keep up with it: move to Shopify Plus on a theme.

What are the biggest migration risks?

The biggest risks are lost search traffic from changed URLs, apps that don't carry over between theme and headless, content your team can no longer edit, and broken analytics. Customer, order and subscription data need their own migration plan. Each is manageable when it's scoped before the build, not discovered at launch.

• URLs and redirects. Every legacy URL needs a mapped 301. This is where SEO equity is lost or kept.
• Apps. Theme app extensions are built to extend Online Store 2.0 themes. Moving to headless means re-integrating those apps through APIs or replacing them; moving back to a theme often lets you drop custom code for native app blocks.
• Content ownership. Decide who edits what after launch, and build the sections or CMS models around those people.
• Data. Customers, order history, subscriptions and any catalog-specific data (fitment, bundles, member pricing) each need a tested migration path.
• Tracking. Rebuild tags and conversion events on the new storefront and check them against platform numbers before cutover.
• Cutover strategy. Running the new store beside the old one for part of the traffic reduces launch-day risk.

What has DYODE seen moving brands between these options?

DYODE has moved brands in both directions: off headless onto Shopify themes, off Salesforce Commerce Cloud and Magento 2 onto Shopify Plus, and onto a shared BigCommerce backend. The pattern is consistent. Brands chose the architecture their team could operate, and moved off the one that needed developers for routine changes.

• [Satechi: headless to a custom Shopify Plus theme](/work/satechi). Satechi's headless frontend had become hard to maintain: content updates needed developers and native Shopify features were difficult to use. DYODE rebuilt it as a custom theme on Shopify's current theme architecture, using Search and Discovery, metafields and sections everywhere. Satechi's team now manages content and merchandising through modular sections without developer support for every change.
• [Glenmorangie: aging headless build to a custom Shopify 2.0 theme](/work/glenmorangie). LVMH's Glenmorangie moved off a headless solution that was becoming obsolete, onto a custom theme with reusable sections, Shopify Markets abroad and ReserveBar for US compliance.
• [Ardbeg: Salesforce Commerce Cloud to Shopify Plus](/work/ardbeg). A phased, market-by-market replatform with France as the pilot, a shared theme across regional stores, and the Ardbeg Committee's Salesforce membership dependencies kept intact.
• [WYZE: Magento 2 to Shopify Plus](/work/wyze). DYODE built a custom theme and launched it as a beta next to the Magento store, with part of the traffic, before the full move.
• [Bandai Namco: one BigCommerce backend](/work/bandai-namco). Fragmented storefronts consolidated onto BigCommerce, with franchise-specific storefronts for properties like Elden Ring, Dragon Ball and PAC-MAN sharing one backend.

If you're weighing a move off a legacy enterprise platform, our comparisons of Shopify Plus against Salesforce Commerce Cloud, Magento and SAP Commerce Cloud cover each platform in detail, and the full comparison index lists the rest.

Final answer: which should you build on?

Build on Shopify Plus with a custom theme unless you can name the requirement it can't meet. Choose headless Shopify when that requirement is real and you have engineers to own the frontend for years. Choose composable only when your commerce model doesn't fit a SaaS platform and you can fund the team to run it.

DYODE is a Shopify Plus and BigCommerce partner in Fullerton, CA. We handle replatforms and custom theme builds and the ongoing development after launch. If you're deciding between these options, tell us what you're running today and we'll come back with a real scope.

About DYODE. Founded in 2016 by former heads of E-Commerce at PacSun and Tilly’s. Shopify Premier Partner.

Add DYODE as a preferred source on Google Google shows you more from the sources you pick.