Tutorials / Swiggy and Zomato — menu, open and close, kitchen tickets

Swiggy and Zomato — menu, open and close, kitchen tickets

Send the Swiggy or Zomato menu, take tickets on KDS, reconcile both payout files, and answer Zomato complaints.

Swiggy and Zomato orders land on the kitchen board in QuickKOT. They are not added to the till’s sales total. Button names match the app.

On KDS, a Swiggy ticket is orange. A Zomato ticket is red. The app name is on the card. Tap Aggregators on KDS to see only those tickets.

1. Turn the pages on

Aggregators sits in the main menu under POS, once Swiggy and Zomato is on for this kitchen. The group kitchens share one add-on. Every other kitchen needs its own paid add-on, assigned under Settings → Add-ons on the same table as Inventory & Purchases. A kitchen without that seat does not show Aggregators in the menu, in Settings, or as a tab on KDS. The house manager, and that kitchen’s station manager, can open it, send the menu, and open reports. A cashier and a station sub do not open that menu. They still accept, reject, mark food ready, and fetch rider or guest number on the orange and red cards on Tickets and KDS.

Settings → Aggregators has Swiggy, Zomato, and Registration. Tick the app you use. You do not need a store id or an ordering link to tick it. Choose Full package, including the menu if this kitchen should send dishes, or Orders only if the menu already on the app should stay. Save the restaurant id on that app’s page, then Submit registration. The store id is filled after that. Write it down and keep it. Changing it can stop orders. QuickKOT support receives that registration. Further integration may take up to 2 working days. You are notified when it is ready. Menu send stays Pending until QuickKOT marks that app Active. Until then the page says integration is in progress.

2. Send the menu

Open Aggregators → Swiggy or Aggregators → Zomato. Each page sends that app only. Send is available after that app is Active. Categories from a disabled kitchen do not show. A category that is itself disabled does not show.

  1. Tick the dishes that should be on the listing. Two dishes in one category cannot share a name. The extra copy is blocked and is not sent. Rename it in Menu.
  2. Set a markup or type a price on a dish if this app should charge more than the counter. A markup is rounded to the nearest rupee, including sizes and add-ons.
  3. Save selection keeps the ticks. It does not send yet.
  4. Send Swiggy menu or Send Zomato menu. The first send does not put the old app menu back. Unticked dishes leave that listing.

You can send the menu five times a day in total, Swiggy and Zomato together. The page shows how many are left, and the last send time for that app.

Zomato usually shows a send within about 30 minutes. Swiggy can take 4 to 6 hours. Refresh menu status if the listing is still quiet.

Live / Offline on a dish is stock for today. It is not a menu send. Live needs the dish sold in the delivery section. A dish not sold there stays Offline until the next menu send after it is sold for delivery. To hide one add-on or one size, send the menu again with that extra off.

3. Open and close the listing

Open and Close sit at the top of the Swiggy page and the Zomato page. Each one is that app only. Type a reason. The listing can take a short time. Refresh status is on Aggregators → Store.

Peak-hour offline is the app. Open does not override it.

4. Store

Aggregators → Store is packaging on or off, packaging GST, and the Zomato delivery charge. Packaging CGST and SGST can be a decimal, for example 2.5. It is not a rupee packing slab on each dish, and it is not copied into the menu. Send charges is Zomato. Open and Close stay on each app’s page.

5. Take the order on KDS

A new card on the house board shows the app, their order number, every dish, notes, and the amount. Accept, reject, food ready, rider, and customer number are on that card. A kitchen board shows the ticket after Accept, with the dishes for that kitchen.

  1. Accept — type how many minutes the kitchen needs.
  2. Reject — pick a reason. A Swiggy reject stays on the house board until Swiggy cancels after support calls, or until Mark served.
  3. Food ready — tells the app the food is ready.
  4. Call Swiggy — on a Swiggy card after accept, for the house manager and that kitchen’s station manager. It asks Swiggy support to phone this restaurant. It does not dial from the device. A cashier and a station sub do not have Call Swiggy, park, or Complaints.
  5. Tap the card for rider and customer number.

Print on the card is a kitchen slip. It has no prices. Print is only on a ticket that was accepted, including auto-accept. When dishes are mapped to more than one kitchen, Print cuts one slip per kitchen, with that kitchen’s name, same as a till KOT. A skip of None on an add-on or option does not print. Tax, packing, packing tax, and OTP sit behind a down arrow on the card. When food is ready and the rider has picked up, Picked up sits next to Food ready. After Food ready, tap the card for Park until payout if the app never sends delivered or cancelled. It is not on a new or accepted ticket. On the house board, a delivered order, a restaurant reject, and an order the customer rejected stay on the card with a bold status. Press Mark served to take it off KDS. It stays on Aggregator orders. Kitchen KDS only opens after Accept. A Swiggy reject that the app later cancels does not open on the kitchen board. After Accept, a customer cancel stays on that kitchen, with an alert, so cooking can stop. Pickup takes the ticket off the station board at once.

6. Reports

Reports → Aggregator orders is by date range. Order-wise is the default list. Item-wise is the dishes. The filter is All aggregators, or Swiggy, or Zomato. Both lists page 25, 50 or 100. Open a row for the rider, OTP, and notes. Cancelled and rejected rows stay on Order-wise. They are not on Cancelled. An amount is Tentative until a payout file matches that order. How to upload those files is the next step.

7. Reconcile Swiggy and Zomato payouts

These tickets are not in Completed and they are not in the till sales total. Reconciliation is on Aggregator orders, for both apps.

Until a payout file matches the order, the amount is Tentative — the guest total from the ticket. After a match it is Actual: what the guest paid, commission, tax withheld, and net payout.

Upload the Swiggy annexure and the Zomato settlement on that same page. Each file is that app only. A matching order id already on this restaurant is saved. An id that was never here is skipped. Ads on that file are stored with the upload.

A parked or still-open kitchen ticket takes delivered, cancelled, or rejected from that same payout row. If the file never names a parked ticket, open it and mark Not on payout, or set delivered, cancelled, or rejected by hand. A later payout row still overwrites that. It does not create a POS sale.

Download Excel walks the filtered dates, one sheet per app, plus Summary, with Actual values where the file matched.

8. Complaints

Aggregators → Complaints is under Aggregators, next to Aggregator orders. It is Zomato order complaints only. Swiggy stays Call Swiggy on the card. A Zomato store notice stays on Aggregators → Store.

The number next to Complaints is unanswered complaints. It drops when you accept a refund or reject one. A Zomato complaint also shows as a chip on the KDS card. A cashier or a station sub sees the chip and cannot open that page. Answer it on Complaints, not on the card.

Each card shows the Zomato order number, the ticket total, the words Zomato sent, and any photo. Accept refund needs an amount up to the ticket total, then confirm. Reject is clearer photos, invalid, or other plus a sentence. An answered card cannot be acted on twice.

All, Unattended, and Resolved filter the list. Unattended stay until they are answered, even outside the dates. The date range looks up resolved complaints. The list pages 25, 50 or 100. If you have not received a complaint yet, All shows a labeled example of that card. The example goes away when a real complaint arrives, or when a resolved one is in the dates you picked.

Done

Apps ticked, store id saved, menu sent if you chose the full package, Open and Close known, orange Swiggy and red Zomato cards on KDS, payout files for both apps, and Complaints for a Zomato guest issue.

All tutorials