Skip to content
PRS India

D2C, marketplace and B2B commerce

Ecommerce Development

Commerce platforms where the checkout turns visits into sales and the back office numbers match. They have multi-warehouse stock, correct GST invoices, marketplace sync and payments that never leave an order stuck.

Last updated

  • Checkout that sells on a 4G phone — under 1.5s before you can use it
  • Marketplace, D2C and shop stock matched against one catalogue
  • GST-correct invoices: HSN, place of supply, e-invoice and e-way bill
  • Payment webhooks checked on the server — no orders that are paid but not confirmed
What this is

The storefront is the easy part.

Selling online in India is not a storefront problem. The storefront is the easy part. The hard part is that your Amazon settlement report, your Shopify payouts and your Tally ledger differ by ₹40,000 every month and nobody can say why. It is that 28% of your COD orders come back as RTO and the courier's reason codes are useless. It is that your GST rate depends on HSN code and place of supply, and your invoice template knows neither.

We build commerce systems for brands that have outgrown the ready-made template. This means multi-warehouse stock, marketplace and D2C running from one catalogue, subscription and rental models, B2B price levels, and ONDC. The customer sees a fast, clean checkout. Your operations team sees orders that match, stock that is right, and invoices that pass an audit.

Sometimes the right answer is Shopify Plus with a well-built theme and three custom apps. Sometimes it is headless Next.js over a Laravel commerce core, because your pricing rules will never fit into somebody else's data model. Neither one pays us a commission, so we will tell you which one you really need.

The real problems

What is actually costing you money.

None of these get fixed by a new theme.

  • Your settlements do not reconcile

    Marketplace payouts take off commissions, shipping and returns in a report that is hard to read. Your Tally ledger says one number, the settlement says another, and the gap grows every month.

  • One in four COD orders comes back

    You have paid for forward shipping, return shipping and packing on an order that earned nothing. Nobody checks the risk before dispatch.

  • You oversold on the sale day

    Amazon, the D2C site and the retail POS each keep their own stock count. The last unit sold three times and you had to cancel two customers.

  • Checkout takes six seconds to load

    Four analytics pixels, a chat widget and a review app all slow the page from showing. More than 75% of mobile shoppers leave, and your ad spend pays for it.

  • Invoices will not survive an audit

    The wrong GST split on inter-state orders, no HSN on the items, credit notes typed by hand. Your GSTR-1 does not match your sales register.

  • Nobody can find anything

    Search is a plain SQL LIKE query. A misspelt brand name returns zero results, and a third of your buyers never see the product they came for.

What fixing the plumbing is worth.

Middle result across D2C and B2B commerce projects in the twelve months after launch.

34%
Lift in mobile conversion

Checkout rebuilt, outside scripts loaded later

31%
Reduction in RTO

COD risk scores plus address checks

0
Oversells on sale day

One stock pool with reserved stock

9hrs/wk
Ops time returned

No more matching numbers by hand

The platform call

Shopify, headless, or a commerce core you own.

  Shopify Plus Headless (Next.js + API) Custom Laravel core
Time to first revenue 6–8 weeks 10–14 weeks 14–20 weeks
Complex or contract-based B2B pricing Painful Possible Native
Subscription, rental, made-to-order App-dependent Yes Yes
Platform fee on GMV Yes Yes, if Shopify backend No
Storefront performance ceiling Good Excellent Excellent
Deep ERP / Tally integration Via middleware Yes Native
Sensible when GMV is Under ₹15 cr ₹15–60 cr Above ₹40 cr or unusual model
What you get

The commerce system, not just the shop window.

A checkout built for 4G

Under 1.5 seconds before you can use it on a mid-range Android. Outside scripts loaded later or removed. One-page checkout with UPI first, because that is how India pays.

One stock pool, every channel

Stock reservation, a safety buffer for each channel, and sync to Amazon, Flipkart, Myntra and your POS within moments. The same unit cannot be sold twice.

Payments that reconcile themselves

Razorpay, PhonePe, Cashfree. Webhooks checked on the server, order confirmation that cannot run twice, a check every fifteen minutes for missed payments, and a settlement report that matches your ledger.

GST done correctly

Rates set by HSN, place-of-supply rules, e-invoice IRN and QR from the IRP, e-way bills, and credit notes made against the original invoice.

Shipping and RTO control

Choosing the courier by pincode and SLA, delivery checks at checkout, COD risk scores, and a returns process your warehouse can really follow.

