ONDC is an Indian initiative creating an open-source, interoperable network for digital commerce, moving from platform-centric to network-centric models.

Made with Rinto — analyse your own content free

Context

Quick orientation

What is it?An open network protocol for digital commerce.

Why does it exist?To democratize e-commerce and break platform monopolies.

Where is it used?Primarily in India, for various retail sectors.

What came before it?Closed, proprietary e-commerce platforms.

What does it depend on?UPI and other digital public infrastructure.

Purpose & Genesis

Why ONDC was created and its foundational inspiration.

Prerequisites

Key components and mindsets necessary for ONDC's functionality.

Core Mechanism

The fundamental workings and architectural principles of ONDC.

The One Big Idea

ONDC standardizes digital commerce interactions, allowing buyers and sellers to connect across different applications, not just within one.

Network Participants

Buyers, sellers, logistics providers, and payment gateways interact through ONDC-enabled applications.

Open Beckn Protocol

ONDC is built on the Beckn Protocol, defining how participants discover, order, fulfill, and pay across domains.

Why Beckn Creates Open Networks

Beckn enables distinct applications to communicate using common language and rules. This fosters interoperability, allowing discovery and transactions across diverse digital services and domains.

The Beckn Protocol Framework

Beckn defines the core components and interfaces for network participants to interact in a decentralized, domain-agnostic manner.

e.g.A user on the 'Pincode by PhonePe' buyer app searches for 'biryani'. The Gateway identifies multiple biryani sellers via the ONDC Registry. The Gateway routes the request, gathers menus, and presents options to the user from various restaurants.

e.g.A buyer app sends a search query to an ONDC gateway, which checks the registry for matching seller apps, then forwards the query to them for product results.

e.g.A buyer app requests 'biryani near me' from its configured Gateway. The Gateway asks the Registry for all food domain seller apps. It then routes the request to those identified seller apps to fetch relevant listings.

Network Participants

Entities like buyer applications, seller applications, logistics providers, and payment gateways connect to the network.

Standardized APIs

Common JSON schemas and API calls (e.g., /search, /init, /confirm) for all interactions across different services.

The One Big Idea

Standardized APIs ensure every participant in the ONDC network 'speaks the same language.' This common interface fosters true interoperability, allowing any buyer application to connect with any seller application, breaking platform silos and enabling network effects.

How Standardized APIs Work

These APIs define common interaction patterns and data formats for all commerce operations within the ONDC network.

A Buyer's Purchase Journey

A buyer app sends a /search API call. A seller app responds with items. Buyer sends /select to add items, then /init for details and /confirm for order finalization.

ONDC Standardized vs. Proprietary APIs

Comparing the core design philosophies and their implications.

Dimension	ONDC Standardized APIs	Proprietary Platform APIs
Ownership	Open and public; defined by Beckn protocol	Owned by a single platform (e.g., Amazon)
Interoperability	High; any compliant app talks to any other	Low; designed for internal platform use
Network Effects	Enable open network effects for all	Confined to a single platform's ecosystem
Development	Build once, integrate with many	Build per platform; vendor lock-in

Risk of Non-Compliance

If ONDC participants fail to strictly adhere to the standardized API specifications and schemas, it can lead to communication breakdowns, data inconsistencies, and failed transactions across the network.

Standardization vs. Flexibility

Achieving universal interoperability demands strict adherence to standards, which can limit the flexibility for individual participants to implement unique, non-standardized features quickly.

Gateways & Registries

Gateways route requests between participants; registries list active network participants and their capabilities.

The One Big Idea

Gateways and Registries enable an open, decentralized network by providing discovery and routing. They allow any buyer to find any seller without a single platform owning the connections, fostering interoperability.

How Requests Flow in ONDC

Gateways and Registries work together to facilitate requests and responses across the ONDC network.

Participant Registration

Seller apps, buyer apps, logistics providers register their capabilities with an ONDC Registry.

Buyer App Initiates Search

A buyer app (e.g., Paytm) sends a search request for a product to a Gateway.

Gateway Queries Registry

The Gateway queries the ONDC Registry to identify relevant Seller Apps based on the search criteria.

Gateway Routes Request

The Gateway forwards the search request to multiple discovered Seller Apps simultaneously.

Sellers Respond

Identified Seller Apps send their product or service availability and details back to the Gateway.

Gateway Consolidates & Forwards

The Gateway consolidates responses from various sellers and sends them back to the original Buyer App.

Not a Centralized Database

