Have you noticed ingredients running out faster than expected, even though menu sales seem normal? The problem may lie in how ingredients are measured and used during production.
This is where a Bill of Materials (BOM) and multi-level recipes help restaurants track the relationship between raw ingredients, prepared components, and finished dishes.
For example, a restaurant sells a chicken rice bowl with its signature sauce. The dish contains rice, chicken, sauce, and garnishes, but the sauce is prepared separately in a central kitchen using several ingredients.
If ingredients are tracked only at the finished-dish level, the restaurant may struggle to determine how many tomatoes, onions, how much oil, and how many seasonings went into the sauce.
As a result, physical stock may differ from system records. These discrepancies become harder to investigate when a restaurant has many menu items, prepared components, or multiple outlets supplied by a central kitchen.
To address this issue, restaurants need a detailed recipe structure. One way to do this is through a Bill of Materials (BOM), which helps link each product component to the ingredients used in its production.
What Is a BOM or Multi-Level Recipe in a Restaurant?
A Bill of Materials (BOM) lists the ingredients, components, and quantities needed to produce an item. In restaurants, it can describe the ingredients required for a finished menu item or a prepared component.
A multi-level recipe connects a finished dish with prepared components that have their own recipes, such as sauces, broths, or pre-cooked ingredients.
For example, a restaurant might sell a chicken rice bowl with sauce. The dish consists of cooked rice, cooked chicken, sauce, and garnishes. The cooked rice is made from rice and water.
The chicken component uses raw chicken, a base sauce, and extra seasonings. The base sauce has its own ingredients. The structure can be illustrated as follows:
Chicken Rice Bowl with Sauce
- Cooked rice: rice and water.
- Chicken with sauce: raw chicken and base sauce.
- Base sauce: tomatoes, onions, oil, and seasonings.
- Garnish: spring onions or other complementary ingredients.
With this structure, restaurants not only know the ingredients used for one serving of rice bowl, but also understand the ingredient requirements for each production process.
BOMs and multi-level recipes show how raw ingredients, prepared components, and finished dishes are connected. This is especially helpful when restaurants produce in large batches or operate a central kitchen serving multiple outlets.
Read also: How to Automatically Deduct Ingredient Stock Based on Menu Sales
How Do Multi-Level Recipes Affect Ingredient Stock?

Source: iStockphoto
Every menu item sold should have a relationship to the use of raw materials. However, this relationship can become more complex when restaurants use semi-finished products.
For example, a restaurant might make a single batch of base sauce. This sauce is then used in several dishes, such as chicken rice bowls, pasta dishes, and grilled dishes.
If a restaurant records sauce as one inventory item without its recipe, the ingredients used to produce it are difficult to trace. A multi-level recipe records the composition of each component.
Key data includes ingredient names, quantities, units, yield, and portion sizes where relevant. Quantity specifies how much of each ingredient a recipe requires.
Units specify grams, kilograms, milliliters, or liters, while yield measures usable output after processing. For example, a central kitchen uses 10 kilograms of tomatoes, 1 kilogram of onions, 500 grams of oil, and 200 grams of seasonings to make a base sauce.
The ingredients weigh 11.7 kilograms before cooking, but the finished sauce weighs only 9 kilograms. The difference should be recorded because evaporation, straining, and residue on equipment can reduce the final yield.
If one serving of rice bowl uses 150 grams of chicken and 30 grams of sauce, the restaurant can calculate the ingredient requirements based on the chicken recipe and the composition of the sauce.
With a structured BOM and multi-level recipes, restaurants can trace stock usage from menu sales back to raw ingredients. This supports purchasing estimates, ingredient-use reviews, and investigation of stock discrepancies.
Why Can Stock Counts Differ Even When Recipes Are Recorded?
Recording recipes does not automatically guarantee accurate stock records. Actual ingredient usage may still differ from the system's calculations.
One example is an outdated recipe. For example, a restaurant might change the sauce ingredients to improve the flavor or adjust ingredient prices. However, these changes haven't been applied to the recipe the system uses.
The system may continue calculating usage from the old recipe. If the updated recipe requires more chicken or sauce, actual stock can run out sooner than expected.
Another issue is the use of different units. Ingredients might be purchased in kilograms, but recipes use grams. If unit conversions aren't consistent, ingredient requirement calculations can be inaccurate.
For example, the system records the need for chicken as 0.15 kilograms per serving, while the kitchen staff uses 150 grams. Mathematically, the quantities are the same. However, conversion errors can occur if these units are treated differently in the system.
Modifiers and add-ons also need to be considered. Customers might add extra cheese, extra chicken, or extra sauce. If these additions aren't mapped to the recipe, actual stock usage will be higher than the system's calculations.
Additionally, changes in yield can affect production results. Chicken that shrinks after cooking may yield lower weight than raw chicken.
Using raw ingredient weight to calculate finished portions without considering yield can distort stock estimates. BOMs and multi-level recipes therefore need to be maintained as operational data.
Read also: How to Count and Correct Restaurant Ingredient Stocktaking Discrepancies
How to Keep Ingredient Usage Consistent with Recipes

