Rappi Building a Full-Stack Platform
Rappi
Rappi is trying to own more of the delivery stack so it can raise order frequency, lower delivery cost per order, and sell higher margin services on top of food traffic. The dark kitchen buildout matters because it changes the network from one courier moving one order at a time to a denser hub-and-spoke system, while payments, ads, travel, and e-commerce give Rappi more ways to keep the same customer and merchant inside one app.
-
The kitchen strategy is less about launching Rappi branded food and more about giving existing restaurant partners extra capacity in delivery-heavy zones. In practice, that lets strong brands open new delivery catchments without funding a full storefront, while Rappi gets more predictable pickup points and better courier utilization.
-
The Meituan comparison is really about revenue mix and customer behavior. Rappi still gets about 75% of revenue from merchant commissions and delivery fees, but it has already added ads, subscriptions, e-commerce, travel, and payments, and more than 90% of customers buy from at least two categories, with frequency rising from 2 orders a month in year 1 to 11 by year 5.
-
This full-stack push also strengthens merchant lock in. Rappi is not just sending orders, it can bundle lead generation, logistics, priority placement, inventory adjacent fulfillment, and integrated payments. That is the same basic logic Meituan used in China, where food created habit and the surrounding services captured more gross profit.
The next phase is a deeper split between thin margin order aggregation and thicker margin infrastructure. If Rappi keeps converting food demand into payments usage, ad spend, subscriptions, and fulfillment density, it can look less like a delivery app and more like the operating system for urban commerce in Latin America.