Most online stores don't need a custom build. That's an awkward thing to say as a company that builds custom e-commerce, but it's true — and saying it up front saves everyone money. Shopify covers the vast majority of selling-things-online cases well, and for a lot of businesses, reaching for a bespoke platform is solving a problem they don't have yet.
The honest answer to "Shopify or custom?" depends on how standard your business actually is. If you're selling a normal catalogue to normal customers with normal checkout, Shopify is almost certainly the right call. The case for custom gets stronger as your workflows, margins, or scale stop looking like everyone else's. We build both, so we don't have a horse in this race — here's how we think it through.
Where Shopify wins
Shopify exists because the basics of running a store are mostly solved. You shouldn't pay anyone to rebuild them.
- Speed to launch. A clean Shopify store can be live in days, not months. If your goal is to start selling and learn from real customers, that head start is worth a lot.
- Lower upfront cost. You're paying a monthly subscription plus transaction fees instead of a build budget. For an early-stage store, that's the difference between launching now and waiting two quarters.
- A standard catalogue just works. Products, variants, collections, inventory, discounts, abandoned-cart recovery — it's all there and battle-tested across millions of stores.
- Payments are sorted. Razorpay, Cashfree, and other Indian gateways plug in cleanly, so UPI, cards, net banking, and EMI work out of the box. You're not building a payments integration from scratch or worrying about PCI scope.
- You're not the only one maintaining it. Security patches, uptime, and platform updates are Shopify's problem. A custom store makes them yours.
A good test: if you struggle to name something your store needs to do that Shopify can't do, you're describing a Shopify store.
Where Shopify starts to hurt
Shopify is opinionated, and those opinions are sensible for most stores. The friction shows up when your business genuinely works differently.
- Unusual workflows. B2B pricing tiers, complex bundles, made-to-order configurations, subscription logic that apps don't quite handle, multi-warehouse fulfilment with custom rules. You can often force these in with apps — but every app is another subscription, another point of failure, and another thing that can break on a platform update.
- App-stack creep. It's common to see a store paying for eight or ten apps, each $10–$50 a month, each owning a slice of critical functionality. The monthly cost adds up, and so does the fragility.
- Checkout and theme limits. Shopify has loosened up here, but deep customisation of the buying flow is still constrained compared to code you own.
- Margins at scale. Transaction fees and app subscriptions are trivial at low volume and meaningful at high volume. At enough revenue, what felt cheap starts to look like a recurring tax.
None of this makes Shopify wrong. It means "Shopify can technically do it" and "Shopify is the right tool for it" are different statements.
When custom or headless pays off
Custom e-commerce earns its cost when the store is the differentiator, not just a way to take payments.
- The buying experience is part of the product. If how customers browse, configure, or interact is central to why they choose you, owning that experience matters. A template caps it.
- Deep integrations into your own systems. Tight, real-time links to your ERP, your warehouse, your pricing engine, or internal tools are easier and more reliable when you own the codebase rather than chaining apps together.
- Scale changes the math. At high order volume, building and maintaining your own platform can cost less than the cumulative fees and app stack — with far more flexibility.
- Genuinely unique logic. Pricing, fulfilment, or merchandising rules that no off-the-shelf app models cleanly are a strong signal that you've outgrown the standard path.
There's also a middle road worth knowing about: Shopify Hydrogen, Shopify's headless setup. You keep Shopify as the commerce backend — catalogue, checkout, payments, the parts that are genuinely hard and well-solved — while building a fully custom storefront on top. You get the freedom of a custom front end without rebuilding the engine underneath. For a lot of stores that have outgrown themes but not Shopify itself, this is the sweet spot.
A quick way to decide
Run your store through three questions:
- Is anything you need genuinely impossible — or only possible through a tangle of apps? Occasional gaps are fine. A pile of fragile workarounds around core functions is a real signal.
- Does your storefront experience help you win customers, or just process orders? If it's the former, custom or headless deserves serious thought.
- Where are you on the volume curve? Low volume favours Shopify's economics. High volume can flip them.
If you're early, default to Shopify and revisit later — you can move to Shopify Hydrogen or a custom e-commerce build when the business demands it, and the data you gather in the meantime makes that decision sharper. Premature custom-building is one of the more expensive mistakes we see.
How we approach it
When a client asks us to build, we start by checking whether they should. Often the right first move is a well-built Shopify store with a small, deliberate set of apps, not a custom platform. When the case for custom or headless is real, we scope a focused version that proves the value early rather than a sprawling rebuild that takes a year to show results.
The aim isn't to build the most impressive store. It's to put your money where it actually moves the business — and sometimes that's a Shopify subscription.
Trying to figure out which side of this line your store is on? Get in touch and we'll give you a straight answer, even if it's "stay on Shopify."