An online store is a system, not a webpage
Anyone can put products on a page. A store that actually sells is a chain of small decisions done right: how products are found, how the price is presented, how few taps stand between "I want this" and "payment done", what happens after the order, and how trust is built for a buyer who has never met you. I build that whole chain — and after 11+ years of web development, I can tell you the chain is where the money is, not the homepage banner.
What a complete build includes
Catalogue done properly
Categories that mirror how customers think, filters matching how they choose (size, price, brand, use-case), and product pages that sell: multiple photos with zoom, an unmissable price, stock status, delivery estimate, specifications in scannable form and a review block. Every product page gets a clean URL, meta tags and product schema so it can rank on Google individually — your catalogue quietly becomes your biggest SEO asset.
Checkout discipline
Guest checkout allowed, address form trimmed to essentials, mobile-number-first flows for India, saved details for repeat buyers, and COD offered where your margins survive it. Every field removed from checkout is measurable money; I remove ruthlessly.
Payments that inspire confidence
UPI, cards, netbanking and wallets through the gateway that suits your volume and settlement needs — Razorpay, PhonePe, Cashfree, PayU or your preference. Card details never touch your server (the gateway handles them under its own security certification), refunds are manageable from your panel, and the account is opened in your business name from day one.
Order operations your staff can run
A dashboard for new orders, packing states, shipping updates and returns; automated order confirmations on WhatsApp and email; GST-ready invoices generated automatically; and CSV exports for your accountant. The store must fit into your daily routine, or it will be abandoned by Diwali — so I design the operations side with the person who will actually run it.
Trust furniture
Visible return and delivery policies, a real address and phone, SSL everywhere, and review collection built into the post-delivery flow. A store with twenty honest reviews outsells a silent store at any price point; we engineer the asking so reviews accumulate on their own.
Platform choice, honestly
WooCommerce gives full control and suits stores that also publish content; costs are mostly one-time. Shopify charges monthly but removes server worries; excellent for fast launches and lean teams. Custom-coded stores win when your selling flow is unusual — B2B pricing tiers, made-to-order configurators, wholesale portals. In our first meeting I'll recommend one for YOUR situation and tell you exactly why, including the costs over three years, not just year one.
Growth after launch
Launch is the midpoint. Then: product-page SEO tuned on real search data, abandoned-cart recovery (politely persistent, never spammy), remarketing to visitors who compared and left, festival campaign support, and a monthly look at what sells so the catalogue evolves. Stores I've built follow a familiar curve — modest first month, then compounding as pages rank and reviews stack. The owners who feed the machine (photos, offers, replies to reviews) get the steep version of that curve.
The mistakes that sink new stores
Launching with 500 half-described products instead of 50 great ones. Photographing products badly — phone photos are fine, dark blurry photos are not. Hiding delivery charges until the last step (the single biggest cart-killer). Ignoring the mobile experience where 80% of your buyers are. And treating the store as finished on launch day. Each of these is avoidable, and avoiding them is part of what you're hiring.
Start with a number, not a guess
Book a free estimate meeting and bring your product list (even rough). You'll leave with a feature plan, an itemised cost, and honest advice on platform and phasing — including which features can wait so the launch fits your budget. Or send an enquiry below and I'll reply within a few hours.
A pricing guide you can hold quotations against
eCommerce quotes vary wildly because the word covers wildly different builds. Anchor points from my desk: a focused single-brand store (up to ~100 products, standard payments and shipping) runs Rs. 40,000–70,000. Larger catalogues, custom shipping rules, or B2B pricing tiers push toward Rs. 1,00,000. Multi-vendor marketplaces — where outside sellers list, sell and get paid — start around Rs. 1,50,000 because you're really buying three systems: the store, the seller panel and the settlement logic. Recurring costs stay modest: hosting a few thousand a year, gateway fees ~2% per transaction, and whatever care plan you choose. When a quote lands far below these bands, the missing money is usually hiding in the admin panel, the mobile experience, or your own ownership of the accounts — ask specifically about all three.
The launch playbook, week by week
Week 1: catalogue structure agreed, payment gateway application filed (KYC takes days, so it starts first), design direction approved. Weeks 2–3: build on a staging link while you prepare product photos and descriptions to the simple template I give you — this parallel track is what keeps launches on schedule. Week 4: your products loaded (I bulk-import from your sheet), test orders end to end including refunds, COD flows verified, GST invoice format confirmed with your accountant. Launch week: DNS, SSL, live payment verification with a real small order, Google Merchant and Search Console submission, and your team's training session — orders, refunds, offers, product edits. Weeks 5–8: the calibration period — watching real carts, fixing the friction real buyers reveal, and setting up abandoned-cart recovery once there are carts to recover.
Operations that survive festival season
Indian eCommerce lives and dies in October–November. Stores I build are load-tested for spikes, and Commerce-level care plans include pre-festival readiness: server headroom checked, backup taken, offer banners scheduled, and a same-day support window through the peak. The difference between a Diwali that doubles your month and one that crashes your checkout is entirely preparation — and it's cheap compared to the alternative.
Beyond the store: where orders actually come from
A store without traffic is a warehouse without a road. The same product pages built for buyers are built for Google — schema, clean URLs, real descriptions — so organic search compounds from day one. WhatsApp catalogue integration turns your existing chat customers into structured orders. And when you're ready for ads, the conversion tracking is already wired, so campaigns optimise on real purchases from their first rupee. I offer all three as itemised add-ons, sequenced to your budget, with the honest ordering advice included: fix conversion before buying traffic, always.
Two store stories
The boutique that left Instagram DMs behind. A clothing seller ran everything through DMs — orders lost in chat, sizes confused, payments chased. Her store moved the catalogue online with size charts and prepaid + COD; DM enquiries became links to product pages. Within two months, order errors nearly vanished and average order value rose, because a proper catalogue upsells in ways a chat never can.
The hardware trader who went B2B online. A dealer wanted wholesale ordering without exposing wholesale prices publicly. His store gates pricing behind approved logins: retail visitors see a catalogue and enquiry buttons; verified dealers see their tier pricing and order in bulk with credit terms noted. One build, two businesses served — the kind of flow where custom eCommerce earns its cost.
A pricing guide you can hold quotations against
eCommerce quotes vary wildly because the word covers wildly different builds. Anchor points from my desk: a focused single-brand store (up to ~100 products, standard payments and shipping) runs Rs. 40,000–70,000. Larger catalogues, custom shipping rules, or B2B pricing tiers push toward Rs. 1,00,000. Multi-vendor marketplaces — where outside sellers list, sell and get paid — start around Rs. 1,50,000 because you're really buying three systems: the store, the seller panel and the settlement logic. Recurring costs stay modest: hosting a few thousand a year, gateway fees ~2% per transaction, and whatever care plan you choose. When a quote lands far below these bands, the missing money is usually hiding in the admin panel, the mobile experience, or your own ownership of the accounts — ask specifically about all three.
The launch playbook, week by week
Week 1: catalogue structure agreed, payment gateway application filed (KYC takes days, so it starts first), design direction approved. Weeks 2–3: build on a staging link while you prepare product photos and descriptions to the simple template I give you — this parallel track is what keeps launches on schedule. Week 4: your products loaded (I bulk-import from your sheet), test orders end to end including refunds, COD flows verified, GST invoice format confirmed with your accountant. Launch week: DNS, SSL, live payment verification with a real small order, Google Merchant and Search Console submission, and your team's training session — orders, refunds, offers, product edits. Weeks 5–8: the calibration period — watching real carts, fixing the friction real buyers reveal, and setting up abandoned-cart recovery once there are carts to recover.
Operations that survive festival season
Indian eCommerce lives and dies in October–November. Stores I build are load-tested for spikes, and Commerce-level care plans include pre-festival readiness: server headroom checked, backup taken, offer banners scheduled, and a same-day support window through the peak. The difference between a Diwali that doubles your month and one that crashes your checkout is entirely preparation — and it's cheap compared to the alternative.
Beyond the store: where orders actually come from
A store without traffic is a warehouse without a road. The same product pages built for buyers are built for Google — schema, clean URLs, real descriptions — so organic search compounds from day one. WhatsApp catalogue integration turns your existing chat customers into structured orders. And when you're ready for ads, the conversion tracking is already wired, so campaigns optimise on real purchases from their first rupee. I offer all three as itemised add-ons, sequenced to your budget, with the honest ordering advice included: fix conversion before buying traffic, always.
Two store stories
The boutique that left Instagram DMs behind. A clothing seller ran everything through DMs — orders lost in chat, sizes confused, payments chased. Her store moved the catalogue online with size charts and prepaid + COD; DM enquiries became links to product pages. Within two months, order errors nearly vanished and average order value rose, because a proper catalogue upsells in ways a chat never can.
The hardware trader who went B2B online. A dealer wanted wholesale ordering without exposing wholesale prices publicly. His store gates pricing behind approved logins: retail visitors see a catalogue and enquiry buttons; verified dealers see their tier pricing and order in bulk with credit terms noted. One build, two businesses served — the kind of flow where custom eCommerce earns its cost.
A pricing guide you can hold quotations against
eCommerce quotes vary wildly because the word covers wildly different builds. Anchor points from my desk: a focused single-brand store (up to ~100 products, standard payments and shipping) runs Rs. 40,000–70,000. Larger catalogues, custom shipping rules, or B2B pricing tiers push toward Rs. 1,00,000. Multi-vendor marketplaces — where outside sellers list, sell and get paid — start around Rs. 1,50,000 because you're really buying three systems: the store, the seller panel and the settlement logic. Recurring costs stay modest: hosting a few thousand a year, gateway fees ~2% per transaction, and whatever care plan you choose. When a quote lands far below these bands, the missing money is usually hiding in the admin panel, the mobile experience, or your own ownership of the accounts — ask specifically about all three.
The launch playbook, week by week
Week 1: catalogue structure agreed, payment gateway application filed (KYC takes days, so it starts first), design direction approved. Weeks 2–3: build on a staging link while you prepare product photos and descriptions to the simple template I give you — this parallel track is what keeps launches on schedule. Week 4: your products loaded (I bulk-import from your sheet), test orders end to end including refunds, COD flows verified, GST invoice format confirmed with your accountant. Launch week: DNS, SSL, live payment verification with a real small order, Google Merchant and Search Console submission, and your team's training session — orders, refunds, offers, product edits. Weeks 5–8: the calibration period — watching real carts, fixing the friction real buyers reveal, and setting up abandoned-cart recovery once there are carts to recover.
Operations that survive festival season
Indian eCommerce lives and dies in October–November. Stores I build are load-tested for spikes, and Commerce-level care plans include pre-festival readiness: server headroom checked, backup taken, offer banners scheduled, and a same-day support window through the peak. The difference between a Diwali that doubles your month and one that crashes your checkout is entirely preparation — and it's cheap compared to the alternative.
Beyond the store: where orders actually come from
A store without traffic is a warehouse without a road. The same product pages built for buyers are built for Google — schema, clean URLs, real descriptions — so organic search compounds from day one. WhatsApp catalogue integration turns your existing chat customers into structured orders. And when you're ready for ads, the conversion tracking is already wired, so campaigns optimise on real purchases from their first rupee. I offer all three as itemised add-ons, sequenced to your budget, with the honest ordering advice included: fix conversion before buying traffic, always.
Two store stories
The boutique that left Instagram DMs behind. A clothing seller ran everything through DMs — orders lost in chat, sizes confused, payments chased. Her store moved the catalogue online with size charts and prepaid + COD; DM enquiries became links to product pages. Within two months, order errors nearly vanished and average order value rose, because a proper catalogue upsells in ways a chat never can.
The hardware trader who went B2B online. A dealer wanted wholesale ordering without exposing wholesale prices publicly. His store gates pricing behind approved logins: retail visitors see a catalogue and enquiry buttons; verified dealers see their tier pricing and order in bulk with credit terms noted. One build, two businesses served — the kind of flow where custom eCommerce earns its cost.
A pricing guide you can hold quotations against
eCommerce quotes vary wildly because the word covers wildly different builds. Anchor points from my desk: a focused single-brand store (up to ~100 products, standard payments and shipping) runs Rs. 40,000–70,000. Larger catalogues, custom shipping rules, or B2B pricing tiers push toward Rs. 1,00,000. Multi-vendor marketplaces — where outside sellers list, sell and get paid — start around Rs. 1,50,000 because you're really buying three systems: the store, the seller panel and the settlement logic. Recurring costs stay modest: hosting a few thousand a year, gateway fees ~2% per transaction, and whatever care plan you choose. When a quote lands far below these bands, the missing money is usually hiding in the admin panel, the mobile experience, or your own ownership of the accounts — ask specifically about all three.
The launch playbook, week by week
Week 1: catalogue structure agreed, payment gateway application filed (KYC takes days, so it starts first), design direction approved. Weeks 2–3: build on a staging link while you prepare product photos and descriptions to the simple template I give you — this parallel track is what keeps launches on schedule. Week 4: your products loaded (I bulk-import from your sheet), test orders end to end including refunds, COD flows verified, GST invoice format confirmed with your accountant. Launch week: DNS, SSL, live payment verification with a real small order, Google Merchant and Search Console submission, and your team's training session — orders, refunds, offers, product edits. Weeks 5–8: the calibration period — watching real carts, fixing the friction real buyers reveal, and setting up abandoned-cart recovery once there are carts to recover.
Operations that survive festival season
Indian eCommerce lives and dies in October–November. Stores I build are load-tested for spikes, and Commerce-level care plans include pre-festival readiness: server headroom checked, backup taken, offer banners scheduled, and a same-day support window through the peak. The difference between a Diwali that doubles your month and one that crashes your checkout is entirely preparation — and it's cheap compared to the alternative.
Beyond the store: where orders actually come from
A store without traffic is a warehouse without a road. The same product pages built for buyers are built for Google — schema, clean URLs, real descriptions — so organic search compounds from day one. WhatsApp catalogue integration turns your existing chat customers into structured orders. And when you're ready for ads, the conversion tracking is already wired, so campaigns optimise on real purchases from their first rupee. I offer all three as itemised add-ons, sequenced to your budget, with the honest ordering advice included: fix conversion before buying traffic, always.
Two store stories
The boutique that left Instagram DMs behind. A clothing seller ran everything through DMs — orders lost in chat, sizes confused, payments chased. Her store moved the catalogue online with size charts and prepaid + COD; DM enquiries became links to product pages. Within two months, order errors nearly vanished and average order value rose, because a proper catalogue upsells in ways a chat never can.
The hardware trader who went B2B online. A dealer wanted wholesale ordering without exposing wholesale prices publicly. His store gates pricing behind approved logins: retail visitors see a catalogue and enquiry buttons; verified dealers see their tier pricing and order in bulk with credit terms noted. One build, two businesses served — the kind of flow where custom eCommerce earns its cost.