A common misconception is that ONDC Gateways or Registries store actual product catalogs or transaction data. They don't. They only facilitate discovery and routing; the data resides with the respective participant apps.

ONDC vs. Traditional Marketplace

Gateways and Registries offer a stark contrast to how traditional e-commerce platforms operate discovery and transactions.

Dimension	ONDC (Gateways/Registries)	Traditional Marketplace
Discovery Model	Decentralized. Gateways find sellers via Registries.	Centralized. Marketplace directly hosts and lists all sellers/products.
Data Ownership	Data remains with Buyer/Seller apps; Gateways only route metadata.	Marketplace aggregates and often owns much of the transaction data.
Interoperability	High. Any buyer app can connect to any seller app.	Low. Buyers and sellers are confined to one platform's ecosystem.

Enable Decentralized Discovery & Routing

Gateways and Registries replace centralized platform functions by allowing diverse participants to find each other and exchange data, making a truly open and interoperable network possible.

How they enable transactions

These components work in tandem to facilitate seamless discovery and routing of requests and responses across the ONDC network, empowering diverse applications.

Not a Central Marketplace

A common misconception is that gateways or registries are a single monolithic platform. They are decentralized network components that facilitate, rather than control, interactions.

Discoverability vs. Efficiency

A key trade-off involves balancing comprehensive participant discovery across a vast network with the need for efficient, low-latency routing of transaction requests.

The One Big Idea

Gateways and Registries enable an open, decentralized commerce network by solving discovery and routing. They allow any participant to find and interact with any other, moving from platform-centric walled gardens to an interoperable ecosystem.

How they work together

These components provide the essential lookup and communication layers for the ONDC network, allowing participants to find and connect dynamically.

Centralized vs. Decentralized Discovery

Comparison of how ONDC's Gateways/Registries differ from traditional marketplaces in enabling participant discovery and routing.

Dimension	ONDC (Gateways & Registries)	Centralized Marketplace (e.g., Amazon)
Participant Discovery	Any participant can find any other through registries.	Buyers only discover sellers within the platform's curated list.
Routing of Requests	Dynamic routing by Gateways across diverse participants.	Internal routing managed by the platform's proprietary backend.
Control & Ownership	Distributed; multiple independent entities operate them.	Owned and controlled by a single platform operator.

Not a Central Authority

A misconception is that Gateways or Registries are single, central controlling entities. In reality, many independent organizations can operate these components, and they interoperate using the open Beckn Protocol.

Transaction Flow on Beckn

A typical user transaction involves a sequence of standardized API calls between participating applications over the Beckn network.

Discovery (Buyer App)

Buyer application sends a /search request to find products or services from seller applications.

Selection & Initialization

Buyer app selects items, sending /init to seller for order details confirmation and buyer info.

Confirmation & Payment

Seller confirms order with /confirm. Payment gateway handles the transaction via /update or /status.

Fulfillment & Tracking

Seller or logistics partner processes order; updates sent via /update or /status for real-time tracking.

Beckn Protocol vs. Traditional Platforms

Contrasting Beckn's open, decentralized approach with centralized, platform-centric models prevalent in digital commerce.

Dimension	Beckn Protocol (e.g., ONDC)	Traditional Platform (e.g., Amazon)
Interoperability	Different apps communicate freely, fostering choice	Apps locked into one platform, limited choice
Control & Ownership	Decentralized, network participants own data	Centralized, platform owns user and transaction data
Monopoly Risk	Low, as competition thrives in an open network	High, potential for a single dominant player
Innovation	Open ecosystem encourages diverse service development	Platform dictates features and service offerings

Misconception: Beckn Is ONDC

Beckn is an open-source protocol—a specification for creating interoperable networks. ONDC is an implementation of Beckn, specifically for digital commerce in India.

Discovery & Fulfillment Flow

The sequence from a buyer searching products to receiving them, involving multiple network participants.

Buyer App Search

Consumer searches for products on any ONDC-enabled buyer app.

Seller App Response

Multiple seller apps on ONDC respond with relevant listings.

Buyer Selection

Consumer chooses products and services from various sellers.

Logistics Selection

Consumer selects preferred logistics provider from available options.

Order Placement

Order details are communicated to seller and logistics apps.

Payment

Payment is processed, often via UPI, across the network.

Fulfillment

Seller processes order, logistics delivers; all tracked by apps.

Interoperability Principle

Standardized APIs and data formats allow diverse apps to communicate seamlessly, breaking platform silos.

Decentralized Network

No single central entity controls the entire transaction flow; participants interact directly via APIs.

