ERP Software for the Manufacturing Industry: Do You Need It?
Full manufacturing ERP is powerful, expensive, and slow to land — and most SMB manufacturers do not need it yet. Here is how to tell whether you genuinely need one, and the right-sized owned alternative for firms outgrowing spreadsheets and disconnected tools.
Choosing ERP software for manufacturing industry use starts with how your factory makes and sells products, not with a vendor’s module list. A system that suits a make-to-stock food producer can be a poor fit for an engineer-to-order fabricator, even when both demos look impressive.
The practical problem is that most selection processes compare features in the abstract. Suppliers show their best paths, the buying team ticks boxes, and the gaps appear after contract signature. This guide is a buying method: define your manufacturing mode, write and weight requirements, script the demo, and compare a packaged ERP, an MRP add-on and a custom application on one shared scenario, including total cost and limitations.

The right system depends on how your floor actually produces work. Illustrative photograph, not an OpsMavix client site.
Image credit: Kevin Limbri, Unsplash License. Resized for web, no other edits.
Key Takeaways
- Start from your manufacturing mode: make-to-stock, make-to-order, engineer-to-order, process or discrete.
- Turn pain points into testable requirements, then weight them before any supplier presents.
- Give every supplier the same scripted scenario using your own products and data.
- Compare packaged ERP, an MRP add-on and a custom application on fit, integration, limitations and five-year cost.
- Score evidence, not promises: demonstrated, configurable, needs development or unsupported.
- Pilot on a representative product family before committing the whole business.
In this guide:
- 1. Start From How You Manufacture
- 2. Turn Pain Points Into Testable Requirements
- 3. Weight and Score Requirements Before Demos
- 4. Script the Demo Around Your Own Orders
- 5. Compare Three Approaches on One Scenario
- 6. Work Out Five Years of Total Cost
- 7. Ask Suppliers the Questions That Expose Gaps
- 8. Decide, Contract and Pilot
- Frequently Asked Questions
- How OpsMavix Can Help
1. Start From How You Manufacture
Name your dominant mode
Most manufacturers run a mix, but one mode usually drives the hardest planning and costing decisions. Identify it first, because it determines which capabilities are essential and which are nice to have. For how ERP processes run inside a factory once chosen, see our companion guide to ERP in manufacturing.
| Mode | How work starts | What the system must handle well | Common selection mistake |
|---|---|---|---|
| Make-to-stock (MTS) | Forecast or reorder level | Demand planning, reorder rules, batch sizing, finished goods stock | Buying job-costing depth you will rarely use |
| Make-to-order (MTO) | Confirmed customer order | Order-specific variants, material availability before release, delivery promising | Assuming a stock-based MRP handles customer variants |
| Engineer-to-order (ETO) | Quote, then design | Project structure, BOMs that evolve, long-lead purchasing, revision control | Expecting a full BOM at order entry |
| Process (batch or continuous) | Recipe or formula | Yields, units of measure, co-products, lot and shelf-life tracking | Testing only with discrete parts |
| Discrete | Parts and assemblies | Multi-level BOMs, routings, serial or lot numbers, work centre capacity | Ignoring shop-floor data capture |
Record the mix honestly
Estimate what share of orders, revenue and planning effort each mode represents. A business that is 70% repeat make-to-stock and 30% custom work may choose differently from one where the custom work carries most of the margin. Write the figures down; they become the weighting basis in section 3.
Check the operating constraints
- Number of sites, legal entities and currencies.
- Regulatory or customer traceability obligations.
- Subcontract operations that leave and return to the site.
- Shop-floor connectivity and the devices people will actually use.
- Accounting, CAD, ecommerce or EDI systems that must stay in place.
2. Turn Pain Points Into Testable Requirements
Rewrite complaints as outcomes
“Stock is never right” is a symptom. A requirement states what the system must make possible and how you will test it. Each one should be specific enough that a supplier can show it working on your data.
| Pain point | Testable requirement | Evidence to ask for |
|---|---|---|
| Jobs released without material | The planner sees shortages for a job before release | Release a job with one short component and show the warning |
| Quotes priced on guesswork | Actual labour and material are compared with the quote per job | Book time and issues, then show the cost-versus-quote report |
| Customer variants re-keyed by hand | An order-specific BOM is created from the sales order | Enter a variant order and show the resulting works order |
| Finance re-enters invoices | Sales and purchase documents reach accounting without re-keying | Post a sale and show the record in the finance system |
| Batch recall takes days | Lot genealogy from supplier batch to customer shipment | Trace one lot both ways in under the agreed time |
Separate must-haves from preferences
Label each requirement as essential, important or desirable. An essential requirement is one where a gap would stop you going live or force a manual workaround on a core process. Keep the essential list short; if everything is essential, the scoring stops discriminating.
Assign an owner to every requirement
The person who feels the pain should own the requirement and attend the relevant part of the demo. A buyer judges purchasing; a production supervisor judges shop-floor booking; finance judges postings and month-end.
3. Weight and Score Requirements Before Demos
Use a simple evidence scale
Agree the scale before anyone sees software, so a confident presentation cannot move the goalposts.
| Score | Meaning |
|---|---|
| 3 | Demonstrated on your scenario in the standard product |
| 2 | Configurable without code; supplier shows the configuration |
| 1 | Needs development, an extension or a third-party add-on |
| 0 | Unsupported or not shown |
Hypothetical worked example: weighted scores
A hypothetical 45-person make-to-order fabricator weights six requirements to a total of 100 and scores three shortlisted approaches. The approaches are explained in section 5. Each weighted score is the weight multiplied by the score; the maximum possible is 300.
| Requirement | Weight | Packaged ERP | MRP add-on | Custom application |
|---|---|---|---|---|
| Order-specific BOM from the sales order | 25 | 3 | 2 | 3 |
| Shortages visible before job release | 20 | 3 | 3 | 2 |
| Job booking on shared floor terminals | 15 | 2 | 2 | 3 |
| Job cost compared with quote | 15 | 3 | 1 | 3 |
| Finance postings without re-keying | 15 | 3 | 2 | 2 |
| Lot traceability for certified material | 10 | 3 | 2 | 1 |
| Weighted total (out of 300) | 100 | 285 | 205 | 245 |
| Percentage of maximum | 95.0% | 68.3% | 81.7% |
For example, the packaged ERP total is (25 × 3) + (20 × 3) + (15 × 2) + (15 × 3) + (15 × 3) + (10 × 3) = 285. All figures are hypothetical and do not describe any named product.
Read the scores with care
The highest score does not automatically win. Section 6 adds cost, and a lower-scoring option may close the gaps that matter most at a fraction of the price. Check whether any essential requirement scored 0 or 1; that is a red flag regardless of the total.
4. Script the Demo Around Your Own Orders
Send the script in advance
Give every supplier the same written scenario, sample data and timetable at least two weeks before the session. Ask them to use your item codes, BOMs and customers rather than their demonstration company. Suppliers who cannot load a small sample of your data are telling you something about implementation.
A practical demo script
- Create a customer order for a product with one variant option.
- Generate the works order and order-specific BOM from that sales order.
- Run material planning and show one component short.
- Raise the purchase order for the shortage and receive it partially.
- Release the job and book two operations from a shared floor terminal.
- Record scrap on one operation and issue replacement material.
- Send one operation to a subcontractor and receive it back.
- Complete the job, ship it with a lot or serial number and invoice it.
- Show actual cost against the quote, including the scrap.
- Show the finance postings and how a failed transfer is corrected.
Control the session
Keep a scorer for each requirement and a timekeeper. When a supplier says “we can do that”, ask them to show it or record the answer as needing development. Note every workaround, spreadsheet export or manual step, because those become daily work after go-live.
5. Compare Three Approaches on One Scenario
Define the shared scenario
The hypothetical fabricator above has 12 office users, 20 shop-floor users, about 600 active part numbers and two-level BOMs with customer variants. It uses Xero for accounting and wants to keep it unless replacing it clearly pays. Three approaches are on the shortlist.
- Packaged manufacturing ERP: one suite covering finance, purchasing, stock, planning and production. Microsoft Dynamics 365 Business Central is one example; Microsoft states that its Premium licensing provides the manufacturing capabilities, with work centres, routings and production BOMs to set up before production. Its MPS and MRP planning worksheets assume infinite capacity, so test capacity scheduling separately.
- MRP add-on to existing accounting: a manufacturing and stock application connected to the accounting package. Katana is one example; its site says it can push sales and purchase orders to Xero as invoices and bills and sync customer and supplier information.
- Focused custom application: software built around the fabricator’s specific job flow, integrated with Xero, and owned by the business. See our guide to bespoke ERP software in the UK for what ownership involves.

