ONDC for restaurants: how to list your outlet and integrate it, step by step

By Restrologic team Published Updated

To list a restaurant on ONDC, you sign up with a seller app that is live on the network for food, complete its checks, build your menu catalogue in it, set up delivery and hours, connect orders to your POS if the seller app allows, and go live. Your menu then becomes visible in the buyer apps on the network that serve your area. You do not apply to ONDC itself. The seller app is your point of entry, your day-to-day tool and usually the party that settles your money.

This guide walks through each step, what to ask a seller app before you sign, and how to bring ONDC orders into the same POS queue as Swiggy and Zomato. If you have not yet decided whether ONDC is worth it for your outlets, read our guide to ONDC for Indian restaurants first. It covers how the network differs from Swiggy and Zomato, its limits today and when to wait.

How does ONDC work for a restaurant?

The Open Network for Digital Commerce (ONDC) is an initiative backed by the Department for Promotion of Industry and Internal Trade (DPIIT). It is not an app. It is a set of open rules that lets separate apps talk to each other, built on the open Beckn protocol.

Four kinds of party are involved in a food order:

  • Buyer apps, where the customer searches, orders and pays.
  • Seller apps, which restaurants use to list their menu and receive orders.
  • Logistics providers, which deliver the order when the restaurant does not use its own riders.
  • The network, which sets the rules, the message formats and the process for complaints.

When a customer orders from you in a buyer app, the order travels over the network to your seller app, which passes it to you. The buyer app owns the customer’s experience, the seller app owns your listing, and a logistics provider may own the delivery. That split is the point of ONDC, and it is also why setup takes more care than signing one contract with one platform.

What should you have ready before you start?

Each seller app sets its own requirements, so check its current list. Restaurants are commonly asked for:

  • an FSSAI licence or registration for the outlet, which any food business in India needs anyway
  • the business PAN
  • the GSTIN, if you are registered for GST
  • bank account details for settlement, often with a cancelled cheque
  • the outlet’s address, location pin, phone number and opening hours
  • the full menu with item names, descriptions, prices, add-ons and photos
  • a contact person who will handle orders, menu changes and complaints

Have the menu in a spreadsheet before you start. Most of the setup time goes into the catalogue, and a clean menu master saves you from typing it twice.

Step 1: choose a seller app

This is the most important decision, because you will live in the seller app every day. Several seller apps serve the food category, including some aggregator middleware platforms that have added ONDC. The list changes, so check the current one on the ONDC website and speak to more than one.

Ask each of them the same questions, and get the answers in writing:

Question Why it matters
What does one order cost me, line by line? The seller app’s fee, the buyer app’s fee, delivery and payment charges all come out of the order. You need the total, not one rate
How and when do you settle payments? Settlement cycles and statement formats differ, and you will reconcile against them
Which delivery options do you offer in my area? Coverage varies by city and by hour. Some outlets use their own riders for part of the area
Can orders come into my POS? Through an existing POS integration, an API for your developer, or only a dashboard and tablet
How do I update the menu, prices and item availability? You will switch items off at the peak. It must be fast
How are complaints and refunds handled? Who decides, how quickly, and what is deducted from you
What support do you give, and when? Dinner peaks and weekends are when things break

Choose the seller app whose answers you understand. A slightly higher fee from an app that settles clearly and connects to your POS can cost less than a cheaper one you have to reconcile by hand.

Step 2: sign up and complete the checks

Register with the seller app, upload the documents it asks for and add your bank account. The seller app verifies your details before your outlet can go live. If you have several outlets, ask how each outlet is set up: as separate stores under one account, or as separate accounts. That choice affects menus, reports and settlements later.

Step 3: build the menu catalogue

Your listing on ONDC is the catalogue in your seller app. Buyer apps show it to customers, and how well it is filled in affects whether customers find and choose you.

  • Use the same item names as your printed menu and your Swiggy and Zomato listings, so staff and customers see one menu.
  • Mark every item as vegetarian or non-vegetarian, and add allergens or spice levels where the seller app has fields for them.
  • Set prices, variants and add-ons exactly as the kitchen makes them.
  • Add a clear photo for each bestseller at least.
  • Set packaging charges, if any, the way your seller app asks.
  • Set opening hours and special hours for festivals and holidays.

Catalogue updates on the network can take longer to appear in every buyer app than an edit in a single platform’s partner app. Make big menu changes ahead of time, not in the middle of service.

Step 4: set up delivery

Decide who delivers. Most restaurants use the logistics providers available through their seller app. Some use their own riders for orders close to the outlet and the network’s logistics for the rest. Set the area you serve, the preparation time and any minimum order value. Then check how a delivery problem is raised and resolved, because with several parties involved it takes more steps than on a platform that runs its own fleet.

Step 5: get ONDC orders into your POS

