ONDC order reconciliation is the process of matching every order placed through the Open Network for Digital Commerce against the payment your restaurant actually receives. Three fees come off before that money lands: the seller app fee, the logistics charge and the payment gateway fee. Without the check, you will not know whether you were paid correctly for each delivery order that left your kitchen.
If your restaurant already sells through a delivery app, adding ONDC as another channel brings a new reconciliation job with it. The order travels through more parties than a single-app order does, because a buyer app, a seller app, a logistics provider and a payment gateway each handle one piece of it. Every one of those pieces produces its own paperwork, and none of it arrives in a single place.
This guide breaks down how ONDC settlements work, where the gaps appear, and how to reconcile ONDC orders without spending hours on spreadsheets.
Key Takeaways
- On ONDC you buy demand, delivery and payment handling as separate line items, so the deductions arrive from separate parties and have to be matched
- The ONDC network processed 326 million+ orders, as of October 2025, with daily transactions crossing 5.9 lakh
- Settlement cycles on ONDC seller apps typically run T+1 or T+2
- NPCI’s NOCS platform is rolling out across seller apps and will take much of the manual matching away once yours supports it
How Does ONDC Order Settlement Work?
ONDC is an open protocol rather than a single platform, which is what makes its settlement different. Think of it the way UPI works for bank transfers. Any buyer app, such as Paytm or PhonePe’s Pincode, can show your menu to customers. A separate seller app (WAAYU, Bizom, Mystore) manages your listing and order acceptance. A third-party logistics provider handles delivery. And a payment gateway processes the transaction independently.
Three of these four participants deduct something before the money reaches you, and each issues its own report. Your final payout is what remains once the seller app, the logistics provider and the gateway have taken their share, and no single one of them can show you the complete picture. That is the whole reason ONDC reconciliation needs a process, and it is the part restaurant owners underestimate when they add the channel.
| Who Handles It on ONDC | What They Do | What They Send You |
|---|---|---|
| Buyer app | Shows your menu to the customer | Order reference only |
| Seller app | Manages your listing and order acceptance | Payout report for the order value |
| Logistics provider | Picks up and delivers the order | A separate delivery invoice |
| Payment gateway | Processes the customer’s payment | A statement showing its fee |
Which Fees Come Out of an ONDC Order?
An ONDC order does not carry one deduction. It carries three, and they come from three different companies. There is a seller app fee charged as a percentage of order value, a logistics charge billed per delivery, and a payment gateway fee on the transaction. Published rate cards differ by seller app and by city, so the only figures worth planning around are the ones on your own agreements.
Splitting the cost this way is the point of the model rather than a quirk of it. A single-app order wraps demand, delivery and payment handling into one deduction; on ONDC you buy each piece separately and pay each supplier separately. The trade-off is that three line items have to be matched instead of one, and small differences pile up across hundreds of orders a month if nobody checks them. Tracking your food cost alongside these deductions gives you a clearer picture of per-order profitability.
Why Does ONDC Reconciliation Break Down?
ONDC reconciliation breaks down because the order, payment, and delivery are handled by separate companies with separate reporting systems. Restaurants that have added ONDC alongside an existing delivery channel report four recurring problems.
1. Multiple payout sources with no unified report
A single-app order gives you one settlement report from one company. An ONDC payout involves the seller app settling the order value, the logistics provider billing separately, and the payment gateway deducting its processing fee. That is three reports to cross-check for a single order.
2. Inconsistent order IDs across the chain
The buyer app assigns one order ID. The seller app assigns another. The logistics provider uses a third reference number. Matching these across reports is manual and error-prone, especially for a restaurant in Surat or Pune doing 30-40 ONDC orders a day.
3. Logistics cost discrepancies
On ONDC, logistics is billed as its own line rather than folded into a single deduction, and the amount moves with distance, time of day and provider. A 3 km delivery at noon does not cost the same as a 6 km delivery during the evening rush. If you are not tracking per-order logistics charges, you could be absorbing costs that should have been passed to the customer.
4. Refund and cancellation gaps
When a customer cancels an ONDC order after preparation, the refund flow involves the buyer app, seller app, and sometimes the logistics provider. If the seller app processes the refund but the logistics provider still charges you for a partial delivery attempt, that gap shows up only when you reconcile at month-end.
How to Reconcile ONDC Orders: A Practical Approach
Reconciling ONDC orders requires downloading daily reports from your seller app, logistics provider, and payment gateway, then matching order IDs and flagging payout gaps above ₹15 per order. Here is the full five-step process for a restaurant running 20-50 ONDC orders daily.
Step 1: Download all settlement reports daily, not weekly
Pull your seller app payout report, logistics invoice, and payment gateway statement every morning for the previous day. Weekly reconciliation means disputes pile up and evidence expires.
Step 2: Match order IDs across all three reports
Create a simple sheet with columns for seller app order ID, buyer app order ID, logistics reference, order value, each deduction, and net payout. For example, if you run a QSR in Ahmedabad’s Vastrapur area and processed 35 ONDC orders yesterday, you should have 35 matching rows across all three sources.
Step 3: Flag mismatches above ₹15 per order
Small rounding differences of ₹1-2 per order are normal due to GST calculations. But if the gap between expected and received payout crosses ₹15 on any single order, raise a ticket with your seller app immediately.
Step 4: Track cancellations and refunds separately
Maintain a separate tab for cancelled orders. Note whether the refund was customer-initiated or restaurant-initiated, whether logistics charges were reversed, and the date the refund actually reflected in your account.
Step 5: Run a weekly summary against your POS data
Your POS system records every order that went out of the kitchen. At the end of each week, total your ONDC orders in the POS and compare against total payouts received. The difference should be explainable by fees, logistics and taxes. If it is not, you have something to raise.
If your restaurant already uses a POS that tracks online orders from multiple platforms, this step becomes much faster. The POS total serves as your single source of truth.
What Is NOCS and How Does It Help ONDC Settlements?
Matching payments across four parties was always going to need a fix at the network level rather than in every restaurant’s spreadsheet. Protean launched its settlement product on NPCI Bharat BillPay’s NOCS (Network Order and Collection Settlement) platform to do that.
NOCS automates the reconciliation between buyer apps, seller apps, logistics providers, and payment gateways. Instead of you downloading three reports and matching them manually, NOCS processes the settlement at the protocol level.
What this means for your restaurant:
- Payouts become predictable with rule-based automated settlement
- Tax calculations (GST on commission, GST on logistics) happen within the system
- Exception handling flags mismatches before they reach your bank account
Network participants already live on it include Bizom, Mystore and the Kotak Bank App. Separately, Razorpay joined ONDC as a payment gateway offering a dedicated reconciliation service for both buyer and seller apps.
These infrastructure improvements are still rolling out. Until your specific seller app integrates with NOCS, manual reconciliation remains necessary.
Should Your Restaurant Add ONDC as Another Channel?
The answer depends on your current order volume and your team’s capacity to manage one more settlement stream.
On cost, work it out on your own records rather than on any published figure. Take your delivery orders for a month and apply the rates on your own agreements. Set that total against the seller app fee, logistics charge and gateway fee quoted to you by the ONDC seller app you are considering. The difference is specific to your city, your average order value and your delivery distances, and it is the only version of the number that means anything.
What that arithmetic will not tell you is where the orders come from. A buyer app has to be carrying customers in your area before an ONDC listing produces volume, and building that takes time regardless of what the fee line says.
At Petpooja, we have seen the restaurants that do best with ONDC are the ones that treat it as a parallel channel rather than a replacement. They keep their existing channels running for volume while gradually building an ONDC presence. Their POS handles orders from every channel, and reconciliation happens against one unified sales record.
If you run multiple outlets, the reconciliation burden multiplies. A chain with 8 outlets across Bengaluru, for example, would need to reconcile ONDC settlements separately for each location. That is where multi-outlet management inside the POS saves real hours every week.
Conclusion
ONDC order reconciliation takes more work than a single-app channel because the money passes through more hands before it reaches your account. Whatever the fee line looks like on paper, it only counts once you have confirmed that the right amount actually landed in your bank.
Download settlement reports daily, match order IDs across seller app and logistics provider reports, and flag gaps early. As NPCI’s NOCS platform rolls out across more seller apps, automated reconciliation will reduce this manual work. Until then, treat ONDC reconciliation the way you would treat any new vendor account: check the first few cycles line by line until the pattern is familiar.
If you are already reconciling one delivery channel, ONDC is one more to track, on a schedule you mostly have in place. Set the process up before the volume arrives, so discrepancies get caught in the week they happen rather than at month-end.
Frequently Asked Questions
It is the check that confirms you were paid the right amount for each ONDC delivery. You take what the order was worth, subtract every fee charged against it, and see whether the figure left over matches what actually reached your bank.
A single-app order produces one settlement report from one company. ONDC splits the transaction across a buyer app, seller app, logistics provider, and payment gateway, and each sends its own report. Confirming a payout therefore means cross-checking multiple sources rather than reading one.
ONDC itself does not charge a commission. Three separate parties do: the seller app takes a share of order value, the logistics provider bills per delivery, and the payment gateway charges on the transaction. What you pay depends on which seller app you sign with and where you operate. Ask for the rate card that applies to your outlet, then work the total out on your own average order value.
Most ONDC seller apps settle payments within T+1 or T+2 days, meaning one or two business days after the order is completed. Your seller app agreement will state the cycle that applies to you. COD orders settle after delivery confirmation.
Yes. A POS that accepts orders from every online channel keeps them all in one place, ONDC included. This gives you a single sales record to reconcile against, instead of relying on each platform’s report individually. Petpooja POSS supports multi-platform order management for this purpose.
NOCS (Network Order and Collection Settlement) is a reconciliation platform built by NPCI Bharat BillPay and Protean eGov Technologies for the ONDC network. It automates payment matching across all parties in an ONDC transaction, reducing the need for manual spreadsheet reconciliation. The platform is currently rolling out across seller apps.
