Custom & Headless eCommerce PlatformsWhen SaaS Hits the Ceiling, Custom Takes Over
Headless storefronts, MACH architectures, and composable commerce stacks - built on Next.js, Medusa.js, commercetools, Shopify Storefront API, BigCommerce Catalyst, and headless CMSes. Shipped since 2012.
Example stack. Each part becomes a swappable module, connected by APIs.
- Next.js
- Medusa.js
- commercetools
- Shopify Storefront API
- BigCommerce Catalyst
- Headless CMS
Trusted by 400+ Brands · Certified Partners
Years in eCommerce
Of results, scale, and quality at the enterprise level.
Expert Team
Specialists across SEO, AI SEO, PPC, design, dev, and strategy.
US Core + Global Talent
US core team for clear communication; vetted global specialists for international client work.
Reputation Score
Rated 4.9/5 across 100+ verified client reviews.
Reviewed by the 1Digital® Development TeamLast updated:
The honest answer
The Platform-Tier Question, Answered Honestly
Most merchants don't need custom. Shopify Plus, BigCommerce, and Adobe Commerce will out-ship a custom rebuild on TCO and speed-to-market nine times out of ten.
But when SaaS hits its ceiling - checkout extensibility caps, multi-channel commerce, B2B + B2C in one cart, content-led DTC, or sub-1.5s LCP as a competitive moat - custom, headless, and composable architectures become the right answer.
This page is the platform-choice hub
- If you already know you're building custom, jump to custom development or custom design.
- WCAG 2.2 AA compliance is engineered into every storefront - see ADA compliance.
- Strategy-led engagements start at eCommerce strategy services, with downstream conversion optimization and digital marketing programs that compound the platform investment.
- If you're preparing for agentic surfaces (ChatGPT Shopping, Perplexity Shop, Gemini), see agentic commerce.
Magnitude chart · which tier fits
Magnitude 1
SaaS platform
Out-ships a custom rebuild on TCO and speed-to-market nine times out of ten.
Magnitude 2
Hybrid
Keep the SaaS backbone, replace the storefront with custom.
Magnitude 3
Custom and composable
When SaaS hits its ceiling. Microservices, API-first, cloud-native, headless.
Custom platforms, step by step
Move past the ceiling without losing ground
When a hosted platform can no longer handle your catalog, pricing or integrations, a headless or custom build takes over. We move your products, customers, orders and URLs across carefully, so the new stack starts with everything the old one earned.
- ›Data and URLs mapped before anything moves
- ›Integrations rebuilt for the new stack
- ›Rankings protected through launch
Point the telescope first
Read the store before you pick the stack
Custom is the right call for some stores and the wrong one for most. These are the signals we read in discovery, both ways.
When custom is the right call
The Six Signals
- SaaS limits are blocking revenue.Checkout extensibility caps, theme bloat, app conflicts, or platform fee creep are now a measurable drag on conversion, AOV, or margin.
- Multi-channel commerce.Web + native app + in-store + marketplace + agentic surfaces (ChatGPT, Perplexity) all need the same catalog, pricing, inventory, and identity layer.
- B2B + B2C in one storefront.Tiered pricing, account-gated catalogs, net terms, quote-to-order, and consumer checkout - all under one brand, one cart, one identity.
- Catalog or pricing logic the platform can't model.Configurators, bundles with cross-vendor inventory, dynamic kits, region-specific tax/duty rules, marketplace seller payouts, contract pricing.
- Content-heavy DTC + editorial.Brands where the story is the product. Headless CMS + commerce engine lets editors ship daily without touching the commerce stack.
- Performance is a competitive moat.Sub-1.5s LCP at the 75th percentile, INP under 100ms, edge-personalized - measurable revenue lift over the SaaS baseline.
When it isn't
When to Skip Custom
- You're under $5M GMV with a standard catalog.Shopify or BigCommerce on a strong theme will out-ship custom on speed-to-market, TCO, and team velocity.
- You don't have product engineering capacity.Composable stacks need owners. If there is no internal eng team (or budgeted partner retainer) to steward the build, SaaS is the safer bet.
- Your differentiator is merchandising, not the storefront.If the moat is brand, supply chain, or community, a faster SaaS launch beats a slower custom one - every quarter the rebuild delays is revenue lost.
- Your roadmap is uncertain.Custom amplifies your decisions - good and bad. Lock product strategy first; build the platform around the proven model.
Not the right fit? Start with our SaaS platform hub. We'll match you to the right backend before you spend a dollar on custom.
Headless & composable stacks we ship
The MACH Toolkit
Microservices, API-first, Cloud-native, Headless. Pick the commerce engine, then compose the rest.
- M
- Microservices
- A
- API-first
- C
- Cloud-native
- H
- Headless
Next.js + Shopify Storefront API
Shopify as the commerce engine, Next.js (Vercel) as the storefront. Hydrogen + Oxygen when you want first-party tooling.
Next.js + BigCommerce GraphQL Storefront API
Open SaaS backend, fully custom front-end. BigCommerce Catalyst as the reference architecture for headless on BC.
Medusa.js (self-hosted, Node + TypeScript)
Open-source headless commerce engine. Maximum control, plugin-based, runs on AWS / GCP / Azure / Vercel.
commercetools (enterprise MACH)
API-first commerce platform for global enterprise - multi-currency, multi-channel, B2B + B2C in one platform.
Vendure (open-source, TypeScript + GraphQL)
Headless commerce framework purpose-built for complex B2B and multi-vendor catalogs.
Headless WordPress (Faust + WPGraphQL)
WordPress as a content engine behind a Next.js storefront - for editorial-led DTC brands with deep content libraries.
Headless CMS layer
Content Engines for Composable Stacks
The CMS is the half of the stack editors live in. Pick it carefully - it ships content velocity for the next five years.
Headless CMS + commerce engine lets editors ship daily without touching the commerce stack.
How we build
From SaaS Ceiling to Composable Launch
Six phases. Feature-flagged throughout. Revenue keeps running on the legacy stack until parity is proven.
- 01
Discovery & fit scorecard
Quantify the SaaS ceiling: where it blocks revenue today, what custom unlocks, TCO over 3 years vs SaaS baseline. Honest no-go is on the table.
- 02
Architecture
Commerce engine, CMS, search, identity, payments, observability, CI/CD. Composability matrix with swap costs documented for every vendor.
- 03
MVP build
Ship a real storefront against a real catalog in 8–14 weeks. Feature-flagged, behind a canary domain, no production risk.
- 04
Iterate behind flags
Migrate categories, customer cohorts, or geographies progressively. Revenue keeps flowing through the legacy stack until parity is proven.
- 05
Cutover & launch
URL mapping, 301s, schema parity, AI-crawler accessibility (llms.txt, GPTBot, ClaudeBot), analytics baselines, CWV monitoring.
- 06
Steward & compound
SLA-backed retainer: dependency upgrades, vendor API bumps, CRO, SEO, agentic-commerce readiness. Composable stacks decay without active care.
What the shopper touchesCustom storefront
Next.js · Hydrogen · Catalyst · PWA
SaaS backbone
- Checkout
- Payments
- Tax
- PCI
- Inventory
Hybrid: SaaS engine + custom storefront
The Highest-Leverage Architecture for Most Brands
Keep the SaaS backbone (checkout, payments, tax, PCI, inventory). Replace the storefront with custom. This is the sweet spot for most mid-market and enterprise brands - 80% of the custom upside at 30% of the TCO.
Shopify Plus + headless storefront
Shopify owns checkout, inventory, payments, and tax - Next.js + Hydrogen owns the customer-facing experience. Best of SaaS reliability and custom UX.
BigCommerce + Catalyst
Open SaaS commerce engine behind a fully composable Next.js storefront with Makeswift visual editing - ideal mid-market hybrid.
Adobe Commerce + PWA Studio
Magento's catalog depth and B2B price-list engine, decoupled from a React PWA storefront for performance and re-platform optionality.
Request a proposal
Tell us where SaaS is breaking
Share your current platform, the constraint you've hit, and your roadmap. A senior architect replies within one business day with a scoped estimate, candidate stacks, and a draft phase plan.
Observation request
- Your current platform
- The constraint you've hit
- Your roadmap
Custom Platforms - FAQ
How much does a custom or headless commerce build cost vs a SaaS theme?
Every custom and composable build is scoped to the project, so we don't publish fixed price bands. The cost is driven by which commerce engine you pick, the depth of B2B / multi-region / multi-channel requirements, the number of ERP / OMS / PIM integrations, and whether you're rebuilding the storefront only or the engine too. Contact us with your current platform, the constraint you've hit, and your roadmap - a senior architect replies within one business day with a scoped estimate.
How long does a custom or composable build take to launch?
Headless storefronts over an existing SaaS backend ship in 12–20 weeks. Composable / MACH builds with new microservices, search, and CMS layers run 20–36+ weeks. We ship an MVP first, then iterate behind feature flags so revenue is never paused for the rebuild.
Who owns the code on a custom build?
You do. Repos, infra, vendor accounts, CI/CD, and CMS workspaces are provisioned in your name. No proprietary lock-in to the agency, no recurring license for the storefront layer, and a clean handoff to in-house teams whenever you are ready.
Does headless or MACH create vendor lock-in?
Less than monolithic SaaS, but it is real. Each vendor (commerce engine, CMS, search, payments) becomes a swappable module - but every swap has a real migration cost. The mitigation is API-first contracts, anti-corruption layers between vendors, and a documented composability matrix we deliver with the build.
Where do custom storefronts get hosted?
Vercel and Netlify for Next.js storefronts (edge-rendered, ISR, image optimization). Shopify Oxygen for Hydrogen builds. AWS, GCP, or Azure for self-hosted Medusa.js / Vendure backends. We provision in your cloud account so cost, observability, and security policy stay under your control.
What does ongoing maintenance look like after launch?
Composable stacks need active stewardship: dependency upgrades, vendor API version bumps, performance budgets, observability, and a roadmap for the swappable layers. Our retainer covers SLA-backed support, CRO, SEO, and continuous iteration so the platform compounds value rather than decaying.
When does headless or composable actually beat staying on a SaaS platform?
When you need (a) UX or merchandising freedom that the SaaS theme architecture caps, (b) multi-channel / multi-region orchestration the platform doesn't model natively, (c) Core Web Vitals targets the platform's stock infrastructure can't deliver, or (d) B2B / B2B2C / marketplace workflows that don't fit native primitives. If none of those apply, staying on Shopify, BigCommerce, or Magento is the honest answer.
What's MACH and is it right for us?
MACH = Microservices, API-first, Cloud-native, Headless. It's the architecture philosophy behind commercetools, Medusa.js, and similar best-of-breed composable stacks. It's right when your roadmap genuinely needs the flexibility - not when a clean Hydrogen or Catalyst build on top of Shopify / BigCommerce would serve the business just as well at a fraction of the cost.
What stacks do you build on?
Next.js (App Router) + Shopify Storefront API, Next.js + BigCommerce Catalyst (Makeswift), Hydrogen + Oxygen on Shopify Plus, Medusa.js (open-source headless commerce), commercetools (enterprise MACH), and custom WordPress + WPGraphQL or WooCommerce + Next.js setups. We choose based on your data model, integrations, and team capability - not framework fashion.
Can you migrate from a SaaS platform to headless or composable?
Yes. SEO-safe URL mapping, 301 redirect deployment, schema graph preservation, data parity QA, and a staged cutover are the standard playbook. We've migrated Shopify, BigCommerce, Magento, and WooCommerce stores to headless and composable architectures - and we'll tell you when the migration isn't worth the cost.