E-commerce development, including the parts after the sale

Soham Dang builds e-commerce platforms end to end — storefront, checkout, inventory, delivery routing and the admin dashboards that run the business — including multi-vendor marketplaces and WebGL product visualisation.

The storefront is the part everyone specifies and the smallest part of the work. The system that keeps running after someone pays is where an e-commerce build actually succeeds or fails.

Reschedules, cancellations, refunds, stock that has to be right, and a delivery partner who needs a different view from the shop owner — none of it is glamorous and all of it is required.

What gets built

  • Storefront

    Product catalogue, search and filtering, responsive from 360px because that is where the traffic is.

  • Checkout that does not lose orders

    Razorpay integration where the order state is driven by a signature-verified webhook, not a browser redirect that can be closed.

  • Live inventory

    Stock accurate across concurrent orders, which is a data modelling problem before it is a feature.

  • Order lifecycle

    Rescheduling, cancellations and refund tracking — the parts that turn a store into a business.

  • Role-separated dashboards

    Admin, vendor and delivery-partner views showing different things from the same data.

  • Multi-vendor where needed

    Per-vendor inventory, delivery-zone routing and settlement, on one platform.

Why checkout is driven by webhooks

A browser redirect after payment can be closed, blocked, or lost when a mobile OS kills the tab during a bank-app handoff. Every one of those means the customer was charged and your system does not know.

A signature-verified webhook is server to server, so nothing the customer does can prevent it, and gateways retry on failure. The redirect keeps its job of showing a confirmation page — it just stops being the source of truth.

3D product visualisation, when it earns its place

For products that sell on form and finish, rotating the item answers a question a photograph cannot. The WebGL viewer built for Gaon Se Ghar Tak runs on Three.js and React Three Fiber, budgeted for mid-range Android — capped draw calls, instanced geometry, device-tiered quality.

For products that do not need it, 3D is bundle size and battery spent on a first impression. Being honest about which category you are in matters more than the technology.

Common questions

What e-commerce platforms has Soham Dang built?

Gaon Se Ghar Tak, a multi-vendor quick-commerce platform with delivery-zone routing, live inventory, Razorpay checkout and a WebGL 3D product viewer; Rohtak Shoe Co., a 3D storefront with admin and delivery-partner dashboards and a full order lifecycle; and Apsara Cafe, a food ordering app with live menu management and sales analytics.

Should I use Shopify or a custom e-commerce build?

Shopify or WooCommerce for a standard catalogue-and-checkout store — they are cheaper, faster to launch and someone else maintains them. Custom becomes right when the model is unusual: multi-vendor settlement, delivery-zone logic, or an order lifecycle the platform does not support.

How are payments handled?

Razorpay integration where order state is driven by a signature-verified backend webhook rather than the browser redirect, so a closed tab or dropped connection after payment cannot leave a paid order unrecorded.

Can a store support multiple vendors?

Yes. Multi-vendor means per-vendor inventory, delivery-zone routing and separate dashboards on one platform, which is what Gaon Se Ghar Tak does. It is a meaningfully larger build than a single-vendor store and worth being clear about up front.