The most useful sentence anyone can hear about ONDC is that it is a protocol rather than a platform. Selling on Amazon means joining somebody's marketplace and accepting its rules. ONDC instead standardises how buyer-facing and seller-facing software talk to each other, so that independent applications can interoperate without any of them owning the network. Every design decision in the integration follows from that, and teams that approach it as another sales channel to plug in tend to underestimate it.
There are four participant roles. A seller network participant is the software a seller lists through. A buyer network participant is the consumer-facing application. A gateway routes buyer searches out to multiple seller participants. Logistics service providers handle fulfilment. Deciding which of these you are is the first architectural question, and it is a business question rather than a technical one — the obligations, the catalogue responsibilities and the customer relationship differ completely between them.
The interaction model is the beckn protocol, and it is asynchronous in a way that surprises teams used to request-response commerce APIs. Actions come in pairs: search and on_search, select and on_select, init and on_init, confirm and on_confirm, status and on_status, with track, cancel, update, rating and support covering the rest of the lifecycle. Your system both calls and is called. That means a publicly reachable, authenticated endpoint with real availability requirements, not a background job that polls when convenient.
Every message carries three parts: a context block with the protocol version, transaction identifiers and participant identifiers; the message payload itself; and an Ed25519 digital signature. A central registry functions as the network's directory, publishing participant public keys and capabilities so signatures can be verified. Key management therefore stops being a checkbox and becomes an operational concern — rotation, storage and the consequences of a key mismatch all need an owner before go-live rather than after.
Onboarding runs through pre-production, staging and production go-live, with ONDC approval as a distinct project phase rather than a step you schedule around. Build the timeline with that as a dependency you do not control. Alongside it sit the compliance obligations any Indian commerce system carries: GST-compliant invoicing, the Consumer Protection E-Commerce Rules, and DPDP obligations on the personal data flowing through the transaction.
The honest assessment is that ONDC integration is a genuine engineering project — asynchronous messaging, cryptographic signing, catalogue modelling, order state machines and a certification gate — rather than a connector someone installs. Whether it is worth it depends entirely on whether your sellers or buyers are where the network already has density. That is a commercial question worth answering properly before the technical one, because the protocol will work regardless of whether anyone is on the other end of it.
