Rappi's Partner-Run Dark Kitchen Network
Sebastian Mejia, co-founder of Rappi, on building for multi-verticality in on-demand
This setup turns dark kitchens into merchant infrastructure, not a bet against merchants. Rappi supplies locations, demand, and courier density, while restaurant partners do the cooking and day to day operations. That keeps kitchen labor and brand execution with the restaurants, gives strong brands a faster way to add delivery only capacity, and helps Rappi cluster orders into a hub and spoke network that lowers delivery cost per order.
-
Rappi frames the kitchens as an expansion tool for existing partners, using its order data to spot which restaurant brands have enough traction to justify more capacity. The partner gets a new production site without building a full dine in location, and Rappi gets more reliable supply in dense zones.
-
The operating model matters because marketplaces usually struggle to integrate further upstream. In online grocery and delivery, platforms add dark kitchens or dark stores to control more of fulfillment and improve economics. Rappi applies that playbook while still leaving food prep with merchants, which is a lighter model than fully owning the kitchen operation.
-
The payoff is in route density. Rappi estimates delivery expense at 10% of GMV versus 14% to 16% for Asian peers and 32% for Uber Eats. Its broader network, 200K plus couriers, and hub based fulfillment let couriers stack orders on similar routes instead of making one restaurant to one home trips.
Going forward, the winners in delivery will look more like logistics operators for merchants than simple listing apps. If Rappi keeps turning partner restaurants into distributed kitchen nodes, it can deepen merchant dependence, raise order density, and extend the same operating system into groceries, convenience, and other fast local commerce categories.