Latest / Marketplace Businesses with Fexingo: Two-Sided Networks, Liquidity, and Take Rates / How Uber Eats Uses Surge Pricing to Balance Restaurants and Riders
Transcript
- Lucas: So Luna, I don't know about you, but I've been staring at my delivery app at 7:30 on a rainy Tuesday, and the same burrito bowl that cost eleven bucks yesterday is suddenly fourteen fifty. And I'm thinking, this is not random. This is a pricing signal doing exactly what it's designed to do. Luna: Right, and most people just see it as a rip-off. But from the marketplace side, surge pricing is one of the most elegant tools for keeping liquidity alive when demand spikes and supply can't keep up. Lucas: Exactly. And today I want to drill into how Uber Eats specifically uses surge pricing to balance two sides of the market: the restaurants that can cook, and the riders who can deliver. Because when that balance breaks, you get the classic marketplace failure — long wait times, cancellations, and people just closing the app. Luna: So walk me through the mechanics. How does Uber Eats actually decide when to turn on surge? Lucas: It's a real-time matching problem. The algorithm looks at the number of active delivery requests versus the number of available riders in a given zone. If the ratio crosses a threshold — say, two requests for every available driver — surge kicks in. That multiplier, usually between 1.1 and 2.5 times, gets applied to the delivery fee or the menu price, depending on the market. Luna: And that price increase does two things at once. It discourages some customers from ordering, which lowers demand, and it makes the trip more attractive to riders, which pulls more supply into the zone. Lucas: Exactly. It's a two-sided price signal. On the demand side, you see a higher total and maybe you decide to cook instead. On the supply side, riders see the multiplier and think, okay, I'll head toward that zone. That simultaneous rebalancing is what makes surge so powerful — it's not just a tax on impatient people. Luna: But there's a catch, right? Surge can overshoot. If the multiplier gets too high, you get no orders at all, and then riders leave because there's nothing to do. Lucas: That's the real art. The algorithm is constantly adjusting, sometimes every few minutes. A 1.5x surge might bring in ten extra riders, but a 2x surge might drive away half your customers. Uber has spent years tuning those thresholds per city, per time of day, even per weather condition. Luna: And the interesting thing is, surge isn't just about the multiplier. It's about where the surge is applied. I've noticed that sometimes the menu price stays the same but the delivery fee jumps. Other times it's the opposite. Lucas: Right, and that's a deliberate design choice. If you surge the delivery fee, it feels more transparent — you're paying for the rider's time. If you surge the menu price, it's less visible but can be more effective because customers anchor to the base price. Uber Eats has tested both, and they've found that a fee surge tends to reduce demand more efficiently, but a menu surge is better at increasing rider earnings per trip. Luna: So it's a trade-off between transparency and efficiency. That's a classic marketplace dilemma. Lucas: It is. And there's another layer: the 'surge shadow.' That's the term for when the app shows a surge multiplier on the customer screen, but the actual rider payout is lower than that multiplier suggests. Uber has faced criticism for this — customers think they're paying a 1.5x premium, but the rider might only get 1.2x. Luna: That seems like it could erode trust on both sides. If riders feel shortchanged, they might decline trips in surge zones, which defeats the purpose. Lucas: Exactly, and that's why Uber has been pushing toward more transparent surge payouts in recent years. They want riders to see the exact multiplier they'll earn before they accept. Because if the rider doesn't trust the surge, the whole mechanism falls apart. Luna: Let's talk about the restaurant side for a second. Restaurants don't control surge, but they're affected by it. If surge drives away customers, they lose volume. But if surge brings in more riders, they get faster delivery, which might mean better reviews. Lucas: That's a great point. Restaurants are kind of the silent third party in this two-sided marketplace. They don't set the price, but they feel the impact. Uber has experimented with giving restaurants some control, like letting them opt out of surge on their own menu items, but that's rare because it can create confusion. Luna: And there's also the question of how surge affects the take rate. When prices go up, does Uber's commission go up too? Lucas: Yes, and that's an interesting revenue angle. Uber takes a commission on the total order value, so when surge inflates the price, Uber's take rate in dollars goes up. But the percentage commission stays the same. So surge actually boosts Uber's revenue per order, which is why they're incentivized to keep it efficient. Luna: So surge isn't just a matching tool — it's a revenue tool. But it has to be used carefully, because if it feels exploitative, customers will churn. Lucas: Exactly. And that's why Uber has been working on making surge more predictable. They've introduced features like 'surge notifications' that tell you prices will go up in 15 minutes, so you can order before the spike. That gives customers a sense of control, even though it's still the algorithm calling the shots. Luna: I want to bring in a comparison. DoorDash doesn't use surge pricing the same way, right? They have a flat delivery fee and rely more on peak pay bonuses for drivers. Lucas: Yeah, DoorDash uses a more static fee model but they do have 'peak pay' which is similar to surge on the supply side. The key difference is that DoorDash tends to keep the customer price stable and adjust driver pay separately, so customers see less volatility. That's a deliberate brand choice — they want to feel predictable. Luna: But that means DoorDash might be less efficient at balancing supply and demand in real time. They might have longer wait times during peak hours. Lucas: That's the trade-off. Surge pricing, when done well, can match supply and demand in minutes. DoorDash's approach is smoother but might lag. There's no universally right answer — it depends on the market and the brand promise. Luna: So what's the lesson for someone running their own marketplace? You don't have to be a delivery giant to use surge pricing. Lucas: Exactly. Any two-sided marketplace with capacity constraints can use dynamic pricing as a signal. Think about a freelance platform where demand for developers spikes during a product launch. You could introduce a premium rate for urgent projects, which encourages developers to take them and discourages customers from posting last-minute jobs. Luna: That's a great example. The key is to design the signal so it moves both sides at once. Lucas: And to monitor the feedback loop. Surge works when the multiplier is high enough to attract supply but low enough to keep demand alive. It's a delicate balance, and it only works if both sides feel like they're getting a fair deal. Luna: Before we wrap up, I want to say something. If today's episode actually helped you think about your own marketplace, the way we keep these conversations ad-free is through listener support. You can buy us a coffee at buy me a coffee dot com slash fexingo. Lucas: Yeah, that's a big deal for us. It means we can keep digging into these mechanics without any sponsor pressure. So if you've gotten value from this, that's the way to keep it going. Luna: And now back to the topic. I want to push back on something you said earlier, Lucas. You mentioned that surge is a durable tool, but haven't some cities tried to ban it? Lucas: They have. In 2020, New York actually capped surge pricing on ride-hailing, and there have been similar proposals for delivery apps. The argument is that surge exploits customers during emergencies, like storms or public health crises. But the counterargument is that without surge, you'd have no drivers at all during those times. Luna: So it's a regulatory flashpoint. How do marketplaces respond? Lucas: They've had to get creative. Some have moved toward 'soft surge' — smaller multipliers that stay within regulatory limits. Others have introduced 'surge caps' that kick in during emergencies but allow normal surge at other times. The goal is to keep the marketplace functional without looking predatory. Luna: That's a smart approach. It shows that surge pricing is not a monolith — it's a flexible tool that can be tuned to fit both market conditions and public expectations. Lucas: And that's the real takeaway. Surge pricing is not just about raising prices. It's about maintaining liquidity, which is the lifeblood of any marketplace. When done right, it benefits all three sides: customers get faster delivery, riders earn more, and the platform stays healthy. Luna: So the next time you see that 1.5x multiplier, you'll know it's not just a price hike. It's a signal that the market is working. Lucas: Exactly. And if you're building a marketplace, think about how you can use pricing signals to keep your own network in balance. It's one of the most powerful tools you have.