Shopify vs WooCommerce vs Custom India: 2026

India's e-commerce market hit USD 137 billion in 2025 and is growing at 21.5% CAGR toward USD 363 billion by 2030 (Mordor Intelligence, 2025). If you're building an online store right now, you're choosing between Shopify, WooCommerce, and custom development — and the wrong pick costs you either lakhs upfront or a recurring platform fee that compounds for years. Here's the India-specific breakdown.

What each platform actually costs in India

Most cost comparisons ignore two things: recurring platform fees and India-specific payment gateway charges. Here's the real math.

Shopify: ₹35,000–₹2,75,000 to build + ₹2,500–₹21,000/month subscription (Basic to Advanced plans). Add 2% transaction fee unless you use Shopify Payments — which isn't available in India. Razorpay/PayU integration works, but Shopify still charges its third-party transaction fee.
WooCommerce: ₹30,000–₹2,50,000 to build. No monthly platform fee. You pay hosting (₹500–₹5,000/month), SSL, and plugin licences — total running cost ₹1,000–₹8,000/month. No transaction fee beyond payment gateway charges.
Custom development: ₹1,50,000–₹10,00,000+ to build. Low ongoing costs once built. Every feature costs dev time, which adds up.

GST invoicing and compliance: who handles it better

Every Indian e-commerce store needs GST-compliant invoices with GSTIN, HSN codes, and correct IGST/CGST split by customer state. This is where the platforms diverge.

Shopify: No native GST invoice support. You need a paid plugin (Sufio, OrderlyEmails, or similar — ₹1,500–₹4,000/month) or a custom order-printer template.
WooCommerce: Plugins like WooCommerce GST (free/paid) or WP-GST handle GSTIN capture, HSN codes, and correct tax split. More control, more setup.
Custom: You define exactly what goes on every invoice. Only viable option for businesses with complex tax structures (multiple HSN codes, composition dealers, export invoices).

Payment gateways: what actually works in India

Razorpay, PayU, Cashfree, and CCAvenue cover 95% of Indian SMB needs. All three platforms support them. The difference is cost.

Shopify: Standard payment gateway fee (2% Razorpay) + Shopify's 2% third-party transaction fee = 4% per order. On a ₹1,000 order, you lose ₹40 in fees alone.
WooCommerce / Custom: Only pay the payment gateway fee (~2%). No additional platform cut.

For a store doing ₹5L/month in GMV, Shopify's extra transaction fee costs ₹10,000/month — ₹1.2 lakh/year — before accounting for the subscription.

Logistics and shipping integrations for India

Shiprocket, Delhivery, Ecom Express, and DTDC are the dominant players. WooCommerce has the deepest native plugin ecosystem for Indian logistics. Shopify supports them via apps but often with USD-priced subscriptions or manual webhook setup. Custom gives you full API control — useful if you're negotiating direct rate contracts with carriers.

Tier-2 and tier-3 city readiness

Tier-2 and tier-3 cities now contribute 66% of new e-commerce orders in India (IBEF, 2025). Your store needs to load fast on 4G/5G connections, support COD (still 50%+ of orders in smaller cities), and handle vernacular language preferences. WooCommerce with a lightweight theme handles this reasonably well. Shopify on a Starter plan struggles with page speed on budget Android handsets. Custom headless builds optimized for Core Web Vitals perform best — but cost the most to build.

D2C scaling path: when to migrate

The typical Indian D2C journey looks like this:

0–₹50L/year GMV: Shopify Basic or WooCommerce. Shopify wins on speed to launch; WooCommerce wins on total cost of ownership.
₹50L–₹5Cr/year GMV: WooCommerce or Shopify Advanced. Shopify's transaction fees become painful at this volume — migrate to WooCommerce or negotiate Shopify Plus pricing.
₹5Cr+ GMV: Custom headless or Shopify Plus. At this scale you need the performance, the custom checkout logic, and the direct API integrations Shopify Plus provides.

Who should use which

Choose Shopify if: You want to launch in under 2 weeks, your team has zero technical knowledge, and you're fine paying ₹2,500–₹21,000/month ongoing. Best for fashion, accessories, and lifestyle D2C brands starting out.
Choose WooCommerce if: You want lower long-term costs, need deep GST invoice customisation, or are building a marketplace-style store with complex product logic. Requires a developer or a tech-comfortable founder.
Choose Custom if: You have unique fulfilment logic, multi-vendor workflows, B2B pricing tiers, or are scaling past ₹5Cr GMV and need performance the off-the-shelf platforms can't deliver.

