Swiggy and Zomato in one queue — and who owes the GST

Walk into a kitchen that does delivery and you will find the same shelf: a tablet for Swiggy, a tablet for Zomato, a phone for the direct orders, and one person whose actual job is watching all three. Nobody chose that. It accumulated.

The cost is not the hardware. It is that no single screen knows what the kitchen owes right now, so the answer to "how long for table four" and "is the Swiggy order out" lives in someone's head.

One queue means one writer

Landing every channel in one line is not a display trick — a dashboard that reads four sources still has four sources. It means every channel writes to the same order table, so the kitchen display, the reports and the books are all reading one set of rows.

Keystonne takes Swiggy and Zomato orders by webhook: the platform posts the order, the signature is verified before anything is recorded, and the order lands priced and tagged in the same queue as the bill you just rang at the counter. The kitchen never learns which platform sent a ticket, because for the kitchen that was never the interesting part.

What ships today is Swiggy and Zomato. ONDC is a channel you can record an order against, but the direct adapter is not built — we list it as roadmap on the integrations page rather than in the same breath as the two that work.

Section 9(5): the platform pays that GST

This is the part that surprises people, and it is worth getting right because it changes what your invoice should say.

Under Section 9(5) of the CGST Act, for specified restaurant services supplied *through* an electronic commerce operator, the operator is the person liable to pay the GST. Not you. The aggregator collects from the customer and discharges the tax on those supplies.

So an aggregator order is not a normal sale on your books. If you charge GST on it again, you have taxed the same supply twice.

Keystonne records those orders and tags them — sec95 on the order, "Sec 9(5)" in the GSTR-1 register, nil tax on the document — rather than taxing them. Your counter sales are taxed the way they always were, in the same run, on the same day. The two sit side by side in one report with the distinction visible instead of implied.

This is a mechanism, not tax advice for your specific registration. Your accountant should see how your returns are built; that is one reason every figure traces to the rows behind it.

Then the money has to match

An order arriving is half the story. The payout is the other half, and it arrives weeks later with commission, platform fees, taxes and deductions already taken out — as one number.

Import the platform statement and each payout is matched to the orders behind it, to the paisa, with every deduction in its own column. Not a summary you have to trust: a reconciliation you can open and disagree with.

The honest limits

- Two adapters, not fifteen. Swiggy and Zomato. Anything else on that page says what it is. - A webhook needs credentials. You paste the platform's keys once per outlet; nothing is shared across a chain unless you say so. - Section 9(5) applies to supplies through the operator. Your own storefront orders are ordinary sales, taxed normally. The distinction is the point.

If the shelf of tablets is still there after all that, the software has not done its job. One queue, one printer, one report — and the tax on the right party's books.