Skip to content
PRS India

ONDC · Omnichannel inventory · Settlements

Retail & Ecommerce Software

Retail has one hard problem: knowing how many you have and where. We build stock tracking with one true number, real ONDC protocol connection, and settlement matching that finds the margin marketplaces quietly deduct.

Last updated

  • Oversell rate under 0.2%
  • ONDC seller app, protocol-level
  • Every marketplace deduction validated
  • Offline-capable store billing
The real problem

You sold the last one twice.

Retail software has one hard problem: knowing, right now, how many of an item you have and where it is. The online store, the suggestions and the loyalty programme all depend on it. None of them work if you get this wrong. The moment you sell in more than one place, you have a stock-tracking problem in disguise. Places can be a website, Amazon, three stores, a quick-commerce partner, and now ONDC. The classic failure is selling the same last unit on two channels in the same minute, and then taking the penalty on your seller rating. We build the stock system first. Always. A beautiful store on top of stock numbers you cannot trust creates angry customers.

Talk about your channels
0.2%
Oversell rate

One true stock number for what you can promise, clear reservations with a TTL, and safe extra stock held back for each channel.

₹41
Recovered in year one

Marketplace deductions that did not match the commission agreement. Nobody was checking, because it all lived in a spreadsheet.

31%
Faster returns cycle

Returns handling planned as carefully as delivery. Returns are 20-30% of fashion GMV.

100%
Uptime at the till

Offline-capable store billing. A dropped connection is not a reason to stop taking money.

Where retail platforms actually break

Retail software has one hard problem and many easy ones that only look hard. The hard one is knowing, right now, how many of an item you have and where it is. Everything else depends on it: the online store, the suggestions and the loyalty programme. None of it works if this is wrong.

Inventory is a distributed systems problem wearing an apron

The moment you sell in more than one place, you have a stock-sharing problem. Places can be a website, a marketplace, three stores, a quick commerce partner, and now ONDC. The classic failure is selling the same last unit on two channels in the same minute.

The fix is not "sync more often". The fix is to keep one true number for what you can promise, set up reservations clearly with a TTL, and never let a channel hold stock it has not reserved. A marketplace that reads your feed every fifteen minutes needs a safe extra buffer held back. Otherwise it will oversell, and the penalty lands on your seller rating, not theirs. Store stock has to be counted. Cycle counting should be a routine part of the software, not a yearly event that everybody dreads.

ONDC is a protocol, not a marketplace, and that changes what you build

Teams keep treating the Open Network for Digital Commerce like another Amazon to list on. It is not. It is a set of protocol rules that you build into a seller app or a buyer app. The network then connects you with people who have never heard of you.

The effects are real. Your catalogue must be matched to the network's categories, and this work is boring but important. Order steps follow the protocol's life cycle, not yours. Cancellation, return, and issue-and-complaint flows are set by the protocol, and you must build them properly, even the ones you would rather skip. Payments are matched against the network, not against one party you can phone. It is real work, and it is worth doing for the reach. But it is not just a listing, and anyone who sells it to you as one has not built it.

Marketplace settlements are where the margin actually goes

Amazon and Flipkart do not pay you what the customer paid. They pay the customer's payment minus a commission, minus a closing fee, minus shipping, and minus whatever else they decided to deduct this week. It comes as one lump sum for hundreds of orders, on their schedule.

If your finance team matches this in Excel, they are not really matching it. They check that the total looks fine and move on. The deductions nobody checked are pure lost margin. We build a tool that reads the settlement report, matches every line to an order, and works out what the deduction should have been under your commission agreement. When it does not match, it adds the order to a list of differences. The money recovered usually pays for the module within a year.

The rest, briefly

Returns are 20 to 30 percent of fashion GMV, and the returns process deserves as much planning as delivery. GST across states, with the right place-of-supply and HSN codes. Store billing that keeps working when the internet does not, and syncs when it comes back. And a product catalogue that handles options like size and colour properly, because a catalogue that cannot show variants well will hold back every channel you connect to it.

Modules

What we build into a retail platform.

Inventory spine

One true number for what you can promise. Clear reservations with TTL. A buffer for each channel. Cycle counting as a routine.

ONDC seller app

Full protocol connection: catalogue category matching, the network order life cycle, and the complaint flows you would rather skip.

Settlement reconciliation

Every marketplace deduction matched to an order and re-worked against your commission agreement. Differences are listed, not assumed.

Storefront

Fast product pages that search engines can read, search that understands your catalogue, and a checkout that holds up on a sale day.

Store billing / POS

Works offline. Keeps taking payments and issuing invoices when the connection drops, then matches up without overselling.

Fulfilment and returns

Stock allocation across many warehouses, courier connections, and a returns process planned as carefully as delivery.

Catalogue and attributes

