Swiggy and Zomato POS integration: one order board for every channel

Swiggy and Zomato POS integration: one order board for every channel

On this page

Walk into the back of most delivery-heavy restaurants and you will find the “tablet wall”: one device for Swiggy, one for Zomato, one for ONDC or Magicpin, and the POS on the side. Staff re-key every order into the POS, or worse, do not — so the kitchen works from tablets and the accounts work from monthly payout statements that never quite match.

Aggregator integration replaces the wall with a single order board. This article explains how it works end to end, the four problems it fixes, and a checklist of questions to ask any software vendor.

How the integration actually works

  1. Onboarding. Your restaurant IDs on each aggregator are linked to your outlets in the POS. Aggregators authorise the POS vendor’s integration through their partner APIs.
  2. Menu push. The POS becomes the single source of truth for items, prices, photos, veg/non-veg tags and availability. Change a price once and it is pushed to every channel; mark an item out of stock and it disappears from the apps within minutes.
  3. Order flow. A new order arrives in the POS’s live order board with the channel badge, items, instructions and the customer’s masked details. Staff accept or reject with one tap; the KOT fires to the kitchen automatically. Status updates (accepted, food ready, picked up) flow back to the aggregator and to the customer’s app.
  4. Settlement and reconciliation. Every order lands in your sales with the channel, gross amount, commission, discounts funded by you versus by the aggregator, and taxes. When the weekly payout arrives, the system reconciles it against the orders.

The four problems it fixes

1. Lost and duplicated orders

With tablets, orders are missed during rush and occasionally cooked twice. On one board with spoken new-order alerts and a kanban view of status, nothing is missed, and an offline-first POS queues acceptance if the network blips.

2. Menu drift

Prices and availability on aggregators diverge from the counter within weeks when updated by hand. Central menu push ends the divergence — and makes per-channel pricing deliberate rather than accidental.

3. Inventory blindness

Aggregator sales that never enter the POS never deduct stock, so recipe-level inventory and food-cost figures are wrong by the entire delivery share of revenue. Integrated orders deduct ingredients like any other sale.

4. Payout reconciliation

The monthly headache: gross sales on the aggregator dashboard, net payouts in the bank, and a spreadsheet in between. When every order carries its commission and discount breakdown, the reconciliation is automatic and the GST treatment of TCS and commissions is correct in the books.

ONDC, Magicpin, Dineout and your own storefront

The same architecture extends to newer channels. ONDC brings lower-commission orders from multiple buyer apps; Magicpin and Dineout bring discovery and dine-in offers; and your own branded online storefront and QR table ordering bring the highest-margin orders of all. The value of a unified board grows with every channel added — as long as each one is a first-class citizen rather than an afterthought.

Questions to ask a POS vendor

Question What a good answer sounds like
Which aggregators are integrated via official APIs? Named list — Swiggy, Zomato, ONDC, Magicpin, Dineout — not “we can build it”.
Is menu push two-way? POS is the master; availability toggles in seconds; per-channel pricing supported.
What happens to an order when the POS is offline? Acceptance queues locally, no duplicates on reconnect.
Does the order deduct inventory? Yes, at recipe level, like a counter sale.
How is the payout reconciled? Automatically against orders, with commission, discounts and TCS in the ledger.
Can one outlet run multiple brands? Yes — cloud-kitchen multi-brand with separate menus and reporting.

How Restro Sarthi does it

Restro Sarthi’s aggregator hub connects Swiggy, Zomato, Dineout, ONDC and Magicpin to the same live order board as your POS, QR ordering and branded storefront. Menus are pushed once, orders fire KOTs and deduct recipe stock automatically, and consolidated payouts are reconciled inside the finance suite. Multi-brand cloud kitchens, food courts and corporate ordering run on the same board. Book a live demo and we will connect a test outlet during the call.

See how Restro Sarthi handles this

See it live

Run this workflow in Restro Sarthi

Offline-first POS, KDS, inventory, GST and e-invoicing, CRM and multi-branch — one platform. Book a 30-minute walkthrough.

Book a live demo →

Keep reading

Related articles