How to choose · ERP
How to choose an ERP for a mid-sized manufacturer
Last updated 25 October 2026 · 2 sources listed · Reading time about 3 minutes
Short answer
Choose an ERP by testing how it handles your production reality: bills of material, routings, lot or serial tracking, planning logic, costing and shop floor reporting. Demonstrations with scripted scenarios drawn from your own products expose gaps faster than feature lists. Weigh fit to your manufacturing mode, the depth of inventory and costing, the quality of the implementation partner, and how much customization the design will require.
Who this is for: An operations or finance director at a manufacturing company outgrowing disconnected accounting, inventory and production spreadsheets.
What to evaluate
Manufacturing mode fit
Make-to-stock, make-to-order, configure-to-order and project-based production use different planning and costing logic. A product built for one mode strains in another.
How to check: Ask the vendor to run a scripted scenario that matches your dominant mode using your own sample bill of materials.
Inventory and traceability
Lot, serial and expiry tracking, multi-location stock and quality holds affect compliance and recalls.
How to check: Trace one finished item back to its raw material lots and forward to customers in the demo.
Planning and scheduling depth
Material requirements planning and capacity scheduling determine whether the system reduces shortages or just records them.
How to check: Ask how it handles lead-time changes, safety stock, and a late supplier delivery, then watch the result.
Costing accuracy
Standard versus actual costing, overhead allocation and variance reporting drive margin visibility.
How to check: Have finance walk through how a production order posts material, labor and overhead to the ledger.
Shop floor data capture
If operators cannot record progress and scrap easily, planning data goes stale.
How to check: See the operator interface on a tablet or terminal and ask who maintains the devices.
Implementation partner capability
Outcomes depend heavily on the team configuring the system and their sector experience.
How to check: Speak to reference customers who make similar products and ask what went wrong during implementation.
Customization versus configuration
Heavy custom code makes upgrades expensive and locks you into particular developers.
How to check: Ask which of your needs are met through settings and which need code, and how upgrades handle the code.
Comparison
| Option | Good when | Watch out for |
|---|---|---|
| Cloud suite with manufacturing module | You want standard processes and managed upgrades | Limited flexibility for unusual production steps |
| Industry-specific ERP | Your sector has regulatory or process peculiarities | Smaller partner network and slower roadmap |
| Self-hosted on-premises system | You need deep control or have strict data residency | Your team carries infrastructure, security and upgrade work |
| Core accounting plus specialist production software | Production is complex and finance is simple | Integration upkeep and mismatched data |
| Lightweight inventory and order tool | Few production steps and simple costing | Outgrown quickly as complexity rises |
Decision worksheet
Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.
1. Have you checked each criterion?
0 of 7 criteria checked.
2. Compare options (0 = fails or unknown, 3 = meets it well)
| Criterion | |||
|---|---|---|---|
| Manufacturing mode fit | |||
| Inventory and traceability | |||
| Planning and scheduling depth | |||
| Costing accuracy | |||
| Shop floor data capture | |||
| Implementation partner capability | |||
| Customization versus configuration | |||
| Total (max 21) | 0 | 0 | 0 |
Questions to ask before you commit
- Can you demonstrate our top five production scenarios using our data, not a canned demo?
- Which manufacturing modes does the product handle natively?
- How does the system handle engineering changes to a bill of material mid-production?
- What reports does shop floor staff see, and can they work offline?
- What does the upgrade path look like for customized parts?
- Who will staff the implementation, and can we meet them before signing?
- What is the typical timeline for customers of our size, and what slowed them down?
- How is data exported if we leave, including historical production records?
Typical trade-offs
Adapt processes to the standard system versus customize the system
- Upside
- Adapting processes keeps upgrades simple and cost lower.
- Downside
- Staff may resist, and a few unique advantages could be lost.
Single go-live versus phased by plant or module
- Upside
- Phasing limits disruption and builds experience.
- Downside
- It requires temporary integrations and extends the project.
Cloud versus on-premises
- Upside
- Cloud shifts maintenance and security upkeep to the vendor.
- Downside
- You accept the vendor's release schedule and some constraints.
Common mistakes
- Selecting from a feature checklist alone. Use scripted scenarios based on your own products and exceptions.
- Excluding shop floor staff from evaluation. They will determine whether the data is entered accurately.
- Underestimating data preparation. Bills of material, routings and item masters usually need cleanup before loading.
- Customizing to mimic the old system. Question every request to copy legacy screens and reports.
- Choosing a partner on price. Weigh sector experience and the named team who will actually do the work.
Related questions
Do we need ERP or is better inventory software enough?
If your difficulty is mainly stock accuracy and ordering, a focused inventory tool may be enough. ERP earns its place when production, purchasing, finance and sales decisions depend on each other, for example when a customer order should trigger material planning and cost roll-up. Look at where errors originate: if they come from handoffs between departments, integration under one data model is the benefit.
How important is the quality of our bills of material?
Very. Planning, costing and purchasing all derive from them, so errors multiply through the system. Many implementations stall because bills of material are incomplete, inconsistent in units, or out of date. Audit them early, assign an owner for engineering changes, and treat their cleanup as a core project task rather than an afterthought.
Can a mid-sized manufacturer run ERP without a dedicated IT team?
Yes with cloud delivery and a reliable partner, but you still need internal ownership of the system: a business administrator who understands processes, manages users and coordinates changes. Without that role, configuration decays and requests stack up with the partner at higher cost.
What should be in a pilot or proof of concept?
Choose a representative product family including at least one awkward case such as substitutions or rework. Load real data, run orders through planning, purchasing, production and invoicing, and compare resulting costs and dates with what you know to be true. A pilot should end with a written list of gaps and agreed ways to close them.
Sources and further reading
These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.
- Manufacturing Extension Partnership — National Institute of Standards and Technology, retrieved 27 October 2026
- Information Technology Laboratory — National Institute of Standards and Technology, retrieved 27 October 2026
Related guides
Comparison · ERP
Single-suite ERP versus a best-of-breed application stack
A single-suite ERP offers one data model, one vendor relationship and consistent reporting, but individual modules may be shallower. A best-of-breed stack gives deeper functions in each area at the price of integration work, divided accountability and reconciliation effort. The right balance depends on how unusual your processes are in the areas that create competitive advantage and how much integration capability you can sustain.
Cost factors · ERP
What drives ERP implementation cost and overruns
ERP cost is dominated by effort rather than licenses: scoping, data cleanup and migration, configuration, integration, customization, testing, training and change management. Overruns usually come from unclear scope, poor data, late requirement changes, and underestimated internal staff time. Budget by workload, hold contingency for discovery, and make scope decisions explicitly rather than letting them accrete.
Requirements · ERP
ERP requirements for multi-entity and multi-country finance
Multi-entity finance needs more than a chart of accounts. Specify intercompany transactions and eliminations, multiple currencies and revaluation, parallel ledgers for different accounting frameworks, local tax and statutory reporting, entity-level security, and consolidation. Define each in terms of a close process you must complete, and verify that local statutory needs are covered by the product or by a supported localization.
How to choose · Business operations
How to choose a point-of-sale system for a shop, cafe or restaurant
Match the system to your workflow first: counter service, table service, appointments or online ordering each stress different features. Then weigh hardware, offline behavior, inventory and reporting depth, integrations with accounting and delivery channels, payment lock-in, support responsiveness and how easily you can export your data. Run a trial during a busy period before committing to a contract.
How to choose · Marketing and sales tools
How to choose an email marketing platform
Pick an email platform by matching list size, segmentation needs and sending habits to the tool, then test deliverability tooling, data import and export, and how pricing scales with contacts. Authentication support, suppression handling and integration with your customer data matter more than template galleries. Run a small pilot send before migrating the whole list, and confirm you can take your subscribers and consent records with you if you leave.
How to choose · CRM
How to choose a CRM for a small sales team
Pick a CRM by how well it fits the way your deals actually move, not by feature count. Map your real pipeline stages, decide who must enter data and how often, confirm email and calendar capture works without manual logging, and test reporting on your own sample records. Small teams usually benefit from simple configuration, fast data entry and clean exports more than deep customization they will never maintain.
Problems & fixes · Software procurement
Why software implementations fail or run late and how to prevent it
Implementations falter less from technology than from unclear scope, poor data, weak ownership and underestimated change effort. Prevent trouble by defining outcomes and boundaries up front, cleaning data before migration, naming a business owner with decision authority, and planning training and adoption as seriously as configuration. When a project slips, reset scope and sequence rather than adding pressure.