ONDC Order Reconciliation for Restaurants: Complete Guide (2026)

ONDC order reconciliation is the process of matching every order placed through the Open Network for Digital Commerce with the actual payment your restaurant receives after deducting seller app fees, logistics charges, and taxes. Without it, you will not know whether you got paid correctly for each delivery order that left your kitchen.

If your restaurant already runs on Swiggy and Zomato, adding ONDC as a third channel brings lower commissions but also a new reconciliation headache. The order travels through more parties (buyer app, seller app, logistics provider, payment gateway) than a typical aggregator order, and each party deducts its own fee before the money hits your bank account.

This guide breaks down how ONDC settlements work, where restaurants lose money, and how to reconcile ONDC orders without spending hours on spreadsheets.

Key Takeaways

• ONDC charges 3-5% in seller app fees versus 25-30% on traditional aggregators, but the multi-party settlement chain creates new reconciliation gaps
• 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, faster than the 7-14 day cycles on traditional platforms
• NPCI’s NOCS platform now automates reconciliation for ONDC transactions, reducing manual matching errors

How ONDC Differs from Swiggy and Zomato for Order Settlement

On Swiggy or Zomato, the aggregator controls everything. One company handles the customer app, the restaurant listing, the delivery, and the payment. Your settlement report comes from a single source, which makes reconciliation relatively straightforward (even if the deductions are high).

ONDC works differently. It is an open protocol, not a single platform. Think of it the way UPI works for bank transfers. Any buyer app (Paytm, Magicpin, PhonePe 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.

Each of these participants charges a separate fee. Your final payout is what remains after all these deductions, and no single party gives you the complete picture. In short, Swiggy and Zomato give you one settlement report from one company, while ONDC splits every transaction across four independent parties, each sending its own report.

How Much Does ONDC Cost Compared to Swiggy and Zomato?

The biggest reason restaurants consider ONDC is the commission gap. According to the NRAI India Food Services Report, aggregator commissions typically range between 25-30% of order value. On a biryani order worth ₹450, that is ₹112-135 going to the platform. The same order through ONDC costs ₹13-22 in total fees, split across a seller app fee (~2%), a logistics charge (₹8-12), and a payment gateway fee (1-2%).

But here is the catch: that ₹13-22 is split across 3-4 different parties, and each one sends you a separate line item or report. If you do not reconcile them against each other, small discrepancies pile up across hundreds of orders per month. Tracking your food cost alongside these commission splits 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 Swiggy and Zomato report four recurring problems.

1. Multiple payout sources with no unified report

Your Swiggy settlement comes from Swiggy. Your Zomato settlement comes from Zomato. But your ONDC payout involves the seller app settling the order value, the logistics provider billing separately, and the payment gateway deducting its processing fee. 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

Unlike Swiggy where delivery charges are built into the commission, ONDC logistics costs vary by distance, time of day, and provider. A 3 km delivery at noon costs differently than a 6 km delivery during 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 commissions, logistics, and taxes. If it is not, you have a leak.

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 Fix ONDC Settlements?

The government recognised that multi-party reconciliation was holding back ONDC adoption. According to DPIIT’s ONDC policy framework, the network aims to unbundle digital commerce the same way UPI unbundled payments. In response, Protean eGov Technologies launched its Recon and Settlement Product (RSP) on NPCI Bharat BillPay’s NOCS (Network Order and Collection Settlement) platform.

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
• Early adopters include Bizom, Mystore, and Kotak Bank App

Razorpay also 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 a Third Channel?

The answer depends on your current order volume and your team’s capacity to manage one more settlement stream.

ONDC makes clear financial sense. A restaurant doing 40 delivery orders a day on aggregators and paying ₹1,200-1,500 daily in commissions could save ₹800-1,000 per day by shifting even half those orders to ONDC. Over a month, that is ₹24,000-30,000 back in your pocket.

A thali restaurant in Maninagar, Ahmedabad, that moved 18 of its 45 daily orders to ONDC in March 2026 reported saving roughly ₹22,400 that month in commission alone.

But the order volume gap is real. Most restaurants on ONDC report receiving 5-15 orders per day initially, compared to 40-50 on established aggregators. The customer base on ONDC buyer apps is growing, but it is not yet at Swiggy or Zomato levels.

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 Swiggy and Zomato running for volume while gradually building their ONDC presence. Their POS handles orders from all three channels, 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 a POS with built-in online order reconciliation saves real hours every week.

Conclusion

ONDC order reconciliation is more involved than Swiggy or Zomato reconciliation because the money passes through more hands before it reaches your account. The commission savings are genuine (3-5% versus 25-30%), but those savings only count if you actually verify that the correct amount 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 same way you would treat a new vendor’s invoices: verify everything, trust nothing by default.

For restaurants already managing Swiggy and Zomato order reconciliation, adding ONDC is one more channel to track. The payoff in lower commissions makes it worth the extra effort, provided you have the process in place to catch discrepancies before they become monthly losses.

Frequently Asked Questions