A Recipe Costing Example: From Ingredient Cost to Menu Price

A chicken sandwich can be one of the best sellers on the menu and still quietly erode margin. The problem is rarely the sandwich itself. It is the gap between what the kitchen thinks it costs and what the current ingredients, portions, and batch yields actually say. This recipe costing example walks one dish through the full journey — ingredient cost, batch-prepped components, menu price, and what happens when a supplier raises prices — so the math is grounded in real numbers instead of a formula on its own.

The objective is not to create a spreadsheet that looks precise once. It is to build a costing process that holds up after a supplier price change or when a new prep cook joins the team.

TL;DR

• This example costs a fried chicken sandwich at $3.04 per serving, built from actual purchase units, recipe portions, and batch yields — not a guess
• The batch-yield formula (batch cost ÷ portions produced) used here is the same one behind any recipe cost calculation — see How to Calculate Recipe Cost for the full formula breakdown
• Turning $3.04 into a menu price uses Menu Price = Recipe Cost ÷ Target Food Cost % — the complete pricing framework, including waste buffers, is in How to Price Menu Items at a Small Restaurant
• A single $4 case-price increase on one ingredient pushed this sandwich's food cost from about 29% to nearly 32% without anyone changing the menu price — margin erodes quietly unless someone is watching

Why recipe costing needs more than a case price

A case price is not an ingredient cost. It only becomes useful when you know the purchase unit, the usable amount, and the exact portion in the recipe. If chicken is purchased by the five-pound case but each sandwich receives six ounces, the recipe needs the cost of those six ounces, not the cost of the entire case.

The same principle applies to sauces, garnishes, seasoning, and sides. Small items are often where a recipe cost becomes misleading. Leaving off one ounce of aioli, a pickle portion, or the fries served with an entree may not move a single plate dramatically. Across hundreds of covers, those omissions create a false sense of margin.

A disciplined recipe cost answers three operating questions:

1. What does one completed serving cost at current supplier prices?
2. Does the selling price support the target food cost percentage?
3. Which ingredient changes require a review before margin slips?

The number is only as credible as the recipe standard behind it. If the team portions chicken by feel, the cost is a guess. If the recipe specifies six ounces and the line uses a scale, the cost becomes a control point.

A recipe costing example for a chicken sandwich

Assume a restaurant sells a fried chicken sandwich with fries. The standardized recipe includes a six-ounce chicken portion, one brioche bun, two ounces of slaw, one ounce of aioli, pickles, and a six-ounce fry portion.

The kitchen buys chicken in five-pound cases for $24. A five-pound case contains 80 ounces, so the chicken costs $0.30 per ounce. At a six-ounce portion, the chicken cost per sandwich is $1.80.

The other ingredient costs are calculated from their purchase units in the same way. The costing sheet should retain the purchase detail, not just the final recipe number. That gives a manager a clear audit trail when an invoice changes or a team member questions the math.

The total recipe cost is $3.04 per serving.

Cost batch-prepped components by yield

Slaw is a useful example because it is not purchased in one ready-to-serve portion — it uses the same batch-yield formula as any recipe with a batch output: total batch cost divided by the portions the batch actually produces. Suppose a prep batch uses cabbage, dressing, seasoning, and other ingredients totaling $4.40. After prep, the batch produces 20 usable sandwich portions.

$4.40 batch cost ÷ 20 portions = $0.22 per slaw portion

That yield matters. If the batch is expected to produce 20 portions but routinely produces 16, the recipe cost is not $0.22. It is $0.275 per portion. The difference may look small, but it signals an execution problem: portions may be oversized, prep may be discarded, or the written recipe may not reflect actual production.

Document the expected batch yield next to the prep recipe. Then have the kitchen record the produced yield when it materially differs. This gives the chef or kitchen manager a fact to investigate instead of an assumption to argue about.

Account for usable product, not ideal product

Some ingredients lose weight through trimming, cooking, or unavoidable prep waste. When that happens, the recipe should reflect the usable quantity the kitchen can serve. A case of produce that yields less usable product than expected has a higher per-serving cost than its invoice price suggests.

This does not mean every item needs a complicated calculation. High-volume proteins, produce with meaningful trim, and house-made prep are the priority. A single-use packaged item can usually be costed directly. Apply detail where it changes decisions.

Turn plate cost into a menu price

Once the completed plate cost is $3.04, pricing becomes a clear calculation instead of a menu-market guess. Using the standard formula — Menu Price = Recipe Cost ÷ Target Food Cost % — a restaurant targeting 30% food cost on this item would price at:

$3.04 ÷ 0.30 = $10.13

A listed price of $10.50 lands at roughly 29% food cost, just inside target. For the complete pricing framework — including how to build in a waste buffer and how to test a price increase without losing customers — see How to Price Menu Items at a Small Restaurant. What matters in this example is the discipline it demonstrates: set the target, calculate from the current plate cost, and decide deliberately — not because a price worked last season.

