What Drives Ecommerce Website Development Cost in India: A Practical Breakdown
By WebNest Studio Engineering Team · Published · Updated · 6 min read
Ask three agencies to quote for "an online store" and you can easily get three figures that are far apart. Usually they are not quoting for the same thing. One is pricing a theme on a hosted platform, another a WooCommerce site with a dozen plugins, and the third a custom storefront with its own order system. Each can be the right answer for a different business.
This breakdown covers the decisions that move the price of an Indian ecommerce site, roughly in the order they matter, and the running costs that continue after launch. It deliberately avoids rupee figures: rates vary by team and city, and a number without your scope attached is not useful. Use it to write a clear brief and to read the quotes that come back.
Decision 1: hosted platform, WooCommerce or a custom build
This choice affects cost more than any single feature.
Hosted platforms such as Shopify. You pay a monthly subscription and use the platform's checkout, hosting and security. Development work is mostly theme setup, configuration and apps, and it is the fastest way to launch a standard catalogue store. The trade-offs are recurring app subscriptions, limits on how far checkout and data can be customised, and platform fees. Indian stores usually connect a third-party payment gateway, so check the current plan terms for any transaction fee charged in that case.
WooCommerce on WordPress. The plugin is free; you pay for hosting, a theme, paid extensions and the time to keep WordPress, the theme and every plugin up to date. It suits stores that also need a strong content site. The cost that is easy to miss is maintenance: plugin conflicts and security updates need someone responsible for them.
A custom build, for example a React storefront with a Python or Java backend and PostgreSQL. It has the highest upfront cost, but no per-order platform fee and full control over checkout, data and integrations. It is justified when the business model does not fit a standard catalogue: made-to-measure products, configurable bundles, per-customer B2B pricing, subscriptions with unusual rules, or tight integration with an existing ERP or warehouse system.
A useful test: write down the five things that make your store different from a typical catalogue store. If a hosted platform plus well-supported apps can handle all five, start there.
Decision 2: catalogue and product complexity
A few hundred simple products with photos and a price are straightforward on any platform. Effort rises with:
- Variants and options such as size, colour and material, especially when stock is tracked per variant.
- Made-to-order or personalised products, where the customer enters measurements, uploads a file or picks components, and that data has to travel with the order to production.
- Catalogue imports from a supplier feed or an ERP, which need field mapping, validation and a schedule.
- Search and filtering across many attributes, which needs proper indexing to stay fast as the catalogue grows.
Decision 3: payments for Indian buyers
Indian customers expect UPI alongside cards, net banking and wallets. Payment gateways such as Razorpay, PayU, Cashfree and CCAvenue offer these through one integration. The integration is well documented; what separates a reliable store from a fragile one is the work around it:
- Confirming payment status on the server through the gateway's webhook or status API, never trusting the browser redirect alone.
- Handling a payment that succeeds after the customer has closed the tab, so the order is still confirmed.
- Making webhook handling idempotent, so a retried notification cannot confirm or refund an order twice.
- Full and partial refunds from the admin panel.
Gateway charges are per transaction and set by each gateway. Compare their current pricing pages rather than relying on anyone's summary.
Cash on delivery is still expected in many categories, and it adds work: limiting COD by pincode or order value, confirming COD orders before dispatch, and tracking parcels returned to origin when a customer refuses delivery. The cost of refused parcels belongs in your margin calculations, not only your development budget.
Decision 4: shipping and fulfilment
Shipping aggregators such as Shiprocket and couriers such as Delhivery provide APIs for pincode serviceability, rate calculation, label generation and tracking. A basic integration creates shipments and shows tracking links. A deeper one checks serviceability at checkout, chooses a courier by rules, handles returns and syncs delivery status back to the order automatically. Decide which of these you need on day one; the deeper version can follow once order volume justifies it.
Decision 5: GST invoicing and accounting
Your store needs tax invoices that show your GSTIN, the HSN code for each item and the correct tax split, CGST and SGST for sales within your state and IGST for sales to other states, plus credit notes for returns. Hosted platforms usually handle this through apps; a custom build has to implement it. If your accountant works in Tally, Zoho Books or similar, decide early whether orders flow there automatically or are exported on a schedule. Confirm your registration and invoicing obligations with your chartered accountant; the store should follow their requirements, not the other way round.
Decision 6: sale-day traffic
Festive sales and influencer campaigns create short, sharp spikes. On a hosted platform the provider handles most of the scaling. On WooCommerce or a custom build, plan for cached catalogue pages, an image CDN, a database sized and indexed for the busiest hour rather than the average one, and a load test before the sale rather than during it. Stock needs particular care: two customers must not both buy the last unit, so reserve stock inside a database transaction at checkout.
Running costs to plan for
The launch price is only part of the cost. Ask every vendor to list:
- Platform and app subscriptions, or hosting and paid plugin licences.
- Payment gateway charges per transaction.
- Shipping charges and the cost of returns, including refused COD parcels.
- Transactional email and SMS or WhatsApp notifications.
- Maintenance: security updates, platform and plugin updates, and fixes when an integration partner changes its API.
- Small improvements after launch, which every active store needs.
What to send agencies for comparable quotes
- Your platform preference, or why you are unsure.
- The number of products and variants, and how stock is managed today.
- Payment methods, including whether you need COD and where.
- Your shipping partners or the regions you ship to.
- How invoices and accounts are handled now.
- Existing systems to integrate, such as an ERP, POS or CRM.
- Expected orders on a normal day and on your biggest sale day.
- Three stores you like, and what specifically you like about each.
With the same brief in hand, quotes will differ for real reasons you can discuss, not because each vendor imagined a different store.
Frequently asked questions
Should a new brand start with a custom build?
Usually not. A hosted platform lets you test demand quickly. Move to a custom build when the platform's limits are costing you sales or margin and you can name those limits.
Can we move from Shopify or WooCommerce to a custom store later?
Yes. Plan the migration of products, customers and order history, and permanently redirect old product URLs to the new ones so search traffic is not lost.
Who is responsible for security on a custom store?
The development team, and it should be written into the contract: server-side payment verification, protected admin access, regular dependency updates and tested backups.
For an example of a custom build, see our VStitch case study, a made-to-measure fashion store with Razorpay payments and automated PDF invoices, or read about our web development service.