How to choose an ERP for a manufacturing business
Most ERP selections fail before the contract is signed, in a demo built on the vendor's data rather than the plant's. A method that keeps the decision anchored in how the shop actually runs.
Contents
Manufacturers rarely choose an ERP more than once or twice in a career, and vendors choose ERPs with buyers every week. That asymmetry explains much of the record: Gartner's ERP strategy lead says 70% of ERP initiatives fail to fully meet their original business case goals1.
Start with how the plant produces
The single most useful classification is the mode of production, because it decides which systems are even in contention.
- Job shop. One-off and short-run parts to order, where quoting speed and job costing decide margin. JobBOSS² is built for "make-to-order manufacturers who have one off parts and need flexibility"2.
- Make-to-order and configure-to-order. Standard products with options, where a configurator and MRP matter. Acumatica lists both, with finite-capacity scheduling3.
- Mixed-mode and engineer-to-order. Several modes in one plant. Infor SyteLine supports engineer-to-order, make-to-order and mixed-mode production4.
- Repetitive and process. Formulas, by-products and lean flows. Odoo's manufacturing app handles by-products and a master production schedule5.
Then list the records the ERP must own
Write down the records that must live in the ERP, and the ones that may live elsewhere. Business Central's documentation shows the chain for a typical plant: production BOMs and routings define the work, production orders consume material and post output and scrap, and finished production costs are calculated for financial reconciliation6. Every link in that chain belongs in one system. Correspondence about it, such as RFQs, supplier confirmations and customer status requests, does not have to.
Test vendors on your own parts
A demo script that reveals fit
- Three real jobs, with drawings, routings and last year's purchase history.
- A rush order that bumps two other jobs on the same machine.
- A supplier price rise on a key material in the middle of a quote.
- A nonconformance found at final inspection, traced to a heat number.
- The month-end: what the controller sees for WIP and job variances.
Ask each vendor to run the same script, and score each step as it happens. Vendors that ask to use their own demo data instead are telling you something about fit.
Check the AI claims precisely
Every vendor now has an AI story. Distinguish features that are generally available from those announced. Epicor reports more than 18 pre-built Prism agents in Kinetic, generally available in the UK and several European markets since June 20267. Business Central's Sales Order Agent is documented in detail, including that designated users review every outgoing message and that it is billed in Copilot Credits8. JobBOSS²'s AI drafts bills of materials from PDFs, spreadsheets and images for review2. Ask for each AI feature: what does it change on its own, who approves it, and what does it cost to run.
Red flags in a selection
- A demo built entirely on the vendor's sample company.
- No answer on how routings, open jobs and inventory will be migrated.
- A price for licences but none for implementation and data migration.
- AI features described only as "coming", with no general-availability date.
- References that are not manufacturers of a similar size and mode.
A short scorecard
| Question | What a good answer looks like |
|---|---|
| Mode fit | Built for how you produce, shown on your parts |
| Production chain | BOM to routing to order to cost, in one system |
| Floor | A realistic way to capture labour, output and scrap |
| AI | Generally available features, with approvals and a stated cost |
| Price | Licence, implementation and support quoted together |
| Exit | Data export and hosting terms in writing |
When scores are close, choose the system the production team found easiest to run on the rush-order test. The cost guide explains how to compare the proposals that follow, and our main guide ranks the systems by situation.
Questions buyers ask
What should a manufacturing ERP include?
At minimum, bills of materials, routings, work or production orders, material requirements planning, inventory, purchasing, sales orders and job or production costing that flows to the general ledger. Depending on the plant, add finite scheduling, a product configurator, shop-floor data collection, quality and maintenance.
How do we run a fair ERP demo?
Give every vendor the same script built from your own data, such as three real jobs with drawings, routings, purchase history and a rush order that disrupts the schedule. Score each step as it happens, with the people who will use the system in the room.
Should we choose a manufacturing-specific ERP or a general one?
Manufacturing-specific systems such as JobBOSS², Global Shop Solutions, Epicor Kinetic and Infor SyteLine are built around production, quoting and job costing. General ERPs with manufacturing modules, such as Business Central Premium and Odoo, suit plants with simpler production and strong finance or Microsoft requirements.
Sources
- ERP carnage continues as orgs jump in unprepared. The Register, 13 Nov 2025. Accessed 8 Nov 2026.
- JobBOSS²: centralize job shop data and scale operations. ECI Software Solutions. Accessed 8 Nov 2026.
- Manufacturing management software. Acumatica. Accessed 8 Nov 2026.
- Infor SyteLine: cloud ERP for manufacturers. Infor. Accessed 8 Nov 2026.
- Manufacturing (MRP) software. Odoo. Accessed 8 Nov 2026.
- Manufacturing overview: Business Central. Microsoft Learn, 15 Jul 2026. Accessed 8 Nov 2026.
- Epicor Prism launches across European markets, bringing embedded, industry-specific AI to manufacturers. Epicor via Business Wire, 23 Jun 2026. Accessed 8 Nov 2026.
- Sales Order Agent overview: Business Central. Microsoft Learn, 2 Oct 2026. Accessed 8 Nov 2026.
Updated 8 Nov 2026: First published.