Households, bakers, caterers, chefs and recipe developers who already know the prices they pay and need a transparent cost model rather than a live grocery-price feed.
RecipeWanted Resources
Ingredient, batch, portion & pricing arithmetic
Recipe Cost Calculator
Cost a recipe from prices you actually pay. Separate proportional ingredient usage from whole-pack cash outlay, preserve explicit usable-yield assumptions, add known batch costs, calculate per-yield cost and explore transparent gross-margin, markup or target-cost-percentage maths without RecipeWanted inventing grocery prices.
Your own prices16-unit registry preservedUsage ≠ cash outlayPricing maths explained
Interactive ResourceRuns without sending your entries to RecipeWanted.
Quick start
Before you start
Turn real package prices and quantities into a reproducible recipe cost while keeping ingredient consumption, purchase cash, usable-yield loss and optional business assumptions visibly separate.
For each ingredient: package quantity/unit/price and recipe quantity/unit. If a prepared-yield percentage, labour cost, energy cost or overhead allowance matters, enter a value you actually know or deliberately choose.
Row-level usage cost, purchase requirement, whole-pack cash outlay, leftover stock value, usable-yield loss cost, complete planning cost base, per-yield cost and optional pricing scenario.
Ingredient usage costWhole-pack cash outlayUnused stock valuePlanning cost baseCost per yield unitOptional pricing scenarioCSV / Print
Examples for home cooking and teaching
Choose a relevant example and check the assumptions before using it in your kitchen or lesson.
Cost a household recipe
See the value consumed by the recipe without confusing it with the full cash required to buy each package today.
Cost a prepared ingredient honestly
Apply a known usable-yield percentage only when the recipe quantity represents trimmed/prepared food and the purchase requirement genuinely needs adjusting.
Build a catering/bakery planning cost
Add known direct, labour and energy amounts, then apply an explicit overhead allowance rather than hiding those assumptions inside ingredient prices.
Use this againRecost after a price/pack/yield change or when repeating a household, bakery or catering batch.
Save the costing on this device and load it later. My Resources checks only whether the known storage key exists; it does not read costing contents.
Practical shortcut: Compatible mass, volume and count units convert inside their own families. Count↔mass and mass↔volume stop for manual review instead of guessing ingredient density or item weight.
Trust & safety at a glance
Use the result for the decision it was built to support
A complete calculation proves only the internal arithmetic for the entered data. It does not prove that prices are current, yields are representative, every operating cost is included, or the proposed selling price is viable.
General costing and pricing arithmetic7 subject references · Reference register provided below; no current review date is asserted for this route.
Calculate recipe ingredient usage from user-supplied package data and model explicit batch-cost and pricing assumptions.
Not bookkeeping, statutory accounts, tax/VAT advice, payroll, legal/financial advice, a grocery-price service, proof of profitability or proof that a selling price is appropriate for a particular business.
Core quantity/cost arithmetic is currency-neutral. VAT/tax, wages, licensing, employer costs, delivery/platform/card fees, consumer-pricing rules and accounting treatment vary by jurisdiction and business model and are not inferred.
Costing rows and optional saved drafts remain in the visitor browser. Tool 10 sends no ingredient names, prices, quantities, labour/energy amounts, yield values or pricing targets to RecipeWanted analytics. Affiliate, sponsor, partner and owned-product surfaces are downstream only and cannot alter unit factors, cost results, pricing formulas, warnings or result order.
When to stop and verify:For statutory accounts, tax/VAT, employment/labour treatment, regulated pricing or formal profitability decisions, use current competent professional/authority guidance. Resolve uncertain quantity or yield data rather than forcing an estimate.
Privacy scope: this describes the working-data behaviour of this Resources tool only. Site-level cookies, analytics, consent and other storage/access technologies remain governed by RecipeWanted’s wider privacy/CMP configuration and applicable law.
Source scope: external authorities and specialist references support specific information; linking to them does not mean they have reviewed, approved or endorsed RecipeWanted.
How this Resource reaches its result
MethodDeterministic user-entered recipe cost model
Package quantity, package price and recipe quantity are normalised only inside compatible mass, volume or count families. Usable yield is an explicit purchase-to-usable adjustment. Whole-pack purchase cash remains separate from recipe usage. Optional direct/labour/energy/overhead/pricing values are visitor-owned assumptions.
Can it be reproduced?Deterministic under this version
The same values under contract 3.0.0 produce the same row costs, package rounding, complete planning base and pricing scenario.
Evidence7 registered references · RecipeWanted review UNREVIEWED
NIST supports disciplined mass/volume measurement; USDA Food Buying Guide formalises as-purchased versus edible/usable yield concepts and cost comparison; current HMRC guidance distinguishes gross margin from mark-up; current GOV.UK VAT guidance supports keeping VAT/tax treatment outside generic arithmetic.
IndependenceNo paid or analytics influence over the result
Commercial inventory, analytics and ecosystem links cannot alter unit factors, package rounding, costs, pricing scenarios or warnings. No runtime AI or grocery-price provider supplies or adjusts costing inputs.
Uncertainty stays explicit: Prices, pack sizes and yields change. Labour, energy, tax/VAT, delivery, insurance, platform/card fees, rent and other overheads can be missing unless deliberately entered or handled elsewhere. Density/item-weight conversion is never inferred.
Evidence reference: RWRES-36B1A82DC34D3B3D — a RecipeWanted integrity/reference fingerprint for this release evidence set, not certification or third-party endorsement.
Report a factual or method concern if a source conflicts with the tool, a calculation appears wrong, or a boundary needs review.
Recipe cost calculator
Cost the recipe from prices you actually pay
Separate what the recipe consumes from what whole packages cost to buy. Add only the batch assumptions you deliberately know, then compare cost per serving or an optional pricing scenario without a live grocery-price feed.
Before you calculate
The cost of ingredients used is not the same as the cash needed to buy whole packs. Mass converts only to mass, volume only to volume and count only to count. RecipeWanted does not invent ingredient density, item weight, current prices, labour rates, energy prices, tax/VAT or a commercially “correct” selling price.
Ingredient costing rows
Match package quantity to recipe quantity safely
Enter the real package quantity, unit and price, then the recipe quantity. Use usable yield only for a known as-purchased → usable difference.
Manual used-cost override
Enter package and recipe quantities to calculate this row.
Complete-cost & pricing assumptions Optional — all default to zero/off
Tax/VAT stays outside this model.Rates and treatment depend on jurisdiction, registration and what is sold. Use current competent-authority/accounting guidance before treating any scenario as a final customer price.
Costing result
See consumption, purchase cash and planning assumptions separately
Other direct—
Labour—
Energy / utilities—
Overhead—
Pricing scenario
Scenario selling price—
Gross margin—
Markup on cost—
Cost percentage—
| Ingredient | Method | Recipe usage | Purchase required | Packs | Cash outlay | Yield loss | Unused stock / review |
|---|
Manual review required
Totals remain partial while active rows/settings are unresolved. Pricing scenarios are suppressed until the cost base is complete.
What the result cannot know
Whether your prices are still current, whether yield assumptions fit this exact ingredient/process, whether unused stock will actually be used, or whether labour, energy, rent, insurance, delivery, platform/card fees, tax/VAT and other costs are complete.
Use the numbers correctly
Six costing distinctions worth keeping visible
One recipe may consume only part of a pack while the shopping trip still requires buying the whole pack.
A known yield below 100% increases the quantity that must be purchased. Do not use yield as a vague “waste buffer”.
Leftover pack value matters only if that stock remains usable and is genuinely consumed later.
Margin uses selling price as the denominator; markup uses cost. The same percentage gives different results.
A 30% target cost percentage means the selected planning cost base is 30% of the scenario selling price.
Formal pricing/profit decisions may require costs, taxes and obligations that this general tool deliberately does not infer.
Continue the workflow
Use the right tool before or after costing
Convert a measurement firstResolve compatible recipe/package units before they enter the costing model.Open Cooking ConvertersChange the recipe yield firstScale the recipe, then cost the quantities you will actually use.Open Recipe ScalerPlan catering quantitiesBuild a transparent quantity plan before entering the final purchase amounts here.Open Party & Catering PlannerPlace the batch in the weekUse Meal Planning Tools after costing when the batch is part of a household plan.Open Meal Planning Tools
Reference & provenance
Sources behind the method
Metric Kitchen: Culinary Measurement Tips
Updated April 2026 measurement guidance supporting mass measurement where practical, correct measuring tools and explicit caution that customary measures can differ between countries.
Open sourceMetric Kitchen: Cooking Measurement Equivalencies
Current reference for approximate common mass/volume measurement equivalencies used to audit the calculator unit-family registry.
Open sourceFood Buying Guide — About the Food Buying Guide
Official reference distinguishing food as purchased from edible portion/yield, purchase units and cost-comparison use cases; RecipeWanted does not import USDA yields automatically.
Open sourceEM3082 — Gross Profit Rate
Current HMRC reference defining gross profit rate as gross profit divided by turnover/sales, supporting the gross-margin formula.
Open sourceEM3504 — Business Models: Communication
Current HMRC guidance distinguishing a percentage margin on sales from a mark-up on cost, supporting separate labels and formulas.
Open sourceEM3503 — Formulae and Terms
Current HMRC formula reference relating gross-profit rate and mark-up rate; used only as an arithmetic cross-check, not tax advice.
Open sourceCharge, reclaim and record VAT — Charging VAT
Current UK VAT guidance confirming rates/treatment can change and depend on the goods/services supplied; Tool 10 therefore does not add VAT automatically.
Open sourceRecipe cost calculator FAQs
Questions that change how the numbers should be used
Why is ingredient usage cost different from whole-pack cash outlay?
Usage cost values only the quantity consumed by the recipe. Whole-pack cash outlay assumes you are starting with no stock and must buy complete packs. The difference remains stock value only if the unused product is actually usable later.
Does RecipeWanted fetch supermarket or supplier prices?
No. Tool 10 has no live grocery-price provider. Every price is entered by you, so the result is reproducible and never pretends to know your current retailer, supplier, discount, tax treatment or package size.
Can the calculator convert cups of flour into grams automatically?
No. Volume-to-mass conversion needs ingredient-specific density and measuring-method assumptions. Use Cooking Converters or an ingredient-specific measured weight first, then cost two quantities in the same measurement family.
What does usable yield mean?
Use it only when the recipe quantity represents the usable or prepared amount but you buy more food as purchased because of trimming or preparation loss. If 400 g usable food requires 500 g purchased, the usable yield is 80%.
Should I use USDA Food Buying Guide yields automatically?
No. USDA yield tables demonstrate the as-purchased versus edible-portion concept, but Tool 10 never imports or applies a generic yield behind your back. Enter a yield only when it fits the exact ingredient/form/process you are costing.
What is the difference between gross margin and markup?
Markup expresses gross profit relative to cost. Gross margin expresses gross profit relative to selling price. A 50% markup and a 50% gross margin therefore produce different selling prices.
What does target cost percentage mean?
It asks what selling price would make the selected planning cost base equal the entered percentage of selling price. For example, a 25% cost target mathematically means price = cost ÷ 0.25. It is a scenario, not a recommendation.
Does the suggested selling price include VAT or tax?
No. Tax/VAT rules vary by location, registration status and what is sold, and rates can change. Tool 10 deliberately keeps tax treatment outside the generic pricing arithmetic.
Should labour, energy and overhead always be included?
That depends on why you are costing. Household ingredient comparison may need none of them; a business planning model may need many more costs than this tool captures. Only enter values you deliberately want in the planning base.
How should I keep a saved costing current?
The browser-local save is a convenience, not a price feed. Recheck package price, pack size, supplier, recipe yield and operating assumptions whenever they change, then recalculate before relying on an old costing.
Continue across RecipeWanted
Use the next route for the next question
Related Resources handle the next practical job. The ecosystem handoffs add another useful format when a visual, video, current update, longer article or wider recipe browse answers something different. Cooking Education remains the deeper teaching layer.
01Cooking Converters
Convert compatible recipe/package measurements before costing.
Open related Resource → 02Recipe ScalerChange the recipe yield before costing the new batch.
Open related Resource → 03Party & Catering Quantity PlannerPlan quantities for a group before costing the final batch.
Open related Resource → 04Meal Planning ToolsPlace a costed batch into a weekly household workflow.
Open related Resource → 05Measurements & ConversionsOpen the related Cooking Education route for deeper method and explanation.
06Meal Planning & PrepOpen the related Cooking Education route for deeper method and explanation.
07Batch CookingOpen the related Cooking Education route for deeper method and explanation.
08Ingredient GuidesOpen the related Cooking Education route for deeper method and explanation.
09Search RecipesApply the tool or decision inside a complete RecipeWanted dish.
Legal, privacy & fair-use notice
Free Resources, with clear limits and clear data boundaries.
RecipeWanted Resources provides general cooking information, deterministic calculations, planning aids and reference tools. It is not legal, medical, dietetic, allergy, regulatory or other professional advice, and it does not replace product labels, manufacturer instructions, competent-authority guidance or qualified professional advice where those are needed.
Each tool explains how it handles your entries. This Resources analytics dataset does not retain recipe or ingredient names, pantry lists, allergy, dietary or health information, other free text, exact quantities, visitor/session/account IDs, IP addresses, user-agent strings or referrer URLs.
This Resources statistics layer is currently enabled and records only allowlisted aggregate interaction and coarse workflow/build-shape counters. Daily aggregate buckets are retained for up to 730 days. Aggregate results are for RecipeWanted/QHE internal RecipeWanted service improvement only; they are not sold or used by this layer for advertising measurement, individual profiling or cross-site tracking.
Any reasonable fair-use or availability rules for free tools are separate from privacy law. Access is not conditional on participating in Resources analytics, and “fair use” is not treated as consent or as a legal basis for collecting personal data. On instrumented Resources pages, the usage-statistics panel provides a simple, free objection control.
Wider site/infrastructure scope: ordinary hosting, security, caching, firewall, consent-management or server-log systems may process technical request information outside the Resources aggregate dataset. Those systems remain governed by RecipeWanted’s wider privacy/CMP arrangements and published privacy information. This Resources notice does not claim that every web request is anonymous.
External authorities linked elsewhere in Resources support specific facts or methods; their inclusion does not mean they approve or endorse RecipeWanted. If a higher-consequence decision is uncertain, stop and verify it with the appropriate current source.First-party usage statistics
Help RecipeWanted learn what is actually useful
Resources records aggregate usage statistics such as qualified tool views, whether a working surface is started, route-level value actions, coarse read depth, broad workflow/build-shape buckets and which non-commercial RecipeWanted handoffs are used. Build-shape signals are deliberately coarse (for example, a small/medium/large row-count bucket or a selected calculator mode): RecipeWanted does not send the recipe name, ingredient list, pantry items, allergen/dietary choices, free text or exact quantities to this analytics dataset; it does not create a visitor/session ID; and it does not store IP addresses, user-agent strings or referrer URLs in the analytics dataset.
Purpose: help RecipeWanted/QHE decide which free tools, workflows, supporting content and first-party integrations to improve next. Aggregate statistics may be reviewed internally across QHE only for that same RecipeWanted service-improvement purpose. They are not sold and are not used by this layer for advertising measurement, cross-site tracking or individual profiling. Free access is not conditional on this measurement: opting out does not disable or reduce any Resource tool.
What is counted and retained?
Allowed counters include 5-second qualified views, 30 seconds of visible engagement, 50%/90% read depth, first working-surface use, selected non-commercial feature/export/continuity actions, hub task choices, broad allowlisted workflow/build-shape buckets and RecipeWanted internal/ecosystem handoffs. Counts are merged directly into UTC daily buckets and retained for up to 730 days under the current admin setting. The only browser preference this layer writes is the first-party objection cookie after you choose to opt out; removing the objection deletes that preference. This describes the Resources aggregate dataset only; ordinary hosting, security, caching, firewall, consent-management or server-log systems remain governed separately by RecipeWanted’s wider privacy/CMP arrangements.
Privacy informationYou can object simply and free of charge at any time. The preference applies only to this first-party Resources statistics layer.
Next step
Use the tool, then get back to cooking.
Resources should remove friction around the task rather than become another layer to manage.
