Bills of materials that hold the real cost

A BOM here holds more than a parts list. It carries the production steps, the scrap you expect, the by-products you get back, and the cost that rolls up out of all of it. Sub-assemblies keep their own BOMs, versions keep their history, and variants come off one template.

Bill of Materials list view showing all product structures

Every BOM in one list

One list holding every product recipe you have. Drafts stay drafts until somebody approves them, so an unfinished BOM cannot be picked up by a work order and taken to the floor.

Drafts stay out of productionOnly an approved BOM can drive a work order. Half-finished structures sit where they cannot do any damage.
Import and export in bulkBring BOMs in from a file rather than typing them. This matters most on the first day, and again whenever a range changes.
Every BOM in one list

Build the recipe once

Materials, production steps and the outputs you expect, on one screen. Apply a routing template and the whole sequence of operations arrives already set up, in order, on the right workstations.

Routings do the repetitive partApply a routing and every operation is configured at once. You are not rebuilding the same sequence for each new style.
A cost total while you buildThe production cost updates as you add materials and operations, so you have the number before you approve anything.
Build the recipe once

Explode a BOM and see the whole bill

Drill through every sub-assembly level to get the total quantity of each raw material a finished item actually needs, and the production cost that comes with it.

Every level in one listOpen a sub-assembly and see the materials underneath it, without hopping between records adding quantities up yourself.
Refresh against current ratesPull current material rates into the BOM in one action, so product costing does not quietly drift out of date behind the market.
Explode a BOM and see the whole bill

The product tree, and its history

Browse the catalogue as a collapsible tree to see how anything is built. Designs can move on without losing what came before: each version is kept as a snapshot, and variants are generated from one template.

A tree you can openExpand a product to see what it is made of, several levels down, without opening a single record along the way.
Versions and variantsOld versions stay readable after you move on, and a variant BOM is generated from its template rather than copied and edited by hand.
The product tree, and its history

One product or ten thousand variants

The structure holds either way. Variant BOMs come off a single template instead of being copied by hand, and old versions stay readable long after you have moved on from them.

🌳
Multi-level Structure
Sub-assemblies nested as deep as the product goes, cost rolling up
⚙️
Operation Costing
Cost per step, from the workstation rate and the time it takes
♻️
Scrap & By-products
Waste and secondary output netted off, so the cost is what you spend
🔖
Version Control
Old versions kept intact, one click to make another one active

See how ERPX can transform your business

Streamline operations, boost productivity, and make smarter decisions with ERPX