Operations first
Stock, dispatch, shipping, returns, tax. Two hours here saves weeks later, and occasionally concludes that you are not ready to sell online yet.
E-commerce · Delhi NCR & remote
Building a catalogue and a checkout is a solved problem. What sinks most Indian online stores is everything after the payment succeeds — stock, courier, returns and the phone call asking where the order is.
Short answer
E-commerce website development builds an online store: product catalogue, cart, checkout, payment gateway, shipping and order management. The build decisions that matter are operational rather than visual — how stock is kept accurate, how orders reach your courier, and how a customer checks their order without phoning you.
Four details. A real reply the same day, from me.
01 The premise
Every store demo looks the same: a grid of products, a cart, a checkout. That part has been commoditised, and if a developer is spending your first meeting showing you cart animations, they are showing you the part that does not matter.
The decisions that determine whether an online store is profitable are almost all operational. Where does stock live, and what happens when the same item sells in the shop and on the website in the same hour? How does an order reach the courier — is somebody copying addresses into a portal? What does a customer do at 9pm when they want to know where their parcel is? Who handles a return, and does the refund reach the gateway automatically or by hand?
Get those wrong and the store creates work rather than revenue. A common outcome is a business that is technically selling online while two staff spend their day reconciling it. Get them right and the store runs with a fraction of the attention, which is the entire point of selling online.
02 Choosing
There is no universally right answer. There is a right answer for your margin, catalogue and operations.
| Route | When it is the right call |
|---|---|
| Shopify | Fast to launch, hosted, reliable, and a real ecosystem. Right for straightforward retail where the monthly fee and transaction cut are comfortably covered by your margin. |
| WooCommerce | You already run WordPress, want no platform fee, and accept that you now own the hosting, updates and security. Cheaper to run, more to maintain. |
| Custom PHP build | Your pricing, bundling or dispatch rules do not fit a platform, or you are integrating tightly with an existing ERP. Most control, most build cost. |
| Marketplace only | Amazon or Flipkart with no site of your own. Sometimes genuinely correct at the start — but you are renting the customer relationship, not owning it. |
03 Decisions
Each of these changes the build. Answering them late is how e-commerce projects overrun.
Free store review
Send me your store or describe the plan. I will tell you where the operational gaps are — the stock, dispatch and returns questions that decide whether this makes money or makes work.
Four details, and a real reply today.
04 Process
Stock, dispatch, shipping, returns, tax. Two hours here saves weeks later, and occasionally concludes that you are not ready to sell online yet.
Categories, variants, attributes and filters, modelled on how customers shop rather than how your supplier lists things.
The two screens that carry the money. Everything else is navigation.
Store, payment gateway, shipping, invoicing, and the admin your team will actually live in.
Real cards, real refunds, real courier bookings, before launch. Test-mode success proves very little.
05 Deliverables
— E-commerce
These sit next to an online store and are usually bought with it. Same person doing the work in each case.
— Questions
Straight answers, including the ones that cost me work. If yours is not here, ask it — I reply the same day.
Shopify if your retail is straightforward and your margin comfortably absorbs the monthly fee and transaction cut — it is reliable and fast to launch, and I will happily recommend it. Custom when your pricing, bundling or dispatch rules do not fit the platform, or you need deep integration with an existing system.
It scales with catalogue complexity and integrations, not with product count. Two hundred simple products cost less than twenty products with size, colour, custom pricing and an ERP connection. The integrations are usually the largest line, and I will show you that breakdown rather than a single number.
Razorpay and PayU are the usual choices for domestic sales; CCAvenue is common in older setups; Stripe matters if you sell internationally. They differ mainly in settlement time, per-transaction rates and support quality. Negotiate the rate — published rates are not always final.
Yes, and for a large part of the Indian market it is still expected. It brings its own problems — higher return-to-origin rates and cash reconciliation — so it is worth setting rules around it, such as a value cap or a pin-code allowlist.
One system has to be authoritative. Either the website owns stock and the counter checks it, or your existing POS owns it and the website reads from it. What fails reliably is two independent systems reconciled by hand.
It can, with a correct product feed and valid product structured data — price, availability, GTIN where one exists. Setting that up properly is part of the build rather than an afterthought, because a rejected feed is a common and frustrating way to lose that channel.
Free consultation · No obligation
Tell me what you sell, how stock is managed and who dispatches it. You will get a straight recommendation on platform and a fixed price for the build.
Name, number, email, what you need.