How to cost a recipe properly

Costing a recipe sounds like adding up receipts. It isn't, and the gap between those two things is where a lot of small food businesses quietly lose money. The number you want is the cost of the exact quantity of each ingredient that ends up in one batch — and almost nothing you buy is sold in the unit your recipe calls for.

Step 1: Get every ingredient onto one unit

You buy flour by the kilo and use it by the gram. You buy oil by the litre and use it by the tablespoon. If you cost by eye, you end up comparing 5 kg against 20,000 g and the arithmetic silently drifts.

The fix is to convert everything to a canonical base unit before you do any arithmetic at all, and only convert back for display:

• Anything measured by weight → grams
• Anything measured by volume → millilitres
• Anything measured by length → centimetres
• Anything counted → pieces

So a ₱85 bag holding 500 g of flour is ₱0.17 per gram. A ₱240 litre of oil is ₱0.24 per millilitre. Once every ingredient has a per-base-unit price, a recipe line is just quantity × price, and units stop being able to bite you.

Step 2: Handle the ingredients you buy by the piece

This is the one that catches nearly everyone. Some ingredients are sold by count but used by weight — eggs, bay leaves, sheets of gelatine, banana leaves. You cannot convert between a piece and a gram without knowing what one piece weighs, and if you guess, the error is the size of the weight itself.

Work it in two moves. Price per piece first, then bridge to grams with a per-piece weight you measure once:

• Price per piece = pack price ÷ pieces in the pack
• Price per gram = price per piece ÷ grams in one piece

A ₱10 pack of 20 bay leaves weighing about 2 g each is ₱0.50 per leaf, and ₱0.25 per gram. Skip the bridge and treat the pack as "₱10 for 20 g" and you get ₱0.50 per gram — double the real cost, on an ingredient you use in small quantities across many recipes. Eggs are the same trap in the other direction and at a larger scale.

Step 3: Cost the batch, then the serving

Add up every line at its per-base-unit price. Include the things people leave out because they aren't food:

• Packaging — boxes, labels, ribbon, the sticker with your logo on it
• Materials that get consumed — parchment, piping bags, gloves
• Anything you make in-house and then use as an ingredient, costed as its own recipe

Divide the batch total by the yield to get cost per serving. Be honest about yield: if a tray reliably gives you 22 usable pieces rather than the 24 you cut, cost it at 22. Trim, spillage and the piece that broke are real costs, and rolling them into the yield is the simplest way to account for them.

Step 4: Stop the number going stale

A costing is a snapshot of supplier prices on the day you did it. Prices move. The common failure is a spreadsheet where each recipe holds its own copy of the flour price — update the price in one place and forty recipes stay wrong.

Keep one price per ingredient, stored against the ingredient itself, and have every recipe read it. Then a single edit to the flour price re-costs everything that uses flour. This is the single highest-leverage structural decision in a costing system, and it's the reason ChefAiQ never stores a price on a recipe line.

A worked example

Batch cost ₱346.50, yield 12 boxed portions, ₱28.88 per serving. Note the eggs: priced per piece at ₱6.67, bridged to ₱0.121 per gram. Treating that ₱200 tray as "₱200 for 30 g" would have put eggs at ₱6.67 per gram — a ₱1,100 error on a ₱346 batch.

What to do with the number

Cost per serving is an input, not an answer. It tells you your floor. What you charge depends on your margin target, and what you earn depends on how many you sell against your fixed costs — which is a different calculation entirely.