This note covers the following aspects of ONDC Launch:
- Different phases are covered here, along with the entry and exit criteria, for each phase;
- Process for participants to join ONDC during any phase;
- Operations-readiness requirements for participants;
- Market-readiness requirements for participants;
| Phases | Infra Readiness | Soft Launch (phase 0) | Soft Launch (phase 1) | Soft Launch (phase 2) 1 | Expansion |
|---|---|---|---|---|---|
| Timelines | 28th Feb - 4th Mar 2022 | 7th Mar - 11th Mar 2022 | 14th Mar - 31st Mar 2022 | 1st Apr - 30th Apr 2022 | 1st May - 15th Aug 2022 |
| Environment | Live | Live | Live | Live | Live |
| Addition to registry | Manual | Manual | Manual | Self-service registration | Self-service registration |
| Certification | Manual | Manual | Manual | Automated | Automated |
| Minimum number of participants | Depends on volunteering participants | 3 (1 retail buyer app, 1 retail seller app, 1 logistics seller app) | No minimum | No minimum | No minimum |
| Entry criteria | As defined in Tech requirements in (b) | As defined in Tech requirements in (b) | As defined in Tech requirements in (b) | As defined in Tech requirements in (b) | As defined in Tech requirements in (b) |
| Users | NA | Test Users | Real-life users (by invitation only) | Open to all users | Open to all users |
| Domains | Retail (Groceries), Logistics | Retail (Groceries + F&B), Logistics | Retail (Groceries + F&B), Logistics | Retail (Groceries + F&B), Logistics | Retail, Logistics |
| Use Cases | NA | TBD | As defined in Tech requirements in (b) | As defined in Tech requirements in (b) | As defined in Tech requirements in (b) |
| Physical movement of goods & services | No | No | Yes | Yes | Yes |
| Transfer of money | NA | No | Yes | Yes | Yes |
| Network Policy | Yes | Yes | Yes | Yes | Yes |
| Network Agreement | No | No | Yes | Yes | Yes |
| Cities | NA | Delhi, Bengaluru, Coimbatore, Bhopal, Shillong | Delhi, Bengaluru, Coimbatore, Bhopal, Shillong | Delhi, Bengaluru, Coimbatore, Bhopal, Shillong | 300 cities |
| Exit Criteria | Successful load test of gateway & registry (as defined in c) | Validation of use cases with network policy | NA | NA | NA |
| # | Requirement | Buyer App | Seller App |
|---|---|---|---|
| 1 | Protocol version | Transaction APIs - use latest version here; Registry APIs - 0.2.0 | Transaction APIs - use latest version here; Registry APIs - 0.2.0 |
| 2 | All APIs implemented | /search, /on_search; /select, /on_select; /init, /on_init; /confirm, /on_confirm; /status, /on_status; /track, /on_track; /cancel, /on_cancel; /update, /on_update, /rating, /on_rating; /support, /on_support |
/search, /on_search; /select, /on_select; /init, /on_init; /confirm, /on_confirm; /status, /on_status; /track, /on_track; /cancel, /on_cancel; /update, /on_update, /rating, /on_rating; /support, /on_support |
| 3 | Protocol Error Codes | N/A | Implement Protocol Level Error Codes here |
| 4 | Key pairs for signing & encryption | Pseudonymous key pairs for signing & encryption, as defined here | Pseudonymous key pairs for signing & encryption, as defined here |
| 5 | Auth header signing & verification | Verify auth headers for all responses;Sign auth headers for all requests; | Verify auth headers for all requests;Sign auth headers for all responses; |
| 6 | Network Policy | Comply with the configurations, schema policy, standard transaction codes that will form the network policy for the launch (draft doc is here) | Comply with the configurations, schema policy, standard transaction codes that will form the network policy for the launch (draft doc is here) |
| 7 | Cascaded Integration | N/A | Cascaded integration between Retail Seller App and one or more Logistics Providers - includes searching for logistics providers, confirming the order and passing status & tracking information to the buyer app |
| 8 | Functional Test - Normal flows | Complete retail order flow (from catalog search to order completion), providing rating, status & tracking, updates; Detailed flows to be provided; |
Complete retail order flow (from catalog search to order completion), providing rating, status & tracking, updates; Detailed flows to be provided; |
| 9 | Functional Test - Exception flows | Includes Normal flow, returns (part), cancel, grievance; Draft proposal for cancellation, return & replacement is here; Detailed flows to be provided; |
Includes Normal flow, returns (part), cancel, grievance; Draft proposal for cancellation, return & replacement is here; Detailed flows to be provided; |
| 10 | Payment Integration | Draft proposal for the Payment & Settlement protocol is here | Draft proposal for the Payment & Settlement protocol is here |
| 11 | Data Privacy & Security | - Maintain logs of confirmed orders, i.e. confirmed payload for /confirm, /on_confirm; - Transparent consent mechanism for sharing of PII; - Purpose limitation, storage limitation for PII; - Security Safeguards - Data Privacy & Security will be the responsibility of the app entity; |
- Maintain logs of confirmed orders, i.e. confirmed payload for /confirm, /on_confirm; - Transparent consent mechanism for sharing of PII; - Purpose limitation, storage limitation for PII; - Security Safeguards - Data Privacy & Security will be the responsibility of the app entity; |
| 12 | Security | Recommended: Web Application Firewall (WAF - L3 / 4 / 7) |
Recommended: Web Application Firewall (WAF - L3 / 4 / 7) |
| 13 | Issue Logging & Monitoring | Using Github Issue & Discussion board. All participants should have the Github IDs for one or more contacts added to ONDC Github Account | Using Github Issue & Discussion board. All participants should have the Github IDs for one or more contacts added to ONDC Github Account |
Footnotes
-
Any participant who enters ONDC from this phase onwards will have to meet the exit criteria for Soft Launch (phase 0) in the Pre-production environment ↩