Unbundling Services

Separates discovery, ordering, and fulfillment, enabling specialized providers to offer services.

Dimension	Modularity	Coordination
Gain	Increased flexibility	More competition
Cost	Potential complexity	Higher overhead

Applications & Impact

Real-world uses and the broader effects of ONDC.

Challenges & Misconceptions

Common difficulties and mistaken beliefs about ONDC.

Network Effects Hurdle

Achieving critical mass requires broad adoption by both buyers and sellers, which is a significant challenge.

Quality Assurance Myth

Misconception: ONDC guarantees product quality. Reality: ONDC provides the rails; participant apps handle user experience.

Why people get this wrong

People mistake ONDC for a traditional e-commerce platform. Existing platforms often provide direct quality guarantees, leading to false expectations.

The correct picture

ONDC is a protocol, like HTTP. It connects buyers and sellers, enabling commerce. It does not directly manage product quality or service delivery.

Contrast: ONDC vs. a store

Expecting ONDC to resolve a faulty product complaint is like asking a road to fix a car's engine. The road enables travel, but doesn't fix vehicles.

ONDC is a network, not a brand

ONDC provides the common 'rails' for commerce. Quality assurance and brand trust are built and maintained by the individual buyer and seller apps running on those rails.

Test yourself

If a defective product is received via ONDC, who is primarily responsible for addressing the quality issue?

Governance Complexity

Managing disputes, fraud, and policy enforcement across a decentralized, open network is a substantial challenge.

Comparisons

How ONDC relates to and differs from other e-commerce models.

ONDC vs. Marketplaces

Compares ONDC's open network model with traditional closed e-commerce platforms.

Dimension	ONDC	Traditional Marketplaces
Control	Network-centric	Platform-centric
Interoperability	Open	Closed
Fees	Lower variable	Higher fixed commissions
Scope	Diverse services	Specific categories

ONDC as Internet Protocol

ONDC resembles the internet protocol by providing a universal layer for diverse applications to communicate.

Common Questions

Typical questions asked about ONDC, with concise answers.

Learning Path

A structured path to understand the Open Network for Digital Commerce.

Relationships

How this topic connects to the broader landscape

Part of	Digital Public Infrastructure	To foster open digital ecosystems
Depends on	UPI	For seamless digital payments
Made of	Beckn Protocol	The underlying open specification
Alternative	Proprietary Marketplaces	Closed platforms like Amazon
Used in	Indian Retail Commerce	Transforming local trade
Created by	Government of India	As a national initiative
Limitation	Network Effects	Requires widespread adoption

▸ 10 Expand

APEX

ONDC is an Indian initiative creating an open-source, interoperable network for digital commerce, moving from platform-centric to network-centric models.

Made with Rinto — analyse your own content free

CTX

Context

Quick orientation

What is it?An open network protocol for digital commerce.

Why does it exist?To democratize e-commerce and break platform monopolies.

Where is it used?Primarily in India, for various retail sectors.

What came before it?Closed, proprietary e-commerce platforms.

What does it depend on?UPI and other digital public infrastructure.

▸ 2 Expand

SECT

Purpose & Genesis

Why ONDC was created and its foundational inspiration.

SUP

Market Concentration Problem

Large e-commerce platforms create vendor lock-in and high commissions, limiting small businesses.

INSG

Digital Public Infrastructure

India's success with UPI inspires ONDC to build an open protocol for e-commerce, designed as a public good.

▸ 2 Expand

SECT

Prerequisites

Key components and mindsets necessary for ONDC's functionality.

SUP

Digital Payments Infrastructure

ONDC relies heavily on UPI for seamless, real-time transaction processing across participants.

SUP

Open Protocol Mindset

Requires participants to adopt common standards and interoperable specifications for network communication.

▸ 7 Expand

SECT

Core Mechanism

The fundamental workings and architectural principles of ONDC.

INSG

The One Big Idea

ONDC standardizes digital commerce interactions, allowing buyers and sellers to connect across different applications, not just within one.

SUP

Network Participants

Buyers, sellers, logistics providers, and payment gateways interact through ONDC-enabled applications.

▸ 5 Expand

SUP

Open Beckn Protocol

ONDC is built on the Beckn Protocol, defining how participants discover, order, fulfill, and pay across domains.

INSG

Why Beckn Creates Open Networks

Beckn enables distinct applications to communicate using common language and rules. This fosters interoperability, allowing discovery and transactions across diverse digital services and domains.

▸ 15 Expand