Without an integration, ONDC orders arrive on the seller app’s dashboard or a tablet, which means one more screen at the counter and orders typed into the POS by hand. That is how orders get missed at the peak and how payouts become hard to match.

There are three ways to avoid it:

  1. Your POS already connects to your seller app. Some POS products and seller apps have built this. Ask both sides.
  2. Your seller app offers an API. Your POS vendor or developer can connect to it so ONDC orders land in the same queue as Swiggy and Zomato orders, with the order ID and items intact.
  3. A custom connector. If neither exists, a connector can be built between the seller app’s interface and your system.

Restrologic’s Swiggy, Zomato and Ownly integration connects POS systems to those three apps through one pass-through API. For ONDC, our custom software and integrations team builds connectors to a seller app’s interface so that ONDC orders reach the same POS and the same reports. The aim is the same in both cases: every order, from every channel, in the system the kitchen already watches. Our POS integration guide explains the general approach.

Step 6: test, then go live

Before you announce anything, place a few test orders from a buyer app, or ask your seller app how to test. Check that:

  • the order reaches your POS or dashboard with every item and add-on correct
  • accepting and marking it ready works from the screen your staff use
  • the rider is assigned and the customer sees the right status
  • switching an item off removes it from the buyer app within a reasonable time
  • the test order appears on the seller app’s settlement statement as you expect

Then go live one outlet at a time. Watch the first weeks closely, as you would on any new channel.

Step 7: run it and reconcile it

Once ONDC orders flow, treat the channel like Swiggy and Zomato. Keep one menu master and publish changes to every channel together. Track acceptance, rejections, cancellations and preparation time for ONDC orders, and act on the same causes. Our guide to cutting cancellations and rejections applies here too.

Reconcile every settlement against your POS and your bank. The method in our payout reconciliation guide works for ONDC as well: match orders by order ID, check status, rebuild each fee and deduction, and compare the net with what reached the bank. ONDC has a common process for raising issues and grievances, so complaints raised in a buyer app reach your seller app. Learn how your seller app shows them, and answer them as quickly as you would on any other channel.

Compare ONDC with your other channels on net revenue per order, not on the headline fee. Our cloud kitchen profit calculator shows the margin per order once commission, packaging, discounts, ads and food cost are counted, and you can run it once for each channel.

How does listing on ONDC compare with Swiggy and Zomato?

Swiggy or Zomato ONDC
Who you sign up with The platform A seller app on the network
Where customers find you That platform’s app Every buyer app on the network that serves your area
Who delivers Mostly the platform’s own fleet Logistics providers on the network, or your own riders
What you pay The platform’s commission and fees, per your contract The seller app’s fee, the buyer app’s fee, delivery and payment charges
Customer data you see What the platform shares What the seller app receives, which is often less than a buyer app holds
Orders into your POS Through a direct integration, a middleware hub or a pass-through gateway Through your seller app’s integration or API, or a custom connector

Which mistakes slow restaurants down on ONDC?

  • Signing with a seller app before seeing a sample settlement statement.
  • Typing the menu by hand into one more system instead of publishing it from a menu master.
  • Running ONDC orders on a separate tablet, so they are missed at the peak.
  • Judging the channel on its first few weeks of volume, before customers in your area have found you.
  • Counting the headline fee and not the total cost per order.

Next step

If you want ONDC, Swiggy, Zomato and Ownly orders in one POS queue and one report, talk to Deepak Kumar, our Head of Operations. Call or WhatsApp +91 70275 16740, write to deepak@restrologic.com, or use the contact page. Tell him which POS you use, how many outlets you have and which seller app you are considering.

Quick answers

How does a restaurant get listed on ONDC?

A restaurant does not join ONDC directly. It signs up with a seller app that is live on the network for food, completes the seller app's checks, builds its menu catalogue there, sets delivery and hours, and goes live. Its menu then becomes visible in the buyer apps on the network that serve its area.

Which documents does a restaurant need for ONDC?

Seller apps set their own list, but they commonly ask for an FSSAI licence or registration, PAN, GSTIN if you are registered, bank account details for settlement, the outlet address and hours, and the menu with prices and photos.

Does ONDC charge restaurants commission?

Costs on ONDC come from the parties involved: the seller app's fee, a fee set by the buyer app, delivery charges and payment charges. How each is charged and how much it is differs between apps, so ask your seller app for a written breakdown of what one order costs.

Can ONDC orders come into my POS?

Yes, if your seller app supports it. Some seller apps offer integrations with POS systems or an API that your POS or developer can connect to. Without that, orders arrive on the seller app's own dashboard or tablet.

Do I need to leave Swiggy and Zomato to list on ONDC?

No. ONDC is an extra channel. Most restaurants that list on it keep their Swiggy and Zomato listings and manage all three from one menu master.

Tell us what you want to build

Send a short note and Deepak will get back to you.

Deepak Kumar, Head of Operations +91 70275 16740 deepak@restrologic.com