Three Principals, One Platform, Zero Consensus
Every pricing decision Swiggy makes is simultaneously a negotiation with three parties who have incompatible preferences. Consumers want food that arrives fast and costs less than ordering from the restaurant directly. Restaurants want delivery volume without surrendering the margins they need to remain viable. Delivery partners want enough orders per hour, at enough pay per order, to justify using the platform. The platform itself needs to generate enough gross margin to cover technology, logistics coordination, customer support, and eventually profit.
In any given transaction, Swiggy collects a delivery fee from the consumer, takes a commission from the restaurant, and pays the delivery partner a per-order fee. The spread between revenue and cost on each order has historically been negative — Swiggy, like every food-delivery platform during the growth phase, subsidized transactions to acquire and retain both consumers and supply. The strategic bet was that scale would improve unit economics: denser order volume in a given area reduces per-order delivery cost, and higher consumer frequency reduces per-user acquisition cost amortized over time.
By 2019, with 130,000 restaurant partners and operating in 500 cities, Swiggy had built the supply side at scale. The question the pricing team faced was no longer "how do we grow?" — it was "how do we build a pricing architecture that's sustainable across three sides of the marketplace, across Indian cities with wildly different consumer price sensitivity, without triggering the spiral where a price increase causes churn that causes restaurant supply to thin that causes more churn?" That question is hard to answer in theory. In practice, Swiggy ran a series of product and pricing experiments between 2019 and 2023 that are worth examining as a set.
The Decision — Delivery Fee Architecture
The first major pricing restructure was on the consumer delivery fee. The original model — free delivery above a minimum order value — was well-intentioned and created a predictable distortion. Consumers added extra items to their cart specifically to avoid the delivery charge, not because they wanted the items. Return rates on add-on items went up. Average order values were higher in nominal terms but didn't represent genuine appetite expansion. Meanwhile, in Tier 2 cities — Indore, Coimbatore, Nagpur, Jaipur — where Swiggy had real market share but where the average order value was ₹200-350, the minimum-order threshold was often unreachable without padding behavior that degraded the actual meal experience.
The transition to flat delivery fees simplified the consumer-facing pricing, but it exposed the price sensitivity that the free-delivery-above-minimum had been masking. In Tier 2 cities, a ₹40 delivery fee on a ₹250 order is a 16% surcharge that consumers can easily benchmark against walking to the restaurant or calling directly. App uninstalls increased in the weeks following the fee restructure in certain markets. The data was unambiguous: flat fees worked for high-frequency urban consumers who were already habituated to the platform, and they damaged adoption in price-sensitive markets where the relationship was still being established.
Swiggy One — the subscription delivery pass, launched in 2022 — was the mechanism that resolved the consumer side of the equation. For a monthly fee (originally ₹89-149 depending on the tier), subscribers got free delivery on orders above a lower threshold, priority customer support, and exclusive discounts. The behavioral change this created was significant: subscribers shifted from occasional ordering to habitual ordering because every order now felt free at the margin. Mental accounting research consistently shows that subscription-based pricing converts the per-transaction friction into a sunk cost, and consumers who have paid a monthly fee order more frequently to "get their money's worth."
The Swiggy One launch meeting probably included a debate about whether the margin impact of free delivery at scale was recoverable. The answer required two assumptions: first, that subscriber frequency would increase enough to offset the per-order margin concession; and second, that the subscriber cohort would be sufficiently valuable in lifetime terms that the upfront subsidy would compound positively. Both assumptions proved correct in metropolitan cohorts. The economics in Tier 2 cities, where consumers had lower disposable income and lower ordering frequency, were tighter and required a lower-priced tier to be viable.
What Worked, What Failed
The subscription layer worked. Swiggy One converted Swiggy's most valuable consumers — the urban high-frequency users who were already ordering three to four times per week — into a more predictable revenue relationship. The subscription created a floor under churn: a consumer who has paid for a month's worth of free deliveries has a financial incentive to use the platform during that month. This is the same mechanism that made Amazon Prime sticky, and Swiggy applied it with enough localization (smaller screen sizes, regional language support, tier pricing) that it worked across income segments.
The restaurant commission structure is the part that has not found a stable equilibrium. Restaurant associations have publicly and repeatedly objected to take rates between 18 and 30 percent, arguing that at this level, delivery economics require restaurants to either raise prices on the app or subsidize delivery from dine-in margin. Both outcomes are bad: higher app prices reduce volume; subsidized delivery erodes restaurant economics to the point where larger chains begin investing in direct-to-consumer ordering.
Several QSR chains — including some with significant delivery volumes — have experimented with driving customers to their own apps through discount offers, loyalty programs, and packaging inserts with QR codes. This is the platform tension playing out in practice: the platform's value proposition (reach, logistics, payment infrastructure) is genuinely useful to restaurants, but at high enough commission rates, the largest restaurants begin to calculate whether the platform value is worth the take rate. The smaller the restaurant, the more dependent they are on platform reach and the less leverage they have in commission negotiations. The larger the chain, the more alternatives they can credibly build.
Swiggy's response was to introduce advertising revenue as a partial substitute for commission dependence. Restaurants can now pay for promoted placement in search results and category pages, which is structurally similar to how Google's quality score mechanism separated relevance from revenue — except in Swiggy's case, the separation is less rigorous, and there are legitimate concerns from restaurant partners about whether paid placement degrades the consumer's discovery experience.
What a PM Should Take From This
The Swiggy case is a worked example of the fundamental marketplace pricing challenge: every pricing lever affects all three sides simultaneously, and the side effects are often more consequential than the primary effect. Delivery fee changes affect consumer frequency, which affects restaurant revenue, which affects restaurant investment in menu quality on the platform, which affects consumer retention. You cannot move one pricing variable and expect the other variables to stay constant.
The Swiggy One approach — converting per-transaction pricing into subscription pricing for high-value consumers — is a legitimate and increasingly standard tool for resolving consumer-side pricing tension in marketplaces. It works when: the consumer's usage pattern is frequent enough to generate value from a subscription, the product is habitual enough that the sunk cost effect kicks in, and the platform can differentiate the subscriber experience enough to justify the premium over casual use. In food delivery, all three conditions are met for urban, high-frequency consumers. They are not reliably met for occasional users or for markets where the base ordering frequency is one to two times per month.
The restaurant commission question doesn't have a clean resolution, and it's worth being honest about that. The platform's take rate is simultaneously what funds the consumer subsidies that drive volume and what erodes the supply side's economics. The equilibrium commission rate is the one at which restaurants make enough margin from delivery to consider the channel worth operating, while the platform makes enough margin to fund operations and technology. In practice, this rate is market-specific, changes with competitive dynamics (when Zomato lowers commission in a city, Swiggy's negotiating position changes), and is subject to regulatory scrutiny. There is no "correct" take rate; there is only a rate that's defensible given the current competitive and regulatory context.
For PMs working on marketplace monetization: the goal is not to maximize the take rate. The goal is to find the take rate at which all three sides of the marketplace are generating enough value that they stay invested in the platform, and then to build product features — subscription, advertising, analytics — that improve the value proposition on each side so the platform can sustainably expand the total margin pool rather than fighting over a fixed one. Swiggy has been working on this in public for seven years, and the strategy is still in progress. That's the normal cadence for marketplace pricing maturity.