Choosing an ERP system is one of the most consequential technology decisions a UK manufacturer will make. Get it right and you have a platform that connects every part of your business — from purchase orders to production scheduling to despatch — in a single, reliable source of truth. Get it wrong and you face years of expensive workarounds, poor data, and a system that the shop floor quietly stops trusting.
At Bailey and Associates, our Fractional CIO team has guided UK manufacturers through ERP selection, implementation, and recovery from failed implementations more times than we care to count. This guide sets out exactly how to approach the decision in 2026 — what to evaluate, what to avoid, and how to make a selection you will not regret.
Why ERP selection goes wrong in manufacturing
Most ERP projects that fail do not fail because the software was bad. They fail because the selection process was flawed. The most common mistakes we see are: choosing based on vendor demos rather than real-world fit, underestimating the cost and complexity of implementation, selecting a system that fits the business today but cannot support the business in five years, and not involving operations, finance, and IT equally in the decision.
A good ERP selection process takes three to six months, involves a structured requirements exercise, and results in a decision that the whole business understands and supports. A bad one takes six weeks, is driven by whoever shouts loudest in the boardroom, and produces a contract that nobody fully read.
Step 1: Define your requirements before you look at a single vendor
The single most important thing you can do before speaking to any ERP vendor is to document what your business actually needs the system to do. This is not a wish list of features. It is a structured requirements document that covers your core processes — how you plan production, how you buy materials, how you manage stock, how you schedule work, how you invoice customers — and the specific problems you need the new system to solve.
Your requirements should be divided into three categories:
- Must-have: Functions without which the business cannot operate. These are non-negotiable and should be tested in every demo.
- Should-have: Functions that would meaningfully improve how the business operates, but that could be managed another way if necessary.
- Nice-to-have: Features that would be useful but that will not influence the final decision.
Without this document, every demo looks impressive, every vendor sounds compelling, and you end up choosing the system with the best salesperson rather than the best fit.
Step 2: Understand the real total cost of ownership
ERP pricing is deliberately complex. The headline licence or subscription cost is rarely the number that matters most. To compare systems properly, you need to understand the full five-year total cost of ownership, which typically includes:
- Licence or subscription fees (per user, per module, or both)
- Implementation and configuration costs (often 1–3x the annual licence cost)
- Data migration from your current systems
- Customisation and integration work
- Training for all users, including the shop floor
- Annual support and maintenance fees
- Upgrade costs over the contract term
- Internal resource cost — the time your own people will spend on the project
For a £20m–£50m UK manufacturer, a realistic all-in ERP budget for selection, implementation, and first year of operation typically runs between £150k and £500k depending on complexity, number of sites, and the state of your existing data. Budgets significantly below this range should be treated with scepticism.
A Fractional CIO from Bailey and Associates will build a like-for-like total cost of ownership comparison across all shortlisted vendors, so you are comparing real numbers, not marketing figures.
Step 3: Shortlist systems that are built for manufacturing
Not all ERP systems are created equal for manufacturers. Some of the most widely marketed ERP platforms are fundamentally financial or distribution systems with manufacturing modules bolted on. Others are purpose-built for discrete or process manufacturing and have deep functionality in production scheduling, MES integration, shop floor data capture, and quality management.
For UK manufacturers, the shortlist in 2026 typically includes systems in one of three tiers:
- Tier 1 (enterprise-scale): SAP S/4HANA, Oracle Cloud ERP. Powerful but expensive, complex to implement, and generally only appropriate for manufacturers above £100m revenue or with highly complex multi-site operations.
- Tier 2 (mid-market manufacturing): Epicor Kinetic, Infor CloudSuite Industrial, SYSPRO, IFS Cloud. Purpose-built for manufacturing SMEs with strong production, MES, and supply chain functionality. The right tier for most UK manufacturers in the £10m–£150m range.
- Tier 3 (SME-focused): Sage 200 Manufacturing, Access Manufacturing, Prodis. Lower cost and simpler to implement, but with functional trade-offs that matter as complexity grows.
The right tier depends on your current revenue, growth trajectory, operational complexity, and integration requirements. Many manufacturers are in a tier that does not match their actual needs — either over-engineered and over-budget, or under-powered and generating workarounds.
Step 4: Evaluate implementation partners as carefully as the software
Your ERP vendor will typically deliver the software. Your implementation partner will deliver the project. These are often different organisations, and the quality of your implementation partner will have more impact on your project outcome than the software itself.
When evaluating implementation partners, the questions that matter most are:
- How many implementations of this specific system have you completed in UK manufacturing?
- Can you provide references from manufacturers of similar size and complexity to ours?
- Who will actually be on our project — name the people and show us their CVs?
- What does your project methodology look like, and what are the key decision points?
- What happens if we go over budget or over time — how is that risk shared?
Be wary of implementation partners who cannot provide manufacturing-specific references, who name senior consultants in the sales process but deploy junior ones on the project, or whose fixed-price proposals contain extensive small-print about what is and is not included.
Step 5: Run a structured, scripted demo process
A vendor demo without a script is an entertainment exercise, not an evaluation. Before any shortlisted vendor presents to you, provide them with a set of scripted scenarios based on your actual business processes — real part numbers, real customer orders, real production scenarios — and ask them to demonstrate how their system handles each one.
This approach has two benefits. First, it reveals where the system genuinely supports your process and where it requires workarounds or customisation. Second, it makes all vendors directly comparable, because they are all demonstrating the same scenarios rather than their own best-practice showpieces.
Involve your operations and shop floor management in the demo process. They will spot practical issues that IT and finance will miss, and their buy-in to the selected system will be critical during implementation.
Step 6: Plan the implementation before you sign the contract
The time to understand implementation risk is before you sign, not after. Before committing to any ERP system, you should have an agreed project plan with milestones, a data migration strategy, a change management plan, a testing approach, and a go-live cutover plan. You should also have clarity on which of your business processes will need to change to fit the system and which system configurations will be required to fit your processes.
Any vendor or implementation partner who is reluctant to provide this level of pre-contract detail should be treated with caution. The best implementations are the ones where everyone understands the full scope of the project before the contract is signed.
How a Fractional CIO from Bailey and Associates helps
ERP selection is exactly the kind of high-stakes, time-consuming, technically complex decision that benefits enormously from independent senior IT leadership. A Fractional CIO from Bailey and Associates will:
- Lead the requirements definition process across operations, finance, and IT.
- Build a structured shortlist based on genuine fit, not vendor marketing.
- Manage the RFP, demo, and evaluation process end to end.
- Build a like-for-like total cost of ownership comparison.
- Evaluate implementation partners with the same rigour as the software.
- Own the contract negotiation to protect your interests on scope, price, and risk.
- Provide ongoing governance during implementation to keep the project on track.
For most UK manufacturers, the cost of a Fractional CIO through the selection and implementation process is a fraction of the cost of getting the decision wrong.
FAQs: ERP selection for UK manufacturers
How long should an ERP selection process take?
A thorough ERP selection process for a UK manufacturing SME typically takes three to six months from requirements definition to contract signature. Processes completed in less than two months are almost always incomplete.
Should we build or buy our ERP?
For the vast majority of UK manufacturers, buying a proven ERP platform and configuring it to your processes is significantly lower risk and lower cost than building a bespoke system. Custom-built ERP projects in manufacturing have a very poor track record.
How do we handle the data migration from our current system?
Data migration is consistently underestimated in ERP projects. You should budget significant time and resource for data cleansing, mapping, and validation before any migration takes place. A Fractional CIO will design and govern the data migration strategy as part of the implementation plan.
What is the most common reason ERP implementations fail?
Poor requirements definition, underestimated scope, inadequate change management, and weak project governance are the four most common causes. All four are preventable with the right leadership and planning before the project starts.
Do we need to replace our MES when we replace our ERP?
Not necessarily, but the integration between ERP and MES is one of the most critical design decisions in any manufacturing technology programme. The two systems need to share data reliably, and the integration architecture should be designed and tested before either system goes live.
