BakeCostDee1. Separate purchase quantity from recipe usage
If a 1-kilogram bag of flour costs 4.50 and the recipe uses 250 grams, the recipe does not use the whole 4.50 package. Convert compatible units to the same base, then cost only the amount used.
Repeat the process for every ingredient. Do not assume that weight and volume are interchangeable without a reliable density or an explicit conversion rule.
2. Build the complete batch cost
Add every ingredient usage cost. Then include the packaging, labour, allocated overhead, and waste that belong in your bakery's costing policy. Keep batch-level costs separate from per-item costs so that the same amount is not counted twice.
Different shops include different costs. Consistency matters: use the same boundary when comparing two products or reviewing how a cost changed over time.
3. Use sellable yield
Yield is the number of pieces, slices, jars, boxes, or other units available to sell from the batch. If a brownie tray produces 16 sellable pieces, divide by 16. If the same tray is cut into 12 larger pieces, the cost per piece changes even when the batch cost stays the same.
Illustrative example: A complete batch costs 36.00 and produces 16 sellable pieces. Cost per piece is 2.25. If the same batch produces 12 sellable pieces, cost per piece is 3.00.
4. Cost is not the selling price
Cost per serving is a base for a pricing decision. A selling price may also need to account for target margin, platform fees, tax, delivery terms, and the market context you verify for your own business. Once the cost is clear, use the profit margin and selling price calculator to review a proposed price.
Common costing mistakes
- Using the full package price when the recipe uses only part of it
- Converting weight to volume without a reliable rule
- Leaving out packaging, labour, overhead, or waste that the shop intends to count
- Dividing by planned output instead of sellable output
- Using sample or outdated purchase prices as current facts
A repeatable workflow
Keep purchase price, purchased quantity, purchased unit, recipe usage, usage unit, and yield as separate fields. When a supplier price or package size changes, you can update the affected input and review the result rather than guessing from the old selling price.