Which ERP requirements does manufacturing create?
Bills of materials, production orders, real-time stock, and quality: what manufacturing SMEs should check when choosing a system, and why individual processes are the norm.
In manufacturing, ERP must connect material flow, production orders, stock, and quality on one data basis. Classic standard packages hit limits as soon as special machines, project manufacturing, or multi-level inspection plans shape daily work. Individual processes are the norm here, not the exception. Entry works when you take one end-to-end core process live and only then expand, instead of rebuilding every department at once.
Which requirements are typical in manufacturing companies?
Recurring check points in system selection:
- Bills of materials and routings linked to production orders
- Warehouse movements from production and purchasing without manual double booking
- Capacity and machine loading where standard logic is not enough
- Quality management with inspection plans and releases on the order
- Integrations to MES, BI, or accounting without media breaks
- Traceability of batch, serial number, and rework
Without a shared data basis, department islands appear: planning plans, warehouse counts, QA inspects, shipping delivers, reporting puzzles. More on planning depth: production planning in ERP. On QA: quality management in ERP.
Why do industry packages often fall short?
Because “industry” is not the same as “your flow.” Two machine builders can buy the same catalog and have entirely different bottlenecks: external processing, customer-specific bills of materials, bottleneck cells, serial-number-controlled assemblies. The package covers the average. Deviations migrate into spreadsheets, shop-floor tools, and parallel processes.
Individual ERP addresses that differently: processes are modeled, not adapted to predefined industry packages. Nuclos uses the same platform for goods receipt, transfers, production planning, and QA. References from mechanical engineering and manufacturing follow that pattern: one data basis, expansion at the next bottleneck.
How do you start without a manufacturing big bang?
Choose one end-to-end process, for example a production order with stock booking for a clear product family. Secure master data (bills of materials, work centers, storage locations). Take the flow live and measure schedule deviation, missing parts, and manual corrections.
Then attach adjacent areas: purchase replenishment, QA release, shipping. That builds acceptance in purchasing, production, and warehouse before the overall project escalates. Releases and traceability: workflow in ERP.
What do you check in demos and proposals?
- Can special cases be mapped on the order without a spreadsheet side process?
- How are feedback and scrap booked?
- Are hold and release steps visible on the same dataset?
- Which integrations to MES, DATEV, and e-invoicing are documented and maintainable?
- How is scope cut: core first, special logic later?
Delivery claims such as ERP in 30 days apply only on agreed scope. That is exactly why the process cut matters more than the feature list. On the product side, Nuclos Enterprise is the guided delivery offer, not the claim “everything at once.”
Which decisions come next?
Define manufacturing type and critical bottleneck. List media breaks between planning, warehouse, QA, and shipping. Decide the first productive subprocess and the mandatory integrations. Clarify whether standard logic holds or process adaptation is required.
Fundamentals: What is ERP?. For releases and traceability: workflow in ERP. Deeper planning: production planning in ERP.