Chef checking a recipe on a laptop while cooking in a professional kitchen
Back to blog
Restaurant Stock Control

Ingredient Stock for Restaurants: How BOM Logic Reduces Guesswork

A restaurant can balance the till and still lose margin through oversized portions, unrecorded waste or a recipe that no longer matches the kitchen. BOM logic turns each menu item into expected ingredient use, then compares that expectation with actual stock.

Published: 5 August 2026 Read: 11 min read Author: Maduuka Operations Team Reviewed: 5 August 2026

A full dining room can hide a stock problem. The till may balance, every table may be closed, and yet cooking oil, meat or vegetables disappear faster than the menu says they should.

A bill of materials, or BOM, gives the restaurant a baseline. It links each menu item to a tested recipe, portion and yield. Meals produced create expected ingredient use; stock counts and recorded exceptions show what actually happened. The difference is where useful questions begin.

A BOM turns a dish into expected ingredient use

In restaurant language, a BOM is the structured recipe behind a menu item. It names the ingredients, quantity, unit, expected yield and portion. The Institute of Child Nutrition describes a standardised recipe as one tested and adapted for a particular foodservice operation so that it produces a consistent product and yield.

That operational detail matters more than the label. If one plate of chicken stew should use a defined amount of chicken, tomatoes, onions, oil and seasoning, the system can multiply those quantities by the number of portions produced. A recipe version and effective date keep a menu change from silently rewriting yesterday’s expectation.

Kitchen team preparing measured ingredients for restaurant dishes

Units and yields must agree before deductions can be trusted

The purchase unit is rarely the same as the kitchen unit. Rice may arrive by sack and enter a recipe by kilogram. Oil may arrive by jerrycan and be used by litre. Meat may be bought with bone and served after trimming and cooking. Every conversion needs one controlled path; parallel shortcuts create unexplained stock.

The USDA Food Buying Guide distinguishes food as purchased from the edible portion and shows how preparation form affects yield. It also warns that product quality, storage, equipment, cooking method and serving utensils can change the result. A restaurant should therefore test its own practical yield when local produce, supplier pack sizes or kitchen methods differ from a reference guide.

Chef seasoning a portion beside prepared ingredients in a restaurant kitchen

Choose the stock-moving event carefully

Ingredient stock should not move merely because a waiter taps a dish. An order may be edited, rejected by the kitchen or cancelled before cooking starts. In Maduuka’s restaurant workflow, kitchen production is the event that expands a menu item into its BOM requirements and issues the ingredient stock.

This keeps demand, production and billing distinct. A cancellation or correction must follow a controlled reversal path instead of leaving a hidden deduction. The owner can then see whether the difference came from the order, the kitchen, the stock record or the count.

Chef comparing fresh ingredients with a recipe on a laptop

Record what the recipe cannot predict

No recipe predicts every kitchen event. Staff meals, complimentary dishes, substitutions, spills, burnt batches, trimming loss, tasting portions and returned food need their own records. Hiding them inside a recipe change destroys the baseline the restaurant needs for comparison.

FAO guidance identifies over-buying, poor stock rotation, over-portioning and preparing too much among the causes of food waste in restaurants and catering. The US Environmental Protection Agency makes the control point equally practical: measure the amount, type and reason for discarded food before trying to reduce it.

Chef holding a tablet beside prepared vegetables in a professional kitchen

Compare expected use with a physical count

Expected use comes from the portions produced multiplied by the approved recipe quantities. Actual use comes from the stock movement evidence: opening quantity, receipts and transfers in, less closing physical stock and supported transfers out. Compare like units and the same period before calculating a difference.

For an illustrative example, 30 portions at 0.25 kg of chicken create expected use of 7.5 kg. If the controlled stock movement and count show 8.4 kg used, the 0.9 kg difference is a variance to investigate. It is not proof of theft, waste or a bad recipe by itself.

Read variance as a question, not an accusation

A variance may come from larger portions, a weak yield assumption, unrecorded waste, a substitute ingredient, an incorrect unit conversion, a receiving error or a poor count. Start with the largest value or most frequently used ingredients, then inspect the supporting events while staff can still remember the shift.

Do not fix every difference by editing the recipe. Change a standard only when repeated evidence shows that the approved method, portion or yield has genuinely changed. Otherwise the restaurant loses both the original expectation and the reason for the exception.

Recipe cost supports decisions, but it is not the whole margin

The Culinary Institute of America calculates ingredient cost per portion by dividing total recipe cost by the number of portions. That gives managers a useful menu baseline and a way to review changes in supplier prices, portion size or yield.

Ingredient cost is not the restaurant’s entire cost. Labour, rent, energy, payment charges and other operating expenses still matter. BOM logic improves the food-cost conversation because it makes the ingredient assumption visible; it does not turn one percentage into a complete profit answer.

Process: A workable ingredient-control routine

1

Standardise the important dishes

Start with high-volume or high-value menu items. Test the recipe, portion, finished yield and serving utensil in the actual kitchen.

2

Control units and conversions

Map supplier packs to stock units and recipe units once. Record edible-yield assumptions instead of relying on memory.

3

Set the production trigger

Deduct ingredients when kitchen production becomes real, with controlled reversal for a cancelled or corrected production event.

4

Capture exceptions

Record waste, staff meals, complimentary portions, substitutions, spills and failed batches with a reason and responsible shift.

5

Count the stock

Count key ingredients on a regular cycle using the same units, locations and cut-off as the production report.

6

Review the variance

Investigate the largest differences first, assign an owner and change recipe standards only when repeated evidence supports the change.

Controls: Before trusting an ingredient report

  • Each menu item points to one approved recipe version and effective date.
  • Ingredient, stock and purchase units have documented conversions.
  • The recipe states expected finished yield, portion and serving utensil.
  • Production, cancellation and reversal events are separately traceable.
  • Waste, staff meals, complimentary dishes and substitutions use reason codes.
  • Physical counts use the same cut-off, location and unit as the report.
  • Variances remain visible until reviewed; they are not silently forced to zero.
  • Recipe costs are refreshed when supplier prices, portions or proven yields change.

Common questions

The kitchen recipe explains how to prepare the dish. The BOM is the structured version the stock system can calculate: ingredient, quantity, unit, yield, portion and version. In a small restaurant, one well-designed recipe record can serve both jobs.
No. They show expected use from recorded production. A physical count is still needed to reveal waste, counting errors, unrecorded events and recipe assumptions that no longer match the kitchen.
Record the approved substitute and quantity against the production event. Do not silently consume the original ingredient or permanently change the standard recipe because of one shortage.
Create a batch recipe for the sauce or prep item, record its finished yield, then let menu items consume that prepared component by a controlled unit. Count or record discarded batch remnants separately.
Review high-value and fast-moving ingredients frequently enough that the shift can still explain exceptions. Use a wider periodic count for the rest of the kitchen; the right cadence depends on volume, perishability and control risk.

Sources and institutions worth crediting

Connect meals produced to the ingredients they should use

Maduuka links restaurant production, recipe deductions, stock movement and inventory review so managers can investigate differences with evidence.