Keep the recipe cost current after purchasing changes

The initial calculation is the easy part. Margin protection depends on what happens next.

If the chicken case rises from $24 to $28, its per-ounce cost increases from $0.30 to $0.35. The six-ounce portion now costs $2.10, adding $0.30 to every sandwich. The full recipe cost rises from $3.04 to $3.34.

At the unchanged $10.50 menu price, food cost moves from about 29% to nearly 32%. That may be acceptable temporarily, or it may require action. The operator can review the supplier, revise the menu price, adjust the recipe only if guest value remains intact, or accept a lower margin for a strategic item. The point is to see the choice before it becomes a monthly surprise.

A recipe costing system should preserve one source of truth for ingredient purchase prices, recipe portions, batch yields, and completed dish costs. When the supplier cost changes, the affected recipe costs need to update with it. Dinezy supports this by letting an authorized user update an ingredient's price after purchasing, which recalculates every recipe using that ingredient automatically — and the recipe margin overview lets you filter by margin threshold to find items like this sandwich before a quiet price increase becomes a quarter-end surprise.

The same discipline scales beyond one location, too — see Multi-Location Restaurant Management Software for how store-level accountability works when more than one kitchen is producing to the same recipe standard.

Where restaurant recipe costs usually fail

Most errors are operational, not mathematical. The spreadsheet formula may be correct while the inputs are outdated or incomplete.

The first failure is using old invoice prices instead of the latest actual purchase price — a fast way for a recipe cost to become a historical record instead of a decision tool.

The second is costing the recipe but not the plate. Sides, sauces, toppings, and packaging for off-premise orders all belong in the serving cost when they are part of what the guest receives — exactly the aioli, pickles, and fries in this example, not just the chicken.

The third is allowing portion standards to drift. A six-ounce protein portion that becomes seven ounces changes food cost by 16.7% for that ingredient alone. A scale, portion scoop, and clear recipe photo can protect more margin than a complicated report.

Finally, operators sometimes treat recipe costing as a finance exercise completed by one person. It is a kitchen execution standard. Cooks need the portion instructions. Managers need approval control over recipe changes. Owners and operations leaders need a current view of which price movements affect the menu.

Make This the Standard, Not a One-Time Exercise

Start with the dishes that carry the most volume or the highest ingredient cost. Cost them completely, verify the portions on the line, and compare the result against their current menu prices. Then review those recipes whenever purchasing costs change and whenever the kitchen changes how an item is made.

A reliable recipe cost is not paperwork. It is proof that the menu can run the same on the days you are not in the store — with portions controlled, prices understood, and margin decisions made before the profit disappears.

Frequently Asked Questions

Do I need to cost every garnish and side, or just the main protein? Cost the whole plate, not just the centerpiece. In this example, aioli, pickles, and fries add up to $0.62 per serving — about 20% of the total recipe cost. Skipping the small components is one of the most common ways a recipe cost understates reality.

What if my batch yield varies day to day, like the slaw in this example? Yield variance usually points to a recipe consistency problem, not a costing problem. If a batch meant to produce 20 portions is only producing 16, the per-portion cost jumps from $0.22 to $0.275 — cost at the lower, more conservative yield until the batch is standardized.

How much does a single ingredient price increase actually move my margin? In this example, a $4 rise in the chicken case price (from $24 to $28) moved the sandwich's food cost from about 29% to nearly 32% at an unchanged menu price. On a single high-volume item, that is a meaningful shift — which is why the recipe cost needs to be revisited when the invoice changes, not just when someone happens to notice.

Does this batch-yield method match how Dinezy calculates recipe cost? Yes. Dinezy calculates recipe cost the same way this example does — total batch ingredient cost divided by the number of portions the batch produces — so the yield already accounts for trim, waste, and prep loss without a separate multiplier.

Key Takeaways

• A recipe cost is only as reliable as its inputs: real purchase units, real recipe portions, and real batch yields — not case price alone
• The batch-yield formula (batch cost ÷ portions produced) applies to any prepped component, from a slaw batch to a signature drink
• Menu Price = Recipe Cost ÷ Target Food Cost % turns a plate cost into a defensible price — see the full pricing framework for waste buffers and price testing
• A single ingredient price change can move food cost several points on one item alone; recipe costs need to be revisited when purchasing changes, not on a fixed schedule
• Recipe costing is a kitchen execution standard, not a finance-only exercise — cooks, managers, and owners each need a different view of the same numbers

Dinezy calculates recipe cost per serving using the same batch-yield math as this example — set your batch yield, and the cost per portion stays accurate. When a supplier price changes, every recipe using that ingredient recalculates automatically, and the recipe margin overview lets you filter by margin threshold to catch items like this one before a quiet price increase becomes a quarter-end surprise.

Try Dinezy free at dinezytech.com