Food production
Recipe BOMs and food-cost control: a practical operating model
Learn how recipes, yields, units of measure, stock and purchasing work together to produce reliable catering costs.
Food cost becomes unreliable when recipes are treated as static text. An operational recipe must connect yield, approved units, purchasable items, stock conversions and the production quantity required by a real event.
Model yield before price
Start with the output a recipe reliably produces. Portions, batch size and expected loss determine how many batches the operation needs and how ingredients scale.
Without a stable yield, even accurate ingredient prices produce a misleading event estimate.
Treat units as controlled conversions
Purchasing, stock and kitchen teams may use different units. Each alternate unit must have an explicit conversion to the stock unit, and the stock unit itself should never be duplicated as an alternate.
Conversions should be applied server-side when quantities and costs affect ERP records.
- Define one stock unit per item.
- Validate conversion factors as positive numbers.
- Recalculate stock quantity and valuation after conversion.
Connect shortages to purchasing
A recipe plan becomes actionable only after comparing requirements with available stock. The result should distinguish covered quantities, shortages and proposed purchases by warehouse and required date.
Keep AI assistance reviewable
AI can draft a complete recipe plan, but catalog matching, units, cost and stock availability must remain authoritative. High-impact writes should happen only after a person reviews the server-validated result.