Shopify vs a custom storefront for Indian D2C brands

For most Indian D2C brands weighing Shopify vs a custom storefront in India, Shopify is the right starting point. It gets you live in weeks, handles payments and security, and lets you focus on product and marketing instead of infrastructure. A custom or headless build wins later, once your catalogue, traffic, or workflow logic outgrows what the platform comfortably allows, or when the monthly platform and app costs start rivalling the cost of engineering you control. The honest answer is that this is a timing decision, not a religious one.

We build both at BotBrained, so we have no incentive to push you one way. What follows is how we actually advise founders who ask us this.

Why Shopify wins for most Indian D2C brands at the start

If you are a new or growing brand selling a few dozen to a few hundred SKUs, the maths usually favours Shopify. You pay a monthly fee to skip a large amount of work: PCI-compliant checkout, hosting that survives a flash sale, inventory, discount engines, abandoned-cart recovery, and a theme system your team can edit without a developer on call.

The Indian payments story is genuinely fine on Shopify now. Razorpay, Cashfree, PayU, and CCAvenue all plug in as gateways, UPI works at checkout, and you can run cards, netbanking, and wallets without writing a line of code. That alone saves weeks. Cash on delivery, still a large share of orders for many Indian categories, is supported natively, and you can gate it by pincode or order value using apps.

The ecosystem is the real reason to stay. Shipping aggregators like Shiprocket and Delhivery have native integrations. GST-compliant invoicing, RTO (return-to-origin) prediction, WhatsApp order updates, loyalty, reviews: there is an app for each. You are renting a working business stack, not just a website.

The honest downsides

Costs stack quietly. The base plan is one thing; the four or five apps you end up installing each carry their own monthly fee, often priced in dollars, and the rupee bill at the end of the month is larger than founders expect. Transaction fees apply unless you use Shopify Payments, which is not available in India, so you are on a third-party gateway plus any Shopify cut on certain plans.

You also inherit the platform's opinions. Checkout customisation is limited unless you are on Shopify Plus. Complex catalogue logic, such as made-to-order configurators, bundles with conditional pricing, or B2B tiered rate cards, fights the data model. And every app you add is another vendor between you and your customer data.

When a custom or headless storefront wins

A bespoke build is not about prestige. It is about three specific pressures: cost at scale, control over experience, and logic the platform cannot model. When two of those three are real for you, it is worth costing out an alternative.

1. Your app bill has become an engineering budget

There is a crossover point where the stack of monthly app subscriptions, each solving one narrow problem, adds up to what it would cost to own that functionality. If you are paying for a dozen apps and several do things a competent team could fold into one codebase, the recurring spend starts to justify a one-time build. The trigger is recurring cost you cannot reduce, not a single large invoice.

2. The buying experience is your differentiator

Some brands sell on experience as much as product: a jewellery house with a try-on configurator, a furniture brand with room visualisation, a nutrition company with a quiz that builds a custom subscription box. When the storefront is the product, the constraints of a theme system become a tax on your brand. A headless setup, a custom React or Next.js front end pulling from a commerce backend, gives you full control of the front end while keeping a proven engine underneath.

3. Your operations have logic the platform cannot hold

This is the one we see most with Indian brands that have an offline arm. Multi-warehouse inventory with serviceability by pincode, dealer or distributor pricing, made-to-measure orders, or a marketplace model where multiple sellers fulfil: these stretch a standard store until something breaks. At that point you are fighting the tool. A custom backend, or a headless front end on top of a flexible commerce API, lets the software match how you actually run.

Headless as the middle path

Headless commerce is worth naming on its own because it is the option founders forget. You keep Shopify (or another engine) as the backend for catalogue, orders, and payments, but you build your own front end. You get the design freedom and speed of a custom storefront without rebuilding checkout, fraud handling, and payment reconciliation from scratch. The cost sits between a theme and a full bespoke build, and so do the engineering demands: you now own a front-end codebase and need someone to maintain it.

A practical decision framework

Run your situation through these questions before you spend anything.

• How many SKUs and how complex is each? Simple catalogue, under a few hundred SKUs: Shopify. Configurable products, bundles, variants with conditional pricing: start questioning it.
• What does COD look like for your category? If COD is heavy and RTO is a real cost, you want the app ecosystem (pincode gating, RTO scoring). That favours staying on platform.
• Is your traffic spiky? Drop culture, influencer launches, festive-sale spikes: Shopify absorbs these without you thinking about servers. A custom build means you own the scaling problem.
• Who maintains it? Be honest. Shopify needs no engineer to keep the lights on. A custom storefront needs ongoing developer time. If you do not have that, the build will rot.
• What is the true monthly cost today? Add the plan, every app, gateway fees, and any developer retainer. That number is your benchmark for whether a build pays back.

A useful rule: start on Shopify, and only migrate the part that is actually hurting. You rarely need to rebuild everything. More often, one piece (checkout, a configurator, a B2B portal) is the bottleneck, and you go headless on just that while the rest stays put.

What this looks like in practice for an Indian brand

A skincare brand doing a few thousand orders a month with a clean catalogue has no business writing custom commerce. Their time goes to performance marketing and retention, and Shopify plus WhatsApp order updates plus a reviews app is the correct, boring answer.

A made-to-order furniture brand with dealer pricing, multi-city warehouses, and a long quote-to-order cycle is a different animal. The standard store will collapse under that, and a headless front end over a flexible backend, or a partly custom build, earns its cost early through fewer manual workarounds.

Most brands sit between these. The skill is reading which pressure is real for you right now and resisting both the temptation to over-engineer early and the inertia of staying on a platform a year after you have outgrown it.

At BotBrained we ship both: clean, fast Shopify stores and custom or headless storefronts, and we will tell you when you do not need us to build the harder thing. If you want a straight read on which side of this line your brand sits, see BotBrained Shopify and custom commerce builds and bring your current monthly app bill to the conversation. It usually settles the argument faster than anything else.