GlossaryLineNow brief

Bill of Materials (BOM): Single-Level, Multi-Level, and Why Recipes Are BOMs

A bill of materials is the complete list of raw materials, components, and sub-assemblies required to produce one unit of a finished product. BOM explosion, yield adjustment, dynamic costing, and why BOMs matter for procurement.

A bill of materials (BOM) is the complete list of raw materials, components, and sub-assemblies required to produce one unit of a finished product — including quantities, units of measure, and yield adjustments — serving as the bridge between sales forecasts and procurement requirements.

Quick answers

What is a bill of materials? A BOM is a structured recipe for a finished product. It lists every input — ingredient, component, packaging — along with the exact quantity needed per unit of output. When you sell 100 units, the system "explodes" the BOM to calculate how much of each input to procure. Without a BOM, component ordering is disconnected from finished goods demand.

What's the difference between a single-level and multi-level BOM? A single-level BOM is a flat list: Product A requires 3 of Part X, 2 of Part Y, 1 of Part Z. A multi-level BOM includes sub-assemblies: Product A requires 1 of Sub-Assembly B, which itself requires 2 of Part X and 1 of Part Y. Multi-level BOMs are common in manufacturing. In food service, most recipes are single-level — ingredients combine directly into the finished dish.

Are recipes BOMs? Yes. A restaurant recipe is a BOM. A cocktail recipe calling for 2 oz bourbon, 1 oz sweet vermouth, and 2 dashes bitters is a three-component BOM with specific quantities. Menu engineering is BOM management. When the price of bourbon rises, the BOM tells you exactly how your dish cost changes.

What about retail bundles? A gift set containing three products is a BOM. A kit assembled from individual components is a BOM. Any time a single sellable unit is composed of multiple procured items, a BOM defines the relationship.

The formula

BOM explosion (component demand):

component demand = Σ (finished good demand × quantity per unit / yield rate)

where:

  • finished good demand — units of the finished product to be produced (from forecast or orders)
  • quantity per unit — amount of this component required per one finished good, per the BOM
  • yield rate — the fraction of the raw input that becomes usable output (e.g., 0.85 for 85% yield)

BOM costing:

unit cost = Σ (component quantity per unit / yield rate × component unit cost) + labor cost

BOM yield adjustment

ComponentBOM quantityYieldProcurement quantity
Beef tenderloin200g per plate70% (trim loss)200 / 0.70 = 286g
Carrots150g per plate90% (peel loss)150 / 0.90 = 167g
Sauce base50ml per plate95% (cooking loss)50 / 0.95 = 53ml
Packaging1 box per plate100%1 box

Without yield adjustment, you procure 200g of tenderloin per plate, get 140g of usable meat, and run short on 30% of plates. The BOM must reflect procurement quantity, not recipe quantity.

Worked example

A bakery sells a signature cake. The BOM per cake:

ComponentRecipe qtyYieldProcure qtyUnit costExtended cost
Flour500g98%510g$0.0018/g$0.92
Butter250g100%250g$0.0088/g$2.20
Eggs6 units95% (breakage)6.3 → 7 units$0.35/unit$2.45
Sugar300g99%303g$0.0012/g$0.36
Vanilla extract15ml100%15ml$0.22/ml$3.30
Packaging1 box100%1 box$1.80$1.80
Subtotal (materials)$11.03
Labor (20 min @ $18/hr)$6.00
Total BOM cost$17.03

The bakery forecasts 80 cakes for next week. BOM explosion: 80 × 510g = 40.8kg flour, 80 × 250g = 20kg butter, 80 × 7 = 560 eggs, and so on. This is the procurement requirement — derived from the sales forecast through the BOM, not from guessing how many eggs to order.

If butter price increases from $0.0088/g to $0.0110/g, the BOM recalculates: butter cost per cake rises from $2.20 to $2.75, total BOM cost rises to $17.58, and the operator can decide whether to raise the cake price, reformulate, or absorb the margin hit — with exact numbers.

Why most operators get BOMs wrong

  1. No BOMs at all. Most SMBs order components by gut feel. The operator "knows" roughly how many eggs they need. This works until the menu expands to 40 items, each sharing ingredients across recipes. Without BOMs, you cannot aggregate component demand across products.
  2. Ignoring yield. A recipe says 200g of salmon. The operator orders 200g per serving. Actual yield after trimming is 75%. The kitchen runs short every service, and the procurement system cannot explain why consumption exceeds forecasted demand.
  3. Static BOM costing. The BOM was costed when the recipe was created. Ingredient prices have changed three times since. Without dynamic BOM costing linked to current supplier prices, menu pricing and margin calculations are based on stale data.
  4. No BOM explosion for forecasting. Operators forecast finished goods demand but order components independently. The BOM explosion — translating finished goods forecast into component procurement requirements — is the step that connects demand planning to purchasing. Without it, the forecast is disconnected from the PO.

How LineNow handles BOMs

  1. Stores BOMs per finished good with component quantities, units of measure, and yield percentages, supporting both single-level (recipes) and kit/bundle structures.
  2. Explodes BOMs against demand — when consumption rate data or manual forecasts indicate finished good demand, LineNow aggregates component requirements across all BOMs that share each ingredient.
  3. Recalculates BOM cost dynamically as supplier prices update, so the landed cost of each finished good reflects current procurement reality rather than historical estimates.
  4. Incorporates yield into procurement quantities — if the BOM specifies 85% yield, LineNow calculates the gross procurement quantity automatically, preventing the systematic under-ordering that yield-unaware systems produce.
  5. Connects BOM demand to EOQ — component order quantities are optimized not just for the component's own demand but for the aggregated demand across all finished goods that use it.

Related

Share on XShare on LinkedIn

Turn the article into an operating system.

See how LineNow connects POS demand, purchase orders, supplier replies, receiving, and accounting handoff.

Book a Demo