How to cut order cancellations and rejections on Swiggy and Zomato

By Restrologic team Published Updated

To cut order cancellations and rejections on Swiggy and Zomato, find which kind you have, fix the cause in the outlet, and check the numbers every day. Most restaurant-side rejections come from four places: orders that nobody accepts in time, items that are sold out in the kitchen but still live on the app, menus that do not match the kitchen, and peaks the kitchen cannot handle. Each has a fix in the outlet’s routine and in how the POS talks to the delivery apps.

This guide explains the difference between rejections and cancellations, what each costs, how to find the causes in your own data, and a 30-day plan for one outlet or a chain.

What is the difference between a rejection and a cancellation?

The words are often used loosely, so it helps to separate them, because the fixes differ.

  • Rejection. The restaurant declines an order, or does not accept it within the time the platform allows, so it is cancelled automatically. The customer never gets the food, and the platform records it against the outlet.
  • Restaurant cancellation. The restaurant accepted the order but cannot complete it, usually because an item has run out or the kitchen is overloaded.
  • Customer cancellation. The customer calls the order off, often because the wait looks too long.
  • Rider or platform cancellation. The platform cancels because no rider could be assigned, the address could not be served, or for another reason on its side.

The first two are fully in your control. The third is partly in your control, because long preparation times and wrong estimates drive it. The fourth is mostly not, but you still need to record it, because it affects what you are paid.

Why do cancellations and rejections cost more than the lost order?

The lost sale is the visible cost. Three others follow it.

First, ranking. Swiggy and Zomato do not publish how they rank restaurants, but their partner apps track acceptance, rejections, cancellations and preparation time for every outlet, and restaurants commonly see their visibility fall when these slip. Fewer people see the outlet, so fewer order, and the outlet may start buying ads to win back placement it used to get for free.

Second, the customer. A customer whose dinner was cancelled is less likely to try you again, and may leave a low rating for an order they never received.

Third, the payout. Depending on who the platform says caused the cancellation and on your contract, a cancelled order may be paid in full, in part or not at all, and a refund may be deducted from your settlement. You may also have cooked and packed the food already. Our payout reconciliation guide shows how to check cancelled and refunded orders line by line, and the cloud kitchen profit calculator shows how thin the margin on a normal order can be, which is why one lost order takes several good ones to make up.

What causes most restaurant-side rejections?

Orders that nobody accepts in time

Both platforms expect an incoming order to be accepted within a short window. If it is not, it is cancelled automatically. This usually happens for ordinary reasons: the tablet sits at the counter out of sight of the kitchen, its battery is low or the app has frozen, the sound is off, or the manager is handling a dine-in table and misses the alert.

It is worst in chains that grew quickly without standardising the setup at each outlet. One outlet has a working tablet on the pass, another has an old phone in a drawer. The fix is to bring order acceptance into the POS that the kitchen already watches, so a new order arrives where the staff are looking, prints a kitchen ticket and can be accepted from the same screen. Restrologic POS accepts Swiggy and Zomato orders automatically, and if you run your own POS or restaurant software, our Swiggy, Zomato and Ownly integration brings the orders into your system the same way.

Items that are sold out but still live

This is the most avoidable cause. The kitchen runs out of paneer on a Friday evening, but the paneer dishes stay live on both apps. Orders keep coming, and each one has to be rejected or cancelled.

The fix is to switch an item off on every app the moment it runs out, and back on when it is restocked. Doing that by hand on two or three partner apps in the middle of a rush is something staff will not do consistently. With a POS that is integrated with the platforms, switching the item off in the POS switches it off everywhere. It also helps to know in the morning which items are likely to run short, from your stock counts and from how much of each dish sold on the same day last week.

Items on the app that are no longer on the menu, prices that differ from the POS, or add-ons that the kitchen stopped offering all lead to orders the outlet cannot fulfil as placed. In a chain, a menu change pushed by hand to dozens of outlet listings on two or more platforms almost always leaves some of them out of step.

The fix is one menu master. Keep the menu in your POS or central system and publish it to every app from there, so a change made once reaches every outlet and every platform together.

Peaks the kitchen cannot handle

At the dinner peak, or on a festival evening, orders can arrive faster than the kitchen can cook them. The temptation is to reject the extra orders, or to accept them and run late, which drives customer cancellations and low ratings.

Most partner apps let you switch items off, close the outlet for a while or change the preparation time shown to customers. Use those controls before the kitchen is overwhelmed, not after. Give each shift a written rule: when the queue passes a certain number of open orders, or tickets are waiting longer than a set time, the manager extends the preparation time or pauses the slowest dishes. Choose the numbers from your own kitchen, and review them after each busy weekend. Our Christmas and New Year delivery rush checklist covers how to prepare for the busiest nights of the year.

