Commerce built for margin, not just for launch

Across the stores we operate, the relationship between load time and conversion is brutally consistent. Moving a mobile storefront from a 4.2-second to a 1.4-second Largest Contentful Paint typically lifts conversion by 30 to 60% on the same traffic and the same creative. No A/B test we have run on copy, colour or layout has ever produced a swing of that size.

The usual culprits are equally consistent: an app ecosystem that has accumulated over two years, each one injecting a script into every page; hero images uploaded at 4000 pixels wide; a review widget that blocks rendering; and a theme that loads its entire JavaScript bundle before the first product image appears. We audit, we remove, we replace the genuinely necessary with server-side or facade-loaded equivalents, and we hold the line with a performance budget after launch.

There is no universally correct answer, and agencies that only sell one option will tell you theirs is it. Shopify is superb when your catalogue is straightforward, your checkout needs are standard, and your team wants to run merchandising without engineers. Its checkout converts extremely well and you should think hard before giving that up.

Headless makes sense when design and performance requirements exceed what a theme can express, when you have significant content alongside commerce, or when you sell across several channels from one catalogue. You keep Shopify's checkout and back office and gain complete front-end freedom — at the cost of a build that needs engineers to maintain.

Custom is right for a narrower set: B2B with customer-specific price lists, credit terms and approval workflows; marketplaces with multi-vendor settlement; or products configured rather than picked. Trying to force these onto a retail platform produces a system that fights you forever.

Most D2C brands we meet are making spend decisions on numbers that are quietly wrong. The platform dashboard claims more orders than the bank account shows, browser-side pixels miss a third of events, and nobody can say what a customer acquired in March was actually worth by September.

We fix the measurement layer first, because optimising against bad numbers is worse than not optimising. Events are captured server-side from the commerce backend — the source of truth for what actually got paid for — then forwarded to advertising platforms with proper deduplication. Orders, refunds and repeat purchases land in a warehouse where cohort, LTV and contribution margin can be computed honestly. Only then does channel optimisation mean anything.

Once a catalogue passes a few hundred SKUs, discovery becomes the constraint. Native platform search is generally poor at typo tolerance, synonyms and Indian-language product names, and the default collection sort rarely reflects what actually sells. We install a real search index, tune it against your query logs, and build faceting that matches how your customers think rather than how your ERP categorises.

We also build the merchandising controls your team actually needs: pinning, boosting, out-of-stock demotion, campaign collections that assemble themselves from rules, and a bundle engine that respects margin floors. These are the levers a good merchandiser pulls weekly, and giving them a self-service interface removes a standing developer dependency.

A store that sells well and ships badly destroys itself. We integrate the operational spine — inventory sync, courier allocation, serviceability by pincode, RTO risk scoring, returns and refunds, GST-compliant invoicing, and reconciliation against payment gateway settlements — so growth does not create chaos in the warehouse.

For brands selling on marketplaces alongside their own store, we build inventory reservation logic that prevents overselling across channels, which is the single most common cause of cancellation-driven rating damage on Amazon and Flipkart.

A significant share of our commerce work is not consumer at all. It is a manufacturer in the Howrah or Durgapur belt whose dealers still order by WhatsApp and phone, whose price list is a PDF with nine customer tiers, and whose sales team spends half its week transcribing orders into Tally.

For these clients we build dealer portals: customer-specific catalogues and pricing, credit limit visibility, order approval chains, dispatch tracking, and downloadable statements — connected directly to the ERP so nothing is re-keyed. The commercial case is rarely about new revenue; it is about removing forty hours a week of manual order entry and eliminating the pricing errors that quietly erode margin.