Connecting Swiggy and Zomato

What connecting actually does

A connection lets a delivery partner's orders arrive as real orders in this product. They land on the kitchen display like anything else, they carry a bill, and they show up in your reports and exports. Until one exists, orders from that partner live only in their own tablet.

Connections run in one direction to begin with. Orders coming in work as soon as you set this up. Pushing your menu or your out-of-stock list back out to the partner needs credentials from them that most accounts do not have, and the screen says which half is live for you.

Before you start

Have three things ready: the outlet ID the partner uses for your restaurant, the kitchen the orders should cook in, and the register they should bill against. The outlet ID is the value the partner puts on every order they send, and it is what tells us the order is yours.

Setting it up

1. Open the aggregator connections card in the back office and pick the platform.
2. Enter the outlet ID and choose the kitchen and the landing register.
3. Copy the webhook address shown afterwards and register it in the partner's own dashboard.
4. Copy the webhook secret beside it into the same place.

That is the whole setup. Both values are shown only to a signed-in owner or manager of your own account.

What the secret is for

Anyone on the internet can send a message to a public address claiming to be Swiggy. The secret is the shared word that lets us tell a real order from an invented one — a message that is not signed with it is rejected outright and never becomes an order.

Rotate the secret if you think it has leaked, or if a former staff member had access to the dashboard. The old secret stops working the instant you rotate, so update the partner's dashboard in the same sitting or orders stop arriving.

There is no way to see the secret without being signed in to your own account, and no other tenant can read it.

Pausing a connection

Disable switches a connection off without deleting it. Orders stop arriving while it is off; the outlet ID, the kitchen and the register are remembered, and enabling it again picks up where you left off. This is the right control for a shutdown week — deleting and rebuilding a connection means re-registering the address and the secret at the partner's end.

If the outlet ID you enter is already connected to a different account, you are told so plainly rather than shown an error. That happens when an outlet moves between owners; the previous account has to release it.

Orders that arrive this way carry a tax tag

Every order that comes in through a partner connection is tagged as one where the operator remits the GST, and the receipt says so. You do not switch that on — it comes with the channel. It is also why your delivery sales appear in a column of their own in the export summary.

The thing that does not work yet, and how to work around it

Marking an item out of stock on the till does not pause it on Swiggy or Zomato. It stops the item being sold at the counter and it hides it on your own ordering site, and that is where it ends today.

The reason is worth knowing so you do not go looking for a setting: the partners identify dishes by their own item numbers, not ours, and we hold no map between the two. Pushing our identifier would pause the wrong dish on their menu, which is worse than pausing none.

So until that mapping exists, when you run out of something, mark it out of stock in the partner's own dashboard as well. It is the only way their customers stop ordering it.