What Is ONDC? India's Open Network for Digital Commerce, Explained

ONDC is India's open e-commerce protocol that lets any app plug into any seller, with no platform lock-in. Here's how it actually works.

Nov 17, 2026 - 12:08
5 min read
 0
What Is ONDC? India's Open Network for Digital Commerce, Explained

Open a dozen different apps to buy groceries, order food, or book a cab, and you're using a dozen different closed systems that don't talk to each other. Now imagine one basic set of rules that let any of them plug into any other — a shop on one app showing up as a result inside a totally different app. That's the idea behind ONDC, and it's already running quietly underneath millions of Indian transactions.

What ONDC actually is

ONDC stands for Open Network for Digital Commerce. It isn't an app you download, and it isn't a company trying to out-discount Amazon or Flipkart. It's a set of open technical standards — built on a protocol called Beckn — that lets buyer apps and seller apps exchange information using a common language, the way email lets a Gmail user message someone on Outlook without either side needing to join the other's network.

In practice, that means a small kirana store or a neighbourhood restaurant can register as a "seller app" on ONDC once, and instantly become visible to shoppers browsing on any "buyer app" connected to the network — currently a mix of apps like Paytm, PhonePe's Pincode, Mystore, and several others, with more joining as the network grows. The seller never had to build a slick app of their own or pay a platform a cut just to be discovered.

It's run as a not-for-profit, incubated with backing from India's Department for Promotion of Industry and Internal Trade (DPIIT) — effectively a public-interest utility for digital commerce rather than a private marketplace.

Why this matters more in India than almost anywhere else

Big e-commerce platforms work by locking in two sides at once: buyers who want selection, and sellers who have no choice but to pay listing fees and commissions to reach those buyers. Over time, that funnels most of the market and most of the data through two or three large companies. ONDC was built explicitly to break that lock-in for a market where tens of millions of small merchants — the corner store, the local tailor, the one-cook cloud kitchen — have smartphones and UPI, India's instant payments network, but no realistic way to build or market their own app.

That's the genuinely India-specific piece of this story. The playbook — UPI did it for payments, Aadhaar did it for identity verification, and now ONDC is attempting it for commerce — is often called India's "digital public infrastructure" approach: the government or a public-interest body builds the plumbing, and private companies build whatever they want on top of it. It's a model other countries are now studying, precisely because it emerged from India's specific mix of scale, low per-transaction margins, and a huge informal retail sector that platforms never fully reached.

The goal isn't a new app to compete with Amazon. It's infrastructure that makes "which app" stop mattering.

How a transaction actually moves across the network

Under the hood, each ONDC transaction passes through a few defined roles:

  • Buyer app (BAP): what the shopper sees and searches on — say, a shopping app with ONDC built in.
  • Seller app (BPP): the system the actual shop or restaurant uses to list products and manage orders.
  • Gateway: routes the buyer's search request to the relevant seller apps in the area.
  • Logistics and payment layers: plug in separately, so delivery and payment providers can also compete on the same open network instead of being bundled by one platform.

The buyer never notices this handoff — they just see results from a store that, behind the scenes, is running on entirely different software than the app they opened.

What's still rough around the edges

None of this means ONDC has "solved" e-commerce. Early users have reported inconsistent delivery timelines, patchy return and refund experiences, and seller onboarding that varies a lot depending on which buyer and seller apps happen to be involved — since standardising the protocol doesn't automatically standardise service quality across dozens of independent companies. It's also had to compete for attention: most shoppers default to habit, and habit currently points to the big platforms.

For sellers specifically, the pitch is lower customer-acquisition cost and freedom from a single platform's algorithm deciding whether their shop gets seen. For that to hold up, the logistics and payment layers around ONDC need to mature roughly as fast as the discovery layer has. That part is still a work in progress.

The takeaway

ONDC is worth understanding less as "another shopping option" and more as a bet on what happens when discovery and transactions get unbundled from any single company's app. If it works the way UPI worked for payments, the app you open to buy something will matter far less than it does today — and a shop with no engineering team of its own could end up competing on equal footing with anyone.

Short URL: https://code24.in/9e60bfce

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Ashif Sadique As an full-stack developer, I'm passionate about sharing tutorials and tips that aid other programmers. With expertise in PHP, Python, Laravel, Angular, Vue, Node, Javascript, JQuery, MySql, Codeigniter, and Bootstrap. To me, consistency and hard work are the keys to success.