Answer first: eCommerce website development in India typically costs Rs 2,00,000 to Rs 8,00,000 and takes eight to sixteen weeks, and the decision that matters most is platform choice – because it determines your running costs, your flexibility and how painful your next three years will be. Shopify suits speed to launch; WooCommerce suits budget control and content-heavy stores; custom builds suit unusual catalogues or deep ERP integration. Getting the platform wrong is the most expensive mistake available in this category.
| Comparison | Customised Theme | Custom Development |
|---|---|---|
| Starting point | A pre-built theme, restyled to your brand | A blank file and your requirements |
| Design freedom | Within the theme's structure | Unrestricted |
| Typical cost | Rs 45,000 - Rs 1,50,000 | Rs 1,50,000 - Rs 8,00,000+ |
| Typical timeline | 3 - 6 weeks | 8 - 20 weeks |
| Page weight | Heavier - themes ship code for features you never use | Lighter - only what you need is built |
| Unusual requirements | Plugin workarounds, or not possible | Built directly |
| Long-term flexibility | Constrained by the theme and its updates | Extends as the business changes |
| Dependency risk | Theme or plugin abandoned by its author | Your codebase, your control |
A pattern worth noting: most Indian businesses that outgrow a platform do so because of catalogue complexity or B2B pricing rules, not because of traffic volume. If you have customer-specific pricing, bulk tiers or configurable products, factor that in on day one – it is the requirement most often discovered late.
The six decisions that actually determine success
How your catalogue is structured
Categories, filters, variants and attributes. This is the least exciting decision and the one that most affects whether customers find products and whether search engines can index category pages usefully. Restructuring a catalogue after launch means redoing URLs, redirects and rankings.
Payment gateways
In India this means Razorpay, PayU, CCAvenue, Cashfree or Stripe, plus UPI, which now carries the majority of digital retail transactions. Compare on settlement time and per-transaction cost, not just the headline rate. Support at least one card option, UPI, and net banking – and if you sell above a certain value, expect to be asked for cash on delivery.
Shipping and logistics integration
Shiprocket, Delhivery, Blue Dart or a direct courier integration. What matters commercially is automatic rate calculation at checkout and tracking that updates without anyone touching it. Manual shipping updates do not scale past a modest order volume, and they are the first thing to break during a sale.
GST and invoicing
Correct GST rates per product category, HSN codes, and compliant invoices generated automatically. Retrofitting tax handling is genuinely painful. Get it right in the build.
Who manages the store afterwards
Products, prices, stock and offers change constantly. If the admin interface requires a developer, the store will stagnate. Ask to use the admin during the build, not after handover – it is your team’s daily working environment for the next several years.
Where your traffic will come from
A store with no traffic plan is a shop in a field. Decide before launch whether you are relying on organic search, paid ads, marketplaces or social – because each requires different technical groundwork: product schema and category content for organic, feed structure and conversion tracking for paid
What eCommerce development involves technically
- Product architecture – categories, variants, attributes, inventory rules
- Storefront – responsive listings, product pages, search and filtering
- Cart and checkout – the highest-value screens on the site, and where most revenue is lost
- Payments – gateway integration, UPI, refunds, failure handling
- Order management – status flow, notifications, returns
- Integrations – shipping, accounting, CRM, marketing automation
- Performance – category pages with fifty products still need to load in under three seconds on mobile
- Search readiness – product schema, canonical handling for variants, crawlable filtered pages
The checkout is where money is lost
Most eCommerce conversion problems are checkout problems, and they are consistent across markets:
- Forced account creation. Offer guest checkout. This single change routinely lifts completion rates.
- Surprise costs at the final step. Show shipping and taxes early.
- Too many fields. Ask for what you need to fulfil the order and nothing else.
- No progress indication. People abandon when they cannot see how much is left.
- A single payment option. In India, missing UPI is missing a large share of buyers.
- A slow or broken mobile checkout. Test it one-handed, on mobile data, on a mid-range Android.
Running costs to plan for
Beyond the build: platform subscription if applicable, hosting, payment gateway charges of roughly 2% per transaction, shipping aggregator fees, premium plugin licences, and maintenance. For a modest store, expect Rs 15,000 to Rs 60,000 per month all in, before marketing spend.
That last clause matters. Businesses routinely budget the build and forget that a store without traffic generates no orders, which is why the traffic plan belongs in the project rather than after it.
