A restaurant can cost every menu item carefully and still get the numbers wrong if shared components are handled inconsistently.
One cook costs garlic sauce as “one scoop.” Another recipe enters the sauce ingredients again. A third menu item uses an old cost from last month. The sauce itself has a batch yield, trim loss and production variance that never appears in the final dish cost.
The solution is to treat sauces, dressings, doughs, marinades, spice blends, stocks and other shared components as sub-recipes.
A sub-recipe is a standardized production recipe that becomes an ingredient inside another recipe.
The operating principle is simple:
Cost the sub-recipe once, calculate its usable unit cost, then reuse that controlled cost everywhere it appears.
What belongs in a sub-recipe
Common examples include:
• sauces,
• salad dressings,
• doughs,
• batters,
• marinades,
• stocks,
• spice blends,
• cooked rice base,
• mashed potato batch,
• pickles,
• syrups,
• dessert creams,
• bakery fillings,
• pre-portioned garnish mixes.
The component should be standardized enough that the restaurant can define:
• ingredients,
• batch size,
• production method,
• finished yield,
• storage/handling procedure,
• unit of issue.
This is not about making every chopped onion a sub-recipe.
Use sub-recipes when the component is produced as a batch and reused across menu items.
Start with a standardized batch
The sub-recipe needs a stable production definition.
Example: house garlic sauce.
| Ingredient | Quantity | Cost/unit | Extended cost |
|---|---|---|---|
| Base ingredient | 4.0 kg | $2.00/kg | $8.00 |
| Oil | 2.0 L | $3.20/L | $6.40 |
| Lemon | 0.8 L | $2.50/L | $2.00 |
| Seasoning | 0.12 kg | $8.00/kg | $0.96 |
Ingredient batch cost:
$8.00 + $6.40 + $2.00 + $0.96 = $17.36
The example is illustrative.
Do not use the ingredient input quantity as the final yield unless the finished batch has been measured.
Measure the finished usable yield
After production, determine how much finished product is available for service.
Suppose the batch yields 6.4 liters of usable sauce.
Cost per liter = $17.36 ÷ 6.4 = $2.7125
Cost per 100 ml = $2.7125 ÷ 10 = $0.27125
If a menu item uses 80 ml:
0.08 L × $2.7125 = $0.217
The recipe can carry approximately $0.22 of sauce cost before other components.
Keep calculation precision internally and round management outputs appropriately.
Use the correct yield definition
Sub-recipes can have several different yields.
Examples:
• raw input yield,
• post-trim yield,
• cooked yield,
• finished batch yield,
• portioned yield.
Do not mix them.
For a sauce, the useful yield may be finished liters.
For dough, it may be finished dough weight or number of dough balls.
For a spice blend, it may be finished kilograms.
For a bakery filling, it may be kilograms or filled units.
Choose the unit that matches how the component is issued to the final recipe.
Define the unit of issue
The unit of issue is how the final recipe consumes the sub-recipe.
Examples:
• liter,
• milliliter,
• kilogram,
• gram,
• scoop with a verified gram weight,
• ladle with a verified ml volume,
• piece,
• dough ball.
Avoid uncontrolled terms such as:
• handful,
• spoon,
• cup,
• portion,
unless the operation has standardized and measured them.
If a “one ladle” serving is 60 ml today and 90 ml tomorrow, the sub-recipe cost is correct but the menu item cost is not.
Create one master record
The restaurant should have one current source for the sub-recipe.
Useful fields:
| Field | Purpose |
|---|---|
| Sub-recipe ID | Stable reference |
| Name | Standard name |
| Version | Current approved version |
| Batch size | Production quantity |
| Ingredient cost | Total batch input cost |
| Finished yield | Usable output |
| Cost per issue unit | Reusable cost |
| Review date | Cost/yield control |
| Owner | Who maintains it |
The final menu recipes should pull or reference that controlled cost.
Avoid rebuilding the same sauce inside each menu item
Suppose house sauce appears in:
• chicken sandwich,
• wrap,
• loaded fries,
• catering platter.
If each dish lists the sauce ingredients separately, four problems appear:
1. price changes must be updated in four places,
2. batch yield is easy to ignore,
3. different recipes can use different ingredient versions,
4. managers cannot see the true production cost of the shared sauce.
A sub-recipe removes that duplication.
Link supplier-price changes to the sub-recipe
If oil price changes, the restaurant should update the ingredient master.
That change should flow to the garlic-sauce batch.
The new garlic-sauce unit cost should then flow to every menu item that uses it.
The chain is:
Supplier price → ingredient unit cost → sub-recipe batch cost → sub-recipe unit cost → final menu item cost
That structure is one reason a recipe-costing spreadsheet should separate the ingredient master from recipes.
For the spreadsheet structure: Restaurant Recipe Costing Spreadsheet Template: Fields, Formulas and Update Rules
Handle nested sub-recipes carefully
Some operations have sub-recipes inside sub-recipes.
Example:
• roasted garlic paste is a sub-recipe,
• garlic sauce uses roasted garlic paste,
• chicken wrap uses garlic sauce.
The logic can work, but nested recipes increase maintenance risk.
Document the chain clearly.
A change to roasted garlic paste must update the sauce before the final menu item.
For small restaurants, avoid unnecessary nesting.
Use it only when the component is genuinely produced and managed separately.
Include production loss when it is real
A batch may lose weight or volume through:
• cooking,
• evaporation,
• straining,
• trimming,
• transfer loss,
• product left in equipment.
Do not force an arbitrary loss percentage.
Measure actual finished yield.
If a 10 kg input produces 8.7 kg usable output, the usable cost is based on 8.7 kg.
The yield difference belongs in the sub-recipe economics.
Example: tomato sauce batch
Suppose a sauce batch costs $46.80 in ingredients.
The recipe standard expects 18 liters.
Actual repeated production tests show a typical finished yield of 16.8 liters.
Using the expected yield:
$46.80 ÷ 18 = $2.60/L
Using the tested finished yield:
$46.80 ÷ 16.8 = $2.79/L
That 19-cent difference per liter becomes meaningful when many dishes use the sauce.
The restaurant should investigate why actual yield differs before automatically changing the standard.
For yield testing: Restaurant Recipe Yield Test: How to Calculate Edible Yield and True Ingredient Cost
Separate cost control from food-safety control
The costing sheet can show ingredients, yield and batch cost.
It does not replace the restaurant’s approved procedures for:
• cooking,
• cooling,
• holding,
• labeling,
• storage,
• allergen control,
• shelf life.
Any production standard must follow applicable food-safety requirements and the restaurant’s approved procedures.
Do not extend shelf life because a costing model says a larger batch is cheaper.
Choose batch size from demand and process
A bigger batch can reduce setup time.
It can also increase:
• storage pressure,
• waste,
• quality decline,
• holding time,
• production risk.
Choose batch size using:
• demand,
• equipment capacity,
• labor,
• safe storage capacity,
• quality,
• service use rate.
For larger-batch planning: Batch Recipe Production: How to Scale, Stage and Control Large-Batch Prep
Cost portions from the sub-recipe unit
Suppose finished dressing costs $3.60 per liter.
Standard portion:
45 ml = 0.045 L
Cost per portion:
$3.60 × 0.045 = $0.162
If the operation uses a 45 ml ladle, verify that the tool actually delivers that amount under normal service conditions.
Theoretical portion cost should match operational portioning.
Use a version number
Sub-recipes change.
Ingredients are replaced. Salt is reduced. Batch size changes. Supplier specifications move. Production equipment changes.
Use simple version control.
Example:
House Ranch v3 — effective October 2026
Record:
• change date,
• what changed,
• approved by,
• expected yield,
• new cost per issue unit.
Do not overwrite the previous recipe without any trace when the change is material.
Re-cost the final dishes after a sub-recipe change
When a sub-recipe changes, identify all menu items that use it.
Example:
House sauce is used in six dishes.
A supplier change increases sauce cost from $2.70/L to $3.15/L.
The restaurant should calculate the effect on:
• each portion,
• each dish,
• menu contribution.
A small batch-cost change may be immaterial in one item and significant in another with a larger sauce portion.
Build a dependency list
For each sub-recipe, maintain a list of final menu items that use it.
Example:
| Sub-recipe | Used in |
|---|---|
| Garlic sauce | Chicken wrap, fries, platter |
| Pizza sauce | Margherita, pepperoni, catering pizza |
| Brioche dough | Burger bun, breakfast bun |
| House dressing | Caesar, side salad, catering salad |
This makes cost-change impact easier to find.
Reconcile theoretical and actual use
A sub-recipe can also support variance control.
Example:
The kitchen produces 20 liters of sauce.
Sales records imply that menu items should have used 15 liters.
Ending usable sauce is 2 liters.
Unexplained difference:
20 − 15 − 2 = 3 liters
That does not prove waste or theft.
Possible causes include:
• over-portioning,
• unrecorded waste,
• incorrect sales recipe,
• staff meal usage,
• transfer,
• measurement error.
The sub-recipe structure makes the question visible.
Control scoop and ladle standards
A high-volume sauce can create significant cost drift through serving tools.
Verify:
• correct tool,
• actual volume/weight,
• fill method,
• service station setup.
If a menu item is designed for 60 ml but the normal ladle delivers 75 ml, the final recipe cost is understated.
Use sub-recipes in catering and bakery too
The same method applies outside à la carte restaurants.
Catering
• bulk sauces,
• marinades,
• rice bases,
• salad dressing,
• garnish mixes.
Bakery
• dough,
• fillings,
• creams,
• glazes,
• syrups,
• crumble mixes.
Cafés
• flavored syrups,
• cold-foam base,
• drink concentrates,
• sandwich spreads.
This is why the Professional Recipes category belongs inside an operator site: the emphasis is repeatable production, yield and cost.
Give production staff a sub-recipe sheet, not only a costing sheet
The costing record tells management what the component costs.
The production sheet should tell the kitchen how to reproduce it.
Useful fields include:
• sub-recipe name and version,
• target batch size,
• ingredients and production quantities,
• expected finished yield,
• issue unit,
• production date/time field,
• actual yield field,
• variance note,
• approved storage/handling reference.
Do not crowd the production sheet with supplier prices if cooks do not need them to execute the recipe.
Management can maintain the financial layer while production uses a clean operating standard.
Know when not to create a sub-recipe
A sub-recipe adds another control point.
Do not create one simply because an ingredient is prepared before service.
It may be unnecessary when:
• the component is used in only one final recipe,
• there is no meaningful batch process,
• finished yield is essentially identical to the input,
• creating a separate record makes the system harder to maintain than the cost benefit justifies.
Use sub-recipes where they reduce duplication and improve control.
A good recipe system should become easier to maintain as it grows, not more complicated with every prep step.
Sub-recipe costing checklist
Before approving a sub-recipe, confirm:
- Ingredients use current controlled costs.
- Units are converted correctly.
- Finished yield is measured.
- Issue unit is defined.
- Portion standard is verified.
- Version is current.
- Final menu items are linked.
- Food-safety procedures are separate and current.
Common sub-recipe mistakes
Using ingredient input weight as finished yield
Cooking and processing loss disappear.
Writing “one scoop” without measuring it
Portion cost becomes unstable.
Recreating the sauce in every dish
Price updates become inconsistent.
Updating the sub-recipe but not final menu items
The menu cost remains stale.
Making every prep item a sub-recipe
The system becomes too complex.
Changing batch size without retesting yield
The old unit cost may no longer be reliable.
A practical monthly review
- Update major ingredient prices.
- Re-cost high-use sub-recipes.
- Check whether batch yield changed.
- Verify portion tools on high-cost components.
- Identify final dishes with material cost movement.
- Record any version change.
- Recheck repeated production variance.
The cadence can be more frequent for volatile ingredients.
Frequently asked questions
Is a sub-recipe the same as a batch recipe?
A sub-recipe is a batch-produced component used inside another recipe. Many sub-recipes are batch recipes, but a batch recipe can also be a final product.
Should labor be included?
Only if the restaurant has a clearly defined direct-production-cost model. Keep ingredient cost separate if that is the costing purpose.
Should packaging be included?
Include packaging if the sub-recipe itself is packaged as a sellable unit. Otherwise packaging usually belongs to the final product.
How often should sub-recipes be re-costed?
When material ingredient prices, yields, specifications or portions change, and on a regular review cadence appropriate to the operation.
Can the same sub-recipe serve multiple locations?
Yes if the recipe, supplier specification and yield are genuinely consistent. Otherwise use location-specific cost inputs.
Next action
Choose the shared component used in the most menu items. Measure one finished batch, calculate cost per liter, kilogram or piece, and replace every copied version of that component with one controlled sub-recipe cost.