Success in a manufacturing ERP does not follow from having an MRP module. The product structure, manufacturing operations, actual consumption, stock movements, quality records and cost information must work consistently on the same data model. This article lists the technical questions manufacturers should ask during evaluation.
Define your manufacturing model first
The same "production module" has to do different things under different manufacturing models. Before evaluating, write down your own:
- Make to stock: forecast-driven planning, series production, stock turnover as the driver.
- Make to order: order-based product structure, quote costing, delivery date commitments.
- Engineer to order / project based: project costing, progress billing, long-running work orders.
- Process manufacturing: recipes, yield, by-products, batch production.
- Mixed: several models running together in the same plant.
Most businesses are not on a single model; what matters is which one carries the revenue.
Product structure
The bill of material or recipe is the load-bearing structure of a manufacturing ERP. What to examine:
- Multi-level structures: should intermediates create their own stock records, or pass through as phantom levels?
- Versioning: when the structure changes, which version calculates past production? Without versioning, the cost of closed periods can change afterwards.
- Variants: are colour, size and dimension variations separate products or variants of one?
- Alternative components: can a second material serving the same purpose be defined?
- Scrap: do you need scrap defined per component, or is a single overall rate enough?
Operations and routings
Routings are built where operation tracking or operation-level costing is needed. Not every manufacturer needs detailed routings; in a single-operation assembly business, building routings creates data entry effort with no return.
If routings are built, these should be settled:
- Are setup and run times held separately? On small batches a significant share of cost can sit in setup.
- Are alternative routings needed? If the same product can run on different machines, the cost difference should be visible.
- Will subcontracted operations be tracked as a routing step? Quantities sent and returned must reconcile with the supplier invoice.
- Is rework a distinct operation type?
Planning
Usable MRP output depends on three things: accurate bills of material, reliable stock and realistic lead times. If one is missing, the team soon stops trusting MRP.
On capacity, ask: does the plan run on finite capacity? A plan assuming infinite capacity always says "it fits" and never reveals the bottleneck. Detailed scheduling (APS) is a separate capability and is not needed everywhere.
Actual production data
Cost and efficiency cannot be measured without data from the floor. Three methods exist, and they can be combined:
- Manual entry (terminal or paper): fastest to start, accuracy depends on discipline.
- Barcode/terminal: operation start–stop capture; a balanced solution in most plants.
- Automatic machine capture (counters, PLC, OPC-UA): the highest resolution and the highest setup cost.
Traceability
Traceability needs vary by sector and regulation: batch and lot with shelf life in food and pharmaceuticals, serial numbers in machinery and automotive, reel and batch tracking in packaging and textiles. The evaluation question is: can you produce, in one query, which finished goods came from a given raw material batch and where they were shipped?
Costing
There is no single correct costing method. Standard cost, actual cost, activity, machine and labour costs and overhead allocation are designed together according to the accounting and manufacturing model.
Standard cost may be recalculated annually, per period or under defined conditions, according to the company's cost accounting policy. What matters is that the version and validity period of the standard in use are traceable; otherwise past-period reports stop agreeing with each other over time.
For production cost to be calculated reliably, material consumption, operation or activity records, labour or machine costs, scrap and the overhead allocation approach must be modelled consistently in the ERP in a way that suits the manufacturing model. Which of those components is required depends on that model.
The evaluation question: "At what level of detail can you show the difference between planned and actual?" If the answer is only "per product" it is limited; splitting the variance into material and time and seeing it by line and shift is more useful in most plants.
Shop floor and machine integration
MES, PLC, IoT, weighbridges, terminals and barcode integrations form the environment around a manufacturing ERP. What matters here is not making the connection but clarity of record ownership: if the same production quantity arrives from both a terminal and a machine, which one prevails and how the difference is handled must be defined up front.
The boundary between ERP and MES should also be clear: the ERP plans and calculates cost, MES manages real-time execution. In small and mid-sized plants the ERP production module can cover most needs; MES becomes relevant when second-level resolution and line automation are required.
Critical requirements differ by sector
- Food manufacturing: batch traceability, shelf life, FEFO, recipe versions.
- Plastics: mould management, cycle times, machine-level costing, regrind ratio.
- Metal and machinery: quote costing, subcontracted operations, project cost accumulation.
- Packaging: multi-unit conversion, reel and remnant tracking, tolerance delivery.
- Textiles: style-variant hierarchy, size runs, subcontractor tracking.
The scenario to test during selection
Run your own end-to-end flow in the demo:
Enter an order → plan it → raise a work order → consume materials → record operation time → enter scrap → put it through quality → receive the finished goods → ship → invoice → show the cost of that job and its variance from plan on screen.
If that flow cannot be run, the evaluation is incomplete however long the module list is.
Is a manufacturing ERP enough on its own?
In most manufacturers the ERP is the core but not the only system. It is usually joined by mobile applications for shop-floor and warehouse terminals, a B2B portal for dealer orders, bank integration for collections and reconciliation, and time and attendance for shifts. Unless how these talk to the ERP is defined at the start, each becomes its own data island.
How to turn product choice into a matrix is covered in the ERP selection guide, and the cost lines in how to calculate ERP cost. To review how this structure would be built in your own plant, you can talk to our ERP consulting team.
Frequently asked questions
Our ERP has a production module but we do not use it. Why?
The most common reason we meet is that bill of material and operation data were never built. The module is available but produces nothing because nothing feeds it. In that case the ERP may not need replacing; the data model needs building first.
What is needed to run MRP?
At least three things: accurate bills of material, reliable stock and realistic lead times. If one is missing, MRP output is unusable.
Does collecting production data require stopping the plant?
Usually not. Data capture is built alongside the existing flow and started on a pilot line. The step that may need downtime is fitting a physical counter or connection to a machine, and that can be done in a planned maintenance window.
We work heavily with subcontractors. How should the ERP handle that?
Whether subcontracting is modelled as a routing step or as a purchasing process should be chosen at the start. Both work; what decides it is whether quantities sent and returned, scrap and the supplier invoice can be reconciled on the same record.
Does a small manufacturer need detailed routings?
Not always. Where operation-level costing or capacity planning is not required, a simpler production record model can be enough. Unnecessary detail becomes a module nobody uses because nobody enters the data.