How do you find the causes in your own data?

You need two sources side by side: the platforms’ reports, which show each rejected or cancelled order with its time, items and the reason recorded, and your POS, which shows what the kitchen was doing at that moment. Put them together for at least four weeks and look for patterns:

  • which hours have the most rejections, and how many open orders the kitchen had at those times
  • which items appear most often in cancelled orders, which points to stockouts or wrong listings
  • whether a few outlets account for most of the problem, or it is spread across the chain
  • whether certain days of the week are worse, which points to staffing or prep on those days
  • whether a promotion brought more orders than the kitchen could cook

Track a small set of measures every day:

Measure What it counts Where it comes from
Acceptance Share of incoming orders the outlet accepted Partner app or order report
Rejections Orders declined or not accepted in time Partner app or order report
Restaurant cancellations Accepted orders the outlet could not complete Order report, with reason
Customer cancellations Orders the customer cancelled, and when Order report, with reason
Preparation time Minutes from acceptance to food ready, against the time shown to customers POS kitchen times and partner app
Items switched off How often and for how long each item was unavailable POS or partner app

A dashboard that shows these by outlet, by hour and by reason, with an alert when an outlet crosses a limit you set, turns this from a monthly complaint into a daily habit. Our restaurant data and analytics work combines the platform data with POS data for exactly this, and our guide to peak hour analytics shows how to plan staff and prep around the rush.

A 30-day plan to cut rejections and cancellations

Week one: measure. Pull four weeks of rejected and cancelled orders for each outlet, with reasons and times. Tag each one by cause: not accepted in time, item unavailable, menu or price mismatch, kitchen too busy, customer, rider or platform. Most outlets find that one or two causes account for most of the problem.

Week two: fix the devices and the screen. Make sure every outlet receives orders where the kitchen can see them, with sound on, power connected and a backup alert. If orders still arrive on a separate tablet, plan the move to a POS that accepts them directly.

Week three: fix the menu. Bring every outlet’s listings in line with one menu master, remove items the kitchen no longer makes, and agree who switches items off when they run out, on which screen.

Week four: fix the peak. Write the rule for extending preparation time and pausing dishes, train each shift lead on it, and review the first two busy evenings against the data.

Then repeat the measurement and compare. Keep the daily view running, because new staff, new dishes and new offers will bring the problems back if nobody is watching.

How do you manage this across many outlets?

In a chain, you cannot leave it to each outlet manager. Head office needs to see which outlets have the most rejections and cancellations, why, and whether they are improving, without logging into every partner dashboard. That needs the data from every outlet and every platform in one place, a short list of measures everyone agrees on, and a weekly review with the managers of the outlets that are furthest off target.

Standardise what each outlet runs: the same POS setup, the same way of receiving orders, the same menu master and the same peak-hour rule. Most of the gap between a good outlet and a poor one is the setup, not the people.

How does Restrologic help?

We connect POS systems and restaurant software to Swiggy, Zomato and Ownly so orders arrive in the system the kitchen already uses, menus are published from one place, and items and outlets can be switched off from the POS. We then bring platform and POS data together in reports by outlet, hour and reason. To talk it through for your outlets, call or WhatsApp Deepak Kumar, our Head of Operations, on +91 70275 16740, write to deepak@restrologic.com, or use the contact page.

Quick answers

What is the difference between an order rejection and a cancellation?

A rejection is when the restaurant declines an order or does not accept it in time. A cancellation is when an order already placed is called off, by the restaurant, the customer, the rider or the platform. Both are recorded against the outlet when the restaurant is the cause.

What causes most restaurant-side rejections on Swiggy and Zomato?

Missed acceptance on a tablet nobody is watching, items that are sold out in the kitchen but still live on the app, menus or prices that differ from the kitchen, and peaks the kitchen cannot handle.

How can a restaurant stop rejecting orders for items that are out of stock?

Switch the item off on every app the moment it runs out. With a POS integrated to Swiggy and Zomato, switching it off in the POS does that in one step for every connected app.

Do cancellations affect a restaurant's payout?

They can. Depending on who the platform records as the cause and on your contract, a cancelled order may be paid in full, in part or not at all, and refunds may be deducted from the payout.

What is a good cancellation rate for a restaurant on Swiggy or Zomato?

Platforms set their own thresholds and do not publish one figure for every restaurant. Use the targets shown in your partner app, and aim to bring restaurant-caused rejections and cancellations as close to zero as your kitchen allows.

Tell us what you want to build

Send a short note and Deepak will get back to you.

Deepak Kumar, Head of Operations +91 70275 16740 deepak@restrologic.com