> For the complete documentation index, see [llms.txt](https://docs.foodcore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foodcore.io/troubleshooting/recipe-cost.md).

# My recipe cost looks wrong

Recipe costs in FoodCore are calculated from your ingredient purchasing data — the cost per pack, the pack size, and the quantity used in the recipe. When any one of those figures is wrong, the cost per recipe will be wrong too. The good news is that the cause is almost always a data entry issue, and it's quick to fix.

***

## Most likely cause: wrong pack size

This is by far the most common culprit. Here's the scenario:

You add "Plain Flour" and enter the cost as £1.80. The pack size field defaults to 1, and you don't change it. FoodCore now thinks you paid £1.80 for 1 gram of flour. A recipe using 500g of flour will show a flour cost of £900.

It looks absurd when written out, but it's easy to miss at the time — especially if you're quickly entering several ingredients in a row.

**Fix it:**

1. Go to **Ingredients** and open the affected ingredient
2. Open the **Purchasing** tab
3. Check the **Pack size** field — it should be the total quantity in the pack (e.g. 500 for a 500g bag, 1000 for a 1kg bag, 5 for a 5-litre container)
4. Check the **Pack cost** field — this should be what you pay for that whole pack
5. **Save** the ingredient
6. Go back to the recipe and click **Recompute**

The recipe cost will recalculate immediately using the corrected figures.

***

## Other common causes

**Ingredient cost is £0.00**

If you added an ingredient as a placeholder and never entered the purchasing data, it will cost nothing. The recipe cost will be understated by exactly the amount that ingredient should contribute.

Fix: open the ingredient → **Purchasing** tab → enter the correct cost per pack and pack size → save → recompute the recipe.

**Wrong unit — grams vs kilograms**

If your ingredient is set up with a unit of kilograms, but your recipe uses it in grams, FoodCore will interpret "500" as 500kg rather than 500g. The resulting cost will be wildly high.

Fix: make sure the unit on the ingredient matches the unit you're using in the recipe. Either change the ingredient to grams (and update the pack size to match) or change the recipe quantity and unit to kilograms.

**Servings count set to 0**

If the recipe's serving count is set to 0, the cost per serving calculation will fail. The total batch cost may be correct, but the per-serving figure will show as an error or zero.

Fix: open the recipe → check the **Servings** field → enter the correct number of portions → recompute.

***

## Checking your work

After recomputing, a quick sanity check:

* Does the cost per pack for the main ingredient make sense? (e.g. a 500g bag of flour for £1.80 → roughly £0.004 per gram — a 100g recipe portion should cost around £0.40 in flour)
* Is the total recipe cost in the right ballpark compared to what you know you spend on ingredients?

If the numbers still look wrong after fixing the obvious issues, check each ingredient in the recipe one by one. A single ingredient with bad data can throw off the whole calculation.

***

## Still stuck?

If you've checked the pack size, cost, and units and the figure still doesn't make sense, get in touch. Email **<info@foodcore.io>** with:

* Your business subdomain (e.g. `mybakery.foodcore.io`)
* The name of the recipe and the ingredient that looks wrong
* What you'd expect the cost to be and what FoodCore is showing

We'll take a look and help you track down the issue.

***

## What's next

* [Update an ingredient price](https://docs.foodcore.io/ingredients/update-price.md)
* [Understand how recipe costing works](https://docs.foodcore.io/recipes/how-costing-works.md)
* [Run your monthly cost review](https://docs.foodcore.io/maintenance-and-best-practices/monthly-cost-review.md)
