Recipe Costing in 2026: Why a Dish You Costed Once Is Quietly Losing You Money Right Now

Tomato prices in India climbed 31% year-on-year to ₹42/kg in June 2026, up from ₹32/kg a year earlier, according to CRISIL Intelligence's Roti Rice Rate report — with edible oil and LPG cylinder prices moving roughly 10% higher over the same period. That report tracks what a home kitchen pays for a plate of food. A restaurant kitchen buys the same tomatoes, the same edible oil, and cooks over the same LPG connections — just at a scale where a 31% swing on one ingredient can quietly move a dish's food cost percentage by several points without anyone touching the menu price.

Most restaurants only discover that shift when someone finally re-runs the numbers — often months after the dish was first costed, if it was costed with real precision at all.

The problem with costing a recipe once and moving on

Recipe costing usually happens once: when a dish is added to the menu, or when a new outlet opens. The ingredient prices at that moment become "the cost" of the dish in everyone's head, and the menu price gets set against them. Then ingredient prices move — sometimes gradually, sometimes the way tomato has in 2026 — and the dish's actual food cost % quietly drifts away from the number the price was originally set against, while the menu still shows the old price.

Here's what that drift looks like on paper. Say a tomato-based paneer curry uses 150g of tomato per portion. Costed back when tomato was ₹32/kg, that's roughly ₹4.80 of the total recipe cost. At June 2026's ₹42/kg, the same 150g now costs roughly ₹6.30 — a difference that looks trivial on a single plate. Multiply it across 40 portions a day, every day, across a menu where five or six dishes lean on a tomato-based gravy, and the "trivial" difference stops being trivial. And that's before accounting for the edible oil in the gravy and the LPG used to cook it, both up roughly 10% over the same stretch.

How to cost a recipe correctly, from scratch

A recipe cost is only as accurate as the inputs behind it. The formula is simple; the discipline is in how it's fed:

• List every ingredient in the recipe by the exact quantity used per portion — grams and millilitres, not "a handful" or "some"
• Price each ingredient at its current market cost, not whatever you happened to pay on your last purchase order
• Include everything the dish actually needs to reach the plate — cooking oil, spices, garnish, and packaging if it's going out for delivery
• Total ingredient cost ÷ number of portions the recipe yields = cost per portion
• Cost per portion ÷ target food cost % = the price that dish needs to sell at to hit that target

A worked example, done properly

Take a dal makhani portion, recosted at June 2026 wholesale prices, with a 30% target food cost:

Ingredient	Quantity used	Cost
Black lentils & kidney beans	120g	₹22
Butter & cream	60g / 40ml	₹28
Tomato (puree & fresh)	100g	₹4.20
Cooking oil, ghee	15ml	₹6
Spices, garnish	—	₹9
Total cost per portion		₹69.20

At a 30% target food cost, that portion needs to sell at roughly ₹231 to hit target. If the menu was last priced when tomato, oil and LPG all sat lower, the dish may currently be listed anywhere from ₹10–20 under that — a gap that's easy to miss on one dish and expensive across a full month of covers.

How often you should actually be recosting

"Once a year" is the default for most restaurants, and it's not enough — not when a single ingredient category can move 31% inside twelve months. A more useful rule is to split ingredients by volatility:

• High-volatility inputs — tomato, onion, edible oil, LPG, and any seasonal produce — deserve a price check monthly, or immediately after a >10–15% market move, since these are exactly the categories that move fastest and hit the most dishes at once
• Stable inputs — packaged dry spices, staples with long shelf lives, branded packaging — can reasonably be reviewed quarterly
• Any dish that leans heavily on one volatile ingredient (a tomato-based gravy, anything fried in a large quantity of oil) should be flagged for a check whenever that specific ingredient moves, regardless of the general schedule

What to do once recosting shows you're underwater

Finding the gap is only useful if it changes something. The usual options, roughly in order of how disruptive they are to the customer:

• Absorb it short-term if the price spike looks temporary — tomato prices in India are seasonal and do come back down, and reprinting a menu for a two-month spike isn't always worth it
• Adjust the recipe spec slightly — portion size, garnish quantity, or a cheaper cut without changing the dish's identity
• Reprice the specific dish rather than the whole menu, when the ingredient driving the gap is concentrated in a handful of items
• Substitute where it doesn't compromise the dish — switching a fresh-tomato base to a stable-priced tinned puree for high-volume prep, for instance

The one option that doesn't work is doing nothing and hoping the gap closes itself. It usually doesn't — it just sits quietly inside your food cost % until someone finally runs the numbers again.

Making this a habit, not a one-time exercise

The hard part of recipe costing was never the arithmetic — it's remembering to redo it. A recipe costing calculator makes the math instant once you have current prices in front of you; what actually protects your margin is treating that recalculation as routine, especially for the handful of ingredients that move the most.

If your online delivery pricing is set separately from your dine-in menu, it's worth checking that too — the same ingredient swings hit both, but the commission and packaging costs on delivery orders mean the gap shows up differently there.

Recost a dish with Setu's free Recipe Costing Calculator →

See how the same cost swings affect your Zomato and Swiggy pricing →

See how Setu Dine keeps live ingredient and recipe costs in one place →