On August 17, Swiggy rolled out Guru, a 24x7 AI assistant for its restaurant partners, across more than 720 cities and 2.7 lakh restaurants. The pitch is a chat interface that lets a restaurant owner check their payout annexure, pull a tax report, review or modify an ad campaign, and see more than 30 performance metrics — GMV, orders, average order value — without digging through a settlement PDF or waiting on a support call, in over 20 languages including Hindi, Kannada and Telugu.
Read that feature list against what more than a thousand Bengaluru restaurants have spent the past month publicly demanding from Swiggy and Zomato, and the overlap is not subtle. Restaurant associations set an August 15 deadline over commissions ranging from 8% to 28%, opaque settlement reports, automatic deductions after customer complaints, and — specifically — discount campaigns activated without the restaurant's consent. Swiggy responded before that deadline by agreeing to seek consent before running promotions and to refund charges for campaigns launched without approval, which bought a deferral: the boycott didn't happen on August 15, and the associations set a new deadline of August 31 to see whether the rest of their demands get met. Two days later, Guru launched with payout tracking, tax reports and consent-driven campaign management as its headline capabilities. Whether that sequencing is coincidence or a product team responding directly to a live commercial dispute, the effect is the same: Swiggy has now shipped a technical answer to a set of complaints that were, until recently, being raised in association meetings and press statements rather than product roadmaps.
What Guru actually fixes, and what it doesn't
A restaurant owner who can suddenly see a clean payout annexure, a tax report and a chat log of every campaign approval has a real grievance addressed — "I can't tell what I was charged for" is a legitimate, solvable visibility problem, and an AI assistant that surfaces 30-plus metrics in a restaurant owner's own language is a genuine improvement over parsing a settlement statement designed by someone else's finance team. That's not nothing, and it's not spin either — better visibility into an opaque process has real value to a small restaurant operator who doesn't have a dedicated accounts team.
What Guru does not touch is the number restaurants are actually angriest about: the commission rate itself. Nothing in the tool's feature set changes the 8%–28% range restaurant associations are objecting to, restructures the underlying agreement, or gives restaurants any new leverage over how that rate is set. A dashboard that shows you exactly how a 25% commission was calculated is more transparent than one that doesn't — it is not a lower commission. Restaurants can now see their situation more clearly. Whether that situation itself has changed is a separate question, and it's the one the August 31 deadline is actually about.
The regulator thinks the underlying agreements are the problem
That distinction matters more given where the Competition Commission of India's long-running probe into Swiggy and Zomato currently stands. The CCI has found a prima facie case on three of the eight charges it investigated: app-owned cloud kitchens competing against the same restaurants listed on the platform, exclusivity clauses restricting which platforms a restaurant can list on, and price parity terms limiting what restaurants can charge elsewhere. A final order is still awaited, but the direction of the finding is notable — it points at structural terms in the platform-restaurant relationship, not at whether restaurants can see their own settlement data clearly. A transparency tool answers the visibility complaint. It does not answer the antitrust complaint, and it can't, because those are different categories of problem: one is a UX gap, the other is a contract-terms and market-structure question that sits with a regulator, not a product team.
Why this isn't the first time a concession bought time, not resolution
The pattern of a deadline producing a partial fix rather than a full one isn't new to this dispute — it's how the whole standoff has unfolded so far. The original deadline was August 15, and Swiggy avoided it the same way: not by changing commissions, but by agreeing to two specific, narrower asks — consent before activating promotions, and refunds for campaigns run without it. Those were real, restaurant-specific wins, and they're the same two problems Guru's campaign-management feature is now built to make visible and auditable. That's a reasonable reading of what's happened over the past month: each deadline surfaces a concrete, fixable complaint, Swiggy fixes that specific thing, and the underlying commission structure carries over untouched into the next round. Restaurants get real, incremental improvements. They also don't get the structural renegotiation several of the associations involved have said they actually want.
Why the deadline is still live
That gap is exactly why an AI assistant with genuinely useful features hasn't made the boycott threat go away. The restaurant associations' remaining demands as of the August 31 deadline still include compensation for orders cancelled after food is prepared, dedicated relationship managers, and an end to what they've called one-sided agreements — none of which a chat interface resolves, however good the interface is. Guru is a real product improvement layered on top of a commercial relationship that restaurants say is still unfair on its own terms. Both of those can be true simultaneously, and the coming weeks — whether the August 31 deadline produces another deferral, a further concession, or an actual boycott — will show whether Swiggy's response to this dispute stops at better visibility or eventually reaches the commission structure itself.
For now, restaurants have a considerably better window into exactly what they're unhappy about. That's progress of a kind. It isn't the fix they asked for.
