ONDC stands for Open Network for Digital Commerce. It is an Indian open digital commerce network designed so buyers and sellers can transact through connected applications without having to use the same closed marketplace or platform.
ONDC is not one shopping app. It is not the seller, the buyer app, or a universal delivery company. The network connects different participant roles through shared specifications, policies, and transaction flows.
A July 2025 Press Information Bureau release describes ONDC as a Section 8 company and an initiative of the Department for Promotion of Industry and Internal Trade under the Ministry of Commerce and Industry. The same release states that ONDC is not an ecommerce platform or marketplace, but an open protocol on which commerce applications can operate (Press Information Bureau).
Why ONDC is a network, not a marketplace
In a conventional platform-centric marketplace, the buyer and seller usually operate inside the same marketplace’s customer experience, seller system, catalogue, search, commercial rules, and transaction infrastructure.
In a network-centric model, the buyer can use one connected application while the seller participates through another connected application. Other network participants can support logistics, technology, or transaction services. Connected applications can therefore transact across the network without being part of one closed marketplace experience.
This distinction changes responsibility. A problem with product information, payment, fulfilment, delivery, cancellation, or support must be traced to the participant and contractual flow involved in that order. “ONDC did it” is not a sufficient operational diagnosis.
The participant roles in an ONDC transaction
Names and role definitions must follow the current ONDC Network Policy. The table below is a reader-facing map, not a substitute for the policy or participant agreement.
| Role or layer | What it does in the network | What it is not |
|---|---|---|
| Buyer application / buyer network participant | Provides the customer-facing discovery and purchase experience and connects buyer requests to the network | The entire ONDC network or every seller’s operator |
| Seller application / seller network participant | Connects sellers, their catalogue, offers, inventory, and order operations to the network | A guarantee that every seller appears identically in every buyer experience |
| Seller | Supplies the product or service and fulfils its commercial obligations under the applicable arrangement | ONDC itself |
| Logistics participant | Provides eligible fulfilment or delivery services within the transaction arrangement | A single universal courier for all ONDC orders |
| Technology or service provider | Supplies software or operational capabilities to a network participant or seller | Automatically the buyer app, seller, or logistics provider |
| ONDC network/protocol layer | Establishes the open network framework, specifications, registries, policies, and participant relationships | A central catalogue, one consumer app, or the merchant of record for every order |
The official ONDC Network Policy controls current legal role names and responsibilities. If this glossary summary conflicts with the current policy, the policy takes precedence.
How an ONDC order can work
A simplified product-order flow can look like this:
- A customer searches through a connected buyer application.
- The buyer-side request is sent through the network flow to eligible seller-side participants.
- Seller applications return relevant catalogue, price, availability, fulfilment, and service information.
- The buyer sees results and chooses an offer in the buyer application.
- Connected participants coordinate order confirmation, payment information, fulfilment, status, and any post-order process under the applicable network and commercial rules.
- The seller and logistics arrangement complete the product and delivery obligations.
The exact sequence depends on the domain, transaction, participant roles, and current protocol. The flow should not be read as a promise that every buyer app has the same catalogue, ranking logic, payment options, support model, or delivery experience.
ONDC versus a traditional ecommerce marketplace
| Attribute | ONDC network model | Closed marketplace model |
|---|---|---|
| Structure | Interoperable network of connected participants | One platform’s integrated buyer and seller environment |
| Buyer entry point | Connected buyer application | Marketplace website or app |
| Seller connection | Seller-side participant/application connected to the network | Marketplace seller account and systems |
| Catalogue discovery | Requests and responses across eligible network participants, subject to buyer-app experience and network rules | Marketplace’s own catalogue index and ranking systems |
| Logistics | Can involve eligible logistics arrangements and participants | Marketplace-managed, seller-managed, or approved-partner model |
| Customer experience | Controlled substantially by the selected buyer application and transaction participants | Controlled substantially by the marketplace |
| Rules | ONDC network policy plus participant and commercial arrangements | Marketplace terms, policies, and systems |
The comparison is structural. It does not mean every open-network transaction is cheaper, faster, broader, or better than every marketplace transaction.
What ONDC means for an Indian seller
A seller does not simply “upload to ONDC” in the abstract. The seller connects through an eligible seller-side route and needs a workable operating setup.
Questions to resolve include:
- Which seller application or network participant will connect and support the business?
- Who controls catalogue ingestion, product identifiers, category mapping, and updates?
- How are price, tax, inventory, serviceability, cancellation, return, and settlement rules handled?
- Which fulfilment and logistics options apply to the seller’s products and locations?
- Which participant receives each customer-service issue and within what process?
- What fees, commercial terms, data access, and contractual responsibilities apply?
- How will orders be reconciled with inventory, payment, finance, and support systems?
Use current official participant information and contractual documentation before onboarding. Buyer apps, seller apps, coverage, domains, and network capabilities can change; this page does not maintain a live directory.
How product discovery works differently
ONDC does not create one universal Google-style ranking for every connected buyer experience. A seller’s catalogue must first be represented accurately through its seller-side systems and network flow. A buyer application then controls how it presents eligible results to its users within the current rules and implementation.
For a seller, catalogue readiness includes:
- stable product and seller identifiers;
- correct titles, categories, attributes, variants, images, price, and tax information;
- current inventory and serviceability;
- fulfilment and delivery information that matches the offer;
- consistent cancellation, return, and support data;
- monitoring for rejected, suppressed, stale, or mismapped catalogue records.
Owned-site SEO remains a separate discovery surface. Google can index a D2C website’s category, product, brand, and educational pages. That visibility does not guarantee ONDC buyer-app placement, and ONDC participation does not guarantee Google rankings. Our D2C ecommerce SEO guide covers the owned-search layer.
What to measure
Avoid using a single top-line order count as proof that the channel works for a seller. A practical ONDC view can include:
| Area | Questions and measures |
|---|---|
| Catalogue | Accepted and active listings, attribute errors, inventory freshness, serviceable coverage |
| Discovery | Eligible impressions or result appearances where supplied, product views, offer selection |
| Order | Orders, units, Average Order Value, cancellation and fulfilment status |
| Logistics | Pickup, delivery completion, promised-versus-actual timing, failed-delivery reasons |
| Economics | Seller proceeds, fees, discounts, fulfilment cost, returns, contribution |
| Customer | Support reasons, refunds, repeat behaviour, participant hand-off issues |
| Reconciliation | Order, payment, settlement, tax, inventory, and finance agreement |
Definitions must remain consistent across participants and time. Where systems disagree, trace the transaction and status policy before reporting a rate.
Related ecommerce terms
- Quick commerce is a fast local fulfilment model; it is not another name for ONDC.
- Gross Merchandise Value (GMV) may be used for network transaction scale under a disclosed policy.
- Return to Origin (RTO) describes an undelivered shipment returning to its origin.
- Browse the ecommerce glossary for related marketplace, logistics, and measurement concepts.
Frequently asked questions
Is ONDC a government company?
The Press Information Bureau describes ONDC as a Section 8 company and a DPIIT initiative under the Ministry of Commerce and Industry. Use the latest official ONDC and government disclosures for current institutional details.
Is there one ONDC app?
No. ONDC is a network. Customers interact through connected buyer applications, while sellers connect through eligible seller-side participants or applications.
Who delivers an ONDC order?
Delivery depends on the logistics and fulfilment arrangement for that transaction. ONDC is not one universal delivery company.
Does joining ONDC guarantee sales?
No. A seller still needs accurate catalogue data, competitive offers, serviceable inventory, reliable fulfilment, workable economics, and discovery through connected buyer experiences.
Reviewed: 20 August 2026
Next accuracy and source review: 20 September 2026