resources

how to cost
a recipe.

the step-by-step process for calculating what every dish and drink on your menu actually costs — and pricing it to make money.
why it matters

recipe costing is the
foundation of profitability.

the reality

most operators don't know what their dishes actually cost.

ask a chef what their signature dish costs and you'll usually get a rough estimate — "somewhere around eight bucks." that's not good enough when your margin on a $24 entree is the difference between $7.20 profit and $4.80 profit.

recipe costing is the process of calculating the exact ingredient cost for every item you serve. it connects your purchasing to your menu to your P&L. without it, you're setting prices based on intuition, competitor menus, or "what feels right" — none of which account for your actual costs.

the restaurants that consistently hit their food cost targets are the ones that cost every recipe, update costs when ingredient prices change, and price their menu from the numbers — not from the gut.
the payoff

recipe costing unlocks menu engineering.

once you know the cost and margin of every item, you can make strategic decisions:

• which items to promote (high margin, high popularity)
• which items to redesign (low margin, high popularity)
• which items to reprice (high margin, low popularity)
• which items to cut (low margin, low popularity)

this is menu engineering — and it's impossible without accurate recipe costs. a well-engineered menu can improve your food cost by 3–5 percentage points without changing a single recipe. that's $15,000–$25,000 per year for a restaurant doing $500K in food revenue.

recipe costing also tells your kitchen team what matters. when they know that the truffle oil costs $0.85 per drizzle, they use a drizzle instead of a pour.
step by step

the five-step recipe
costing process.

step 1

list every ingredient with exact quantities.

write down every ingredient that goes into the dish — including the ones people forget: oil for sauteing, salt, pepper, garnish, sauce on the side, the bread that comes with it.

example: mushroom risotto (1 batch = 6 servings)
• arborio rice: 2 lbs
• mixed mushrooms: 1.5 lbs
• yellow onion: 0.5 lbs
• garlic: 2 oz
• white wine: 8 oz
• vegetable stock: 48 oz
• butter: 4 oz
• parmesan: 6 oz
• olive oil: 2 oz
• salt, pepper, herbs: estimated

be specific about quantities. "some butter" is not a recipe — it's a suggestion. use weight (ounces, pounds) or volume (fluid ounces, cups) consistently.
step 2

find the unit cost for every ingredient.

for each ingredient, calculate the cost per unit of measure used in your recipe. this requires converting from purchase units to recipe units.

examples:
• arborio rice: $18 for a 10 lb bag → $1.80/lb
• mixed mushrooms: $6.50/lb from your produce vendor
• yellow onion: $12 for a 50 lb bag → $0.24/lb
• garlic: $3.20/lb → $0.20/oz
• white wine (cooking): $8 bottle / 25.36 oz → $0.32/oz
• vegetable stock: $14 for 1 gallon (128 oz) → $0.11/oz
• butter: $4.50/lb (16 oz) → $0.28/oz
• parmesan: $12/lb → $0.75/oz
• olive oil: $22/liter (33.81 oz) → $0.65/oz

use your actual purchase prices from invoices — not retail prices. update these when your distributor changes pricing.
step 3

calculate total recipe cost.

multiply each ingredient's quantity by its unit cost, then sum everything up.

mushroom risotto (6 servings):
• arborio rice: 2 lbs × $1.80 = $3.60
• mixed mushrooms: 1.5 lbs × $6.50 = $9.75
• yellow onion: 0.5 lbs × $0.24 = $0.12
• garlic: 2 oz × $0.20 = $0.40
• white wine: 8 oz × $0.32 = $2.56
• vegetable stock: 48 oz × $0.11 = $5.28
• butter: 4 oz × $0.28 = $1.12
• parmesan: 6 oz × $0.75 = $4.50
• olive oil: 2 oz × $0.65 = $1.30
• salt/pepper/herbs: $0.50 (estimated)

total batch cost: $29.13

