A food BOM needs to describe what the operation will actually make
For Plant heads, production planners and manufacturing managers · Compare approaches
TL;DR — what you’ll learn
- Define the output quantity and units before listing ingredient and packaging requirements.
- Connect the approved recipe with the packaging and operating version used for the run.
- Distinguish proportional consumption from fixed or step-based requirements where the process needs them.
- Keep planned requirements separate from actual issues, returns and output.
The recipe spreadsheet is correct for a kitchen trial. Purchasing needs cases, production works in kilograms and packing needs bottles, caps, labels and cartons. Copying the ingredient list into an ERP does not yet create a complete manufacturing requirement. The missing relationships appear when the first commercial order is released.
What should a food manufacturing bill of materials include, and how does it relate to the recipe?
A food BOM or formula should describe the approved material requirements for a stated output basis, with the relevant versions and process relationships. The terminology varies by ERP. The practical test is whether planning can calculate the required inputs and production can reconcile what was actually used.
- 01Define inputs and outputsUnits, yield and process scope
- 02Create the controlled versionOwner and applicability
- 03Review the production basisScale, substitutions and lossesIs the recipe version approved?YesRelease for useNoResolve the formulation or data issue before activation.
- 04Release for useLink runs to the version
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
State the output basis clearly
Define the product, output quantity, unit and expected process basis. A recipe expressed per 100 kilograms of mix is different from a packaging requirement per 1,000 saleable packs. If the system connects those stages, the conversion and expected output relationship need an approved basis.
ERPNext's BOM documentation describes materials, quantities and operations associated with manufacturing. Microsoft's formula documentation addresses process-manufacturing inputs and outputs. These illustrate different product models; choose the representation that fits the operation rather than assuming every ERP uses recipe and BOM interchangeably.
Source: Frappe / ERPNext · Materials, quantities and operations. Reference details
Source: Microsoft Learn · Formula ingredients, quantities and outcomes. Reference details
Keep the packaging requirement with the finished format
An illustrative run targeting 1,000 one-bottle packs needs the appropriate bottles, caps and approved labels, plus the defined outer-pack requirement. If twelve packs form one shipping carton, the exact shipping configuration and treatment of partial cartons must be agreed. Do not round a materials calculation without showing its operational effect.
The same beverage sold in two bottle sizes may share a formulation but require different packaging and line settings. Connect the finished format to the relevant requirements. An aggregate packaging item without revision or format identity can make the production plan look feasible while the correct material is unavailable.
Not every requirement scales in the same way
Many ingredient quantities may scale with the planned output under the approved formulation, while some operating requirements may be fixed or change in steps. The system should represent those distinctions where they apply. Multiplying every line by the same factor can produce an unrealistic plan for a very small or unusually large run.
Use qualified process input to define the permitted batch sizes and scaling rules. The software should not improvise a new formulation or process parameter to fill an order quantity. If a demand quantity falls outside the approved production model, planning needs a visible exception and an authorised decision.
A version needs an effective scope
Record the approved version and when or where it applies. A change may affect a product format, site or future production date. Preserve the version selected for an existing work order so a later master update does not rewrite the planned requirement behind a completed run.
Keep the change's review and approval references. A new supplier pack, ingredient substitution or artwork revision can affect purchasing, quality, labelling and costing as well as production. The version-control workflow should route those dependencies to the relevant owners instead of treating the edit as a purely technical database update.
Use actual transactions to test the planning model
For one completed run, compare calculated requirements with actual material issues, returns, accepted output and recorded differences. The comparison can reveal a wrong unit, missing packaging component or an incomplete stage relationship. It can also identify a real process variation, which needs its own investigation.
Do not edit the standard simply to erase every variance. Preserve the baseline and determine why actual use differed. A valid approved change should create a controlled revision; a recording error should be corrected in the transaction history. Those are different actions with different consequences for future planning.
Choose the first implementation around a real product family
Select a family containing a shared formulation and at least two pack formats. Build the item and unit relationships, approved versions and expected output basis. Then calculate one planned run and reconcile one actual run using the same model.
An AI tool may help organise existing recipe documents into a draft structure, but the responsible owners must verify quantities, units and applicability. The project's acceptance evidence should be a reproducible requirement and variance account, not merely a successful import of many spreadsheet rows.
Summary
A useful food BOM connects the approved product definition to purchasing, production and packaging on explicit units and output bases. Versioned requirements support planning; actual transactions explain execution. Keep those accounts related without allowing a master-data edit to overwrite production history.
What to do next
- Map one formulation and two pack formats with their stock and output units.
- Verify the approved scaling rules and version applicability with the responsible owners.
- Reconcile a completed run before expanding the model to more products.
Compare this workflow with your current setup
Share the step that takes the most manual work, the systems involved and the exceptions your team handles. That gives us a concrete starting point for comparing approaches.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Bill of MaterialsFrappe / ERPNext · Online product documentation, accessed October 2026
Product reference for materials, quantities and operations in a BOM. Product specifications and authorised recipe decisions require their own approval process.
- Formulas and formula versionsMicrosoft Learn · Dynamics 365 Supply Chain Management documentation, accessed October 2026
Reference for formula inputs, outputs, versions and activation. Proposed recipe changes still require the business's qualified approval process.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).
