THE HIDDEN REVENUE BEHIND EVERY ZOMATO ORDER

Ever waited for your Zomato order and noticed the delivery partner's status just sit on "picked up" for a few extra minutes?

What if I told you that the little gap is actually a fascinating operations problem, across Zomato's massive fleet, small waiting gaps like this add up to over 7.2 lakh hours a day.

Here's the math I did to find out what unlocking that gap could actually be worth and the number surprised me.

Every time we order food from Zomato, a delivery partner nearby gets a notification, picks up our order, and drops it at our doorstep. Simple enough.

But here's the part most people miss out on: between deliveries, that partner doesn't just vanish and reappear when a new order comes in. They're still online, logged into the app, available, but they're still waiting. Maybe they're parked at a signal. Maybe they're standing outside a mall hoping the next order comes from somewhere nearby. This waiting period is termed as idle time.

It's neither laziness nor a flaw, it's just physics. Orders don't arrive in a perfectly even manner. Sometimes there's a rush (lunch hour, dinner hour, rainy days), and sometimes there's a pause. A delivery partner can't control when the next order lands, so some amount of idle time is completely unavoidable in any system like this, whether it's Zomato, Swiggy, Uber, or Amazon delivery.

That's exactly the kind of problem data analysts are asked to think through in interviews, not because there's one "correct" answer, but because it tests whether you can take a vague, real-world question and break it into something you can actually calculate.

Every guesstimate needs real, sourced numbers to stand on, not random guesses. Here's what I used and where each one came from.

Final Guesstimate Assumptions:

Now let's actually do the math, plugging our assumptions in, one step at a time.

Before trusting any guesstimate, ask: does this number actually feel realistic?

Zomato processes roughly 23,00,000 orders a day. Our extra 1,45,684 deliveries/day works out to:

That's a small, believable lift, not an outrageous jump. If a 10% idle-time fix suddenly unlocked 50% more orders, that would be a red flag. A ~6% gain from a modest 10% efficiency improvement passes the smell test = proportionate, not magical.

Same goes for the rupee side: ₹72.8 lakh/day (≈₹266 crore/year) sounds big alone, but against Zomato's FY25 revenue of ₹20,243 crore, it's a reasonable operational-efficiency figure, not something that doubles the business overnight.

Numbers are easier to trust when you can actually see them. Here are two quick charts that bring this whole guesstimate to life.

So, what could Zomato actually do about this?

A simple, realistic starting point: predictive zone-wise demand mapping

Using historical order data (time of day, weather, local events, weekday vs weekend patterns) to nudge idle partners toward high-demand micro-zones before the rush hits, rather than reacting once orders pile up.

It doesn't require hiring more partners or changing anyone's hours but just smarter positioning of the partners already online. Even a modest shift in "partner is available but standing in a low-order area" idle time could meaningfully close the gap we calculated above, without adding cost to the system.