don't skip the small ingredients. salt, pepper, herbs, and cooking oil add up to 2–4% of total recipe cost across your menu. use a flat estimate per recipe or calculate it — but don't ignore it.
step 4

determine cost per serving.

divide total recipe cost by the number of servings the recipe produces.

$29.13 ÷ 6 servings = $4.86 per serving

if the dish comes with sides, add those costs too. a mushroom risotto served with a side salad ($0.85) and bread ($0.40) brings the total plate cost to $6.11.

this is your true cost per plate — the number you use for menu pricing. for cocktails and drinks, the same logic applies: total ingredient cost divided by number of drinks the recipe makes. see our pour cost calculator for drink-specific examples.

important: recipe costing covers ingredient cost only. it does not include labor, overhead, or waste. those are accounted for in your overall food cost percentage target.
pricing

from cost to menu price.

step 5

set your sell price using target food cost.

menu price = plate cost ÷ target food cost %

for our mushroom risotto at $6.11 plate cost:
• at 28% food cost: $6.11 ÷ 0.28 = $21.82 → price at $22
• at 30% food cost: $6.11 ÷ 0.30 = $20.37 → price at $21
• at 32% food cost: $6.11 ÷ 0.32 = $19.09 → price at $19

your target food cost depends on your venue type and overall prime cost goals. see our food cost formula guide for benchmarks by venue type.

always round to a clean number. $21.82 becomes $22. the extra $0.18 per plate is pure margin — across 30 servings a week, that's $280 per year from one rounding decision.
ideal margins

target margins by category.

food items:
• appetizers: 65–75% gross margin (25–35% food cost)
• entrees: 62–72% gross margin (28–38% food cost)
• desserts: 70–80% gross margin (20–30% food cost)
• sides: 72–82% gross margin (18–28% food cost)

beverage items:
• cocktails: 78–85% gross margin (15–22% pour cost)
• wine by glass: 70–75% gross margin (25–30% pour cost)
• draft beer: 75–80% gross margin (20–25% pour cost)

your menu doesn't need every item at target. it needs the blended average at target. high-cost proteins can run at 40% food cost if they're balanced by high-margin appetizers and desserts at 22%.
role-based views

different teams need
different information.

who sees what

recipe costing data should be role-appropriate.

not everyone needs to see every number. the most effective operations show each role exactly what they need:

kitchen / bar team: recipe specs, ingredient quantities, plating instructions, allergen flags. they need to execute the recipe correctly every time. they don't necessarily need to see costs.

sous chef / bar manager: recipe specs plus ingredient costs, waste tracking, and prep quantities. they're responsible for execution and efficiency.

chef / GM / owner: full recipe costing, food cost percentages, margin analysis, menu engineering data. they're making pricing and menu decisions.

front of house: ingredient lists (for guest questions), allergen information, and menu descriptions. no cost data — just what they need to sell and serve safely.

this isn't about secrecy. it's about clarity. showing a line cook the cost breakdown of every dish doesn't help them cook better. showing them exact quantities and clear instructions does.
keeping costs current

a recipe cost card is only as good as its last update.

the number one reason recipe costing fails is that costs go stale. you build beautiful recipe cost cards, ingredient prices change over the next six months, and suddenly your "30% food cost" menu is running at 35%.

when to re-cost recipes:
• when any key ingredient price changes by more than 10%
• when you change suppliers or distributors
• when you modify the recipe (even slightly)
• at minimum, quarterly — even if nothing seems to have changed

what triggers a menu price update:
• re-costed recipe shows food cost more than 2 points above target
• seasonal ingredient costs shift significantly
• you're consistently above your target blended food cost

in a spreadsheet, re-costing 50–100 recipes is a multi-hour project. most operators put it off, which is exactly why food cost drifts. the solution is a system that re-costs automatically when ingredient prices update — so your recipe costs are always current, not three months old.
olldae. costs your recipes automatically.
start free trial
14 days free · no card required · set up before service