Source: iStockphoto
To keep ingredient usage consistent, restaurants need a standard operating procedure (SOP) for recipe changes. Every change should be documented and approved before it is applied.
First, determine who has the authority to change the recipe. For example, the chef or product development team might propose changes, and then the operations manager or a designated party would approve them.
Second, record any changes made. This information includes added or removed ingredients, updated quantities, units, yields, and portion sizes. If changes occur to a semi-finished product, the restaurant should review other menu items that use that product.
Third, determine the effective date for the new recipe. This is important to ensure that transactions and production before the change date continue to use the correct recipe.
Fourth, determine which outlets are affected. The new recipe may apply to all branches, but it may also only be applied to certain outlets during a trial period.
Fifth, conduct a check after the changes are implemented. Compare the ingredient usage based on recipe calculations with the physical inventory to see if there are any discrepancies that need to be investigated.
For example, the central kitchen might change the basic sauce recipe from using 10 kilograms of tomatoes to 12 kilograms. This change will affect tomato requirements, sauce production yield, cost per batch, and the amount of sauce used in each dish.
If the sauce is used by five outlets, all outlets using the new recipe must have the same reference. However, the change must also take into account the stock of the old version so that its use can still be traced.
Structured BOM and multi-level recipe management reduces the risk of inconsistent recipes across outlets. Every change should have a record, an owner, and an effective period.
FAQs About BOMs and Multi-Level Recipes in Restaurants
1. Do All Restaurant Menu Items Need Multi-Level Recipes?
No. Simple dishes that use ingredients directly may need only a single-level recipe. Multi-level recipes are more useful when a dish contains prepared components with their own recipes.
2. What is the difference between BOM and a regular recipe?
A standard recipe describes the ingredients and quantities used to prepare a dish. A BOM can represent the relationships among raw materials, prepared components, and finished products in more detail.
3. Can recipe changes affect stock reports?
Yes. Changes in quantity, units, yield, or ingredient composition will affect stock usage calculations. Therefore, recipe changes need to be updated in the system and implemented by their effective date.
4. How Can Restaurants Check Whether Actual Ingredient Use Matches the Recipe?
Compare expected ingredient usage from sales and production with physical inventory. Review waste, portion errors, recipe changes, and unrecorded add-ons.
Conclusion
Controlling restaurant inventory requires more than simply recording incoming and outgoing ingredients. Merchants need to understand how each ingredient is used in the production process, including when raw ingredients are processed into semi-finished products before being used in the final menu.
A BOM helps restaurants structure their ingredients, while a tiered recipe provides an overview of the relationships between each production component.
Consistent ingredient, quantity, unit, yield, and portion data makes usage estimates more reliable. Managing BOMs and multi-level recipes also helps restaurants maintain recipe consistency, reduce stock discrepancies, and assess ingredient and production cost changes.
For more connected recipe, inventory, and production management, consider ESB Core. This F&B ERP system supports multi-level BOMs and inventory workflows so teams can trace ingredient usage more effectively. Contact the ESB team to discuss a solution for your restaurant.
