Skip to main content
USA-Based Digital Agency
(530) 553-8883
WebVello

Platform Comparison

Shopify vs Custom Website: Rails, Walls, and the Headless Middle

Commerce raises the stakes of every platform question: downtime is revenue, checkout is sacred, and the middle path — custom storefront on Shopify’s engine — deserves the airtime most comparisons deny it. Updated August 2026.

Illustration of a train on fixed rails beside an open road under construction, with a hybrid vehicle bridging both

The short version

This decision has three answers, not two. Shopify’s rails for most merchants, most of the time. Full custom for the few whose model the rails cannot carry. And — the resolution many growing brands actually land on — headless: custom experience on Shopify’s engine, keeping checkout, compliance, and ops where they’re strongest.

Stay on Shopify’s rails if…

  • Standard retail flows serve the model (they usually do)
  • Operations and compliance should stay invisible
  • Theme-level experience is differentiation enough

Go custom (full or headless) if…

  • Experience ambition exceeds what themes express
  • Business logic strains the rails (B2B, configurators, regulated flows)
  • Fee economics at your volume justify owning infrastructure
  • Content/SEO architecture is a primary growth engine

At a glance: ten dimensions

DimensionShopifyCustom buildEdge
Time to sellingDays: catalog in, payments on, live.Months: commerce is the hardest thing to build well from scratch.Shopify
CheckoutContinuously optimized by a company whose revenue depends on it; deep customization Plus-gated.Entirely yours — every field, flow, and rule — and entirely your liability to secure.Depends
Payments & compliancePCI scope, fraud tooling, and payment rails handled.Processor integrations are routine; the compliance burden shifts to your architecture.Shopify
Storefront experience ceilingTheme architecture is flexible; truly bespoke experiences fight the mold.Unbounded: the storefront is whatever you can design and engineer.Custom
Business-logic freedomApps and Functions within the rails; exotic models (complex B2B, configurators, regulated flows) strain.First-class: your pricing, your rules, your integrations.Custom
OperationsSpikes, uptime, patching: invisible.Yours — commerce ops are unforgiving, and downtime is measured in revenue.Shopify
Fees at scalePercentage economics forever ($39–$399 base + per-sale rates, verified Aug 2026).Raw processing only; infrastructure costs flatten as volume grows.Custom
Content & SEO architectureServiceable; programmatic and editorial scale are not the platform’s shape.Full control — the same engineering surface as any custom build.Custom
Performance (field data)78% of desktop origins passed CWV (Nov 2025) — a strong managed baseline.Your ceiling and floor; lean custom stacks measure best-in-class, careless ones don’t.Depends
Risk profilePlatform dependence: policies, pricing, and rails can change under you.Execution dependence: a bad build is worse than any platform.Depends

Tally: Shopify 3 · Custom 4 · Depends 3 — with commerce’s stakes making every “depends” heavier than usual (Shopify's published pricing · WebVitals.tools platform benchmarks (CrUX + HTTP Archive)).

The headless middle: custom experience, Shopify engine

The dichotomy is false for a growing class of brands, because Shopify itself sells the escape hatch: the Shopify's Storefront API documentation exposes catalog, cart, and checkout to any frontend you build. The architecture splits the stack at its natural seam — Shopify keeps what platforms do best (checkout conversion, PCI, fraud tooling, spike-proof ops) while your custom frontend owns what platforms do worst: bespoke experience, content architecture at scale, and a performance ceiling in your hands rather than a theme’s.

The honest price list: you are building and operating a storefront application — engineering up front, a development relationship forever, and the seam (cart state, previews, edge caching) is real work. Standard-stack talent is plentiful (React at 46.9% of developers, Stack Overflow Developer Survey, 2025 edition), and the conversion stakes justify care in both directions — the canonical Deloitte Digital & Google, “Milliseconds Make Millions” (2020 study, 37 brands, 30M mobile sessions) measured revenue moving with tenths of a second. Below the experience-ambition threshold, headless is expensive theater; above it, it’s the only architecture that doesn’t force a false choice. The checkout wall stays regardless: Shopify Help Center, checkout customization documentation documents deep customization as Plus territory even headless.

Shopify vs custom: FAQ

Including the headless questions most comparisons skip.

At three documented walls. Checkout: standard plans customize branding only, and even Plus's Checkout Extensibility operates within platform rails — regulated flows, complex B2B pricing, and exotic funnels strain or exceed them. Experience: truly bespoke storefronts (configurators, immersive product experiences, unconventional browsing models) fight the theme architecture. Economics: percentage fees at high volume eventually exceed the cost of owning infrastructure. One wall reached is a signal; two is a plan; none — which describes most merchants — means Shopify remains the right answer indefinitely.
The middle path this comparison actually resolves to for many growing brands: Shopify remains the commerce engine — catalog, cart, checkout, payments, admin — while a custom frontend (typically Next.js-class) consumes it via Shopify's Storefront API and owns the entire customer experience. You keep the rails where they're strongest (checkout, compliance, ops) and take control where platforms are weakest (experience, content architecture, performance ceiling). The cost is real engineering: you're building and maintaining a storefront application. It's the right answer when experience ambition exceeds themes but replacing checkout and commerce ops would be reckless.
We don't print fake numbers: custom commerce spans from focused headless storefronts to full platform builds, and scope drives everything. The structural comparison: Shopify's verified pricing runs $39–$399/month plus per-sale rates (2.9%→2.5% + 30¢ online) — costs that scale with revenue forever. Custom concentrates cost in engineering up front, then charges raw processing plus infrastructure that flattens with scale. The crossover math is merchant-specific; run it with your real volume, and weight Shopify's included operations honestly — commerce downtime is revenue, and the Deloitte/Google research (2020) measured conversion moving with tenths of a second.
It can be — and it isn't automatically. Shopify's field baseline is genuinely strong: 78% of origins passed Core Web Vitals (November 2025 desktop data), the fruit of uniform managed infrastructure. Custom builds own both ends of the range: the leanest storefronts measure among the fastest commerce experiences on the web, and careless builds fall below any managed platform. As throughout this series, the difference is who controls the outcome — with the commerce-specific stake that speed correlates with conversion in the cited research.
Standard-stack custom commerce draws from the largest developer pools — React leads Stack Overflow's 2025 framework usage at 46.9% — and headless-Shopify skills are increasingly common in commerce-focused agencies. The procurement rules from our custom-build guides apply doubled here: code assigned to you, boring/portable technology, and documentation a successor could operate from — because a store, unlike a brochure site, cannot tolerate an unmaintainable emergency.

Where we stand

Webvello builds custom websites and Shopify storefronts, including headless architectures — every branch of this page is a service we sell. The threshold tests exist so the recommendation follows your model, not our invoice.

Keep going

The pillar guide: Choosing a Website Platform in 2026All the comparisons, one decision framework, full evidence appendix.

Shopify vs WooCommerce

The operator’s comparison, with verified fee arithmetic.

Read the guide

When a Custom Website Is Worth It

The general threshold framework this page applies to commerce.

Read the essay

Shopify Development

Rails-based and headless storefront work.

Explore

Ecommerce Design

The conversion layer, whichever architecture wins.

Explore
Get Free Growth Plan