Knowing what a dish costs sounds simple. Add up the ingredients, divide by the number of portions, and compare that number to the menu price.In practice, restaurant recipe costing gets complicated quickly.
You may buy an ingredient by the case but use it by the ounce. A sauce on the plate may contain six ingredients of its own. Prep yields change what an ingredient actually costs to use. And the price you paid for eggs, beef or produce last month may not be the price you're paying today.
That means a recipe that worked when you created it can quietly become a margin problem.
Accurate recipe costing gives chefs and operators a way to see those changes earlier—and make decisions before they show up in the P&L.
To calculate food cost for a restaurant dish, add the cost of every ingredient used in the recipe, including sub-recipes, and divide the total recipe cost by the number of portions produced. To calculate food cost percentage, divide the cost per serving by the menu price and multiply by 100.
What Is Restaurant Recipe Costing?
Restaurant recipe costing is the process of calculating the total ingredient cost of a recipe based on the quantities actually used to produce it.
Three basic calculations provide the foundation:
Total Recipe Cost = Sum of the Cost of Every Ingredient Used
Food Cost per Serving = Total Recipe Cost ÷ Number of Servings
Food Cost % = Food Cost per Serving ÷ Menu Price × 100
The math isn't particularly difficult. Getting accurate numbers into the calculation is where restaurant operations get complicated.
How to Calculate Restaurant Food Cost in 5 Steps
1. List every ingredient and sub-recipe
Start with everything that goes into the finished dish—not just the most expensive or obvious ingredients.
Include proteins, produce, sauces, dressings, oils, garnishes and other components. If an ingredient is itself a prepared recipe, such as an aioli or tomato sauce, include the appropriate portion cost of that sub-recipe.
2. Convert purchase units into the units you actually use
Restaurants rarely use ingredients in the same units in which they purchase them.
You might buy pizza dough by the case, cheese by the pound and pepperoni in a bulk package. The recipe, however, might call for one dough ball, four ounces of cheese and 30 slices of pepperoni.
Accurate costing requires converting the purchase price into the unit actually used in the recipe.
3. Account for yield
Determine how much usable product your purchase or batch actually produces.
Trimming, fabrication and cooking can change ingredient yields. Prepared sauces, dressings and other batch recipes also need accurate finished yields so you know what each ounce, pint or quart actually costs.
4. Calculate the recipe cost and cost per serving
Add the cost of every ingredient used to determine the total recipe cost.
Then divide that number by the number of servings the recipe produces.
5. Calculate the food cost percentage
Finally, divide the food cost per serving by the menu price and multiply by 100.
That gives you the food cost percentage for the dish.
Restaurant Food Cost Formula: A Simple Example
Suppose a restaurant sells a chicken entrée for $18.
IngredientQuantity UsedCostChicken8 oz$2.40Rice6 oz$0.45Sauce3 oz$0.75Vegetables4 oz$0.80Garnish—$0.20
Total cost per serving
$4.60
Using the food cost percentage formula:
$4.60 ÷ $18 × 100 = 25.6% food cost
The calculation itself is straightforward. The challenge is making sure that $4.60 accurately reflects current ingredient prices, actual yields and the real cost of any sub-recipes used in the dish.
That's where recipe costing becomes an ongoing operational process rather than a one-time calculation.
Why Restaurant Recipe Costing Gets Complicated
Account for Yield, Not Just Purchase Price
Yield is one of the easiest ways for restaurant recipe costs to become inaccurate.
A restaurant doesn't necessarily use 100% of what it purchases. Produce gets trimmed. Proteins may lose weight during fabrication or cooking. A batch recipe may produce a different quantity than the person entering the recipe assumes.
Even the way recipes are written can create problems.
Curtis Dettman, Director of Operations at Pau Hana, describes yield as one of the bigger hurdles his team encounters when documenting recipes. One chef might develop a recipe in grams that produces half a pint, while the prep team actually needs to produce the item by the quart.
Pau Hana's goal is to standardize those yields so the prep team can easily scale production based on what the restaurant actually needs.
Instead of relying on institutional knowledge—"I know this batch usually gives us about this much"—the yield becomes part of the recipe itself.
That matters for costing because the cost of a batch isn't particularly useful until you know how much usable product the batch produces.
A centralized restaurant recipe management system can also help teams maintain those yields, conversions and preparation standards as recipes change.
Don't Forget the Recipes Inside Your Recipes
Most restaurant dishes aren't built entirely from purchased ingredients.
They're built from other recipes.
A pizza might include a house-made tomato sauce. A steak might include a demi-glace, compound butter and dressing. A sandwich could contain a house pickle, aioli and slaw.
Each is a sub-recipe with its own ingredients, yield and cost.
If four ounces of sauce goes onto a pizza, the cost of those four ounces should reflect the current cost of every ingredient that went into the sauce.
This is where spreadsheet-based costing can become particularly difficult to maintain. Change the cost of an ingredient used across several sauces, dressings and finished dishes, and that change needs to flow through every recipe that uses it.
Connected recipe costing makes those relationships visible.
Use Current Ingredient Costs, Not Last Month's Spreadsheet
A perfectly constructed recipe cost isn't particularly useful if it is based on old purchasing data.
Ingredient prices move.
James Passafaro, a chef and the founder of opsi, pointed out during a recent conversation with Dettman that the challenge of menu development has changed. Developing the idea may not be the hardest part anymore. With supply-chain changes and fluctuating prices, understanding whether the idea works financially can be considerably harder.
Dettman gave eggs as a simple example. When egg prices change dramatically, the team can see not only that the cost of a dish is moving, but identify which ingredient is causing it.
That distinction matters.
If the food cost of a dish moves from 26% to 31%, the solution isn't necessarily to rethink the entire recipe. One ingredient may account for most of the increase.
Knowing which one gives the chef options.
Can you source it differently? Change the portion? Substitute an ingredient? Adjust the menu price? Rework the dish?
You can't answer those questions if all you know is that "food cost went up."
Connecting restaurant invoice processing with recipe costing can help teams keep ingredient prices current as new purchases are made rather than periodically rebuilding costs from old spreadsheets.
Know What a Dish Will Cost Before It Hits the Menu
Recipe costing becomes much more useful when it is part of menu development rather than an analysis performed afterward.
Dettman's team recently experienced this while developing a new steak dish at Pau Hana.
They built the recipe from the ground up, adding the steak, sauces and other components. By the time the recipe was complete, they could see that it was running at approximately 52% food cost.
The reaction was immediate: the dish wasn't going to work as constructed.
That's the value of costing during development.
Instead of putting the steak on the menu, selling it for several weeks and eventually discovering that the margin isn't there, the culinary team can ask the important questions before launch:
What can we change?
Maybe it's the cut of steak. Maybe it's the portion. Maybe it's a component on the plate. Maybe it's the menu price.
The specific answer depends on the restaurant.
The important thing is having the information while there's still time to make the decision.
Recipe Costing Should Help Chefs Create, Not Prevent Them From Creating
There's a natural tension between culinary creativity and operational controls.
But standardization and costing don't have to restrict creativity. Done well, they create useful boundaries around it.
Pau Hana brings in fresh fish regularly and develops weekly specials. Dettman doesn't need to stand over the chefs as they create those dishes. He can see the recipe being developed, understand its cost and make sure it fits the culinary and financial expectations of the restaurant.
His chefs can see the same information.
Instead of waiting for the Director of Operations to tell them a dish is too expensive, they already understand the cost target they're working toward.
That's a fundamentally different relationship between creativity and cost control.
The system isn't there to tell chefs what to cook. It gives them the information they need to create something that works for both the guest and the business.
Recipe Costs Should Change as Your Costs Change
A recipe isn't finished just because someone entered it into a system.
Purchase prices change. Vendors change. Pack sizes change. Yields get refined. Portions evolve.
That means recipe costing shouldn't be an exercise the restaurant performs once a year—or only when somebody suspects food cost is getting out of control.
The most useful model connects what the restaurant is buying today with what the kitchen is producing today.
When the cost of an ingredient changes, operators should be able to understand which recipes it affects.
When the team changes a recipe, they should be able to see how that affects the cost.
When a new invoice changes the price of a product, that information should feed the restaurant's broader cost picture. Connecting recipe costing with restaurant inventory management can help keep product, recipe and inventory values aligned.
And when someone develops a new dish, they should know whether the economics work before it reaches a guest.
From Recipe Costing to Better Restaurant Operations
The real value of recipe costing isn't the calculation.
It's what the restaurant can do with the answer.
Accurate recipe costs can help teams:
- Evaluate new dishes before putting them on the menu.
- Identify the ingredient responsible for an unexpected cost increase.
- Standardize portions and prep yields.
- Understand the cost of sauces, dressings and other sub-recipes.
- Respond more quickly to changing vendor prices.
- Give chefs visibility into the financial implications of their decisions.
- Maintain consistency as more employees and locations become involved.
That last point becomes increasingly important as restaurants grow.
When recipes, costs and standards exist only in the executive chef's head, the chef has to remain involved in countless small decisions.
Documenting those standards and connecting them to current purchasing information allows the knowledge to move from an individual to the organization.
Recipe Costing in Practice
Beyond Green Partners uses opsi to centralize its recipe information and costing while connecting invoice information with current costs. The team reports that this approach has helped it manage recipe costs while reducing the manual work previously required to reformat invoices and receipts.
See how Beyond Green Partners approaches restaurant recipe costing with opsi →
How opsi Simplifies Restaurant Recipe Costing
opsi connects restaurant recipes with purchasing and invoice data so operators can understand what dishes cost based on how ingredients are actually being purchased and used.
Recipes can include yields, purchasing-to-usage conversions and linked sub-recipes. As ingredient costs change, teams have greater visibility into how those changes affect the dishes that use them.
With opsi food costing software, current invoice data can update ingredient pricing used for recipe costing, while cost histories and profitability reporting help operators understand how those costs are changing over time.
That allows recipe costing to become part of everyday restaurant operations rather than another spreadsheet someone has to remember to update.
For chefs like Dettman, the larger benefit is time.
As his role has expanded from Executive Chef to Director of Operations, he has increasingly relied on systems that allow his teams to work independently while still giving him visibility into what's happening.
The goal isn't to put more numbers in front of chefs.
It's to give them the information they need to make better decisions—and more time to lead their teams.
Explore opsi Food Costing Software →
Restaurant Recipe Costing FAQs
How do you calculate food cost?
Add the cost of every ingredient used in a recipe, including the appropriate cost of any sub-recipes. Divide the total recipe cost by the number of servings produced to determine food cost per serving. Accurate calculations should account for purchase-unit conversions and usable yields.
How do you calculate food cost percentage?
Divide the food cost per serving by the menu price and multiply by 100.
Food Cost % = Food Cost per Serving ÷ Menu Price × 100
For example, if a dish costs $4.60 to produce and sells for $18, its food cost percentage is approximately 25.6%.
How do you calculate the cost per serving of a recipe?
Add the cost of all ingredients used to determine the total recipe cost. Then divide that amount by the number of servings the recipe produces.
Cost per Serving = Total Recipe Cost ÷ Number of Servings
What is recipe costing?
Recipe costing is the process of determining what it costs to produce a recipe based on the quantities and costs of the ingredients used. Restaurant recipe costing can also account for factors such as ingredient yields, unit conversions and the cost of prepared sub-recipes.
What is a good food cost percentage for a restaurant?
There isn't one appropriate food cost percentage for every restaurant or every dish. Targets depend on the concept, menu mix, pricing strategy and broader economics of the operation. The more useful comparison is often whether a dish meets the restaurant's established cost target and contributes appropriately to the overall menu.
Why does recipe yield matter?
Yield determines how much usable product a purchased ingredient or prepared recipe actually produces. If yield isn't accurate, the cost assigned to each portion can also be inaccurate.
What is a sub-recipe?
A sub-recipe is a prepared component used within another recipe, such as a sauce, dressing, dough, marinade or spice blend. Its ingredient costs and yield should be calculated so the appropriate portion cost can be included in the finished dish.
How often should restaurants update recipe costs?
Recipe costs should reflect current purchasing information closely enough to help operators make decisions as ingredient prices change. Connecting recipe information with current purchasing and invoice data can make significant cost changes easier to identify than relying entirely on periodic manual updates.