AS | Ankit Sarawagi · Founder, CFOmatrix · June 17, 2026 · 13 min read · Updated June 2026 |
Food tech in India is a business of thin margins, high platform dependency, and brutal fixed costs. Swiggy and Zomato take 20 to 30% of every order before the kitchen has paid for ingredients or packaging. Cloud kitchens pay rent on a facility that sits empty during off-peak hours. And yet, many founders track only revenue per kitchen or order volume, and discover the problem only when they run out of cash. This guide covers the 15 metrics that tell the real story of a food tech business: what to measure, how to calculate it, and what the numbers are actually telling you.
Key Takeaways
- Aggregator commission of 20 to 30% is the single largest variable cost on most cloud kitchen orders and must be modelled explicitly before claiming profitability
- Contribution margin per order is the only metric that tells you whether each order is making or losing money after all variable costs
- Kitchen utilization below 60% means your fixed costs per order are too high to build a viable unit economics model
- Food cost percentage above 30% for a delivery kitchen almost always results in negative contribution margins once packaging and commission are added
- AOV below Rs. 250 on aggregator platforms makes it nearly impossible to generate a positive contribution margin per order
- Repeat order rate is the food tech equivalent of NRR: it tells you whether customers find enough value to return without a discount
Table of Contents
20-30% Aggregator commission rate that every cloud kitchen must account for before claiming profitability. | Contribution margin Most food tech founders track revenue per kitchen but the real test is contribution margin per order after all variable costs. | 60%+ Kitchen utilization below this means your fixed kitchen costs are spread too thin per order. |
Why Food Tech Unit Economics Are Different
A cloud kitchen is not a software business. It has physical inventory that spoils, kitchen staff who need to be paid regardless of order volume, and a landlord who charges fixed rent whether you serve 50 orders or 500. Unlike SaaS, where every new customer is almost pure incremental margin, food tech has hard variable costs on every single order: ingredients, packaging, and often delivery.
What makes Indian food tech uniquely challenging is the platform layer. Swiggy and Zomato are not just distribution channels; they are toll booths that sit between the kitchen and the customer on every transaction. A founder who builds a unit economics model without putting aggregator commission front and centre is building a fictional business. The commission is not a marketing expense you can cut. It is the price of access to the customer.
The third layer of complexity is fixed cost absorption. A cloud kitchen typically has a breakeven occupancy level below which every additional order still leaves the kitchen in the red on a fully-loaded basis. Unlike a pure variable-cost business, the economics get dramatically better as volume increases, which means there is a critical mass problem: you need to reach a volume threshold before your economics work, but reaching that threshold requires discounts and promotions that destroy your contribution margin in the short term.
Revenue Metrics
Revenue metrics in food tech tell you the scale and structure of your business, but they need to be read carefully. High revenue per kitchen does not mean profitable per kitchen. High order volume does not mean strong unit economics. Always read revenue metrics alongside margin metrics.
Average Order Value (AOV)
AOV is the average revenue generated per order and is one of the most important levers a cloud kitchen can control. It directly affects how much margin is left after fixed costs like aggregator commission and packaging are deducted. A higher AOV spreads these fixed-per-order costs across more rupees of revenue, improving your contribution margin percentage.
For delivery-focused cloud kitchens, the benchmark is Rs. 250 to Rs. 450 per order. For dine-in restaurant setups, Rs. 600 to Rs. 1,200 is the range. Below Rs. 250 on an aggregator platform, achieving a positive contribution margin becomes structurally very difficult.
Revenue per Kitchen
Revenue per Kitchen measures the total revenue generated by each active kitchen location in a month. It is the top-level efficiency metric for a multi-kitchen cloud kitchen business and helps you identify which locations are scaling well and which are underperforming.
For a sustainable cloud kitchen operation, the benchmark is Rs. 8 to Rs. 15 lakh per kitchen per month. Below Rs. 5 lakh, most cloud kitchens struggle to cover their fixed costs of rent, staff, and utilities even before accounting for food and packaging costs.
Revenue per SKU
Revenue per SKU measures how much revenue each menu item generates in a given period. It identifies which dishes are driving your business and which are consuming kitchen capacity, ingredients, and staff time without contributing meaningfully to revenue. In most food businesses, the Pareto principle applies: the top 20% of SKUs drive roughly 80% of revenue.
Use this metric to make menu rationalisation decisions. Removing low-revenue, high-complexity SKUs reduces prep time, kitchen errors, and ingredient waste, which directly improves your food cost percentage and kitchen utilization rate.
Margin Metrics
Margin metrics are the most critical section of food tech unit economics. This is where founders discover whether their business model is actually viable or whether they have been growing a loss-making operation at scale. Every metric in this section must be positive and within benchmark before a cloud kitchen considers expanding to new locations.
Food Cost Percentage
Food Cost Percentage is the share of revenue consumed by raw ingredient costs. It is the most fundamental cost metric in any food business and the starting point for all margin analysis. A kitchen with high food cost percentage cannot achieve healthy contribution margins regardless of how well it manages other costs.
The target is below 30% for a delivery-focused cloud kitchen and below 35% for dine-in formats where ticket size is higher. Kitchens that run above 35% food cost on delivery are almost certainly contribution-margin negative once packaging and aggregator commission are added.
Packaging Cost per Order
Packaging Cost per Order is consistently one of the most underestimated costs in food tech. Founders who model their unit economics early often use a placeholder of Rs. 10 per order, only to discover that quality packaging for delivery, including containers, bags, tamper seals, and cutlery, costs Rs. 25 to Rs. 40 per order in practice.
Packaging costs typically range from Rs. 15 to Rs. 40 per order depending on cuisine type, portion size, and packaging quality standards. On a Rs. 300 order with 25% aggregator commission (Rs. 75), even Rs. 30 in packaging costs consumes another 10% of the order value before you have accounted for ingredients or delivery.
Aggregator Commission Rate
Aggregator Commission Rate is the percentage of each order’s value that Swiggy or Zomato retains as their fee for order placement, delivery facilitation, and platform access. It is typically the largest single variable cost on any aggregator-placed order and the number that most dramatically separates food tech economics from other consumer businesses.
Standard commission rates range from 20 to 30% depending on volume, exclusivity arrangements, and negotiated terms. At 25% commission on a Rs. 300 order, the platform retains Rs. 75 before the kitchen has spent a rupee on ingredients. This is why cloud kitchens must model contribution margin explicitly rather than working from a gross margin calculation.
Contribution Margin per Order
Contribution Margin per Order is the single most important metric in cloud kitchen unit economics. It measures how much each order contributes toward covering the kitchen’s fixed costs after every variable cost has been deducted. If this number is negative, every order you take is making your business worse, not better, and no amount of volume will save you.
A sustainable cloud kitchen should target a contribution margin of Rs. 40 to Rs. 80 per order. On a Rs. 350 order: 28% food cost (Rs. 98) + Rs. 30 packaging + 25% aggregator commission (Rs. 87.50) + Rs. 20 delivery allocation = Rs. 235.50 in variable costs, leaving Rs. 114.50 contribution margin. That contribution margin must then cover fixed costs like rent, staff, and utilities before generating profit.
Delivery Metrics
Delivery metrics measure the speed, cost, and reliability of getting orders from the kitchen to the customer. These metrics directly affect customer ratings on aggregator platforms, repeat order rates, and the cost structure of each order. Poor delivery metrics compound quickly because lower platform ratings reduce visibility, which reduces order volume, which worsens kitchen utilization.
Delivery Cost per Order
Delivery Cost per Order measures the total cost of delivering one order to the customer. For kitchens using aggregator delivery infrastructure, this cost is embedded in the commission structure. For kitchens operating their own delivery fleet or using third-party logistics for direct channel orders, this is a separate and significant cost line.
For own-delivery operations, the target is below Rs. 50 per order. At Rs. 70 or above, own delivery becomes a drag on contribution margin and many kitchens find that aggregator delivery is more cost-efficient even accounting for commission, unless they have very high order density in a small geographic area.
Average Delivery Time
Average Delivery Time measures the number of minutes from order confirmation to delivery at the customer’s door. It is a direct driver of customer satisfaction ratings on aggregator platforms, which in turn affects platform ranking, visibility, and order volume. It is also a proxy for operational efficiency within the kitchen.
Below 30 minutes is competitive in Indian metros. Consistently above 45 minutes typically results in lower customer ratings, more cancellations, and reduced platform visibility. Average delivery time is the output of two sub-metrics: preparation time and rider pickup and travel time.
Order Cancellation Rate
Order Cancellation Rate is the percentage of accepted orders that are subsequently cancelled before delivery, whether by the customer, the kitchen, or the platform. High cancellation rates damage platform ranking on Swiggy and Zomato, which directly reduces organic order visibility. They also represent wasted food preparation cost when cancellations happen after cooking has begun.
An acceptable cancellation rate is below 3%. Above 5% typically triggers algorithmic suppression of the restaurant’s visibility on aggregator platforms. The leading causes are order acceptance without capacity, long estimated delivery times that prompt customers to cancel, and menu items listed as available that are out of stock.
Operations Metrics
Operations metrics measure how efficiently the kitchen is converting its capacity into revenue. These metrics connect directly to fixed cost absorption and are the levers a cloud kitchen management team controls most directly day-to-day.
Kitchen Utilization Rate
Kitchen Utilization Rate measures how much of the kitchen’s maximum order capacity is being used. It is the most direct measure of fixed cost efficiency. A kitchen with high fixed costs (rent, staff, equipment) and low utilization has a very high fixed cost per order, which makes it almost impossible to achieve positive unit economics even with good variable cost management.
Maximum capacity is determined by prep time per order, number of kitchen staff, and available equipment. A kitchen with a 12-minute average prep time has a theoretical capacity of 5 orders per station per hour. At 60% utilization, you are using 3 of those 5 possible order slots, meaning your fixed cost per order is 1.67x what it would be at full capacity.
Preparation Time per Order
Preparation Time per Order measures the average number of minutes from order receipt to the order being ready for pickup by a delivery partner. It is a direct input into both Average Delivery Time and Kitchen Utilization Rate, and reducing it without sacrificing quality is one of the highest-leverage operational improvements a cloud kitchen can make.
The benchmark for a well-run cloud kitchen is 10 to 15 minutes per order. Above 20 minutes, delivery time suffers, rider wait times increase, and kitchen throughput decreases. Preparation time is reduced through menu rationalisation (fewer complex dishes), pre-preparation of components, clear station design, and SOP standardisation.
Repeat Order Rate
Repeat Order Rate measures the percentage of customers who placed more than one order from a kitchen within a defined period, typically 90 days. It is the food tech equivalent of Net Revenue Retention: it tells you whether your product is good enough to bring customers back without relying on discounts or platform promotions to drive each subsequent order.
A benchmark of 35% or above in a 90-day window indicates a healthy customer experience. Repeat customers have lower effective CAC, higher AOV on average (because they know what they like and order more), and significantly higher LTV. A kitchen with a 40% repeat rate needs to acquire only 60% as many new customers to maintain the same revenue as a kitchen with a 0% repeat rate.
Acquisition Metrics
Acquisition metrics in food tech are complicated by the platform layer. Most new customers are acquired through aggregator algorithms rather than through the kitchen’s own marketing. Understanding the true cost of acquiring a customer, including platform promotions and discounts, is essential to building a sustainable growth model.
Platform CAC
Platform CAC measures the total cost to acquire one new customer through Swiggy or Zomato, including all discounts funded by the restaurant, promotional campaigns, and sponsored listing fees. It is distinct from the aggregator commission, which is paid on every order. CAC is the additional spend required specifically to generate a first order from a customer who had not ordered from the brand before.
Platform CAC in Indian food tech varies widely, from Rs. 80 to Rs. 300 per new customer depending on the category, city, and discount depth. Given that contribution margin per order is often Rs. 40 to Rs. 80, a customer who places only one order is almost always acquired at a loss. Breakeven on CAC typically requires 3 to 4 repeat orders.
Customer LTV
Customer LTV in food tech measures the total contribution margin generated by a customer over their ordering lifetime. Unlike SaaS LTV, food tech LTV is driven by order frequency, AOV, and contribution margin per order rather than a subscription contract. A customer who orders twice a month at Rs. 350 AOV with Rs. 60 contribution margin generates Rs. 1,440 in annual LTV.
Breakeven on platform CAC typically requires 3 to 4 orders at standard contribution margins. A customer with a lifetime of 8 to 10 orders (reasonably achievable with a 35% repeat rate over 12 months) generates an LTV of Rs. 480 to Rs. 600 at Rs. 60 contribution margin per order, which comfortably exceeds a Rs. 150 to Rs. 200 platform CAC.
Food Tech Benchmarks for Indian Cloud Kitchens
These benchmarks reflect the typical range for Indian cloud kitchens and food tech startups across different stages of maturity. Early Stage refers to single-kitchen operations under 12 months. Growth Stage refers to kitchens that have proved their model and are expanding to 3 to 10 locations. Mature refers to established multi-city operations with optimised unit economics.
“In food tech, revenue per kitchen is vanity and contribution margin per order is sanity. Every cloud kitchen founder needs to know their contribution margin number before opening a second location.”
Ankit Sarawagi, CFOmatrixNeed help building your cloud kitchen unit economics model? CFOmatrix helps food tech founders set up contribution margin tracking, kitchen utilization dashboards, and investor-ready unit economics before their next raise. | Talk to CFOmatrix |
Frequently Asked Questions
What is a healthy contribution margin per order for a cloud kitchen in India?
A healthy contribution margin per order for an Indian cloud kitchen is between Rs. 40 and Rs. 80 per order. After accounting for food cost (25 to 30%), packaging (Rs. 15 to Rs. 40), aggregator commission (20 to 30%), and any delivery cost, the margin that remains must be enough to cover your kitchen’s fixed costs of rent, staff, and utilities. Kitchens with AOV below Rs. 250 on aggregator platforms often find it structurally impossible to generate a meaningful positive contribution margin per order.
How does aggregator commission affect cloud kitchen unit economics?
Aggregator commission from Swiggy or Zomato typically ranges from 20 to 30% of the order value. On a Rs. 300 order, that is Rs. 60 to Rs. 90 going to the platform before you have paid for ingredients or packaging. This single cost line often makes the difference between a positive and a negative contribution margin per order. Cloud kitchens must either negotiate lower commission rates as order volume grows or develop direct ordering channels to reduce aggregator dependency. There is no way to build a healthy unit economics model while ignoring this number.
What kitchen utilization rate is needed for a cloud kitchen to break even?
A cloud kitchen typically needs at least 60 to 70% kitchen utilization to cover its fixed costs. Below 60%, the fixed cost per order (rent, staff, equipment) is spread across too few orders and remains too high to allow the business to break even even with good variable cost management. At 75 to 85% utilization, fixed costs are absorbed across enough orders that the kitchen can generate meaningful profit. Utilization rate is arguably the single most important operational lever in cloud kitchen economics.
How do you calculate food cost percentage for a cloud kitchen?
Food Cost Percentage = (Total Food Ingredient Cost / Total Revenue) x 100. For a delivery-focused cloud kitchen, the target is below 30%. To calculate this accurately, track actual raw material consumption against orders produced rather than just using purchase invoices, since waste, spoilage, and over-portioning all increase true food cost above what procurement records show. Track food cost at the dish level, not just the aggregate, because a blended food cost of 28% can hide individual dishes running at 45% that are dragging down your overall margins.
What AOV should a cloud kitchen target on Swiggy and Zomato?
A cloud kitchen on Swiggy or Zomato should target an Average Order Value of Rs. 300 to Rs. 450 for delivery. Below Rs. 250, the aggregator commission and packaging cost consume such a large proportion of the order value that achieving a positive contribution margin becomes very difficult. Kitchens can increase AOV through meal bundles, add-on upsells, and minimum order thresholds. Even a Rs. 50 increase in AOV can meaningfully improve contribution margin percentage since the variable costs of commission and packaging represent a lower percentage of a larger order value.
Related Articles
Unit Economics Every Startup Must Track: The Complete CFO Guide Logistics Unit Economics: Metrics Every Delivery Startup Must Track Marketplace Unit Economics: Metrics Every Platform Startup Must TrackAS | Founder, CFOmatrix | Finance Strategy & Equity Compliance CFOmatrix is a knowledge platform focused on how finance actually works inside growing companies. Every insight is shaped by real operating experience across startups and growth-stage companies, including cross-border setups. |