Score each supplier against the same script, with the requirement owner in the room. Illustrative photograph, not an OpsMavix client meeting.
Image credit: Vitaly Gariev, Unsplash License. Resized for web, no other edits.
Compare fit, integration and limitations
| Factor | Packaged manufacturing ERP | MRP add-on | Focused custom application |
|---|---|---|---|
| Best fit | Broad needs across finance, planning and multiple functions | Repeatable products, simpler routings, accounting kept in place | A specific, well-bounded workflow the market does not fit well |
| Integration | Most processes in one database; external tools still need interfaces | Depends on the connector’s scope and sync rules | Built to your systems, but you specify and maintain every interface |
| Configuration effort | High: many settings, roles and master data | Moderate | Defined during build; changes need development |
| Main limitations | Change effort, partner dependence, features you may not use | May lack depth for ETO, complex costing or multi-entity finance | Narrower scope; depends on documentation, support and continuity of the developer |
| Upgrade path | Vendor roadmap and release cycle | Vendor roadmap; may outgrow it | You decide; you also fund it |
Note what the comparison does not prove
These are patterns, not verdicts on any product. A packaged ERP may be lighter to implement than expected; an MRP add-on may cover your costing needs. The scripted demo is where those assumptions are confirmed or rejected. For an overview of the UK market, see manufacturing ERP systems in the UK.
6. Work Out Five Years of Total Cost
Hypothetical worked example: five-year total cost
Every figure below is hypothetical, rounded and excludes VAT. It is not a quote or a published price for any product. Replace the numbers with real quotes from your shortlist. The packaged ERP replaces the accounting package, so it carries no separate accounting subscription; the other two keep it.
| Cost line | Packaged ERP | MRP add-on | Custom application |
|---|---|---|---|
| Implementation, build or setup | £45,000 | £8,000 | £40,000 |
| Integration work | £0 | £2,000 | £6,000 |
| Training | £6,000 | £3,000 | £2,000 |
| Internal staff time (one-off) | £15,000 | £8,000 | £10,000 |
| One-off total | £66,000 | £21,000 | £58,000 |
| Software subscription or hosting, per year | £18,000 | £9,000 | £3,000 |
| Support and change requests, per year | £5,000 | £1,500 | £4,000 |
| Existing accounting subscription, per year | £0 | £1,200 | £1,200 |
| Annual total | £23,000 | £11,700 | £8,200 |
| Five-year total (one-off + 5 × annual) | £181,000 | £79,500 | £99,000 |
Combine cost with fit
Dividing the five-year total by the weighted score from section 3 gives one comparison lens: about £635 per point for the packaged ERP (£181,000 ÷ 285), £388 for the MRP add-on (£79,500 ÷ 205) and £404 for the custom application (£99,000 ÷ 245).
In this hypothetical case the MRP add-on is cheapest per point, but it scored 1 on job cost against quote, a requirement weighted 15. If margin visibility is the reason for the project, that gap may outweigh the saving. The packaged ERP covers the most, at the highest cost. The decision belongs to the people who own the requirements, not to the ratio.
Lines buyers often miss
- Data cleansing and migration of open orders, stock balances and BOMs.
- Additional user types, such as shop-floor or warehouse licences.
- Partner days for reports, forms and label changes after go-live.
- Testing time from your own staff, not just the supplier’s.
- Exit costs: data export, contract notice periods and archive access.
For more on what moves a quote, see our guide to ERP price.
7. Ask Suppliers the Questions That Expose Gaps
Product and fit
- Which of our scripted steps use standard functionality, configuration or custom development?
- How does the product handle an order-specific BOM that changes after the order is accepted?
- What capacity assumptions does planning make, and how is finite scheduling handled?
- Which features require a higher edition, an extra licence or a third-party add-on?
Integration and data
- Which records sync with our accounting, CAD or ecommerce systems, in which direction and how often?
- What happens when a transfer fails, and who sees the error?
- Can we export all our data in a usable format at any time, including after the contract ends?
Delivery and support
- Who will do the work, what have they implemented in a similar manufacturing mode, and can we speak to that customer?
- What do you need from our staff, and for how many days?
- How are support requests prioritised, and what is included in the annual fee?
- How are upgrades applied, and what happens to our configuration and extensions?
Commercial terms
- Which prices are fixed, which are estimates, and how are changes to scope priced?
- What are the renewal terms, notice period and any minimum user commitments?
Ask for written answers and attach them to the contract schedule where they matter.
8. Decide, Contract and Pilot
Make the decision visible
Bring the weighted scores, five-year cost, unresolved gaps and supplier answers into one decision paper. Record why the chosen option won and what risks were accepted. That record is useful when scope pressures arrive during implementation.
Contract for acceptance, not effort
Tie payments, where possible, to accepted outcomes from your demo script rather than to days spent. Specify the acceptance tests, who signs them off and what happens when one fails. For delivery planning, see our ERP implementation guide.
Pilot checklist
- One representative product family, including a variant and a long-lead component.
- Real opening stock, open purchase orders and open works orders loaded.
- At least one partial receipt, scrap event and subcontract operation processed.
- Job cost compared with quote and reviewed by finance.
- Finance postings reconciled, including one deliberately failed transfer.
- Floor users booking work on the devices they will actually use.
- Requirement owners signing off each essential requirement.
- An agreed go or no-go point before wider rollout.
Expand once the pilot is accepted, not when the calendar says so.
Frequently Asked Questions
What is the best ERP software for manufacturing industry buyers?
There is no single best system. The right choice depends on your manufacturing mode, product complexity, existing systems and budget. Score shortlisted options against your own requirements and a scripted demo rather than relying on rankings.
How is this different from understanding how ERP works in a factory?
This guide covers selection and buying. For how ERP processes such as planning, stock and costing connect inside a factory, read ERP in manufacturing.
Do engineer-to-order manufacturers need special ERP features?
Usually they need project-based structure, BOMs that can evolve after the order, revision control and long-lead purchasing tracked against the job. Test these explicitly, because many systems assume a complete BOM at order entry.
Is an MRP add-on enough for a small manufacturer?
It can be, particularly for repeatable products with straightforward routings where the accounting package stays in place. Check costing depth, traceability and integration scope against your essential requirements before deciding.
When does a custom application make sense?
When a specific, valuable workflow is poorly served by packaged products and its boundaries are clear. You gain fit and ownership, but you must fund maintenance, documentation and future changes.
How many suppliers should we shortlist?
Enough to compare genuinely different approaches, typically three or four. More than that makes scripted demos hard to run properly and dilutes the team’s attention.
Should we replace our accounting software with the ERP?
Only if integrated finance clearly pays for the change. Many manufacturers keep their accounting package and connect it; others benefit from one database. Include the accounting impact in the five-year cost.
Can OpsMavix help us choose rather than build?
Yes. OpsMavix can help define requirements and test scenarios, and can configure or integrate existing tools, build focused applications or develop a full custom ERP where that fits.
How OpsMavix Can Help
OpsMavix can turn your manufacturing pain points into weighted requirements and a scripted demo, then help you judge packaged, add-on and custom options against the same evidence.
That may lead to configuring your current tools, adding manufacturing production tracking on the shop floor, connecting stock through an inventory automation system, or developing a full custom ERP.
Contact OpsMavix with one recent order that went wrong, the records behind it and the step where information was re-keyed or lost. We can use that evidence to define requirements and a practical pilot.
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.