Multi-Level BOM: Count a Shared Component Without Buying It Twice
Work through finished goods, stocked subassemblies and a component used at two levels. See how the BOM connects with Smart Suggest and new material actions.

A multi-level bill of materials, or BOM, shows the parts inside a finished product and the components inside its subassemblies. We connect that structure with production and material planning in Optiwise, so you can see the lower-level requirement before raising another purchase or job.
Optiwise supports nested BOMs up to five levels, with subassemblies, scrap, by-products, costs, routing and attachments. The material tree explains what goes into the product. Routing explains the work stages. Keep their units and quantities consistent.
Follow one component through two branches
Consider an illustrative order for ten pumps. Each pump needs one rotor assembly and one housing. Each rotor needs one shaft and two bearings; each housing needs one gasket and one bearing. With no existing supply, the complete gross requirement is ten shafts, ten gaskets and 30 bearings.
Counting only the rotor branch would give 20 bearings and miss ten. Buying 30 without checking stocked subassemblies can also overstate the new requirement.
Use the stocked subassembly before expanding its children
Suppose two accepted rotor assemblies are already usable and selected for this order, with no competing demand in this example. You need to make eight rotors and ten housings. The new work needs eight shafts, ten gaskets and 26 bearings: 16 for the rotors plus ten for the housings.
| Component | Rotor branch | Housing branch | Combined requirement |
|---|---|---|---|
| Shaft | 8 | 0 | 8 |
| Bearing | 16 | 10 | 26 |
| Gasket | 0 | 10 | 10 |
If six loose bearings are also usable for this requirement, 20 remain before other supply, timing and allowances are considered. Do not subtract the bearings inside the two stocked rotors again; those complete rotors already reduced the quantity that needs making. This hand calculation assumes one unit per piece, no scrap, no open purchases or other production supply and no competing orders.
Turn the requirement into the right action
Smart Suggest accumulates demand through the material hierarchy and considers stock, existing production and open purchases. Review the planning basis and the state of actions already created before accepting another recommendation. A pending purchase may cover a quantity while still arriving too late for the selected job.
Use the action centre to move the remaining need into purchasing, in-house production or subcontracting. If an alternative component is proposed, the engineering and quality responsibility for its suitability still applies. A selectable alternate is not a technical approval for every customer specification.
Keep a drawing change with the affected work
Maintain item codes, units, the parent-child structure and the drawing or instruction used for the job. When a design changes after release, identify which work is affected before changing the requirement. Retain the relevant attachment and decision with that work; do not assume every open order should adopt the same change.
ERPNext’s BOM documentation explains the parent/subassembly model. Follow our production workflow and usable-stock records, then bring a shared-component example to your walkthrough.
Questions about multi-level requirements
Why can the same component appear more than once?
A component may be used in several subassemblies. Combine the demand across the relevant branches while retaining their parent quantities and units.
Should we explode children of an already available subassembly?
First decide how much accepted subassembly supply covers the requirement. Expand the quantity that still needs making, with other demand and supply considered in the actual planning context.
Does a gross BOM total equal a purchase quantity?
No. Review usable inventory, existing production, open purchasing, dates and configured allowances before deciding the action quantity.
Related Posts

Food Rework Traceability From the Tub to the Receiving Batch
Trace an approved food rework tub into the receiving batch. Record what was issued, used, returned and held with a worked quantity example.
4 Nov 2026Read more →
How to Trace a Regrind Bag Before It Reaches the Hopper
Trace a recovered resin bag through weighing, job issue and actual hopper entry. Resolve a missing grade or source lot before approving reuse.
4 Nov 2026Read more →
Splitting a Supplier Lot Across Containers Without Double Counting
Follow a supplier lot through two container splits. Reconcile actual stock, retire the emptied tote and keep held pieces visible in Optiwise.
4 Nov 2026Read more →
Solder Paste Tracking: Keep Each Jar’s Storage and Opening History
Track solder-paste jars beyond the expiry date. Keep storage removal, opening, job issue and returned paste linked, with a worked timing example in Optiwise.
3 Nov 2026Read more →

