Shopify vs Custom E-Commerce: The Honest 2026 Comparison
Shopify vs custom e-commerce, honestly: 3-year TCO ($99K vs $190K illustrative), fee curves past $1M/mo, headless costs, migration triggers and verdicts by catalog size.
A fast-growing DTC brand at roughly 5,000 SKUs asked us last quarter whether it was finally time to leave Shopify. Two weeks later, a two-sided marketplace asked the opposite question — whether it could delay a custom build for another year. Both got the same answer: the decision is arithmetic, not opinion, and the arithmetic starts with three numbers — total cost over three years, the value of speed versus flexibility, and your fee curve as revenue scales.
This is the comparison we run with every client before anyone touches a checkout flow: what you actually pay on each path, where Shopify's speed wins, where a custom build earns its cost, the headless middle path, and the triggers that tell you it is time to migrate. Platform pricing below is published list pricing (subject to change); everything modeled from our own engagements is labeled illustrative.
Here is the honest version up front.
Key Highlights
- Shopify's self-serve plans list at roughly $29–$399/month from Basic to Advanced (annual billing), with Plus from about $2,000–$2,500/month depending on term (published list pricing).
- Shopify Payments processes online sales at 2.9% + 30¢ on standard plans; routing to an external gateway adds 0.5%–2.0% on top (published Shopify fee schedule).
- Platform plus app costs fall from ~1.4% of revenue at $25K/month GMV to ~0.7–0.8% at $1M/month — then bend back up as the app stack grows (illustrative model).
- Three-year TCO for a brand at
$150K/month revenue: **$99K on a Shopify stack vs ~$190K for a custom build** (illustrative) — custom is a bet on differentiation, not savings.- Feature velocity inverts over a year: theme stores ship 4–5 revenue features a quarter from week one; custom builds start at 1–2 and overtake by Q3–Q4 (illustrative model).
- A 0.1-second load improvement lifted retail conversions 8.4% (Deloitte, Milliseconds Make Millions, 2020).
- Average documented cart abandonment sits near 70% (Baymard Institute) — which is why checkout and UX flexibility is worth real money at scale.
- Replatforming later costs roughly $40K at 500 SKUs, ~$90K at 5,000 and ~$220K at 50,000 (illustrative agency ranges) — the switch gets more expensive every quarter you wait.
The Real Cost of Choosing Wrong: The 2026 Baseline
Choosing a commerce platform is not a website decision — it is a three-to-five-year operating commitment that touches checkout, inventory, content and every integration you will ever buy. The wrong choice rarely announces itself as a disaster; it announces itself as a slow tax: apps you rent instead of features you own, workarounds that pile up, and a replatform bill that grows with your catalog.
Speed to market is where the paths diverge most visibly on day one. A themed Shopify store launches in weeks because thousands of decisions are already made for you; a custom build spends those weeks making the decisions instead:
Neither answer is wrong. A first-time founder burning cash while pre-selling a 60-product line should be live in a month; a marketplace splitting payments between vendors cannot launch on a theme at any speed. The mistake is choosing for identity ("we're a real company, we build") or fear ("we could never afford custom") instead of for the business model.
Key takeaway: Match the platform to your business model and time horizon, not to your ego or your budget anxiety — the expensive mistake is almost always a mismatch, not a price tag.
Factor 1: Three-Year TCO — What You Actually Pay
Sticker prices mislead in both directions. Shopify's monthly plan looks tiny next to a five-figure build, and a custom quote looks enormous next to "$39 a month." Three years of real costs — subscriptions, apps, gateway economics, development, hosting and maintenance — tell a fairer story. The table models a single-brand store at roughly $150K monthly revenue (illustrative):
| Cost line | Shopify stack (per year) | Custom build (per year) |
|---|---|---|
| Platform subscription | $4K–$5K (Advanced list) | $0 |
| Apps and plugins | $8K–$12K | $0 — features owned, not rented |
| Payment gateway premium | $0 (Shopify Payments) | $0 (direct Stripe, similar rate) |
| Design and development | $8K–$13K (theme, tweaks, retainer) | $110K year 1 (the build) |
| Hosting and infrastructure | Included | $12K–$14K |
| Ongoing feature work | Often more app fees | $24K–$28K |
| 3-year total | ~$99K | ~$190K |
The same model, year by year, shows the shape of the decision. Shopify's cost is a steady ramp that grows with apps and support; custom front-loads a build and then runs on maintenance plus whatever you choose to invest in differentiation:
Three-year totals come out around $99K for the Shopify stack versus $190K for the custom build — at this revenue, single-brand and reasonably standard, Shopify wins the raw money math and usually deserves to. The custom build only out-earns its premium when differentiation or business-model complexity converts into margin the theme stack cannot reach. That conversion is what the next two factors measure.
Key takeaway: At single-brand scale under roughly $5M a year, Shopify wins the three-year TCO — so justify custom with differentiation and business-model fit, never with the promise of saving license fees.
Factor 2: Flexibility vs Speed — The Trade Nobody Escapes
Every platform decision is a position on one trade-off: how much control you trade away to ship fast. Shopify trades you speed for guardrails — a mature checkout, a payments stack, an app ecosystem and a theming system with hard edges. Custom trades you months of building for a blank page. Neither contract can be renegotiated from inside; you can only add the other side around the edges.
What the guardrails cost becomes visible in shipping velocity. A theme store ships revenue-relevant features — bundles, upsells, a new landing system — almost from week one, while a custom build spends its first quarters building foundations and then compounds:
The lines cross around Q3–Q4 in this illustrative model, and the crossing point is the honest answer to "when is custom worth it." Some businesses never reach it — a focused single-brand store with standard checkout needs may ship from themes forever. Others hit it immediately, because their core mechanic does not exist on any theme:
- Multi-vendor marketplaces — vendor onboarding, split payments, commission rules and per-vendor payouts.
- Configured or made-to-order products — quoting, deposit flows, production handoffs.
- B2B pricing logic — contract prices, net terms, account hierarchies per buyer.
- Unusual subscription mechanics — swapping, pausing and bundling logic the app store only approximates.
When the business model itself is the product, build the platform. We watched that arithmetic play out on a multi-vendor marketplace whose database and order flow had to scale past what any template assumed — the marketplace scaling case study walks through why the custom backend was the whole ballgame.
Key takeaway: Speed wins the first two quarters, flexibility wins the next two years — buy the platform that matches which of those matters more, and never punish a standard business model with a custom build it does not need.
Factor 3: Transaction Fees and Margins at Scale
Payment economics are the most misunderstood part of this comparison. On standard plans, Shopify Payments processes online sales at 2.9% + 30¢, and pushing volume to an external gateway costs a 0.5%–2.0% surcharge on top (published Shopify fee schedule). Here is the nuance most comparisons miss: a custom build pays Stripe or its peers almost the same 2.9% + 30¢ — so the gateway rate is roughly a wash, and the real fee story at scale is your software stack, not your transaction rate.
The stack effect is double-edged. On the way up, platform costs amortize: the same $399 Advanced plan costs 1.6% of revenue at $25K monthly GMV but a fraction of that at scale. On the way down, app sprawl bends the curve back up — growing brands stack reviews, subscriptions, loyalty, search and upsell apps, and the meter never stops:
Read the bend at the right end carefully: at $1M monthly GMV, a realistic app stack plus a Plus subscription pulls the software take back up to ~0.8% — roughly $96K a year of rent on capabilities a custom build would own. Past about $2M–$3M annual revenue, three levers start favoring the custom or headless path: Plus rate negotiation, eliminating app sprawl, and checkout optimization worth real points of conversion once abandonment is already near 70% (Baymard Institute's long-running documented average). Below that line, the wash holds and Shopify's fee story stays honest.
Key takeaway: Compare stacks, not gateways — the transaction rate is a wash, and the fee that decides your margin at scale is the app rent bending your cost curve back up past $1M monthly GMV.
Factor 4: The Headless Middle Path
Between "theme store" and "full custom platform" sits the option most scaling brands should evaluate first: headless commerce. Shopify (or a custom backend) keeps running catalog, orders and payments as the commerce engine; a custom frontend — usually built on a modern framework — renders the storefront. You keep the commerce plumbing you already trust and replace only the presentation layer where differentiation actually pays.
The business case is speed, in the visitor's sense rather than the launch sense. Deloitte's Milliseconds Make Millions research found a 0.1-second improvement in mobile load time lifted retail conversions by 8.4% — and headless storefronts we deliver typically cut load times 30–50% over theme stacks (illustrative, from our own deployments). That conversion delta, multiplied by real traffic, is what pays for the build:
- Typical investment: $60K–$150K for a production headless storefront (typical agency ranges), plus ongoing maintenance.
- Best fit: brands past ~$2M annual revenue with meaningful organic and paid traffic, content-led growth, or UX needs themes cannot express.
- Worst fit: young stores still searching for product-market fit — headless adds engineering surface before revenue justifies it.
We build these regularly, and the honest caveats matter: previews, apps and merchandising tools get re-wired; your team needs developers on retainer; and the conversion gains must be measured, not assumed. Done for the right reasons, it is the cheapest differentiation money can buy — the headless e-commerce storefront case study shows the pattern end to end.
Key takeaway: Headless is not a fashion — it is a surgical trade of frontend freedom for frontend cost, and it pencils out almost exactly when traffic times conversion delta outruns the $60K–$150K build.
Factor 5: Migration Triggers — When to Leave (or Stay)
Most replatforming happens either two years too early or two years too late, because nobody wrote down the triggers in advance. Write these down and review them quarterly; they convert a vague itch ("our site feels limiting") into a checklist with numbers attached:
| Trigger | The signal to watch | What it usually means |
|---|---|---|
| Business model outgrows the platform | Marketplace, B2B terms or custom subscriptions forced into app workarounds | Custom backend, or headless with a custom order layer |
| Fee curve bends against you | App stack plus Plus fees exceed ~0.8–1% of revenue and keep climbing | Consolidate apps, negotiate Plus, or go headless/custom |
| Conversion plateaus while traffic grows | Checkout and UX constraints you cannot fix inside the theme | Headless storefront with measured speed gains |
| Data and inventory complexity | Multi-channel stock, wholesale and retail sharing one truth | Custom backend with a real database, not app sync |
| Content-led growth stalls | Editorial velocity and SEO limited by theme architecture | Headless with a proper CMS |
The reason triggers deserve quarterly review is that migration cost compounds with catalog size — every quarter of growth adds SKUs, order history, integrations and SEO surface that must survive the move:
Note what the chart implies: waiting is not free in either direction. Replatforming a 500-SKU store is a sprint; replatforming a 50,000-SKU catalog is a program with an SEO preservation plan attached. If a trigger fires, act within the quarter — if none fires for two consecutive reviews, stop shopping and go sell.
Key takeaway: Write your migration triggers down before you need them, review them quarterly, and let the checklist — not a conference talk or a designer's mood board — fire the decision.
Verdicts by Catalog Size and Growth Plans
Every factor above collapses into one table. These are the verdicts we actually give clients, matched to catalog size and growth plan rather than to fashion:
| Your situation | Honest 2026 verdict |
|---|---|
| Under 500 SKUs, single brand, standard checkout | Shopify, Basic or Shopify plan. Do not build. Spend the budget on traffic and product. |
| 500–5,000 SKUs, growing DTC, standard mechanics | Shopify Advanced with a curated app stack; consider headless only when conversion plateaus with traffic growing. |
| 5,000+ SKUs, B2B terms, multi-channel inventory | Shopify Plus plus custom middleware, or a custom backend with a headless storefront — app-sync inventory will eventually corrupt. |
| Multi-vendor marketplace, split payments, commissions | Custom platform. This is your business model, not a feature request. |
| Content-led brand where editorial and SEO drive revenue | Headless storefront over your current engine, with a real CMS attached. |
Two closing disciplines make any of these verdicts cheaper to execute. First, own your data layer: wherever the storefront lives, keep a clean export path for products, orders and customers, because that is what migration costs are made of. Second, keep SEO stewardship on the checklist for every change — category pages are your goldmine, as our e-commerce SEO guide details, and they are the asset replatforms destroy most often.
Key takeaway: The verdict follows the business model — Shopify for standard mechanics at almost any size, custom for marketplaces and exotic models, headless for the scaling middle — and both disciplines that cut migration cost are free.
What Your Business Should Do
Platform decisions reward sequence and punish vibes. Here is the 90-day plan:
Days 1–30: Get the real numbers.
- Pull 12 months of revenue, orders, average order value and refund rates — every model below depends on them.
- List your current monthly stack: plan fee, every app, gateway rates and any retainer, with dollar amounts.
- Score your business model against the flexibility list: marketplaces, B2B terms, custom subscriptions, made-to-order.
Days 31–60: Run the three-way comparison.
- Build the three-year TCO table for your real volumes: current stack, Plus negotiation and a scoped custom or headless quote.
- Quantify one differentiation bet — checkout, speed or a business-model feature — in conversion or margin points, not feelings.
- Check every migration trigger in the table above against your last two quarters of numbers.
Days 61–90: Commit and protect.
- Pick the path the arithmetic says, and write down the threshold numbers that would reverse the decision.
- If staying: kill unused apps, negotiate your plan term and re-audit the stack quarterly.
- If moving: commission the data-migration and SEO-preservation plan before any design work starts.
The Bottom Line
The honest 2026 answer is that Shopify wins the money math for most single-brand stores and custom wins the business-model math for marketplaces, complex B2B and heavily differentiated brands — with headless as the surgical middle for scaling brands whose traffic deserves a faster storefront. What separates good outcomes from expensive ones is never the platform itself; it is running the TCO, fee-curve and trigger analysis before emotions or aesthetics get a vote.
If you want that analysis run on your real numbers, that is our daily work. Book a free strategy call and we will model the three-year math for your catalog together — or send us a message with your questions and we will reply within one business day.
Free download: the Learning Guide (PDF)
Everything worth keeping from this article — key numbers, tables and the action checklist — in one print-ready, fillable PDF.
Join our newsletter — more growth tips, twice a month
Playbooks from real projects. No spam, unsubscribe anytime.
FAQ
Is Shopify still worth it in 2026?+
For most single-brand stores, yes — the speed, payments integration and app ecosystem still beat building equivalents from scratch. The honest caveats: app sprawl pushes software costs back up past roughly $1M monthly GMV, checkout customization is constrained, and marketplace or complex B2B models outgrow the platform entirely. Run the three-year TCO at your real volumes before deciding either direction.
How much does a custom e-commerce site cost?+
A production custom build typically runs $110K+ in year one with $38K–$42K a year after for hosting, maintenance and feature work (illustrative agency ranges) — roughly $190K over three years at mid-market scale versus about $99K for a Shopify stack. Headless storefronts over an existing engine cost less: $60K–$150K. Custom pays for itself only where differentiation or business-model complexity converts to margin.
What is headless commerce, and do we need it?+
Headless keeps your commerce engine — catalog, cart, payments — and replaces the theme-based frontend with a custom application, typically cutting load times 30–50% (illustrative, our deployments). It fits brands past roughly $2M annual revenue with real traffic and UX needs themes cannot express; Deloitte found a 0.1-second speed gain lifts retail conversions 8.4%. Young stores still proving product-market fit should wait.
When should a brand move off Shopify?+
When a written trigger fires, not when a mood strikes: a marketplace or B2B model forced into app workarounds, software costs bending past ~0.8–1% of revenue, conversion plateaus with traffic growing, or multi-channel inventory that app sync cannot keep honest. Remember the migration bill compounds with catalog size — about $40K at 500 SKUs versus $220K at 50,000 (illustrative) — so act within the quarter a trigger fires.
Engineering-led team at Emerson Technology — building apps, web platforms and growth systems for ambitious businesses. Every guide comes from real client work.