E-commerce development
The storefront is the easy part. What decides whether an e-commerce build succeeds is the catalogue model underneath it — and catalogue models are where businesses discover that their product data has been three inconsistent spreadsheets all along.
Catalogue is the whole problem
A product with three sizes and four colours is not twelve products, and it is not one product either. It is one product with a variant axis, a set of option combinations that may not all exist, and a pricing rule that might differ per combination, per customer, per quantity and per region. Getting this wrong is the single most common reason an e-commerce replatform runs late.
B2B makes it harder. Customer-specific price lists, quantity breaks, credit limits, approval workflows on orders above a threshold, and a sales rep who needs to place an order on a customer’s behalf. None of that fits a consumer storefront cleanly, and bolting it on afterwards is how you end up with a checkout nobody can safely change.
Platform or custom
If you are selling a few hundred reasonably conventional SKUs direct to consumers, a hosted platform is almost certainly correct and we will say so. Paying us to rebuild a checkout that Shopify already runs is not a good use of your budget, and we would rather build you the three integrations you actually need around it.
Custom becomes the right answer at the point your pricing, catalogue or fulfilment logic stops fitting the platform’s model — multi-vendor settlement, made-to-order configuration, complex B2B contract pricing, or an inventory position spread across warehouses, shops and a marketplace channel that all need to reconcile to one number.
The integrations that decide the project
Payment gateway is rarely the hard one. The hard ones are inventory synchronisation with the ERP or Tally, courier allocation and rate-shopping, GST-compliant invoicing, and returns — which touch stock, refunds, accounting and customer communication simultaneously and are almost never in the original scope.
We map these in discovery and build them as first-class parts of the system, because an e-commerce site whose stock figure disagrees with the warehouse is not a website problem, it is a business problem that shows up as a website.
What this actually covers
D2C storefronts
Fast, well-structured commerce sites with product schema, faceted search and a checkout that does not lose people at step three.
B2B ordering portals
Customer-specific pricing, quantity breaks, credit limits, order approvals and rep-assisted ordering.
Multi-vendor marketplaces
Seller onboarding, commission and settlement, payouts, dispute handling and the reporting each side needs.
Catalogue and PIM
A variant and attribute model that survives contact with your actual product range, plus bulk import that reports its failures.
ERP and inventory sync
One stock number across storefront, marketplace and shop floor, reconciled on a schedule you can inspect.
Commerce SEO
Product and category structured data, canonical handling for faceted URLs, and pagination that does not shred your crawl budget.
The sequence
Same shape on every engagement, so you always know what week you are in and what happens next.
Audit the product data
Before anything is designed we take a real export of your catalogue and find out what shape it is actually in. This is usually where the project’s true scope becomes visible.
Model catalogue and pricing
Variants, attributes, price lists and the rules that select between them. Written down and agreed before the storefront exists.
Build checkout and fulfilment together
Checkout is designed alongside the order state machine and the warehouse process, because a checkout that creates orders operations cannot fulfil is worse than no checkout.
Integrate, reconcile, then launch
ERP, courier and accounting integrations run in parallel with the real business for a period before cutover, so discrepancies surface while the old system is still there.
Handed over, in your accounts
Not a demo and a login. These are the artefacts you keep, and they are what makes leaving us possible.
- A catalogue and variant model documented against your real product range
- Payment, shipping and tax integrations with sandbox and live environments both working
- Product, breadcrumb and offer structured data emitted from the catalogue itself
- An order state machine — placed, paid, packed, shipped, delivered, returned — written down
- Admin tooling your team can actually run the business from
- Analytics and conversion tracking configured and verified end to end
Typically built with
- Next.js
- TypeScript
- PostgreSQL
- Medusa
- Shopify
- WooCommerce
- Razorpay
- Stripe
- Algolia
The selection principle is deliberately dull: largest hiring pool, longest support window. See why we choose these.
E-commerce, answered
The things people ask on the first call, written down so you do not have to.
Should we use Shopify or build a custom store?
Use Shopify if you are selling conventional products direct to consumers and your pricing and fulfilment fit its model. It is very good, and rebuilding what it already does is a poor use of your money — we would rather build the integrations you need around it. Build custom when your catalogue, pricing or fulfilment logic no longer fits: multi-vendor settlement, made-to-order configuration, contract B2B pricing, or inventory spread across several channels that must reconcile to one number. We will give you a straight recommendation in discovery, including the one where you do not need us for the storefront at all.
Can you integrate the store with our ERP or Tally?
Yes, and it is usually the part that decides the project timeline rather than the storefront. The pattern that works is a scheduled, inspectable reconciliation with an explicit conflict policy — not a live two-way write, which fails badly the first time one system is briefly unavailable. We run the integration alongside your existing process for a period before cutover so discrepancies surface while the old system is still there to check against.
How do you handle GST invoicing and Indian compliance?
GST-compliant invoice generation, HSN codes on products, state-wise tax determination and e-invoicing where your turnover requires it. These are modelled into the order and product schema from the start rather than added as a report at the end, because retro-fitting tax logic into an order history that was not built for it is genuinely painful.
Will the site rank? What about SEO for e-commerce?
Commerce SEO is mostly architecture, and it is decided at build time. Faceted navigation that generates a million crawlable URL combinations will consume your crawl budget and dilute your category pages; the fix is canonical and robots handling designed in, not bolted on. We emit Product, Offer and BreadcrumbList structured data from the catalogue itself so it cannot drift from what is on the page, and we keep category pages server-rendered. The content and link building side is a separate engagement — see digital marketing.
Can you build a multi-vendor marketplace?
Yes, and it is worth being clear that a marketplace is a substantially bigger build than a store. The storefront is perhaps a third of it. The rest is seller onboarding and verification, commission and settlement logic, payout scheduling and reconciliation, dispute handling, and separate reporting surfaces for buyers, sellers and you. The settlement model in particular needs to be right before anything is built, because it is close to impossible to change once real money has moved through it.
What usually comes with this
- BuildCustom Software DevelopmentCustom platforms, marketplaces and SaaS. We write the parts that are specific to your business and buy the parts that aren’t.Read more
- GrowDigital Marketing & SEOSEO and performance marketing measured against revenue, not impressions. We will show you the query data before you sign anything.Read more
- RunERP SolutionsImplementation, plus the custom modules the implementation always turns out to need in month four.Read more
- GrowUI/UX DesignProduct design and design systems. Usually the first thing that turns out to be wrong, and the cheapest thing to fix.Read more
Thinking about e-commerce?
Start with a call rather than a brief. Thirty minutes, no deck, and an honest answer about whether we are the right people for it.