Key takeaways
- A food or beverage recipe is functionally a bill of materials: ingredients and quantities needed to produce one batch of a finished product.
- Recipes need yield percentage and unit-of-measure conversion that a generic discrete-manufacturing BOM usually does not handle — a recipe in cups and ounces has to convert to purchasing units in pounds or liters.
- Batch size scaling has to hold ingredient ratios constant while recalculating total quantities and cost, which a flat BOM built for one fixed quantity does not do automatically.
A recipe is a bill of materials, with different math
Functionally, a recipe and a bill of materials solve the same problem: listing what goes into a finished product, and how much of each. Where food and beverage production differs from discrete manufacturing is the math layered on top — recipes are usually expressed per batch rather than per unit, ingredients are measured in volume or weight units that need converting to purchasing units, and yield loss (evaporation, trim waste, spillage) means the batch does not produce exactly the raw quantity of ingredients that went in.
What recipe management needs beyond a generic BOM
A recipe management system built on the same BOM foundation as discrete manufacturing needs a few food-specific capabilities layered on top.
- Unit-of-measure conversion between recipe units (cups, ounces, grams) and purchasing/stocking units (pounds, liters, cases)
- Yield percentage per recipe, so the expected finished quantity accounts for trim, evaporation, or spillage rather than assuming 100% conversion
- Batch scaling that recalculates total ingredient quantities and cost while holding ratios constant, for producing a larger or smaller batch than the recipe's base size
- Ingredient cost rollup to a per-unit cost of the finished product, accounting for yield loss
- Lot and expiry tracking on ingredients, since perishability affects both food safety and which lot actually got used in a given batch
Multi-level recipes: sauces, bases, and sub-recipes
Many food products are built from sub-recipes — a sauce or base prepared separately and then used as an "ingredient" in a finished product's recipe. This is the same multi-level BOM structure used in discrete manufacturing: the sub-recipe gets its own recipe and cost, which then rolls up into any finished product that uses it, so a price change in a base ingredient updates every product built from that sub-recipe automatically.
Trusted by small businesses
What our customers say
“Super Kind! Quick replies from their support and very easy fixes, changed the dashboard a bit and customized it. Also gave me 450 items extra on the free plan just for me. Highly recommend and again great service!”
“Best customer service! Stockflow's customer support is fast and extremely helpful. They assisted me with customization of the software to improve my experience as a user.”