Rappi delivery strategy: the traditional method versus the Masterestaurant method

The aggregator channel does not destroy margin because of the commission; it destroys margin because nobody costs a delivery order as a separate business unit. A Rappi delivery strategy works when you run the channel as its own P&L, with its own menu, its own food cost ceiling of 32% per dish and its own break-even in orders per hour. The traditional method adds a flat 20% to every price and hopes; the Masterestaurant method builds the decision architecture — per-channel menu engineering, a virtual brand riding the same kitchen line, dashboards that read operational variability while it happens — and the order stops being a favor you do for the app. Food delivery apps keep growing year over year: the channel is not going away. The channel is not going away. What you decide is whether you enter it with unit economics or with faith.
An operator in the USD 500,000 to 1 million revenue band showed me a quarterly Rappi report: 4,100 orders, a solid average ticket, and a channel margin that turned red the moment we loaded packaging, hot-line waste and the hours of one prep hand assigning bags. Commission was not the culprit. The delivery menu was simply the dining-room menu, same low-margin dishes, same execution times a single line cannot hold when two channels fire at once.
That is the pattern almost everywhere. Owners judge the channel by gross sales — the number the app dashboard puts in front of them — instead of contribution margin per order, which is the only figure that decides whether to scale or shut it down. Growth hides the flaw: online food delivery keeps expanding in both Colombia and Mexico, and in neither market does volume replace proper channel costing. When volume rises on its own, inefficiency hides behind revenue.
My argument is not that you should negotiate harder with the aggregator. Stop treating delivery as a byproduct of the dining room and engineer it: a channel-specific menu, a virtual brand when the kitchen has slack, BOH automation so orders reach the KDS without anyone retyping them, and a board that tells you this week — not at month close — whether channel prime cost moved.
Side-by-side: Rappi delivery strategy
| Traditional Rappi playbook | Masterestaurant method | |
|---|---|---|
| Channel unit economics | ✕One P&L; app orders blend with the dining room and per-order margin stays unknown | ✓Per-channel P&L: contribution margin per order including commission, packaging and assembly labor |
| Delivery menu food cost | ✕Same dining-room card; dishes above 35% food cost ship to the app unfiltered | ✓Filtered card with a 32% food cost ceiling per dish; slow, low-margin items removed |
| Channel average ticket | ✕Left to the customer, with no combos or attach architecture | ✓Menu engineering with combos and beverage/dessert attach designed for the channel |
| Order entry into the BOH | ✕Separate tablet; orders retyped into the POS, with errors at peak | ✓POS/KDS integration; zero retyping and acceptance time under control |
| Installed kitchen capacity | ✕One brand on a line with paid off-peak hours that bill nothing | ✓Virtual brand on the same line, switched on only in low-occupancy windows |
| Data reading and decisions | ✕The aggregator panel at month close; decisions by perception | ✓Smart dashboard tracking food cost variance and orders/hour against break-even, reviewed weekly |
| Territory risk and dependency | ✕A single aggregator concentrates demand; no owned channel | ✓Governed mix of aggregators plus direct ordering, with territory risk measured by delivery zone |
| Price governance | ✕Flat 20% uplift across the menu, no per-dish elasticity | ✓Per-channel price set dish by dish against the order break-even |
1. Why does the Rappi channel eat your margin even as revenue climbs?
Because the delivery order gets costed inside the dining-room P&L, and that is where the bleeding stays invisible.
The quarterly report I mentioned —4,100 orders, an average ticket of 38,000 pesos— showed respectable gross sales, yet channel profit turned negative the moment we loaded packaging, hot-line waste and the hours of the assistant who assembles bags. Commission was not the culprit. The missing piece was a separate income statement, in a market that moved USD 1.18 billion in Colombia during 2024 and grows at a 7.32% CAGR through 2029 (Statista Market Insights, 2024). Volume rises on its own and hides the inefficiency: you bill more every month while contribution margin per order falls, and no dashboard tells you. Close that blind spot before you argue rates with anyone.
2. A P&L per channel: the accounting decision that orders every other one
Open a separate income statement for delivery and charge it every peso the channel consumes. Platform commission, packaging, the extra waste of dishes that travel badly, and —almost nobody does this— the labor hours dedicated to assembly and dispatch. With delivery apps in sustained year-over-year growth, a channel without its own costing stopped being a tolerable experiment: it is a business line you run blind. At Masterestaurant that separation opens every diagnosis, because it changes the whole conversation. Once delivery carries its own prime cost, the question stops being «how much did we sell through Rappi?» and becomes «how much did we KEEP on each order dispatched?». Two different questions, and only the second one decides anything.
3. The dining-room menu is not the delivery menu
Publishing the full menu on the app looks generous and is the fastest way to give away profit. Long-execution, high-food-cost dishes leave with a flat 20% surcharge that never covers commission plus packaging plus waste, while they occupy the griddle your kitchen needs for the dining room. The rule I apply: publish what survives the trip, sits below 30% food cost and executes in under twelve minutes. That usually leaves 35% to 45% of the original menu. Against the urge to show everything, the short catalog sells more per order, because a guest looking at nine options decides in twenty seconds and adds a side. Mexico, at USD 9.22 billion with a 14.66% CAGR (Statista, 2024), rewards whoever tidies the catalog before scaling.
4. Under USD 500K a year: don't scale, prune
In this band there is one decision: no virtual brand, no buying more volume, prune the current catalog until every published dish yields positive contribution margin after commission. The operating threshold is 25% contribution margin per order, calculated on the app price, never the dining-room price. A dish that misses it leaves the catalog that same week. The small band remains fertile ground —the global cloud-kitchen market was estimated at USD 45.65 billion in 2024 (MarkNtel Advisors, 2024)— but the recurring error here is chasing that growth before the arithmetic is settled. First the pruned catalog and a properly built surcharge; afterward, and only afterward, the conversation about volume. A venue in this band with twelve profitable dishes earns more than one with forty undifferentiated ones.
5. USD 500K to 1M: cost the order and split the station
Here the lever is operational rather than commercial: build a separate dispatch station and measure channel prime cost every week. The operator in the case lived exactly this problem, with two channels fighting over the same hot line and an assistant whose cost nobody charged to delivery. The threshold I set him: channel prime cost —food plus direct dispatch labor— stays under 62% of net delivery sales, already net of commission. Two consecutive weeks above it and you cut catalog or raise the surcharge, no debate. That flat 20% surcharge also needs a dish-by-dish review, because a 22% food-cost starter and a 34% main course do not deserve the same treatment. Brazil, at roughly USD 18.8 billion in 2024 (Statista, 2024), proved that volume forgives nothing when there is no dedicated station.
6. Above USD 1M: a virtual brand only if the kitchen has slack
A virtual brand earns its place when your kitchen runs below 70% capacity in the valley shifts and you can launch it on existing inventory. That is the threshold. Without real slack, a second brand generates no incremental sales: it cannibalizes the first and adds dispatch complexity that degrades both their times. With slack, the arithmetic turns good, because fixed cost is already paid and each extra order arrives almost free of structure. Mexico's cloud-kitchen market reached USD 1.1 billion in 2024 with a 10.74% CAGR toward 2033 (IMARC Group, 2024), and that is the window. One more rule: the virtual brand shares no dishes with the main one —it shares INGREDIENTS, a very different thing— or the guest spots the trick and you lose both reputations at once.
7. Above USD 5M: automate the back of house before you touch commission
At this volume, an order somebody types by hand into the KDS costs you more than any commission point you might negotiate. Integrate the app into the ticket system and kill the manual entry: fewer dispatch errors, fewer remakes, fewer dead minutes. This band holds the profile we all recognize —the large-format themed venue, or the one backed by a media figure— where delivery usually runs as an appendix of the dining room and ends up damaging the brand through delivery times nobody tracks. My criterion: above five million, delivery either has an owner with a name and a budget, or it should not exist. Asia-Pacific ghost kitchens went from USD 21.73 billion in 2024 toward a projected USD 60.59 billion by 2032, a 12.8% CAGR (Coherent Market Insights, 2024): the scale arrived, dispatch discipline has not.
8. Above USD 10M: govern the channel as a business unit
A group or chain in this band needs formal channel governance: a consolidated P&L plus one per location, a monthly committee reviewing contribution margin by unit, and a written shutdown threshold. Mine: if a location spends two quarters under 18% contribution margin in delivery, with catalog and station already fixed, the channel goes dark at that location. It hurts and it works, because delivery is no strategic obligation: it is a line that must earn its place. Consider what happens if commission rises three points tomorrow —the sector has seen it more than once—: with a channel P&L you know within forty-eight hours which locations and which dishes fall underwater, and you act; without one, you find out next quarter, after the loss. Ghost kitchens ran near USD 70.4 billion in 2024 (Research and Markets, 2024), and that pool hands no margin to whoever fails to measure it.
9. The four differences that move EBITDA
The first one is accounting, and it orders everything else: the traditional playbook runs a single income statement, so delivery either subsidizes or gets subsidized with nobody noticing, while the Masterestaurant architecture opens a per-channel P&L and charges every order its commission, packaging, waste and the hours of whoever packs the bag. With delivery apps still expanding year after year, an uncosted channel is no longer an experiment. It is a blind business line. Menu design is the second gap. Publishing the whole dining-room card looks generous and turns out to be the fastest way to give margin away, because long-execution, high-food-cost dishes travel with a flat 20% uplift that never covers commission plus packaging. We filter on two hard criteria — a 32% food cost ceiling per dish and execution times compatible with two simultaneous channels — and then run channel-specific menu engineering, where combos lift the average ticket without touching unit price. Third comes installed capacity.
10. The four differences that move EBITDA — in practice
A kitchen that bills hard from noon to 2:00 p.m. and again from 7:00 to 9:00 p.m. carries paid hours that produce nothing, which makes a virtual brand on the existing line the cheapest scalability play available today. Cloud kitchens are growing at an 11.65% CAGR between 2022 and 2032 according to Statista/Toast (via OysterLink), with close to 7,606 ghost kitchens already active in the US. Building a dark kitchen from scratch is not the entry ticket. The fourth difference is the one fewest operators work on: data governance. If your read on the channel is the aggregator panel at month close, you decide with stale numbers biased toward revenue. A dashboard that crosses food cost variance, orders per hour against channel break-even and acceptance time by window turns the operation into a decision architecture — and it hands you operational due diligence arguments when you sit down to negotiate with the app or raise capital.
Scorecard: traditional versus Masterestaurant
What the average operator does
- Reads the channel through gross sales in the Rappi panel, never contribution margin per order.
- Publishes the full dining-room menu, including dishes above 35% food cost.
- Applies a flat 20% uplift and trusts it covers the commission.
- Retypes orders from tablet to POS and loses minutes during the 8:00 p.m. peak.
- Does not know how many orders per hour the channel needs to clear break-even.
- Depends on one aggregator and owns no customer database.
What the Masterestaurant architecture does
- Opens a channel P&L with commission, packaging, waste and assembly labor inside prime cost.
- Filters the delivery card at a 32% food cost ceiling with measured execution times.
- Prices each dish against the order break-even instead of a flat uplift.
- Integrates orders into POS/KDS and automates the BOH to kill retyping.
- Runs a virtual brand on the same kitchen only in off-peak windows with free capacity.
- Governs the mix between aggregators and direct ordering, with territory risk by zone.
- Reviews food cost variance and orders/hour weekly on a dashboard, not at month close.
Figures that frame the decision
“We had 4,100 orders in the quarter and I was convinced Rappi was my best salesperson. Once we split the channel income statement, USD 1,900 a month showed up in packaging, hot-line waste and the hours of the prep hand who packed bags; none of it sat in my commission report. We cut the delivery card from 46 dishes to 19, all under 32% food cost, and switched on a virtual chicken brand over the same fryer between 3:00 and 6:00 p.m. Two months later the average ticket climbed about 22% and the channel finally feeds EBITDA instead of masking it.”
Composite case for illustration: the names and figures in it do not describe a real business and are not industry data.
Strategic roadmap in three phases
Deliverable: the Rappi delivery P&L split from the dining room, with commission, packaging, waste and assembly labor inside prime cost, plus the orders per hour needed to clear channel break-even. Timeline: 21 days using the last 90 days of aggregator and POS data. Success metric: contribution margin per order known within ±3%, and 100% of published dishes classified by real food cost. This is where the surprise usually shows up — the channel was not expensive, it was uncosted.
Deliverable: a delivery card filtered at a 32% food cost ceiling per dish, combos built to lift average ticket, order integration into POS/KDS with no manual retyping, and per-dish pricing calculated against break-even rather than the flat 20% uplift. Timeline: six weeks, with the new card live by week 6. Success metric: channel average ticket up 12% or more, acceptance time under 90 seconds at peak, and zero orders typed by hand. If your dining room runs a physical menu, keep it: the QR and the app complement the digital channel and never replace control of the table experience.
Deliverable: one virtual brand running on the same line only during off-peak windows, a weekly dashboard with food cost variance, orders/hour against break-even and territory risk by delivery zone, plus a governed mix of aggregators and direct ordering backed by an owned customer database. Timeline: ten weeks, with a committee review every 14 days. Success metric: 15% or more of delivery revenue coming from the owned channel, and channel food cost variance under 2 points month over month. Scaling before this board exists is betting, not investing.
And with AI?
Optimize channels, pricing and unit economics of your dark kitchen. Diego F. Parra is an expert in AI applied to restaurants.
Rappi delivery strategy: free tools
How it gets executed
This architecture does not live in a spreadsheet someone updates when they remember. It lives in the Masterestaurant tool ecosystem, where costing, break-even and channel reading all hang off the same data.
Diego F. Parra built these tools so an owner under USD 500,000 in annual revenue decides with the same rigor as a group above USD 10 million: same model, different scale.
Questions a board asks
What does it cost NOT to fix the Rappi delivery strategy?
What does it cost NOT to fix the Rappi delivery strategy?
It costs the margin of a channel that grows on its own. With delivery apps in sustained growth, volume rises and hides inefficiency; without a per-channel P&L you cannot tell whether you scaled profit or loss, and you decide blind on your fastest-growing line.
Should we open a dark kitchen from scratch or launch a virtual brand?
Should we open a dark kitchen from scratch or launch a virtual brand?
Start with a virtual brand on your current kitchen: it uses off-peak hours you already pay for and needs no capex. A dark kitchen from scratch makes sense once channel volume saturates your line and the market supports it, as the sustained growth of the cloud kitchen market suggests.
Should we depend on one aggregator or several?
Should we depend on one aggregator or several?
A single aggregator concentrates territory risk and strips your negotiating power. Spread across aggregators — Rappi, iFood depending on the country — and build direct ordering on an owned database; in large-scale markets, single-channel dependency is a corporate governance risk.
What food cost can a delivery dish carry?
What food cost can a delivery dish carry?
The ceiling is 32% per dish, and that ceiling is a maximum, not a target. Above it, aggregator commission plus packaging and assembly labor eat contribution margin. Filter the card before publishing it and leave slow-execution dishes out.
Rappi delivery strategy by the numbers (2026)
Verifiable industry benchmarks from official, non-commercial sources (government, industry associations, market research) - not competitors.
| Metric | Value | Source |
|---|---|---|
| Share of US restaurant operators that get 0-10% of revenue from third-party delivery, 2026 mid-year report | 47,2 % de los operadores (0-10 % de ingresos desde delivery de terceros, 2026) | Restaurant365 — 2026 State of the Restaurant Industry: Mid-Year Report (2026) |
| Typical per-order commission that delivery platforms charge U.S. restaurants (range), on top of delivery and payment processing fees (2025) | 15 a 30 por ciento por pedido (2025) | Wharton Magazine — Are Food Delivery Apps Hurting Restaurants? (2025) |
| Estimated value of Mexico's food delivery market, second largest in Latin America after Brazil (2024) | 2,530 millones de dólares (2024) | Expansión citando a Statista — México es el segundo lugar en el uso de Rappi, Uber Eats y Didi Food gracias a Mipymes (2025) |
| Share of the 70,000+ restaurants on the Didi Food platform in Mexico that are small and medium businesses (2025) | 60 % de más de 70,000 restaurantes (2025) | Expansión citando a Didi Food — México es el segundo lugar en el uso de Rappi, Uber Eats y Didi Food gracias a Mipymes (2025) |
| Mexican SMBs on Uber Eats that reported higher revenue since joining the platform (Quadrant Strategies study) | 91 % de las MiPymes afiliadas | Expansión citando a Quadrant Strategies — México es el segundo lugar en el uso de Rappi, Uber Eats y Didi Food gracias a Mipymes (2025) |
| Mexican SMBs on Uber Eats saying the app helped them reach new customers they otherwise would not have reached (Quadrant Strategies) | 89 % de las MiPymes encuestadas | Expansión citando a Quadrant Strategies — México es el segundo lugar en el uso de Rappi, Uber Eats y Didi Food gracias a Mipymes (2025) |
Download this document as PDF
The full text is free to read on this page. To take the corporate PDF with you, leave your details — we'll also email you the direct link.
Related content
Rappi delivery strategy: the Masterestaurant method
Applied in +8.400 restaurants across 43 countries.
