A founder messaged us last month with a simple question: should she rebuild her store on a custom stack, or just stay on Shopify and fix what's broken? She was doing $340,000 a year in a skincare brand, growing fast, and a developer had convinced her that Shopify would "cap her ceiling" eventually.
That's the pitch a lot of growing brands hear. It's rarely the right one at her revenue stage, and the shopify vs custom ecommerce build decision deserves more nuance than a developer's sales pitch.
This isn't a platform war post, it's a framework for figuring out which path actually fits your stage, your team, and your margins. The wrong choice here costs real money and real time.
Why This Question Keeps Coming Up
Ecommerce founders hit this fork at a few predictable moments. Usually it's after a funding round, a viral product moment, or a frustrating six months of platform limitations that made the team start Googling alternatives at 11pm.
The honest answer is that most brands never need a custom build. Shopify now powers everything from $50,000 side hustles to billion-dollar brands like Gymshark and Allbirds, and the platform has closed most of the gaps that used to force a custom rebuild.
But "most brands" isn't every brand. Here's how to tell which camp you're in.
Shopify's appeal is simple. You get hosting, checkout, payment processing, fraud detection, and a massive app ecosystem out of the box. A reasonably skilled developer can launch a functional store in two to four weeks. A custom build, by contrast, usually takes three to six months before it handles real transactions.
That speed difference matters more than founders admit when they're mid-pitch to a VC or trying to catch a trend cycle. Waiting half a year for a perfect backend while a market window closes is its own kind of expensive.
What Shopify Actually Gets You
Shopify ecommerce stores run on infrastructure built for exactly this job: selling products online at scale, reliably, during traffic spikes. You're not paying a developer to rebuild checkout security or PCI compliance from scratch.
The app ecosystem is the other underrated piece. Need subscriptions, loyalty points, a size-chart widget, or post-purchase upsells? There's a vetted app for nearly all of it, often installable in an afternoon.
A few things Shopify handles well without custom engineering:
- Checkout optimization, including Shop Pay's accelerated one-click flow
- Inventory sync across multiple sales channels (Instagram, TikTok Shop, Amazon)
- Automatic PCI-DSS compliance and fraud scoring
- Theme customization through Liquid, without touching core infrastructure
- Built-in analytics that cover most founder-level reporting needs
The tradeoff is real, though. You're renting infrastructure, which means Shopify's rules apply to your store: transaction fees if you skip Shopify Payments, app subscription costs that stack up fast, and design limits once your vision outgrows what a theme can flex into.
When Shopify Plus Enters The Conversation
Once a brand crosses roughly $1 million to $2 million in annual revenue, Shopify Plus usually comes up. It removes some of the standard plan's checkout limits, adds script editor access for custom checkout logic, and includes dedicated support.
Shopify Plus costs more, starting around $2,300 a month depending on volume, but it buys scripting flexibility that standard Shopify doesn't offer. For brands running complex B2B wholesale alongside DTC, or multiple international storefronts, Plus often closes the gap that used to require a custom build entirely.
This matters because the old argument for custom builds, "Shopify can't handle our complexity", has gotten weaker every year. Plus and the headless options below absorb a lot of what used to force a rebuild.
What A Custom Ecommerce Platform Actually Buys You
A custom ecommerce platform means your team owns the full stack: frontend, backend, database, hosting, everything. No Liquid templates, no app marketplace dependency, no platform fees cutting into margin.
The upside shows up in a few specific scenarios. If your product requires a genuinely novel buying experience (think configurable furniture with 3D previews, or a subscription model with logic no app supports), custom code gives you room that a theme never will.
Performance is the other real argument. A lean custom frontend, built right, can load faster than a Shopify theme weighed down by a dozen installed apps. For brands where page speed directly moves conversion rate, shaving even 500 milliseconds off load time is worth engineering hours.
But the costs are steep and persistent:
Development cost: a serious custom build runs $80,000 to $300,000+ depending on scope, and that's before ongoing maintenance.
Time to launch: three to nine months is typical, sometimes longer when integrations get complicated.
Ongoing engineering overhead: every payment gateway update, every security patch, every new sales channel integration is now your team's job, not a platform vendor's.
Hiring risk: you need developers who understand ecommerce specifically, not just general web development, or you'll rebuild things Shopify solved years ago.
That last point trips up more brands than any technical limitation. A custom ecommerce platform is only as good as the team maintaining it, and losing your lead developer six months after launch can leave a brand stuck with code nobody fully understands.
Headless Commerce: The Middle Path
Headless commerce decouples the frontend (what customers see) from the backend (inventory, payments, order management). You can run Shopify as the backend engine while building a fully custom frontend in a framework like Next.js or Remix.
This is where a lot of the "Shopify vs custom" debate has actually moved. Brands get Shopify's reliable backend, checkout, and app ecosystem, paired with total design freedom on the storefront. Shopify's own Hydrogen framework was built specifically for this approach.
The catch is that headless commerce isn't free complexity-wise. You still need frontend developers who understand the Storefront API, and you lose some of the plug-and-play simplicity that makes standard Shopify so approachable for non-technical teams.
For brands between $2 million and $10 million in revenue with a specific performance or design problem that themes can't solve, headless often lands in the sweet spot. It's worth scoping properly before committing, since a half-finished headless migration is worse than staying on either pure option.
A Practical Decision Framework
Skip the philosophical debate and run through these questions honestly.
Revenue and growth stage. Under $2 million a year, Shopify or Shopify Plus almost always wins on cost and speed. Above $10 million with specific technical bottlenecks, custom or headless starts making financial sense.
Team composition. Do you have, or can you hire, in-house engineering talent dedicated to ecommerce? If the answer is no, a custom build means hiring an agency indefinitely, not once.
Product complexity. Standard product catalog, standard checkout flow? Shopify handles it. Configurators, complex subscription logic, or marketplace-style multi-vendor setups push toward custom or headless.
Timeline pressure. If you need to launch in under two months, custom builds are off the table regardless of budget.
Margin sensitivity. Transaction fees and app subscriptions eat into margin on thin-margin products. Run the actual math on your specific volume before assuming custom saves money, because development and maintenance costs often outweigh the fees you'd save.
One founder we talked to, running a $4 million supplement brand, ran this exact math and found that Shopify Plus fees cost her about $14,000 a year more than standard Shopify app subscriptions. Her custom-build quote came in at $180,000 plus ongoing maintenance. She stayed on Plus.
Where A Website Partner Actually Helps
Most of the pain founders describe isn't a platform limitation, it's execution, and a slow Shopify store is usually just a badly built Shopify store. That's rarely proof the platform itself has failed.
Before signing off on a six-figure custom build, it's worth getting a second opinion on whether the real problem is platform choice or implementation quality. That's genuinely a website design conversation, not necessarily a "rip and replace the whole stack" one.
We've seen brands spend months evaluating a custom rebuild, compare agency quotes that wildly disagree with each other, and eventually discover that a focused Shopify Plus migration plus theme cleanup solved 90% of what they thought needed custom code. That's a cheaper, faster outcome, and it's the one worth ruling out first.
If search visibility is part of what's driving the conversation, pulling in dedicated SEO support for product and collection pages often moves the needle faster than a platform migration ever will, since rankings rarely move because of backend architecture alone.
Some related reading that digs into the adjacent decisions brands in this exact spot tend to face next: whether to bring a Shopify partner in-house or stay agency-side, and the actual cost math of Shopify Plus versus standard Shopify once you've picked a lane.
The Takeaways
Shopify and Shopify Plus solve the problem for the vast majority of DTC brands under $10 million in revenue, full stop.
Custom builds make sense when you have a genuinely novel product experience, dedicated engineering talent, and a budget north of $100,000.
Headless commerce is the real middle path for brands wanting design freedom without abandoning Shopify's backend reliability.
Run the actual cost math on fees versus development and maintenance before assuming custom saves money long-term.
Most "platform problems" are actually execution problems, worth ruling out before committing to a rebuild.
If you're weighing this decision for your own store and want a second set of eyes on the actual numbers, a short call tends to save more time than another week of vendor calls: book a 30-minute session and walk through your specific situation.
Compare that against where other growing brands have landed on the same question in our case studies, or just read our take on why founders keep redesigning websites that didn't need it before the platform question even comes up.