Discover Alpide ERP

Learn why Alpide ERP is the right choice for your business. Explore our technology advantages, AI capabilities, and get started with live demos and free trials.

Products

Comprehensive suite of business applications designed to streamline operations, enhance productivity, and drive growth across all departments.

Alpide vs Traditional ERP

Implementation Timelines

Platform

The extensible data platform powers unified security, full-stack observability, and limitless custom applications.

Alpide ERP: Unified Workflow

Solutions for across industries Globally.

Ideal for businesses across industries seeking to create customized software solutions for a wide range of use cases.

Franchise Solution

RMA Software

Resources

Stay informed with our latest articles, blogs, and white papers on ERP trends, best practices, and industry insights.

Bill of materials structure diagram showing multi-level BOM with finished product, 
sub-assembly, and purchased component levels with required fields for MRP planning 
in manufacturing ERP

How to Build a Bill of Materials That Actually Works

13 Mar 2026

A bill of materials that actually works for production planning is accurate down to the last component, structured to capture every level of the assembly hierarchy, and maintained with enough discipline that the system always reflects what production actually builds. Most manufacturers have a bill of materials. Far fewer have one that their MRP system can plan from without generating shortages, excess orders, or quality failures. The difference is not complexity. It is whether the BOM was built with planning in mind or with documentation as the only goal.

What Every BOM Line Item Must Contain

A BOM that drives reliable MRP planning requires specific fields on every line. Missing any of them creates a gap that either generates a planning error or forces a planner to manually compensate every time the BOM is used.

  • Part number. A unique identifier for every component that matches the part number used in purchasing, inventory, and the supplier's records. Inconsistent part numbering across systems is one of the most common causes of duplicate inventory records and mis-allocated purchase orders.
  • Description. Clear enough that any planner, buyer, or shop floor operator can identify the component without needing to look it up. Abbreviations that only the original author understands cause delays at the worst possible moments.
  • Quantity per assembly. The exact quantity of this component required to produce one unit of the parent. This number must come from the engineering drawing or specification, not from memory or estimation.
  • Unit of measure. Must match the unit used in purchasing and inventory. A component measured in meters in the BOM but purchased in centimeters generates purchase order quantities that are off by a factor of 100.
  • BOM level. The position of this component in the assembly hierarchy. Level 0 is the finished product; level 1 is its immediate children; level 2 is the children of those children, and so on.
  • Revision. The engineering revision this BOM line reflects. When a component specification changes, the revision field is what tells the system which version of the BOM applies to each production run.

The Unit of Measure Trap

Unit of measure mismatches between the BOM and purchasing are among the most damaging and hardest-to-detect BOM errors. They produce purchase orders that appear correct on screen but arrive in the wrong quantity at the dock. Validating UOM consistency across BOM, purchasing, and inventory records should be a mandatory step in any BOM setup or migration process.

Why Does BOM Structure Matter as Much as BOM Content?

A BOM with accurate component quantities but incorrect structure produces the same planning failures as a BOM with wrong quantities. Structure determines which components MRP calculates requirements for, when it calculates them, and how it sequences procurement and production across the assembly hierarchy.

The most important structural decision is how many levels to capture. A single-level BOM that lists a manufactured sub-assembly as a top-level component without capturing that sub-assembly's own component list leaves MRP blind to everything below that level. The system generates a work order for the sub-assembly but no purchase orders for the components it requires, because those components are not visible in the BOM.

Every manufactured sub-assembly needs its own BOM record with its own component list, linked to the parent BOM through the assembly hierarchy. This multi-level structure is what allows MRP to explode requirements across every level simultaneously and generate complete, accurate purchase orders for every purchased component in the product, regardless of how many levels deep it sits.

Five Steps to Building a BOM From Scratch

Step 1

Start From the Engineering Drawing, Not From Memory

Every component, quantity, and specification in the BOM must trace back to an approved engineering document. BOMs built from memory or copied from a previous product without verification against current drawings contain errors that accumulate silently until they stop a production run. The discipline of building from drawings is non-negotiable for any BOM that will drive purchasing and production decisions.

Step 2

Identify Every Manufactured Sub-Assembly Before Building the Top Level

Before entering the top-level BOM, identify every component that is itself manufactured rather than purchased. Each of these sub-assemblies requires its own BOM record. Building sub-assembly BOMs first and linking them upward through the hierarchy is cleaner and less error-prone than building top-down and trying to insert sub-assembly records into a structure that is already partially complete.

Step 3

Verify Every Quantity Against the Drawing, Not Against the Previous BOM

When building a BOM for a new product variant or updating an existing one, it is tempting to copy quantities from a similar product and adjust only the differences. This approach inherits every error in the source BOM. Quantity verification must go back to the drawing for every component, every time, regardless of how similar the new product appears to an existing one.

Step 4

Apply Scrap Factors Where Process Yield Is Consistently Below 100 Percent

If a specific operation consistently produces scrap, the BOM should include a scrap factor for the components consumed at that operation. A scrap factor of five percent on a component tells MRP to order five percent more than the net quantity required, ensuring that scrap losses do not create a shortage at the end of the operation. Scrap factors should be based on measured process performance data, not on conservative estimates.

Step 5

Have Someone Who Did Not Build the BOM Validate It Before It Goes Live

A second reviewer comparing the completed BOM against the engineering drawing catches errors that the original builder missed because of familiarity with the product. This review should check every line for part number accuracy, quantity correctness, unit of measure consistency, and structural completeness. Skipping this step to save time costs far more in planning errors and production delays than the review itself requires.

See BOM Management Built Into Manufacturing ERP

Alpide ERP manages multi-level BOMs, engineering change control, and where-used analysis natively within the same system that drives MRP planning and shop floor execution.

Schedule Your Demo

Frequently Asked Questions

What should a bill of materials include?

A complete bill of materials should include a part number and description for every component, the quantity required per assembly, the unit of measure for each component, the level in the assembly hierarchy, and the revision status tied to the current engineering release. For purchased components, lead time is also a required field so MRP can calculate procurement timing correctly. Missing any of these fields creates gaps that produce planning errors when MRP calculates material requirements.

What is the difference between a single-level and multi-level BOM?

A single-level BOM lists only the immediate children of a finished product without showing the components that go into each sub-assembly. A multi-level BOM captures the full assembly hierarchy, showing every purchased component and raw material at every level of the product structure. For manufacturers whose products include sub-assemblies or fabricated parts, only a multi-level BOM gives MRP the complete picture it needs to calculate requirements at every level, not just the top.

How do you keep a bill of materials accurate over time?

Keeping a BOM accurate over time requires a formal engineering change control process that routes every product modification through an approval workflow before updating the BOM in the manufacturing system. Changes made informally through email or verbal instruction bypass the system and create gaps between what the BOM says and what production actually builds. Assigning a named owner to each BOM who is responsible for its accuracy, and requiring validation against physical engineering drawings at least annually, maintains data quality as products evolve.

Related Reading

About the Author

Alpide Digital Innovation CoE

The Alpide Digital Innovation Center of Excellence advances enterprise resource planning through robust cloud-native architecture, streamlined business logic, and modern technology. Our manufacturing research draws on implementation experience across discrete and mixed-mode production environments serving growing manufacturers across industries. For inquiries, contact sales@alpide.com.

Talk to Expert

Transform Your Business With Alpide

Streamline your business operations, access real-time insights, enhance control, ensure data accuracy, lower expenses, fulfill orders efficiently, and elevate customer service with.

Transform-Your-Business-With-Alpide