FRMW

The Beckn Protocol Framework

Beckn defines the core components and interfaces for network participants to interact in a decentralized, domain-agnostic manner.

e.g.A buyer app sends a search query to an ONDC gateway, which checks the registry for matching seller apps, then forwards the query to them for product results.

SUP

Network Participants

Entities like buyer applications, seller applications, logistics providers, and payment gateways connect to the network.

▸ 6 Expand

SUP

Standardized APIs

Common JSON schemas and API calls (e.g., /search, /init, /confirm) for all interactions across different services.

INSG

The One Big Idea

▸ 3 Expand

SUP

How Standardized APIs Work

These APIs define common interaction patterns and data formats for all commerce operations within the ONDC network.

SUP

Common API Calls

A defined set of API calls like /search, /select, /init, /confirm, and /track orchestrate the entire buyer-seller journey.

SUP

JSON Schemas for Data

Strict JSON schemas dictate the precise structure and data types for all requests and responses, ensuring data consistency across participants.

SUP

Digital Signatures for Trust

Every API request and response is digitally signed. This verifies sender identity and ensures data integrity, crucial for trust in an open network.

EXMP

A Buyer's Purchase Journey

A buyer app sends a /search API call. A seller app responds with items. Buyer sends /select to add items, then /init for details and /confirm for order finalization.

CMPR

ONDC Standardized vs. Proprietary APIs

Comparing the core design philosophies and their implications.

Dimension	ONDC Standardized APIs	Proprietary Platform APIs
Ownership	Open and public; defined by Beckn protocol	Owned by a single platform (e.g., Amazon)
Interoperability	High; any compliant app talks to any other	Low; designed for internal platform use
Network Effects	Enable open network effects for all	Confined to a single platform's ecosystem
Development	Build once, integrate with many	Build per platform; vendor lock-in

RISK

Risk of Non-Compliance

TRDF

Standardization vs. Flexibility

Achieving universal interoperability demands strict adherence to standards, which can limit the flexibility for individual participants to implement unique, non-standardized features quickly.

SUP

Gateways & Registries

Gateways route requests between participants; registries list active network participants and their capabilities.

INSG

The One Big Idea

FLOW

How Requests Flow in ONDC

Gateways and Registries work together to facilitate requests and responses across the ONDC network.

Participant Registration

Seller apps, buyer apps, logistics providers register their capabilities with an ONDC Registry.

Buyer App Initiates Search

A buyer app (e.g., Paytm) sends a search request for a product to a Gateway.

Gateway Queries Registry

The Gateway queries the ONDC Registry to identify relevant Seller Apps based on the search criteria.

Gateway Routes Request

The Gateway forwards the search request to multiple discovered Seller Apps simultaneously.

Sellers Respond

Identified Seller Apps send their product or service availability and details back to the Gateway.

Gateway Consolidates & Forwards

The Gateway consolidates responses from various sellers and sends them back to the original Buyer App.

OPP

Not a Centralized Database

CMPR

ONDC vs. Traditional Marketplace

Gateways and Registries offer a stark contrast to how traditional e-commerce platforms operate discovery and transactions.

Dimension	ONDC (Gateways/Registries)	Traditional Marketplace
Discovery Model	Decentralized. Gateways find sellers via Registries.	Centralized. Marketplace directly hosts and lists all sellers/products.
Data Ownership	Data remains with Buyer/Seller apps; Gateways only route metadata.	Marketplace aggregates and often owns much of the transaction data.
Interoperability	High. Any buyer app can connect to any seller app.	Low. Buyers and sellers are confined to one platform's ecosystem.

INSG

Enable Decentralized Discovery & Routing

Gateways and Registries replace centralized platform functions by allowing diverse participants to find each other and exchange data, making a truly open and interoperable network possible.

▸ 2 Expand

SUP

How they enable transactions

These components work in tandem to facilitate seamless discovery and routing of requests and responses across the ONDC network, empowering diverse applications.

SUP

Registries: Participant Discovery

Registries list all active ONDC network participants (buyer apps, seller apps, logistics providers) and their capabilities, allowing others to discover them dynamically.

SUP

Gateways: Request Routing

Gateways receive network requests from buyer applications, query registries to find eligible sellers, and intelligently route these requests to relevant participant applications.

OPP

Not a Central Marketplace

A common misconception is that gateways or registries are a single monolithic platform. They are decentralized network components that facilitate, rather than control, interactions.

TRDF

Discoverability vs. Efficiency