Search that finds things

Search that forgives typing mistakes, knows similar words, and has filters, on Algolia or Meilisearch. Display rules you control without a developer.

How we build

Replatforming without a revenue hole.

Nobody turns off a working store to find out if the new one sells. We move over in stages.

  1. 01

    Commercial and technical audit

    2 weeks

    We follow one order from start to finish: from ad click to checkout to payment webhook to warehouse pick to courier manifest to invoice to the accounting ledger. Every place it breaks or needs a person gets written down. That map, not a wish list of features, becomes the scope.

  2. 02

    Catalogue and data model

    2–3 weeks

    Variants, bundles, HSN codes, tax classes, pricing tiers, warehouse locations. Cleaning the catalogue is dull work, and it is where most platform moves fail. We do it before we build anything on top of it.

  3. 03

    Storefront and checkout

    4–7 weeks

    Product, listing and cart pages built to a speed limit, with the checkout treated as its own product. We A/B test the payment order, the address form and the COD check on real traffic wherever there are enough visitors.

  4. 04

    Back office and integrations

    4–6 weeks

    Order management, stock sync, courier choice, GST invoicing, and the links to Tally, Zoho Books or your ERP. This runs at the same time as the storefront, and it is where the money is saved.

  5. 05

    Staged cutover

    2 weeks

    The redirect map is ready before launch, not after. We move a small part of the traffic first, watch sales, errors and Search Console every day, then move the rest. The old store stays ready until the numbers say we do not need it.

  6. 06

    Peak-season hardening

    Ongoing

    Before your Diwali or end-of-season sale we test the site at three times your expected peak, warm up the caches, practise what happens when things fail, and keep a team on call for the first six hours. Nobody wants to find a database connection limit at 12:01am.

The stack

Commerce tooling that fits the Indian rails.

Shopify Plus
Hydrogen
MedusaJS
Laravel commerce core
WooCommerce
Next.js storefront
FAQ

The commerce questions worth asking.

Still have a question?

If your catalogue is simple, your pricing is simple and you want to be live in eight weeks, Shopify Plus is usually the honest answer. We will build you a fast, custom-themed store on it. You outgrow it when pricing depends on the customer contract, when you run rental or subscription models it cannot handle, when B2B and D2C need different catalogues, or when platform fees on your GMV cost more than an engineering team. This usually happens around ₹15–25 crore of yearly GMV.

This is one of the most common jobs we take. We put one trusted source in the middle. It can be your ERP, an OMS like Unicommerce, or a service we build. Every channel reads and writes through it with stock reservation, so the same unit cannot be sold twice. Amazon, Flipkart, Myntra, your D2C site and your retail POS all use one pool. Overselling on a sale day is a design failure, not bad luck.

Yes, properly. Tax is worked out from HSN code and place of supply. Sales within a state split into CGST and SGST, and sales between states become IGST, without anyone editing a spreadsheet. Above the turnover limit we connect to the IRP for e-invoice IRN and QR, and to the e-way bill portal for consignments above the value limit. Credit notes for returns are made against the original invoice, so your ledger and your GSTR-1 really match.

Several clear things. Address checks and pincode delivery checks at checkout, not after dispatch. A risk score on COD orders using order value, pincode history and customer history. High-risk orders get a WhatsApp or IVR confirmation before they are packed. Part-prepay offers for risky groups of buyers. And a reason-code dashboard so you can see which couriers and pincodes really cause the returns. Brands usually see RTO fall by a third within two quarters.

By never trusting the browser. The order is confirmed by a signed message from the payment gateway to our server. We check it against the payment ID and amount, and make sure a retry cannot fulfil the order twice. A matching job runs every fifteen minutes, asks the gateway about pending payments and fixes anything the webhook missed. Customers who paid always get their order, and your support team stops giving manual refunds every morning.

Yes, and this is where most platform moves lose money. We scan the existing site, match every ranking URL to its new address, and set up 301 redirects as part of the launch, not as a later task. Structured data, canonicals and product feeds for Google Shopping and Meta carry over. We keep the old sitemap live for a while and watch Search Console every day for the first month. A traffic drop of more than a few percent is treated as an emergency.

Bring us the order that never reconciles.

Send the settlement report, the Tally export and the number that will not tie out. We will tell you where it breaks and what it costs to fix.

Let's talk ecommerce development

Bring us the hard version of the problem.

A senior engineer reads every enquiry. You'll get a real answer — scope, risk and a number — within one business day.