A production order is due next week. The raw materials appear available, but the intermediate required for the next stage is still awaiting release. Meanwhile, packing materials are ready for one configuration, although the order requires another.

A consolidated material list may show what the finished product needs. The planner also needs to know where each material enters production, what must be completed first and which output is available for the next stage.

Distinguish materials from operations

A bill of materials, or BOM, defines the components needed to produce an item. These can include raw materials, ingredients and semi-finished products. Operations, resources and manufacturing sequences require related process definitions; the BOM alone does not describe the complete manufacturing process.

One level may be sufficient for a straightforward product. Separately managed intermediates, bulk products and packing configurations may justify a layered structure. Follow the actual process rather than a preference for a more complicated setup.

Where a flat material list becomes difficult

Consider an illustrative manufacturer that produces a common bulk tablet and later packs it into different saleable configurations. The team needs to distinguish the materials required for bulk manufacture from those needed for each pack.

If every input sits under each finished pack as one long list, users may need separate calculations to understand shared bulk requirements and packing demand. A separately managed bulk output can provide a clearer planning boundary where the business needs it.

Create intermediate items where they serve a purpose

Not every operation needs a separate item code. An intermediate item becomes useful when the business must manage an output separately: holding stock, planning demand, recording a hand-off or distinguishing its availability from the finished product.

• Is the output stored or transferred separately?
• Does another stage consume it?
• Does it require its own identity or status?
• Would a separate record improve planning or reconciliation?
• Who will maintain the additional transactions?

Too few levels can hide dependencies. Unnecessary levels can burden users with records that add little value.

Make quantity assumptions visible

Agree the intended batch or output quantity, units, conversions and applicable yield assumptions for each structure. Establish where expected quantities end and actual production recording begins.

Manufacturing and packing need a consistent conversion basis. Bulk recorded by weight cannot be connected reliably to packs recorded in units without an agreed relationship. Ask production, stores and planning to explain the same requirement calculation.

Separate demand from usable availability

A BOM establishes that a material is required. It does not establish that the material is usable. Planning must also consider the applicable stock status, allocations and outstanding supply.

These controls belong in the wider manufacturing workflow. Discuss them alongside BOM design rather than assuming they follow automatically from it.

Plan revisions and packing differences

Agree how material changes and packing variants are approved, when they become applicable and how existing production orders are treated. Preserve a way to identify the version relevant to historical production.

A master-data edit is not a complete change-control process. Define the responsible decisions before configuration.

Test one product from end to end

Choose a representative product with an intermediate and packing variation where relevant. Demonstrate requirement calculation, shortages, stage outputs, use of existing bulk and reconciliation of actual quantities. Include a difference between expected and actual output.

This gives buyers a stronger evaluation basis than a demonstration using only a simple finished item. The example is a planning exercise, not a manufacturing instruction.

How Pharma Protocol can support the stage-wise discussion

When an ERP handles purchasing and finished-stock transactions but planners still calculate intermediate needs outside the system, the project should examine the manufacturing model. Pharma Protocol addresses pharmaceutical operations across material control, production planning, quality and dispatch.

Material control across manufacturing levels

The product scope includes traceability of raw materials, intermediates and finished goods. Define which stage outputs need their own item identity and how that identity follows the subsequent transaction. This connects the BOM discussion to stores and production responsibilities.

Planning that reflects the actual product structure

Production-planning requirements should connect demand, material availability and the relevant stage definitions. During evaluation, use your own representative structure to confirm the required BOM levels, unit conversions, packing variations and calculations. These details belong in the agreed configuration and development scope.

Quality and approvals around the plan

QC and QA workflows, controlled electronic approvals and audit trails provide relevant context for deciding when records may change and when material may progress. A BOM does not replace those decisions; the implementation needs to connect them.

A useful demonstration: bring one bulk or intermediate used by two finished packs. Ask us to trace the requirements, material status, stage output and packing demand, identifying any gaps that need scoped work.

Neurons Software Consultants has served pharmaceutical customers for 23 years, with installations across 45+ formulation and bulk-drug manufacturers. Our implementation discussions connect software requirements with the way production, stores, quality and IT teams work.

Explore Pharma Protocol pharmaceutical ERP, or read about readiness for eBMR. Bring one representative product flow and discuss your requirements with Neurons to identify the structure, stage dependencies and integration scope your implementation needs.

Reference

Microsoft Learn: Bills of materials and formulas explains components, associated routes and BOM version concepts. The practical selection questions above are Neurons’ editorial recommendations.

Related guides

Vendor and Customer Onboarding: From Registration to ERP Master Creation
Delivered, Rejected or Partly Accepted? Closing the Delivery Reconciliation Gap
Before Moving to eBMR: Are Your Masters, BOMs and Manufacturing Stages Ready?
ERP, MES and eBMR: Which Manufacturing Problem Does Each Address?
Where Should Pharma ERP Testing Focus? Risk and Business Impact in Practice
Pharma ERP Validation: What Should the Customer and Software Vendor Each Prepare?