If you are looking for an ERP for manufacturing, the real question is not which brand has the longest feature list. It is which system will plan your materials correctly, give the shop floor clear instructions, record what was made from what, and tell finance what each job truly cost. A manufacturing ERP that does these four things well pays for itself in fewer stock-outs, less rework and calmer month-ends. One that does them badly becomes an expensive layer on top of the spreadsheets you were trying to retire.
This guide is written for managing directors, finance directors and operations or IT leads at UK manufacturers. It walks through each production need in turn, shows which of the systems we cover are suited to it and on what conditions, and lists the questions to put to an integrator before you sign anything. For the wider picture, start with what an ERP is and how to choose one.
What a manufacturing ERP (GPAO) must actually do
In French-speaking markets the term is GPAO; in the UK you will see it described as production management, MRP or MRP II, and increasingly simply as an industrial ERP. The scope is the same: turn customer demand and forecasts into purchase orders and works orders, run them through your routings and report the result in cost and stock.
A useful way to judge any system is to follow one product from quote to cash:
- A quote or sales order is created, with delivery dates that reflect real capacity.
- Demand triggers planning: what to make, what to buy, and when.
- Works orders release to the shop floor with routings, instructions and materials.
- Operators report progress, scrap and time.
- Finished goods are inspected, stored and despatched, with traceability intact.
- Actual costs are compared with standard costs and posted to the ledger.
If an ERP breaks that chain anywhere, someone will rebuild the missing link in a spreadsheet. That is the pattern to avoid.
Summary of needs and fit
| Need | What the ERP must cover | Systems usually shortlisted |
|---|---|---|
| Bills of materials and routings | Multi-level structures, versions, alternatives, work centres | All five, with differing depth |
| Planning and MRP | Demand, lead times, safety stock, rescheduling | Business Central, SAP Business One, NetSuite, Sage, Odoo |
| Shop-floor control | Works orders, time and scrap reporting, barcode capture | Odoo, Business Central, Sage |
| Traceability | Lot and serial tracking, recall reports | All five, depending on configuration |
| Quality | Inspection plans, non-conformance, certificates | Odoo, Sage, Business Central, with add-ons |
| Maintenance | Assets, planned tasks, downtime | Odoo, Sage, or a dedicated system |
| Costing | Standard and actual costing, work in progress | All five |
Read the last column as a starting point, not a verdict. Each system is configured differently by each integrator, and the gap between a basic and a well-implemented set-up is larger than the gap between products.
Bills of materials and routings
The bill of materials (BOM) and the routing are the foundation of everything else. Errors here multiply: a wrong quantity per unit distorts purchasing, costing and stock simultaneously.
What the ERP must cover
- Multi-level BOMs, with phantom assemblies and by-products.
- Version control, so engineering changes take effect on a controlled date.
- Alternative components and alternative routings.
- Routings with work centres, set-up and run times, and outsourced operations.
- Variants and configurable products, if you sell options.
Which systems suit, and when
Odoo offers a manufacturing application with BOMs, work centres and routing operations, and tends to suit firms that want flexibility and are comfortable with a more tailored build. Microsoft Dynamics 365 Business Central covers production BOMs, routings and capacity, and is a common choice where the business already lives in the Microsoft environment. SAP Business One provides BOMs and production orders suited to smaller discrete manufacturers. Sage is worth a look where Sage accounting is already in place and the production side is conventional. Oracle NetSuite supports assemblies and work orders in a cloud-only model.
Questions for the integrator
- How are engineering changes handled, and who approves them?
- Can you demonstrate a variant-heavy product from our range, not a sample one?
- How will our existing BOM data be cleaned and loaded?
Planning, MRP and scheduling
Planning is where most manufacturers feel the benefit, and where most disappointments start. MRP is only as good as the data fed into it: lead times, lot sizes, safety stock and accurate stock records.
What the ERP must cover
- Net requirements calculated from sales orders, forecasts and reorder rules.
- Suggested purchase orders and works orders, with the ability to firm them.
- Rescheduling messages when dates slip.
- Finite or at least capacity-aware scheduling for bottleneck resources.
- Visibility of the effect of a late supplier on promised dates.
Conditions to know about
Most mid-market ERPs perform infinite-capacity MRP by default, then give you capacity views to check the result. That is adequate for many firms. If you run a heavily constrained plant, with a single critical machine or long set-ups, ask whether finite scheduling is standard, an add-on, or a separate scheduling tool connected to the ERP.
Business Central and SAP Business One both offer planning functions that suit conventional make-to-stock and make-to-order mixes. Odoo gives a flexible planning set-up but depends on careful configuration of routes and rules. NetSuite offers planning and supply management suited to growing cloud-first firms. Sage's mid-market range is long established in production businesses.
Questions for the integrator
- How does the system treat engineer-to-order work, where the structure changes mid-order?
- Which planning parameters will we need to maintain, and who owns them?
- How is the plan reviewed each day: by exception, or by scrolling lists?
Shop-floor control and data capture
A plan nobody follows is not a plan. The shop floor needs clear instructions and a simple way to report back.
What the ERP must cover
- Release of works orders with the right documents and drawings.
- Time, quantity and scrap reporting at operation level.
- Barcode or touchscreen capture, ideally on tablets at the machine.
- Material issue and backflushing, with the choice of which to use.
- Real-time work in progress for the planner.
Odoo offers a work-order interface designed for operators and is often chosen where simplicity at the machine matters. Business Central can be extended with shop-floor and barcode solutions from its ecosystem, which your integrator should name and support. Sage and SAP Business One both support shop-floor reporting, often with partner tools for scanning.
The condition to remember: the quality of shop-floor capture depends far more on the training and the simplicity of the screen than on the brand. Insist on a pilot with real operators.
Traceability, batches and recalls
For food, medical, aerospace and automotive suppliers, traceability is mandatory in practice. For many other manufacturers it is simply good protection against a warranty claim.
What the ERP must cover
- Lot and serial numbers captured at goods receipt, in production and at despatch.
- Forward and backward trace: from a supplier batch to every customer who received it, and the reverse.
- Expiry and shelf-life management where relevant.
- Supplier and customer certificates linked to batches.
- A recall report you can run in minutes, not days.
All five systems can track lots and serials. The difference is how smoothly that tracking runs through multi-level production, where components from several lots feed one finished batch. Ask for a live recall demonstration on a product with several levels, and have your quality manager watch it. If you work in food, see also ERP for food and beverage.
Quality management
Quality is often handled in a separate system, but the data belongs close to production.
What the ERP must cover
- Inspection plans at goods receipt, in process and at final inspection.
- Recording of measurements and results against specification.
- Non-conformance reports, corrective actions and supplier ratings.
- Holding or quarantining stock until it is released.
- Certificates of conformity produced from the data.
Odoo offers quality functions as part of its application range. Business Central and Sage cover quarantine and inspection to a useful degree and can be extended. SAP Business One and NetSuite are commonly paired with specialist quality tools when the requirement is rigorous. Be honest about your customer audits: if they require a controlled quality system with document control and approvals, specify that explicitly. UK manufacturers placing products on the market should also check how product marking and compliance records, such as UKCA documentation, will be stored and linked to products.
Maintenance and asset management
Unplanned downtime hurts margin quickly. The question is whether maintenance sits inside the ERP or alongside it.
Some ERPs provide asset registers, planned maintenance schedules and work requests, which suits a modest plant with a small maintenance team. Odoo and Sage are often considered when an integrated option is wanted. For plants with complex asset hierarchies, spare-parts stores and condition monitoring, a dedicated maintenance system integrated with the ERP is the safer route. Ask the integrator to show how a breakdown becomes a work order, consumes spares from stock and appears in cost reports.
Costing, finance and the shop floor connection
The finance director's test of a manufacturing ERP is simple: can it explain the margin on a job without a spreadsheet?
- Standard costing compares planned with actual cost and shows variances for materials, labour and overheads.
- Actual costing rolls real purchase prices and time into the cost of each batch.
- Work in progress valuation keeps the balance sheet accurate at period end.
Check that the system supports the costing method your auditors and management accounts expect, and that VAT, multi-currency purchasing and intercompany flows work as you need them. If you export, ask how the system handles customs documentation and multi-currency pricing. The wider cost of ownership is covered in our ERP cost guide.
Choosing between systems for your type of production
The right choice depends on what you make and how.
- Discrete manufacturing with straightforward routings: Business Central, SAP Business One, Odoo and Sage are all credible.
- Mixed make-to-stock and make-to-order with distribution: Business Central and NetSuite are strong where wholesale activity sits alongside production; see wholesale and distribution ERP.
- Small producers seeking flexibility: Odoo, with the open source ERP guide explaining what that means in practice.
- Multi-entity or international groups on a cloud platform: NetSuite is frequently considered.
- Firms already invested in Sage or Microsoft: start with Sage or Business Central respectively, then test whether the production depth is enough.
For head-to-head views, see Odoo vs Business Central, SAP Business One vs Business Central and NetSuite vs Business Central. If you are smaller, the page on ERP for small business is a better starting point.
How to run the selection
- Write down your real processes, including the awkward ones: rework, subcontracting, samples, returns. Our requirements template helps.
- Rank needs as essential, useful or nice to have.
- Ask for scripted demonstrations built on your own products, not a generic factory.
- Check references of similar size and sector, which the integrator should be able to arrange without naming confidential clients.
- Plan the data migration early. BOMs, routings and stock balances are rarely clean. See the ERP migration guide.
- Agree who in your team owns the project. Most failures come from the organisation, not the software; read the common ERP project mistakes.
Choosing the integrator matters as much as the software
Two integrators can deliver very different results with the same product. Look for one that has implemented manufacturing, not only financials, and that can describe a comparable project in plain terms. Our guide on choosing an ERP integrator lists what to check, and how the matching service works explains how we introduce you to firms suited to your project. The service is free for you, we are not tied to any software publisher, and the integrator, not us, carries out the project.
Next step
Tell us about your products, your sites and your priorities, and we will introduce you to an ERP integrator with relevant manufacturing experience. You can then compare their approach on your own terms. For the full picture of options, see ERP software and the guide to implementation.
Frequently asked questions
What is the difference between an ERP and a standalone production planning tool?
A standalone production planning tool schedules work but usually relies on exports and imports for stock, purchasing and finance. An ERP holds all of that in one database, so a change to a bill of materials or a supplier delay flows straight into planning, costing and the ledger. For most growing manufacturers, that single source of truth is what removes spreadsheets.
Which ERP is best for a small UK manufacturer?
There is no single answer. Odoo and Microsoft Dynamics 365 Business Central suit many smaller producers, SAP Business One suits firms that want a structured, mature system, and Sage is often shortlisted by firms already using Sage accounting. The deciding factors are your type of production, your sites and the skills of the integrator. A short, honest requirements document settles it faster than a feature table.
Can an ERP handle both make-to-stock and make-to-order production?
Yes, the systems covered on this site can all support both, and many manufacturers run a mix. What differs is how much configuration each mode needs and how well the planning engine copes with engineer-to-order work, where the bill of materials changes during the order. Describe your real mix to the integrator and ask for it to be demonstrated, not just described.
How do I keep traceability if I already use paper travellers on the shop floor?
Start by deciding what you must prove to customers and auditors: usually which batches of material went into which finished goods, and who released them. An ERP can capture lot and serial numbers at goods receipt, consumption and despatch, with barcode scanning replacing the paper. Keep the paper process running in parallel until the first full recall exercise has passed.
Does an ERP replace a maintenance management system?
Sometimes. Some ERPs include maintenance modules covering assets, planned tasks and work requests, which can be enough for a modest plant. Larger sites with complex asset hierarchies often keep a dedicated system and integrate it. The integrator should tell you which route fits your equipment and your maintenance team, and what it means for reporting.
Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.