Real handling of variants. A catalogue that cannot show its own attributes will hold back every channel you connect to it.

GST and finance

Place-of-supply across states, HSN codes, e-invoicing, and a handoff to Tally or ERP that finance does not have to type in again.

Loyalty and CRM

One customer identity across store, web and marketplace. This is the only thing that makes loyalty mean anything.

India, specifically

What an Indian retail build has to handle.

  • ONDC protocol

    A seller or buyer app built to the network rules: catalogue categories, the protocol order life cycle, complaint flows and network payments.

  • Marketplace APIs

    Amazon SP-API, Flipkart Seller, Myntra, Nykaa. Each with its own catalogue rules, its own penalties and its own settlement format.

  • GST done properly

    Place-of-supply rules across state lines, HSN classification, e-invoicing above the set limit, and returns that match your filings.

  • COD and reverse logistics

    COD is still a large share of orders, and returns are 20-30% of fashion GMV. Both need a real process, not an afterthought status.

  • Courier aggregation

    Shiprocket, Delhivery, Blue Dart, Ekart with delivery checks by pincode and a backup when the first-choice partner cannot deliver.

  • Tally and ERP handoff

    Finance runs on Tally whether you like it or not. A clean, matched handoff beats asking them to type in your day again.

The metrics that matter

What a retail operator actually watches.

Not sessions. Not bounce rate. These are the four numbers a retail business really runs on. A platform that cannot show them without a data export is not finished.

Talk to us
4.1x
Inventory turns

The number that shows whether your working capital is doing its job. Most retail software cannot work it out live.

0.2%
Oversell rate

Because an oversell is not just a refund. It is a marketplace penalty and a hit to your seller rating.

18%
Return rate

By SKU and by reason. One SKU causing many returns is a product problem you should find in week two, not at the end of the quarter.

2.4%
Settlement variance

The gap between what marketplaces should have paid and what they did. Unmeasured, it is simply margin you never see.

Has anyone checked what the marketplace actually deducted?

Line by line, against your commission agreement, for every order. If the honest answer is that finance just glances at the total in a spreadsheet, there is money left on the table. We can usually show you roughly how much in two weeks.

The stack

Built on tools that will still be here in five years.

  • Laravel
  • Next.js
  • PostgreSQL
  • Redis
  • Elasticsearch
  • ONDC protocol
  • Amazon MWS/SP-API
  • Flipkart Seller API
  • Razorpay
  • Shiprocket
  • Delhivery
  • Tally integration

FAQ

The questions you were going to ask on the call.

One true number for what you can promise, with clear reservations that have a TTL, and no channel ever holding stock it has not reserved. Syncing more often is not the fix. A marketplace that reads your feed every fifteen minutes will oversell anyway, so it gets a safe extra buffer. The penalty for overselling lands on your seller rating, not theirs. Add cycle counting as a built-in routine and the oversell rate drops below 0.2 percent.

More than teams expect, because ONDC is a protocol, not a marketplace. You build a seller app or a buyer app to the network rules, and the network connects you with people who have never heard of you. Your catalogue must match the network categories. Order steps follow the protocol life cycle, not yours. Cancellation, return, and issue-and-complaint flows are set by the protocol and must be built properly, even the ones you would rather skip. Payments are matched against the network, not a party you can call. It is worth doing for the reach. It is not just a listing.

Usually not on purpose. But their payment reports contain commissions, closing fees, shipping charges and other deductions. They arrive as one lump sum for hundreds of orders, and almost nobody checks them line by line. If your finance team matches this in Excel, they are checking that the total looks fine and moving on. We build a tool that matches every line to an order, works out what the deduction should have been under your commission agreement, and lists the differences. The money recovered usually pays for the module within a year.

Shopify if you are D2C with a simple catalogue and want to spend your money on marketing, not engineering. We will tell you that even though it means a smaller project for us. WooCommerce for a small catalogue where you want to own the whole setup. Custom when the complexity is real: omnichannel stock across stores and marketplaces, B2B price levels, ONDC, complex delivery, or a catalogue whose attributes no platform handles well. The reason is almost never traffic. It is complexity.

It has to. A store that cannot bill because the connection dropped is losing money right now while someone phones the head office. We build store billing that saves data on the till first. It keeps taking payments and issuing invoices offline, queues the sales, and matches them up when the connection returns. A stock buffer stops an offline till from selling stock you do not have once everything syncs.

An omnichannel core of inventory, catalogue, orders, one marketplace and an online store typically takes 16 to 24 weeks, from around ₹20,00,000. We build the stock system first, always. A beautiful store on top of stock numbers you cannot trust creates angry customers and marketplace penalties. ONDC and settlement matching are usually phase two, once the core is proven.

Let's talk retail & ecommerce software

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.