Home · DINO for F&B · Swiggy and Zomato orders
DINO · Swiggy and Zomato
Swiggy and Zomato orders, in the same queue as dine-in.
DINO, the NukkadShops restaurant POS, takes Swiggy and Zomato orders through Urban Piper into the same billing and KOT flow as dine-in, takeaway and QR orders. Staff accept each order on the DINO screen, it reaches the kitchen as a KOT in the same queue, and it closes into the same day-end report.

Functionality
What DINO does with Swiggy and Zomato orders
One queue, not a shelf of tablets
Swiggy and Zomato orders arrive in DINO as KOTs, in the same queue as counter, Captain App and QR orders. The kitchen works one list instead of a tablet for each app. Explore →
Accept, reject and mark ready in DINO
Staff accept or reject each order on the DINO screen and manage it there until it is ready. Handover and delivery are then completed in the Swiggy or Zomato rider app.
On the kitchen screens
Aggregator orders land on the same kitchen display screens as dine-in, so cooks and packers work one queue across every channel. Explore →
Billed with everything else
Swiggy and Zomato orders land in the same billing as dine-in and takeaway, each order tagged to its channel, so the counter never juggles systems mid-rush. Explore →
Menu and prices from DINO
Menu items and prices are pushed from DINO to Swiggy and Zomato, and you choose which platforms list each item. To take a dish off, remove it and push the menu again.
Ingredients deduct by recipe
Every dish carries its recipe, and Swiggy and Zomato orders deduct ingredients the same way as dine-in and takeaway bills, so stock stays true on delivery-heavy days. Explore →
Delivery sales, shown separately
Channel mix reporting shows dine-in, takeaway, QR and aggregator orders side by side. Each Swiggy or Zomato bill carries its platform as the tender, so the two can be separated in the bill reports. Explore →
One day-end report
Counter, table, QR and delivery orders close into one day-end report and one reconciliation, not a separate count for each app.
Several brands, one kitchen
Cloud kitchens run several brands out of one kitchen with every aggregator order in one queue.
On DINO for Android
The Swiggy and Zomato integration runs on DINO for Android, including the NukkadShops Android POS machines. See the devices →
Swiggy and Zomato orders, aggregated through
How it works
A delivery order’s way to the kitchen
-
1
The guest orders on Swiggy or Zomato
Nothing changes for the guest. They order in the delivery app as usual.
-
2
Staff accept it in DINO
Urban Piper passes the order to DINO, where staff accept or reject it on screen.
-
3
The KOT fires
Once the order is accepted, DINO creates a KOT for it, in the same queue as dine-in and takeaway, routed to the right station like any other KOT.
-
4
The kitchen works one queue
Cooks see it on the printer or the kitchen screen next to dine-in orders, and packers work from the same list.
-
5
Marked ready in DINO
Staff mark the order ready in DINO. Handover and delivery are then completed through the Swiggy or Zomato rider app.
-
6
It closes into the day-end
The order sits in the same billing and reports as every other channel, shown as an aggregator order in the channel mix.
Outcomes
What changes when delivery joins the POS
One list at peak
The kitchen stops reading a screen per app. Every order, from the counter or a delivery app, is in one queue.
No more tablet juggling.Delivery keeps kitchen discipline
Aggregator orders are KOTs like any other, so delivery runs to the same kitchen rhythm as dine-in.
One kitchen rhythm.The day closes once
Counter, table and delivery sales sit in the same reports, so the day-end is one job, not three.
One day-end.Delivery gets a number
Channel mix shows what delivery contributes next to dine-in, so decisions about where to invest run on data.
Channels side by side.Where it fits
Any kitchen that takes delivery orders
Cloud kitchens live on Swiggy and Zomato, often with several brands in one kitchen; the cloud kitchen POS guide covers what to test. QSRs take aggregator orders in the same queue as counter and kiosk orders. Restaurants and cafés that also deliver keep one kitchen and one report instead of a tablet for each app.
New to the term? The glossary explains what a KOT is in Swiggy and Zomato orders. You can also watch DINO in two minutes, Swiggy and Zomato orders included. DINO already runs the F&B counters at Delhi and Hyderabad airports.
Questions, answered.
Does DINO integrate with Swiggy and Zomato?
Yes. DINO, the NukkadShops restaurant POS, takes Swiggy and Zomato orders through Urban Piper into the same billing and KOT flow as dine-in, takeaway and QR orders, so the kitchen works one queue and one day-end report covers every channel. The integration runs on DINO for Android.
How do Swiggy and Zomato orders reach DINO?
Through Urban Piper, which aggregates orders from delivery platforms and passes them to DINO. Staff then accept or reject each order on the DINO screen.
Do Swiggy and Zomato orders come in as KOTs?
Yes. When a Swiggy or Zomato order is accepted, DINO creates a KOT for it and sends it to the kitchen exactly like a dine-in order, in the same queue, printed or on the kitchen display screens.
Do I still need a tablet for each delivery app?
Not for orders. Staff accept or reject each order and mark it ready in DINO, and the kitchen works one queue across every channel. Handover and delivery are completed in the Swiggy or Zomato rider app.
Can I see delivery sales separately from dine-in?
Yes. Channel mix reporting shows dine-in, takeaway, QR and aggregator orders separately. To separate Swiggy from Zomato, each bill carries its platform as the tender in the bill reports.
Can I manage my Swiggy and Zomato menu from DINO?
Yes. Menu items and prices are pushed from DINO to Swiggy and Zomato, and you choose which platforms list each item. To take a dish off, remove it and push the menu again.
Do Swiggy and Zomato orders deduct ingredient stock?
Yes. Every dish in DINO carries its recipe, and Swiggy and Zomato orders deduct ingredients the same way as dine-in and takeaway bills.
Which billing machine works with Swiggy and Zomato orders?
An Android POS running DINO. The Swiggy and Zomato integration runs on DINO for Android, including the NukkadShops Android POS machines, which are priced on the hardware page.
Is the Swiggy and Zomato integration part of DINO?
Yes. One integration covers both Swiggy and Zomato. Costs for DINO and the integration are confirmed for your outlet after the demo.
How long does it take to start taking Swiggy and Zomato orders in DINO?
About six to eight working days if your restaurant already has Swiggy and Zomato accounts. Our operations team handles onboarding: linking your accounts through Urban Piper takes 2 to 3 working days, setting up and pushing the menu another 2 to 3, and go-live 2 more working days for a request raised Monday to Thursday, 9 am to 5 pm. Book a demo to start.
More of DINO