We build on all three depending on what the business actually needs. See our e-commerce development services — and if you're not sure which platform fits, the discovery call helps us figure that out before we quote.

What should you verify before using this E-Commerce guide?

Before acting on shopify vs woocommerce vs custom ecommerce india 2026, verify the current rules or platform behavior with the Core Web Vitals. The practical answer depends on your business model, state, turnover, documents, software stack, and whether the decision affects tax, customer data, paid media spend, or a production workflow.

Use this article as a working checklist, then confirm LCP, INP, CLS, mobile performance, image delivery, and JavaScript loading constraints. In our audits, most expensive mistakes do not come from ignoring the whole process. They come from one stale assumption, one mismatched address, one missing event, or one automation path that nobody tested after launch.

Checkpoint	Why it matters	Where to confirm
Current rule or platform status	Limits, forms, policies, and APIs can change after a blog update.	Core Web Vitals
Your exact business case	A local shop, freelancer, D2C store, agency, and SaaS team rarely need the same next step.	Documents, invoices, campaign data, analytics setup, or workflow logs
Implementation evidence	The safest website decision is backed by proof, not memory or screenshots from an old setup.	Portal acknowledgement, dashboard export, invoice sample, test lead, or error log

How do we apply this in real business work?

We start with the smallest decision that can be verified. For compliance work, that means matching PAN, address, bank, invoices, and portal status before filing. For websites, marketing, analytics, and automation, it means testing the real user path from first click to final record. The boring checks catch the costly failures.

A useful rule: if a claim changes money, tax, reporting, or customer communication, keep evidence for it. Save the acknowledgement, export the report, test the form, and note the date you verified the source. That gives you a clean trail when a client, officer, platform, or internal team asks why the setup was done that way.

When should you get expert review?

Get expert review when the next action can create tax exposure, lost reporting data, ad waste, broken customer communication, or production downtime. A simple self-check is enough for low-risk learning. A filed return, new registration, tracking migration, paid campaign restructure, or live automation deserves a second set of eyes before it affects customers or records.

How often should this be rechecked?

Recheck the decision whenever your turnover, state, product mix, campaign budget, website stack, analytics property, or workflow ownership changes. Also recheck it after major portal updates, platform policy changes, annual filing deadlines, and vendor migrations. The guide is useful today only if the facts behind it still match your business.

What is the fastest safe way to decide?

Write the decision in one sentence, list the proof needed for that sentence, and verify only those items first. This keeps the work focused. If the proof confirms the decision, proceed. If one item is unclear, pause and resolve that point before changing filings, campaigns, tracking, website code, or automation logic.

What can go wrong if you skip verification?

The usual failure is not dramatic at first. It looks like a rejected application, a wrong tax invoice, a missing conversion, a duplicate lead, a broken report, or a workflow that silently stops. Those small failures become expensive when nobody notices them until month-end reporting, filing day, or a customer escalation.

What evidence should you keep after making the change?

Keep enough evidence to reconstruct the decision later. For a compliance topic, that usually means the application reference number, registration certificate, invoice sample, return acknowledgement, payment challan, notice reply, or source link checked on the day of filing. For a website, campaign, analytics setup, or automation, keep the before-and-after screenshot, test submission, dashboard export, webhook log, and the exact setting that changed.

This matters because most business fixes are revisited months later, when nobody remembers the original reason. A short evidence trail makes audits faster, handovers cleaner, and vendor conversations more precise. It also keeps the advice in this guide tied to your real operating context instead of becoming a generic checklist that gets copied without review.

Date checked: record when the official source, dashboard, or portal screen was reviewed.
Business context: note the entity, state, product, campaign, property, or workflow affected.
Proof of action: save the acknowledgement, report export, test result, or live URL.
Owner: assign one person to re-check the item when rules, tools, or business volume change.

Repeat this check whenever rules, platform settings, business volume, or ownership changes.

Which next step should you take after reading this?

Turn the article into one action list. Mark what is already true, what needs proof, and what needs expert review. If you want to go deeper, compare this guide with Websites for E-commerce, E-commerce Website Build, and Website Design & Development. Then update the decision only after the official source and your own records agree.

Shopify vs WooCommerce vs Custom Ecommerce India 2026