Almost every founder, ecommerce lead, and CTO eventually hits the same fork in the road: stay on a hosted platform like Shopify, or invest in something custom. It is one of the highest-leverage technology decisions an online store makes, because it quietly sets your cost structure, your ceiling on growth, and how much your team can change without asking a vendor for permission. Get it right and you ship fast with healthy margins; get it wrong and you either over-engineer a store that should have been a five-figure template, or you outgrow a platform that taxes every order you process.
The honest answer in 2026 is that this is not a binary. Ecommerce now lives on a spectrum that runs from standard Shopify, to Shopify Plus, to headless Shopify with Hydrogen, all the way to a fully custom build on something like Next.js Commerce, Medusa, or Saleor. Each step trades simplicity for control. This guide walks the entire spectrum and compares the dimensions that actually decide it, including upfront cost, total cost of ownership, time to launch, design and UX freedom, performance and SEO, scalability, checkout and B2B logic, integrations, and data ownership, then gives you concrete rules, with directional GMV and SKU thresholds, for knowing which side of the line you belong on.
The ecommerce spectrum in 2026: it is not Shopify vs. everything else
The most common mistake in this debate is framing it as a single choice between "Shopify" and "custom." In reality there are at least four distinct tiers, and most of the wrong decisions come from skipping the tier that actually fit. Standard Shopify (Basic, Shopify, and Advanced) is a fully hosted, themed store where Shopify owns the frontend, the checkout, and the infrastructure, and you assemble functionality from the theme and the app store. Shopify Plus is the same core platform with higher limits, more checkout and B2B capability, and a different price tier aimed at high-volume merchants. Both keep you inside Shopify's rendering and hosting.
The other two tiers decouple the storefront from the backend. Headless Shopify keeps Shopify as the commerce engine for catalog, cart, checkout, and payments, but replaces the themed frontend with a custom one, typically built on Shopify's React framework Hydrogen and deployed on its edge host Oxygen, or on a framework like Next.js talking to the Storefront API. Fully custom goes one step further and replaces some or all of the backend too, using an open-source commerce engine such as Medusa (Node.js) or Saleor (Python/GraphQL), an enterprise composable platform like commercetools, or an in-house system, usually paired with a Next.js frontend. As you move right along this spectrum you gain control and lose convenience, and the cost curve tends to bend upward at every step.
Holding these tiers distinct matters because they fail differently. A brand that needs a slightly faster, more branded storefront does not need a fully custom backend; it likely needs headless Shopify. A brand drowning in app subscriptions and transaction fees on tens of millions in GMV is not helped by upgrading from Basic to Advanced; it may need to leave the hosted frontend entirely. The rest of this article is about matching the tier to the actual constraint.
Standard Shopify (Basic / Shopify / Advanced)
Fully hosted and themed; Shopify owns frontend, checkout, and infrastructure. Fastest to launch, lowest upfront cost, most constrained. Best for SMBs and most DTC brands.
Shopify Plus
Same engine, higher limits, native B2B, expanded checkout extensibility, and dedicated support. Aimed at high-GMV merchants; pricing shifts toward a variable model at scale.
Headless Shopify (Hydrogen + Oxygen, or Next.js)
Shopify stays the backend; you build a custom React/Next.js storefront against the Storefront API. Unlocks design and performance freedom while keeping Shopify's checkout and payments.
Fully custom (Next.js Commerce, Medusa, Saleor, commercetools, in-house)
You own the frontend and some or all of the backend. Maximum flexibility, data ownership, and no platform GMV tax, in exchange for the highest upfront and maintenance cost.
Upfront cost: what it actually takes to launch each tier
The four tiers do not just differ in monthly fees; their build cost can differ by one to two orders of magnitude, and that gap is the single biggest filter for most businesses. A standard Shopify store using a paid theme can be live for a few hundred to a few thousand dollars: paid themes are typically a one-time purchase in the low hundreds, and a competent setup with brand styling, core apps, and product import is realistic in the low thousands. This is why Shopify is the default for new and small stores; the upfront commitment is trivial relative to almost any custom alternative.
Custom and headless builds live in a completely different range because you are paying for engineering time, not a subscription. Based on current agency and freelance pricing, a headless storefront sitting on top of an existing commerce API (for example a Hydrogen or Next.js frontend over Shopify's Storefront API) commonly lands in roughly the $20,000 to $75,000 range. Mid-complexity custom builds with bespoke business logic and several integrations run roughly $75,000 to $250,000, and enterprise-grade fully custom platforms with custom backends, B2B, and multi-region needs can run from around $250,000 well past $1,000,000. Senior developer rates in the US generally sit in the rough range of $100 to $250 per hour, which is why scope discipline matters so much.
The takeaway is not that custom is "expensive" in the abstract; it is that the upfront number only makes sense relative to your revenue and the ongoing costs it replaces. Spending $80,000 on a headless build is reckless for a store doing $200,000 a year and entirely rational for one doing $20,000,000 a year that is bleeding margin on transaction fees and app subscriptions. Always read upfront cost together with the total cost of ownership, which is where hosted platforms quietly catch up.
Why custom quotes vary so widely
Two custom ecommerce quotes can differ several-fold for the same-looking store, and the difference is almost always in the parts you cannot see in a screenshot. The biggest cost drivers are the number and complexity of integrations (ERP, PIM, CRM, tax, shipping, payment), the amount of custom business logic (B2B pricing tiers, subscriptions, multi-vendor marketplaces), and the depth of design and interaction work. A storefront that simply reads products and runs a standard cart is cheap; one that synchronizes inventory with an ERP like NetSuite in real time and enforces contract pricing per customer is not.
Team composition is the other lever. The same scope can cost very differently across an offshore team, a freelancer, a boutique studio, and a large enterprise agency, and the cheapest hourly rate is frequently the most expensive total once rework is counted. This is also where a focused build partner earns its keep, by scoping carefully, reusing proven components, and not charging you to reinvent things that open-source starters like Next.js Commerce or Medusa already provide for free.
Total cost of ownership: where Shopify's real bill shows up
Upfront cost flatters Shopify and frightens people away from custom, but total cost of ownership (TCO) tells the more honest story, especially as you scale. Shopify's standard plans are inexpensive monthly: per Shopify's published pricing, Basic is roughly $39/month, the mid Shopify plan around $105/month, and Advanced around $399/month, with discounts on annual billing. The fees that actually move the needle are the ones tied to volume: payment processing on every order, plus an additional transaction fee if you do not use Shopify Payments (roughly 2.0% on Basic, 1.0% on the mid plan, and 0.5% on Advanced for third-party gateways), and a long tail of app subscriptions.
Apps are the most underestimated line in Shopify TCO. Many stores run roughly 10 to 30 apps, and monthly app spend commonly ranges from about $50 to $200 for small stores up to $200 to $1,000 or more for established ones, with larger Plus merchants often spending several thousand dollars a month. Critically, many of the most important apps, such as Klaviyo for email, Recharge for subscriptions, and various search and loyalty tools, price on a percentage of revenue or order volume, so the bill grows roughly as your business does. Functionality that costs several hundred to a thousand dollars a month indefinitely in apps is often the same functionality a custom build pays for once.
Custom and headless builds invert this curve. There is no GMV tax and no per-app subscription creep, but you take on hosting, monitoring, security, and ongoing engineering. A reasonable planning rule is that maintenance runs around 15% to 25% of the initial build cost per year. So the real question is not "which is cheaper" but "at what revenue does Shopify's volume-based bill exceed a custom build's fixed-plus-maintenance bill," and for most SMBs that crossover never arrives, while for high-GMV brands it can arrive clearly.
Shopify recurring costs
Platform fee (roughly $39–$399/month on standard plans), payment processing on every order, third-party gateway transaction fees (about 0.5%–2.0% on standard plans), and app subscriptions that often scale with revenue.
Shopify Plus recurring costs
A reported starting platform fee in the low thousands per month on a multi-year commitment, with a variable revenue-based component reported to apply for very high-volume merchants (subject to a cap), plus the same app and processing layers.
Custom / headless recurring costs
Cloud hosting (e.g., Vercel, AWS), observability and security tooling, and ongoing engineering, typically planned at roughly 15%–25% of build cost per year. No GMV tax, no per-feature subscription stacking.
The crossover
Below roughly mid-six-figure annual GMV, Shopify's variable costs are usually cheaper than custom maintenance. Well into seven and eight figures, transaction fees and app spend can eclipse what a custom build would cost to run.
Time to launch, design freedom, and the developer experience
Speed to market is where Shopify is genuinely hard to beat, and it should weigh heavily for anyone who needs revenue now rather than a perfect platform later. A standard Shopify store can be merchandised and live in days to a few weeks because the hardest parts, including checkout, payments, hosting, PCI compliance, and security patching, are already built and maintained for you. That is real engineering value you are not paying salaries for, and for a new brand validating demand, shipping in two weeks usually beats shipping a flawless custom platform in six months.
The cost of that speed is design and UX freedom inside the constraints of themes and Shopify's checkout. Standard Shopify themes are flexible enough for most brands, but the checkout in particular is owned by Shopify; you customize it through Checkout Extensibility, including Checkout UI Extensions, Shopify Functions, and branding APIs, rather than editing it freely, since the older checkout.liquid customization was deprecated. That model is deliberately upgrade-safe, which is good for stability and limiting for any brand whose differentiation depends on a non-standard purchase flow. You work within defined extension points, not a blank canvas.
Headless and custom flip this trade. With Hydrogen on Oxygen, or Next.js against the Storefront API, the frontend is entirely yours: every interaction, animation, layout, and content model is under your control, and developers work in modern React tooling with git-based deploys and per-branch previews rather than theme editors. The price is time and talent. You cannot launch headless in a weekend, and you need engineers who can build and maintain it. For teams that have those engineers, the developer experience is markedly better; for teams that do not, it is a liability dressed up as flexibility.
Performance, Core Web Vitals, and SEO
Performance is one of the strongest arguments for going headless, but it is routinely overstated, so it is worth being precise. Google's Core Web Vitals set concrete targets: Largest Contentful Paint (LCP) under 2.5 seconds, Interaction to Next Paint (INP) under 200 milliseconds, and Cumulative Layout Shift (CLS) under 0.1 (INP replaced First Input Delay as a Core Web Vital in 2024). These are part of Google's page-experience signals, and there is consistent evidence linking speed to revenue. Google and Deloitte's "Milliseconds Make Millions" study reported that a 0.1-second improvement in mobile site speed was associated with a lift of roughly 8% in retail conversions, and Portent's research has found sites loading in around one second converting meaningfully higher than those loading in five.
Headless architectures can hit those targets more easily because they use modern frameworks, edge rendering, and a frontend you fully control. Hydrogen on Oxygen renders server-side across a global edge network, and a well-built Next.js storefront can be tuned aggressively for LCP and INP. The important caveat is that headless is not automatically faster. A poorly engineered headless site, bloated with client-side JavaScript and unoptimized images, can easily perform worse than a clean, well-optimized standard Shopify theme. Performance is an outcome of engineering discipline, not of the word "headless" on an architecture diagram.
On SEO, the platform choice usually matters less than people hope and the execution matters more. Core Web Vitals are a real ranking input but one of many, and content relevance still does much of the heavy lifting. Standard Shopify is perfectly capable of ranking; its main SEO friction points are limited control over URL structure and some technical edges. Headless gives you near-total control over rendering, metadata, structured data, and internal linking, which is an advantage only if you actually use it well. For most stores, fixing content and information architecture beats re-platforming for SEO; for large catalogs where milliseconds and technical control compound, headless can be a genuine edge.
When Shopify starts costing more than it saves: scale, GMV, and complexity
Every hosted platform has a zone where its convenience stops paying for itself, and recognizing that zone is much of the point of this decision. The signals are rarely a single dramatic event; they accumulate. You start stacking apps to cover gaps and paying a percentage of revenue on several of them. You hit the limits of theme and checkout customization on a flow that is core to your brand. Your transaction fees on third-party gateways become a line item finance asks about. Your catalog or traffic stresses the platform, and "just add another app" becomes the answer to everything. Individually these are tolerable; together they signal you may be paying a tax for flexibility you have outgrown.
The clearest way to know is to model it. Add up your Shopify platform fee, your blended transaction and processing fees on actual GMV, and your full monthly app stack, then annualize it and compare against the all-in run cost of a custom or headless alternative (build amortized plus 15%–25% maintenance). For an SMB the hosted number usually wins comfortably and the conversation should end there. For a high-GMV brand the volume-based fees and app subscriptions can clearly exceed what it would cost to build and run something custom, at which point staying hosted may be the expensive choice rather than the safe one.
Complexity is the other trigger, independent of revenue. If your business depends on logic Shopify constrains, such as intricate B2B approval and quoting workflows, deeply custom pricing, a non-standard checkout, real-time two-way ERP sync, or a marketplace with many sellers, you can hit the ceiling well before the dollar math alone would push you off. In those cases the question is not whether you can afford to leave, but whether you can afford to keep contorting your business to fit a platform that was not built for it.
Custom checkout and B2B logic
Checkout and B2B are where the platform ceiling shows up first for many growing brands. Shopify Plus has materially improved both: native B2B brings company profiles, customer-specific catalogs and pricing, payment terms, and quantity rules, and you can run B2B and DTC from one store. Checkout Extensibility lets you customize discount, shipping, and payment logic, plus validation, through Shopify Functions and UI Extensions in an upgrade-safe way. For a large share of merchants, that is genuinely enough, and going custom to get it would be over-engineering.
The ceiling appears when your requirements exceed Shopify's defined extension points. Very complex B2B, such as multi-step approval chains, sophisticated quoting, deeply conditional contract pricing, or tight ERP-driven workflows, can outgrow native capabilities and even what apps can patch. The same is true of a checkout whose flow is itself part of the product. Because you customize within Shopify's model rather than owning the checkout, there are things you simply cannot do. A custom or headless build removes that constraint and lets you own the rules end to end, which is the right move only when those rules are genuinely central to how you sell.
Integrations, ERP, and operational fit
Integration depth quietly decides more re-platforming projects than design ever does. Shopify has a vast app and partner ecosystem, and for common needs, such as email, reviews, shipping, accounting, and basic ERP connectors, there is almost always an off-the-shelf option that works well and installs quickly. For the majority of stores this breadth is a decisive advantage over building connectors yourself, and it is a reason to stay hosted longer than your ego might want to.
The friction starts with deep, real-time, two-way integration into systems of record, such as enterprise ERPs like NetSuite or SAP, custom PIMs, and warehouse or OMS platforms, where pre-built connectors are often shallow, brittle, or simply absent. When your operation depends on inventory, pricing, and order data staying in lockstep across systems in real time, you are effectively doing custom integration work regardless of platform, and a custom or headless architecture gives you the control to do it properly. The decision then becomes less "do we want custom" and more "our operational reality already requires custom-grade integration, so which foundation makes that sane."
Data ownership and lock-in: the cost you only feel later
Data ownership and platform lock-in are the dimensions teams discount at launch and regret at scale, because they are largely invisible until you try to leave. On Shopify you operate inside Shopify's ecosystem: your storefront rendering, your checkout, and much of your operational tooling are Shopify's, and while you can export core data, your customizations, theme work, app configurations, and checkout logic do not travel with you. The platform is excellent, but it is a platform you rent, and the switching cost compounds the deeper you build into it.
Custom and open-source stacks invert that relationship. With Medusa or Saleor you self-host (both run on PostgreSQL, with Medusa in Node/TypeScript and Saleor in Python with a GraphQL-first API), and you own the code, the database, and the architecture outright. With an enterprise composable approach in the spirit of MACH (microservices, API-first, cloud-native, headless), you assemble best-of-breed components you control. The upside is durable: no GMV tax, no vendor dictating your roadmap, and the freedom to swap any layer. Gartner, which popularized the term "composable commerce," has argued this modularity lets organizations ship new capabilities faster, though that benefit assumes the engineering maturity to manage the added complexity.
The right way to weigh lock-in is by time horizon and strategic centrality. If ecommerce is one channel among many and you want to move fast, renting Shopify's excellence is a feature, not a flaw; lock-in is a fair price for not maintaining a platform. If ecommerce is the core of the business, you expect to scale for years, and your differentiation lives in the software itself, then owning your data and stack stops being a luxury and becomes the point. There is no universally correct answer here, only a correct answer for your horizon.
The decision: clear rules for choosing Shopify vs. going custom
Stripped of nuance, the rule is simple: most stores should be on Shopify, and a meaningful minority should go custom or headless, and the trouble comes from people on the wrong side of that line in either direction. Shopify fits the overwhelming majority of SMBs and DTC brands because it converts capital you do not have into a working store you can iterate on, with the hard infrastructure handled. Custom and headless tend to win at scale, at high complexity, or when the software is itself the differentiator. The thresholds below are directional, not laws; your numbers and constraints decide, but they are a reliable starting frame.
Use revenue, catalog size, and complexity together rather than any one alone. A modest-GMV store with unusual B2B requirements may need custom; a high-GMV store with a totally standard flow may happily stay on Plus for years. The mistake is treating the decision as a status symbol, as in "real brands build custom," instead of an economic and operational calculation. Run the TCO model, weigh the complexity and lock-in honestly, and let the answer be boring if boring is correct.
This is also where a build partner who is genuinely neutral on the outcome matters. A studio that only builds custom will find a reason you need custom; a Shopify-only shop will keep you on Shopify past the point it serves you. The useful partner is the one that will talk you out of an expensive build you do not need, and is also capable of executing the headless or fully custom build properly when you do.
Choose Shopify (standard or Plus) if…
Choose a hosted Shopify plan if you are an SMB or DTC brand, want to launch in days to weeks on a budget measured in hundreds to low thousands, and your requirements are well covered by themes, the app ecosystem, and Shopify's checkout. As a rough frame, standard plans fit comfortably from launch up into the low millions in annual GMV with a manageable app stack, and Shopify Plus extends that into the higher seven and eight figures while adding native B2B and deeper checkout extensibility. If your differentiation is your product, brand, and marketing rather than novel software, and your B2B and integration needs fit native capability or proven apps, staying on Shopify is almost always the right call, and re-platforming would be solving a problem you do not have.
Go headless or fully custom if…
Go headless or custom when at least one of three conditions is clearly true. The first is scale, where Shopify's variable costs (transaction fees plus a revenue-scaling app stack) start to exceed a custom build's amortized plus maintenance cost, often in the high seven figures of GMV and up. The second is complexity that exceeds Shopify's extension points, such as intricate B2B or quoting logic, a checkout that is core to the product, large or unusual catalogs, marketplace models, or real-time two-way ERP and OMS sync. The third is strategy, where data ownership, freedom from lock-in, and software as a differentiator justify the investment. A common pragmatic path is headless Shopify first, keeping Shopify's checkout and payments while owning a custom Next.js or Hydrogen storefront, and reserving a fully custom backend on Medusa, Saleor, or commercetools for when the backend itself is the constraint.
How NixMar approaches the choice
NixMar works across the entire spectrum on purpose, because the right answer changes per client and we would rather build the correct thing than the most expensive one. For many stores that means shipping a clean, fast Shopify or Shopify Plus build quickly: a properly merchandised store with a disciplined app stack and the checkout and B2B capabilities Plus provides, live in weeks rather than quarters. When a brand outgrows that, we build headless storefronts on Hydrogen and Oxygen or on Next.js against the Storefront API, keeping Shopify's checkout and payments while giving the brand full control of design, performance, and Core Web Vitals.
When the backend itself is the limit, we build custom commerce on modern foundations: Next.js on the frontend, with engines like Medusa or Saleor, or bespoke services where the logic demands it, wired into the ERP, PIM, and payment systems the business actually runs on. Because we build on both sides of the line, our recommendation is not predetermined by what we are able to sell. We will run the TCO and complexity math with you and say plainly when Shopify is the smart, margin-friendly choice, and architect a custom platform that lasts when you have genuinely outgrown the hosted model.
Frequently asked questions
Is Shopify or custom ecommerce cheaper overall in 2026?
For most small and mid-sized stores, Shopify is cheaper overall. A standard Shopify store can launch for a few hundred to a few thousand dollars and costs roughly $39 to $399 per month per Shopify's pricing, plus payment processing and apps. A custom or headless build typically starts around $20,000 to $75,000 and rises to $250,000 or more for enterprise scope, plus ongoing maintenance of roughly 15% to 25% of the build cost per year. Custom usually becomes cheaper only at high GMV, where Shopify's transaction fees and revenue-scaling app subscriptions can exceed the largely fixed cost of running a custom platform. In short, Shopify tends to win on total cost for most SMBs, and custom tends to win mainly at large scale or high complexity.
How much does Shopify Plus cost compared to standard Shopify?
Per Shopify's published pricing, standard plans cost roughly $39 per month for Basic, around $105 per month for the mid Shopify plan, and around $399 per month for Advanced, with discounts on annual billing. Shopify Plus is sold as an enterprise tier with a reported starting platform fee in the low thousands of dollars per month, usually on a multi-year commitment, and a variable revenue-based component reported to apply for very high-volume merchants (subject to a cap); exact Plus pricing is negotiated and not publicly listed. Plus also reduces third-party gateway transaction fees and adds native B2B and deeper checkout extensibility. The jump from Advanced to Plus is large, so it is generally justified by GMV scale, B2B needs, or checkout requirements rather than by a single feature.
What is headless Shopify, and how is it different from a fully custom build?
Headless Shopify keeps Shopify as the commerce backend (catalog, cart, checkout, and payments) but replaces the themed storefront with a custom frontend, typically built with Shopify's Hydrogen framework on its Oxygen edge host or with Next.js talking to the Storefront API. A fully custom build goes further and replaces some or all of the backend too, using an open-source engine like Medusa or Saleor, an enterprise composable platform, or in-house services. The practical difference is that headless gives you full design and performance control while still relying on Shopify's proven checkout and infrastructure, whereas fully custom also gives you control over the backend logic and data. Headless is often the pragmatic middle step before committing to a fully custom backend.
When should a store move off Shopify to a custom platform?
A store should consider moving off Shopify when at least one of three conditions is clearly true. First is scale: when transaction fees plus a revenue-scaling app stack start to exceed what a custom build would cost to run, which often appears in the high seven figures of annual GMV and above. Second is complexity: when requirements exceed Shopify's extension points, such as intricate B2B and quoting workflows, a checkout that is itself part of the product, very large or unusual catalogs, marketplace models, or real-time two-way ERP and OMS integration. Third is strategy: when data ownership, freedom from vendor lock-in, or software as a core differentiator justifies owning the stack. If none of these apply, staying on Shopify is usually the smarter, more cost-effective choice.
Does headless or custom ecommerce rank better on Google than Shopify?
Not automatically. Core Web Vitals (LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1) are part of Google's page-experience signals, and headless builds can hit them more easily through modern frameworks and edge rendering. However, a poorly engineered headless site can perform worse than a well-optimized standard Shopify theme, so speed is an outcome of engineering quality rather than of the architecture label. More importantly, Core Web Vitals are one ranking input among many, and content relevance still does much of the work. Standard Shopify ranks perfectly well for most stores; headless mainly helps SEO when you actually exploit its full control over rendering, structure, and metadata, which matters most for large catalogs.
What are the leading custom and open-source ecommerce platforms in 2026?
For the storefront, Next.js is a dominant choice, and Vercel's Next.js Commerce is a free, production-ready starter that works with Shopify and other backends. For the commerce backend, two widely used open-source options are Medusa, built in Node.js and TypeScript on PostgreSQL with a modular architecture, and Saleor, built in Python with a GraphQL-first API, also on PostgreSQL. For enterprise composable needs, commercetools is a well-known API-first MACH platform, and Shopify's own Hydrogen plus Oxygen is a strong headless path that keeps Shopify as the backend. The right pick depends on your team's stack expertise and whether you need to own the backend or only the frontend.
Can Shopify Plus handle complex B2B and custom checkout requirements?
Shopify Plus handles a large share of B2B and checkout needs natively. Its B2B features include company profiles, customer-specific catalogs and pricing, payment terms, and quantity rules, and you can run B2B and DTC from one store. Checkout customization works through Checkout Extensibility (Checkout UI Extensions, Shopify Functions, and branding APIs) since the older checkout.liquid approach was deprecated, which keeps customizations upgrade-safe but constrained to defined extension points. The ceiling appears with very complex requirements such as multi-step approval chains, sophisticated quoting, deeply conditional contract pricing, or a checkout flow that is central to the product. When requirements exceed those extension points, a custom or headless build that owns the rules end to end becomes the better fit.
What do data ownership and lock-in really mean when choosing an ecommerce platform?
On Shopify you operate inside Shopify's ecosystem: the storefront rendering, the checkout, and much of the operational tooling belong to Shopify, and while you can export core data like products and customers, your theme work, app configurations, and checkout logic do not transfer if you leave. With custom and open-source stacks such as Medusa or Saleor you self-host and own the code, the database, and the architecture outright, and composable approaches let you swap individual components. The practical impact is switching cost and roadmap control: renting Shopify's excellence is a sensible trade when ecommerce is one channel and speed matters, while owning your stack matters more when ecommerce is the core business, you plan to scale for years, and your differentiation lives in the software itself.
The right answer is the one your numbers and roadmap support
The Shopify-versus-custom decision is not a test of ambition; it is an economic and operational calculation. Most stores should be on Shopify or Shopify Plus because the platform turns capital you may not have into a fast, reliable store and handles the hardest infrastructure for you. A real minority, including high-GMV brands, businesses with complexity that exceeds Shopify's extension points, and companies where the software is the differentiator, are better served going headless or fully custom, and for them staying hosted can be the expensive choice rather than the safe one. The spectrum exists precisely so you can match the tier to the constraint instead of forcing a binary.
If you are weighing this for a real store, the most valuable next step is to put numbers on it: model your true Shopify total cost of ownership against the all-in cost of a headless or custom build, then weigh complexity, integration depth, and lock-in over your actual time horizon. NixMar builds across the whole spectrum, from clean Shopify and Plus stores to headless Hydrogen and Next.js storefronts and fully custom platforms on engines like Medusa and Saleor, so we have no incentive to push you toward the most expensive option. We will help you run the math and build whichever foundation is genuinely right.