A key trade-off involves balancing comprehensive participant discovery across a vast network with the need for efficient, low-latency routing of transaction requests.

INSG

The One Big Idea

▸ 2 Expand

SUP

How they work together

These components provide the essential lookup and communication layers for the ONDC network, allowing participants to find and connect dynamically.

SUP

Registries: The Directory

Registries are distributed directories that list all active network participants (e.g., buyer apps, seller apps, logistics providers). They store each participant's domain, capabilities, and endpoint URLs, enabling others to discover them.

SUP

Gateways: The Router

Gateways act as smart routers. When a participant (e.g., a buyer app) needs to find services, it sends a request to a Gateway. The Gateway queries the Registries, identifies relevant participants, and routes the request accordingly.

CMPR

Centralized vs. Decentralized Discovery

Comparison of how ONDC's Gateways/Registries differ from traditional marketplaces in enabling participant discovery and routing.

Dimension	ONDC (Gateways & Registries)	Centralized Marketplace (e.g., Amazon)
Participant Discovery	Any participant can find any other through registries.	Buyers only discover sellers within the platform's curated list.
Routing of Requests	Dynamic routing by Gateways across diverse participants.	Internal routing managed by the platform's proprietary backend.
Control & Ownership	Distributed; multiple independent entities operate them.	Owned and controlled by a single platform operator.

OPP

Not a Central Authority

FLOW

Transaction Flow on Beckn

A typical user transaction involves a sequence of standardized API calls between participating applications over the Beckn network.

Discovery (Buyer App)

Buyer application sends a /search request to find products or services from seller applications.

Selection & Initialization

Buyer app selects items, sending /init to seller for order details confirmation and buyer info.

Confirmation & Payment

Seller confirms order with /confirm. Payment gateway handles the transaction via /update or /status.

Fulfillment & Tracking

Seller or logistics partner processes order; updates sent via /update or /status for real-time tracking.

CMPR

Beckn Protocol vs. Traditional Platforms

Contrasting Beckn's open, decentralized approach with centralized, platform-centric models prevalent in digital commerce.

Dimension	Beckn Protocol (e.g., ONDC)	Traditional Platform (e.g., Amazon)
Interoperability	Different apps communicate freely, fostering choice	Apps locked into one platform, limited choice
Control & Ownership	Decentralized, network participants own data	Centralized, platform owns user and transaction data
Monopoly Risk	Low, as competition thrives in an open network	High, potential for a single dominant player
Innovation	Open ecosystem encourages diverse service development	Platform dictates features and service offerings

OPP

Misconception: Beckn Is ONDC

Beckn is an open-source protocol—a specification for creating interoperable networks. ONDC is an implementation of Beckn, specifically for digital commerce in India.

FLOW

Discovery & Fulfillment Flow

The sequence from a buyer searching products to receiving them, involving multiple network participants.

Buyer App Search

Consumer searches for products on any ONDC-enabled buyer app.

Seller App Response

Multiple seller apps on ONDC respond with relevant listings.

Buyer Selection

Consumer chooses products and services from various sellers.

Logistics Selection

Consumer selects preferred logistics provider from available options.

Order Placement

Order details are communicated to seller and logistics apps.

Payment

Payment is processed, often via UPI, across the network.

Fulfillment

Seller processes order, logistics delivers; all tracked by apps.

▸ 5 Expand

INSG

Interoperability Principle

Standardized APIs and data formats allow diverse apps to communicate seamlessly, breaking platform silos.

SUP

In one line

ONDC connects diverse buyer and seller apps through shared rules, like different phones on the same network.

INSG

The deeper reason

ONDC specifies open APIs and data formats. This ensures all participant applications 'speak' the same digital language, enabling direct communication.

EXMP

Concrete illustration

A buyer on App A can order from a seller on App B, using a delivery service via App C. They all interoperate seamlessly via ONDC.

OPP

The counter-argument

Some argue open networks are complex and less secure. ONDC addresses this via strict participant validation and integrated grievance systems.

SUP

Why this matters in practice

It creates a level playing field, freeing businesses from single platform dependencies. This boosts competition and expands market reach for all.

INSG

Decentralized Network

No single central entity controls the entire transaction flow; participants interact directly via APIs.

TRDF

Unbundling Services

Separates discovery, ordering, and fulfillment, enabling specialized providers to offer services.

Dimension	Modularity	Coordination
Gain	Increased flexibility	More competition
Cost	Potential complexity	Higher overhead

▸ 2 Expand

SECT

Applications & Impact

Real-world uses and the broader effects of ONDC.

