The honest answer to ecommerce website cost in India is a range: under Rs 50,000 for a small catalogue on a hosted platform, and Rs 5 lakh or more for a custom build with ERP sync and multi-warehouse logic. The gap is not agency greed. It is catalogue size, integrations and how much of the work you hand over. Before you compare quotes, work out which of those levers you are actually pulling.
This guide breaks the price down the way our team scopes a store build: platform, catalogue, design, integrations, content, and the running costs that start the day you go live. You will also see the line items owners routinely leave out of the budget and then have to fund in month two.
What does an ecommerce website cost in India?
Most Indian builds land in one of four bands. Under Rs 50,000 buys a hosted store with a theme and a small catalogue. Rs 50,000 to Rs 2 lakh covers a designed store with real integrations. Rs 2 to 5 lakh adds custom features and workflow, and Rs 5 lakh plus is application territory.
Those bands describe complexity, not quality. A store built at the lower end can outsell an expensive one if the products photograph well and the checkout is short. What the higher bands buy is custom logic: dealer pricing, warehouse-wise stock, approval flows, or an app-like front end on your own stack.
If you are comparing a store against a plain business site, the difference shows up clearly in a breakdown of business website pricing. A brochure site is a fixed set of pages. A store is a system with inventory, money movement and tax attached to it. Every quote you receive is really a quote for that system.
Platform choice sets the floor
Three routes are common in India: a hosted platform such as Shopify, a self-hosted WooCommerce build on WordPress, or a fully custom application. Hosted platforms trade a monthly subscription for speed of launch. Self-hosted builds trade a lower licence bill for more responsibility on hosting, updates and security. Custom applications cost the most and earn their keep only when your operations refuse to fit a standard cart.
Subscription and app pricing changes on every platform, and India-specific pricing changes too, so check the vendor's own pricing page on the day you decide rather than trusting a figure in any article. The pattern holds even when the numbers move: hosted stores push cost into recurring fees, and self-hosted stores push cost into build and maintenance. Our comparison of the two platforms for Indian sellers walks through that trade in detail.
The custom route deserves a hard test before you fund it. If your reason for going custom is speed, design control or SEO, a standard platform already handles all three. If the reason is dealer-specific pricing, multi-entity GST, or a catalogue that changes shape every season, then the argument for a bespoke build becomes real.
Why do two stores with the same design cost different amounts?
Because the catalogue does the work. Twenty products with one variant each is a weekend of data entry. Two thousand SKUs with size, colour and GST slabs behind them means taxonomy, bulk import, image handling and QA. Design is close to a fixed cost. Catalogue complexity scales with every row you add.
Ask every quote to state the SKU count it assumes and who is entering the data. A 300 product catalogue with three variants each is 900 rows of price, stock, weight, HSN code and images. If you supply that as a clean sheet, the build stays cheap. If the team has to chase it from WhatsApp photos and an old price list, data entry becomes a project of its own.
Variants are the quiet multiplier. Size and colour are simple. Size, colour, fabric and a made-to-order lead time is a matrix that affects stock rules, shipping weight and returns, and every extra axis adds testing time.
Photography, product content and the copy nobody budgets for
This is the line item owners forget most often. A store lives or dies on the product page, and the product page is photography plus description plus specification. Stock images will not do for physical goods, and phone photos on a cluttered table cost you conversions in a way no design fix repairs.
Budget for a shoot at the SKU level, not the project level. Studio time, a stylist for apparel, and post-production are priced per shot or per day, so ask two or three local studios for a per-SKU rate before you finalise the website budget. Descriptions follow the same logic: 40 products need 40 pieces of original copy, and thin duplicated text holds the whole store back in search, which is why getting product pages found on a large catalogue starts with copy only a seller can write.
Payments, shipping, GST and ERP integrations
Standard plumbing is cheap because it is already built. A Razorpay or UPI checkout, a shipping aggregator and order emails are configuration work on any mainstream platform. Cost appears when your operation is not standard.
The usual culprits: GST invoices with correct HSN codes and state-wise place of supply, stock syncing both ways with Tally or an ERP, courier serviceability by pincode, cash on delivery rules by order value, and WhatsApp Business order updates. Each one is an interface with someone else's system, and each one needs testing against real orders. Two or three of these together can move a project from one budget band to the next.
Count the fees as well as the build. Payment gateways take a cut of every transaction and the rate varies by method and provider, so read the current rate card on the gateway's own page before you model your margin. Shipping aggregators, SMS credits and WhatsApp message credits work the same way.
Here is how the main drivers move a project between bands.
| Cost driver | Keeps the price low | Pushes you to a higher band |
|---|---|---|
| Platform and build approach | Hosted platform, licensed theme, light customisation | Custom application on your own stack |
| Catalogue size and variants | Under 100 SKUs, simple variants, clean data sheet supplied | Thousands of SKUs, multi-axis variants, agency does the data entry |
| Design | Theme styled to your brand with a custom home page | Bespoke UI for every template, motion, product configurator |
| Integrations | One gateway, one shipping partner, basic GST invoice | ERP or Tally sync, multi-warehouse stock, dealer pricing tiers |
| Content and photography | You supply images, descriptions and specifications | Full studio shoot, model photography, copy written for every SKU |
What does it cost to run an ecommerce site after launch?
Running costs never stop, and they are why a cheap build can become an expensive store. Expect four recurring lines: hosting and domain, platform or plugin subscriptions, transaction fees on every order, and maintenance. Marketing sits on top of all of it and is usually the largest number of the lot.
Maintenance is not optional on a store. Platform updates, plugin conflicts, expired certificates and broken payment webhooks all cost sales while they are live. A monthly retainer covering updates, backups, uptime checks and a fix window is cheaper than a shut checkout on a Saturday. Our monthly upkeep routine sets out what that work actually covers.
Then there is demand. A store with no traffic is a warehouse with no road to it, and the budget for paid acquisition is a separate conversation from the build. Digital marketing retainers in India run from Rs 15,000 to Rs 2,00,000 or more per month depending on channels and scope. Plan the first six months of that spend before you approve the website quote.
How to scope a build you can afford
Scoping badly is what makes quotes look wildly different. Fix the inputs first, then ask for prices, and the numbers you get back become comparable.
- Count your real SKUs and variants, and put them in one sheet before you request quotes.
- List every system the store must talk to: gateway, courier, accounting, ERP, WhatsApp.
- Decide who writes descriptions and who shoots products, and price that work separately.
- Choose the platform on the shape of your operations, not on what a competitor uses.
- Ask each agency to quote build, content and first-year running costs as three separate figures.
- Launch with your best selling 30 products, then widen the catalogue after a month of real orders.
Before you sign anything, get these confirmed in writing.
- The SKU count and variant count the price assumes
- Who supplies product images, descriptions and specifications
- Named integrations, each with a test plan
- Who owns the hosting account, domain and platform logins
- Warranty window after launch, response time and retainer scope
- Training for your team on adding products and processing orders
We scope stores in four stages: Connect, Build, Launch and Optimise. Discovery settles the catalogue, the integrations and the content owner, and only then do we put a number on it. Most website projects run six to twelve weeks depending on catalogue and integration load, with a checkpoint every week. If you want a scoped figure for your own catalogue, send us your product list and integration needs.
Frequently asked questions
Can I launch an ecommerce site for under Rs 50,000?
Yes, if the catalogue is small, you use a hosted platform with a licensed theme, and you supply images and descriptions yourself. That budget buys configuration and light customisation, not bespoke design or deep integrations. It is a sensible way to test demand before committing to a bigger build.
Is Shopify cheaper than WooCommerce in India?
It is usually cheaper to launch and more expensive to keep, because you pay a subscription plus app fees every month. WooCommerce moves that spend into hosting, maintenance and developer time instead. Platform and app pricing changes often, so check both vendors' current pricing pages before you compare.
How long does an ecommerce build take?
Plan for six to twelve weeks. Catalogue preparation and photography usually take longer than the development, and integration testing needs real orders to verify properly. Projects slip when product data or images arrive late, not because code is slow.
Do I need GST invoicing built into the website?
If you sell taxable goods to businesses or across states, yes. You need correct HSN codes, place of supply and invoice numbering, either in the store or in the accounting system it connects to. Decide this before the build, because retrofitting tax logic is expensive.
Spending in the right order
The common mistake is a large build with nothing left for photography, content or traffic. Spend on the product page first, integrations second, design polish third. A modest store with strong product pages and a working checkout beats a beautiful one with no orders.
Ask for quotes that separate three numbers: build, content, and first-year running costs. Two of those follow you forever, so they matter more than the one-time figure. Our Pune build team works with sellers across Maharashtra and Gujarat, and Vadodara clients are served from the same Akurdi office. Tell us what you sell and we will scope it band by band, without guessing.
