Manufacturing ERP Guide: BOMs, MRP, Shop Floor and Costing
A practical guide to manufacturing ERP: modelling BOMs and routings, making MRP trustworthy, shop-floor data capture, costing, quality and traceability.
Industry · Manufacturing
Context
A manufacturing ERP replaces that patchwork with one model of the business: what you sell, what it is made of, how it is made, what it costs, and what needs to happen next. The hard part is not installing it — it is modelling BOMs, routings and costing in a way that reflects the shop floor without burying planners in data maintenance.
01Operational challenges
Production plans built manually each week from sales orders and gut feel, with no visibility of component shortages until a job is already on the floor.
Engineering changes made on drawings but not in the system, so material requirements and costs are calculated from outdated recipes.
Standard costs set years ago, labour and overhead absorbed by rule of thumb, and no comparison of actual to standard by job.
Buyers react to shortages with expedited freight and premium prices because demand never reached them in time.
02Core flows
03Industry workflows
BOM and routing revisions tracked with effective dates, so new orders use the new version while work in progress finishes on the old one.
Different replenishment routes per product: stocked items replenish by reorder rules, configured items create manufacturing orders directly from the sales order.
Components sent to a subcontractor for plating, heat treatment or assembly, with the subcontract cost added to the product and the stock at the subcontractor tracked.
Non-conforming parts routed to rework orders or scrapped with a reason code, so quality costs appear in reporting rather than disappearing into overhead.
04 — Reporting
05 — Compliance
Requirements depend on what you make. ISO 9001 environments need controlled documents, traceable non-conformances and calibration records. Customers in automotive or aerospace may require lot genealogy and first-article inspection records. The ERP should hold quality checks, lot and serial history and change records so audits are answered from the system rather than from filing cabinets.
Regulatory requirements vary by jurisdiction. We configure the system to support your obligations; confirm specific rules with your auditor or compliance advisor.
06 — Integrations
Common integrations include CAD or PLM systems for BOM imports, machine monitoring for actual run times, carrier platforms for shipping, eCommerce or EDI for customer orders, and BI tools for management reporting. BOM import from engineering is the one we see most often requested — and most often done badly, with no revision control.
07AI opportunities
Practical uses that sit on top of clean ERP data. None of them replace getting the core transactions right first.
Read supplier confirmations, invoices and certificates of conformance, and match them to purchase orders and receipts automatically.
Flag customers whose ordering pattern has shifted so planners review forecasts before shortages appear.
Draft quotes for repeat or similar products by finding past jobs with comparable specifications and actual costs.
08ERP modules
09Roadmap
Clean item master, multi-level BOMs and routings for the top products by volume, with work centres and realistic times.
Sales, purchasing, inventory and accounting go live with manufacturing orders, before detailed work-order tracking.
Work orders, operator interfaces, scrap recording and quality checks introduced work centre by work centre.
MRP tuned with real lead times and safety stock; actual-versus-standard analysis reviewed monthly.
Maintenance scheduling, machine data integration and advanced reporting.
10Common mistakes
Twenty operations per part with second-level timing looks precise but nobody keeps it current. Start with the operations that matter for capacity and cost.
MRP is only as good as lead times, stock accuracy and BOMs. Running it on dirty data produces nonsense proposals and destroys trust on day one.
If reporting production takes operators longer than before, they will stop doing it, and WIP and costs become fiction.
Costing method and overhead absorption are finance decisions. Get them wrong and every margin report is wrong.
Explore further
Insights
A practical guide to manufacturing ERP: modelling BOMs and routings, making MRP trustworthy, shop-floor data capture, costing, quality and traceability.
Who you need on an ERP implementation team: sponsor, project lead, key users, data owner, consultants and developers, with realistic time commitments.
Why ERP adoption fails and how to fix it: role-based training, key users, floor-level sessions, quick reference guides, and measuring adoption after go-live.
FAQ
If you need to schedule capacity by machine or measure labour per operation, work orders help. Simple assembly with one or two steps often works fine with manufacturing orders alone, which keeps shop-floor reporting light.
Yes. Replenishment routes are set per product, so stocked items and configured items can coexist in the same plant.
Accurate enough that MRP proposals make sense. We usually recommend a full count of components shortly before cutover and cycle counting from day one.
Yes, on components and finished goods, with upstream and downstream traceability reports for recalls and customer queries.
Similar industries
Next step
We will map your shop floor onto an ERP model and show you where it fits — and where it needs care.