Swiggy orders
Takes Swiggy orders straight into the kitchen. Every order lands on the Online orders screen with the rider, the delivery OTP and the customer's items, prints its kitchen tickets by itself, and is accepted or refused without leaving the counter.
| At a glance | |
|---|---|
| Type | Add-on module |
| Group | Sell |
| Price | Free |
| Provides | Receive orders from food-delivery platforms |
| Needs | Nothing to switch on. Orders become ordinary orders, and kitchen tickets need Restaurant ops (KOT). |
| Offered to | Restaurant |
| Permission | Manage add-ons (addons.manage) to connect; View orders to see Online orders |
What it does
Swiggy orders works exactly as Zomato orders: both provide Receive orders from food-delivery platforms, and either one opens Online orders under General in the menu and on the POS top bar. A restaurant on both sees both platforms' orders on one screen, with a platform filter.
Each order arrives as an ordinary order on the online channel (kitchen tickets print, stock moves, reports count it), with Swiggy's order id, the rider's name and phone, the delivery OTP and Swiggy's money breakdown. Items are priced from your menu, matched by SKU, then short code, then name; an unknown dish still reaches the kitchen under Swiggy's name. A repeated push never makes a second order.
Connecting Swiggy
- Go to Workspace → Modules, filter to Add-on modules. Swiggy orders is under Sell.
- Open its ⋮ menu and choose Enable.
- Choose an Order push token. Give Swiggy the Order push URL shown at the top of the dialog, with the token as the
x-api-keyheader. - Press Enable.

| Field | Required | What to enter |
|---|---|---|
| Order push URL | (shown) | Read-only. Swiggy's order push endpoint. Treat it like a password. |
| Order push token | Yes | Any secret string, sent by Swiggy as the x-api-key header. |
| Swiggy restaurant ID | No | Your outlet id at Swiggy, used when confirming orders back to them. |
| Platform GSTIN (e-commerce operator) | No | Swiggy's own GSTIN, as printed on its invoices to you. Stamped on each order as it arrives and named by the GST returns. A Swiggy order never takes Zomato's number. |
| Swiggy partner API key | No | From your Swiggy partner manager. Needed only to send accept and refuse decisions back. Write-only once saved. |
Working the orders
The same as for Zomato: Accept (with a preparation time) or Refuse (kitchen tickets voided, reason kept), then Food ready and Handed to rider, all told to Swiggy in the background. Stores opens or closes the outlet on Swiggy. Settings → Online orders holds auto-accept, the default preparation time, the decision deadline and the ordering hours. See Zomato orders → Working the orders for each step, with a screenshot.
Turning it off
Turn off on the ⋮ menu asks first. Swiggy's pushes are refused from that moment; the settings are kept.
Ready-made automations
None. Its orders go straight to the kitchen display and Online orders.
In the desktop and mobile apps
The restaurant desktop app shows Online orders as an online-only screen (one notice when offline). The Captain phone app does not carry it.
Related guides
- Online orders, Zomato orders, Restaurant ops (KOT)
- Module guides index