EXMP

Hyperlocal Commerce

Facilitates local businesses to reach customers directly through buyer apps, bypassing high platform fees.

SUP

Diverse Retail Sectors

Applies across groceries, food delivery, fashion, and mobility, expanding digital access to new markets.

▸ 3 Expand

SECT

Challenges & Misconceptions

Common difficulties and mistaken beliefs about ONDC.

RISK

Network Effects Hurdle

Achieving critical mass requires broad adoption by both buyers and sellers, which is a significant challenge.

▸ 5 Expand

OPP

Quality Assurance Myth

Misconception: ONDC guarantees product quality. Reality: ONDC provides the rails; participant apps handle user experience.

OPP

Why people get this wrong

People mistake ONDC for a traditional e-commerce platform. Existing platforms often provide direct quality guarantees, leading to false expectations.

▸ 3 Expand

SUP

The correct picture

ONDC is a protocol, like HTTP. It connects buyers and sellers, enabling commerce. It does not directly manage product quality or service delivery.

SUP

Buyer App Role

Buyer apps integrate quality display, returns, and dispute resolution for users. They manage the overall user experience.

SUP

Seller App Role

Seller apps onboard merchants and are responsible for product quality, descriptions, and fulfillment directly from their sellers.

SUP

Logistics Provider Role

Logistics providers ensure product safety and timely delivery. Their performance directly impacts the customer's overall experience.

EXMP

Contrast: ONDC vs. a store

Expecting ONDC to resolve a faulty product complaint is like asking a road to fix a car's engine. The road enables travel, but doesn't fix vehicles.

INSG

ONDC is a network, not a brand

ONDC provides the common 'rails' for commerce. Quality assurance and brand trust are built and maintained by the individual buyer and seller apps running on those rails.

▸ 1 Expand

SUP

Test yourself

If a defective product is received via ONDC, who is primarily responsible for addressing the quality issue?

SUP

Answer: Apps are accountable

The respective seller app and buyer app are accountable. ONDC provides the framework for their interaction, not direct product liability.

RISK

Governance Complexity

Managing disputes, fraud, and policy enforcement across a decentralized, open network is a substantial challenge.

▸ 2 Expand

SECT

Comparisons

How ONDC relates to and differs from other e-commerce models.

CMPR

ONDC vs. Marketplaces

Compares ONDC's open network model with traditional closed e-commerce platforms.

Dimension	ONDC	Traditional Marketplaces
Control	Network-centric	Platform-centric
Interoperability	Open	Closed
Fees	Lower variable	Higher fixed commissions
Scope	Diverse services	Specific categories

INSG

ONDC as Internet Protocol

ONDC resembles the internet protocol by providing a universal layer for diverse applications to communicate.

▸ 2 Expand

SECT

Common Questions

Typical questions asked about ONDC, with concise answers.

▸ 2 Expand

QUIZ

How does ONDC differ from Amazon or Flipkart?

ONDC is a network protocol, not a direct consumer-facing platform.

SUP

Open Network Model

ONDC connects multiple buyer and seller applications, fostering interoperability.

SUP

Closed Platform Model

Amazon and Flipkart operate proprietary ecosystems for transactions.

▸ 2 Expand

QUIZ

Is ONDC a consumer-facing app or website?

No, ONDC is the underlying digital infrastructure.

SUP

Infrastructure Layer

ONDC provides the 'pipes' and standards for digital commerce.

SUP

User Interaction

Consumers interact with ONDC through various buyer apps built by different entities.

▸ 1 Expand

SECT

Learning Path

A structured path to understand the Open Network for Digital Commerce.

▸ 3 Expand

CHKL

Mastering ONDC Concepts

Follow these steps to build a solid understanding of ONDC.

1Problem & Vision→2Core Architecture→3Economic Impact

STEP

Problem & Vision

Understand the challenges of existing e-commerce and ONDC's goals.

STEP

Core Architecture

Grasp the network's structure, participants, and transaction flow.

STEP

Economic Impact

Analyze ONDC's potential to democratize commerce and foster competition.

REL

Relationships

How this topic connects to the broader landscape

Part of	Digital Public Infrastructure	To foster open digital ecosystems
Depends on	UPI	For seamless digital payments
Made of	Beckn Protocol	The underlying open specification
Alternative	Proprietary Marketplaces	Closed platforms like Amazon
Used in	Indian Retail Commerce	Transforming local trade
Created by	Government of India	As a national initiative
Limitation	Network Effects	Requires widespread adoption