A discrete manufacturer, one that makes distinct, countable products from defined parts, needs an ERP built for that way of making things. This guide sets out what a discrete manufacturing ERP must do and how it differs from a general ERP or one built for process manufacturing.
Why "discrete" qualifies the ERP
An ERP, in general, is one connected system for running a business: sales, inventory, purchasing, production, finance. A discrete manufacturing ERP is that system with its production capability built specifically around discrete manufacturing, the assembly of countable units from components. The qualifier matters because the same word, ERP, covers systems whose manufacturing model is wrong for discrete work, either too generic to handle BOMs and routings well, or built for the flows and formulas of process manufacturing.
Bills of materials, done properly
The bill of materials is the foundation of a discrete manufacturing ERP. A discrete product is defined by its BOM, and a real discrete BOM is rarely a flat list. It is multi-level: the product is made of sub-assemblies, and those sub-assemblies have their own components. A discrete manufacturing ERP must handle that structure natively, so a change to a sub-assembly flows correctly into every product that uses it. It should also handle product variants, where a family of similar products shares most of a BOM and differs in defined ways, without forcing a manufacturer to maintain a separate BOM for every variation.
Routings and work orders
If the BOM says what the product is, the routing says how it is made: the sequence of operations and the work centres they run on. A discrete manufacturing ERP must let a manufacturer define routings and then run production as work orders against them, issuing components and tracking each operation through to finished units. This is the operational heart of the system, and it is where a generic ERP without true manufacturing capability falls short, it can hold a parts list, but it cannot run operations.
Planning in whole units
Discrete manufacturing plans in countable units, and a discrete manufacturing ERP's planning, its MRP and scheduling, must work that way. MRP explodes demand for finished units through multi-level BOMs to compute component requirements; scheduling sequences work orders across work centres. The planning logic assumes units, assemblies, and operations, which is exactly right for discrete work and exactly wrong for process manufacturing, where planning works in weights and volumes against formulas.
Costing that rolls up the structure
The cost of a discrete product is built up: the cost of its components, plus the cost of the operations that assemble them, rolled up through the BOM and routing. A discrete manufacturing ERP must compute cost that way and then show the variance when actual production differs from the standard. Because the product decomposes into parts and operations, its cost can be known precisely rather than estimated, and the ERP should make that precision available.
Unit and batch traceability
Many discrete products need traceability by serial number, the individual unit, or by lot, the batch. A discrete manufacturing ERP should record the genealogy of what was built, which components, which operations, which results, so a manufacturer can trace any unit backward to its parts and forward to its customer. For regulated or safety-critical products this is essential, not optional.
All of it connected
The point of a discrete manufacturing ERP, as opposed to a standalone manufacturing tool, is that the BOMs, routings, work orders, planning, and costing are connected to sales, purchasing, inventory, and finance in one model. A confirmed sale becomes demand, demand becomes a plan, the plan becomes work orders, completed work updates stock and cost, and all of it reaches the accounts. That connection is the value.
The takeaway
A discrete manufacturing ERP is an ERP whose manufacturing core is built around multi-level BOMs, routings, unit-based work orders, structural costing, and item-level traceability. A discrete manufacturer should check, specifically, that those are genuine and native, not a thin layer over a generic or process-oriented system. For how we approach this, see our manufacturing work.