Recipe identity
Name the exact recipe version.
Identify the preparation before its ingredients so costs remain comparable.
- Recipe name, code, category, and location.
- Version, effective date, and preparer.
- Status such as test, active, or archived.
Describe how your kitchen buys and portions ingredients. Makeform creates a recipe ingredients cost report form for yields, units, pack prices, waste, and per-portion costs.
Send recipe cost records to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the Makeform builder.
Audience
Chefs costing plated menu items
Format
Ingredient table with yield and portion summary
Prompt size
352 chars
Example form structure
Ingredient table with yield and portion summary
Recipe name, category, and version
Batch yield and serving size
Ingredient, pack, price, and recipe quantity
Waste or yield adjustment
Total and per-portion cost
Suggested routing tags
Needs review
Costed recipes
Price update
Record purchase pack size and recipe-use quantity separately; the conversion between them is what makes unit cost usable.
Step 1
Define
recipe, yield, portion, and version
Step 2
Price
pack costs, units, conversions, and waste
Step 3
Calculate
ingredient, batch, and portion costs
Step 4
Review
approve, reformulate, or reprice
Why structured recipe costing
Recipe cost depends on pack size, conversion, trim loss, yield, and portions. A form gathers these inputs consistently.
Capture purchase unit, recipe unit, quantity, supplier, and price in structured rows.
Separate ingredient, batch, and portion costs to reveal where price changes matter.
Tie costs to a recipe code, yield, effective date, and reviewer.
Built for food operations
Choose a prompt, then edit units, categories, and review choices.
Compare batch and portion cost with the menu price.
Use weights, sellable yields, waste, and packaging.
Connect base yields, guest counts, purchasing, and cost per guest.
Compare supplier changes by recipe code and effective date.
Costing workflow
Generate the structure, tailor its units, collect prices, and route the report.
Name the recipe type, units, cost outputs, and reviewer.
Add suppliers, pack units, recipe units, waste rules, and version fields.
Enter vendor prices and recipe quantities beside calculated results.
Send it for acceptance, reformulation, or repricing.
Form vs notes vs spreadsheet
A spreadsheet can hold formulas; a form standardizes the quantities and prices feeding them.
Field guide
These six sections preserve the assumptions behind the number, not only the final food cost.
Recipe identity
Identify the preparation before its ingredients so costs remain comparable.
Yield and portions
Record the denominator behind batch and serving costs.
Ingredient usage
Give every ingredient its own repeatable row.
Purchasing basis
Keep the buying basis beside recipe usage.
Conversion and yield
Capture conversions and yield so ingredient cost can be checked.
Totals and decision
Summarize costs, then record the review decision.
Related tools
Collect recipes, order stock, adjust inventory, review suppliers, and record expenses.
Collect standardized recipe methods, yields, and ingredient lists before costing begins.
Open toolTurn replenishment decisions into organized purchase requests for approved ingredients.
Open toolRecord corrections, waste, spoilage, and other changes affecting ingredient stock.
Open toolCapture operating expenses that sit outside individual ingredient rows.
Open toolReview vendor quality, delivery, service, and consistency alongside price decisions.
Open toolCollect customer orders using a separate workflow from internal recipe costing.
Open toolFAQ
Answers for kitchen managers and chefs.
It records the ingredients, quantities, purchase packs, prices, conversions, yields, and portions behind a recipe's cost. Managers can review both the inputs and results.
Start with recipe identity, version, batch yield, and serving size. For every ingredient, capture recipe quantity and unit, purchase pack size and price, conversion factor, usable yield or waste, and extended cost. Finish with total batch cost, portions, cost per portion, price date, and reviewer.
Store both units and ask for the conversion between them. For example, a product purchased by the five-kilogram case may be used by the gram. Keeping the pack quantity, pack price, grams per pack, and grams used visible makes the ingredient cost easier to check.
Include a usable-yield percentage or waste adjustment when trimming, draining, cooking, spoilage, or production loss changes the quantity available. Label the basis clearly so teams do not apply a loss twice. Use a simple zero-waste default for ingredients where the full pack is usable.
You can request calculation fields for ingredient extensions, batch totals, and cost per portion. Define the formula inputs precisely and test the result with known recipes before relying on it operationally. You can also send submissions to a spreadsheet for additional costing analysis.
Choose a review trigger that fits purchasing volatility, such as a regular calendar check, a new supplier price list, a pack-size change, or a variance beyond your internal threshold. Recording the price date and effective recipe version makes older reports interpretable.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses with your form. The paid tier removes the Makeform badge.
Yes. Keep the shared costing core, then add conditional questions for plated portions, bakery units, catering guest counts, packaging, or location-specific suppliers. Separate versions help when teams use different units.
Make every recipe cost explainable.