MRP software for UK manufacturers: how to compare and shortlist

The symptoms are always the same. Delivery dates slipping. A stock count that never quite matches the picking list. Every morning starting with phone calls to chase components nobody noticed were short.

Underneath it, almost always, is the same cause. Production planning lives in spreadsheets, and spreadsheets do not talk to each other.

This guide is about MRP specifically: what it does on the floor, when you need it rather than a full ERP, how to work out which capability level fits your production model, and how to shortlist without spending six months in demos.

We should say where we stand first. We are an MRPeasy partner and we implement MRPeasy, so we may earn a referral fee if you buy it through us. We have still written this to help you choose properly, including the parts where something else fits you better.

What MRP actually does on the shop floor

From order to build plan in one step

Material requirements planning takes a confirmed sales order, explodes it through your bill of materials, checks stock and open purchase orders, and works out exactly what has to be made, bought or moved, and by when.

That is the calculation you currently run by hand in Excel. The difference is not speed, it is visibility.

In a spreadsheet, one short line quietly cascades. A works order stalls, a delivery date moves, and nobody knows until a customer rings. In an MRP system the shortage flags the moment it appears, the system proposes a reschedule, and the planner acts before the job reaches the floor.

Stock, costing and scheduling stop drifting apart

Most growing manufacturers run three things separately: stock replenishment, production scheduling and job costing. Accuracy leaks at every handoff between them.

Material gets consumed on the floor but stock does not move until somebody remembers to key it in. The job cost report shows the standard BOM rather than what was actually used. Lead times are estimates dressed up as data.

Connect them and material consumption feeds stock in real time, scheduling runs off real capacity and lead times, and job costs come from what happened rather than what was planned.

What that looks like in practice

We work with UK manufacturers who have been through this. Oceanic Saunas in Wolverhampton moved off Sage 50 and got full visibility and accurate costing. Their director put it plainly: “I can log in anywhere in the world and see how the business is doing, how many sales we’ve had today, what’s in production, everything.”

Hovat, a food packaging manufacturer with 75 staff, replaced a system dating from the 1970s and now has full traceability. Their head of finance said they had “saved thousands of pounds on postage alone in less than a year” and could “deal with actual margins now, not theoretical”.

Vanquish Hardware Protection, who make fire protection products, grew revenue 25 per cent in their first year on the system while holding on-time delivery above 99 per cent.

MRP or full ERP?

Where one ends and the other begins

MRP is the planning engine at the centre of most manufacturing ERP systems. ERP wraps finance, HR, CRM and purchasing around that engine and joins them in one database.

For a small or growing manufacturer, going MRP-first often captures most of the operational benefit at a fraction of the cost and timescale of a full ERP rollout. A twenty person manufacturer with a clear production model rarely needs a system built for a three hundred person multi-site group.

If you are weighing full ERP platforms rather than MRP, we have written a separate buyer’s guide to ERP for small manufacturers covering tiering, total cost of ownership and UK compliance.

Work out your capability level first

The common mistake is demoing enterprise ERP when what you need is focused production planning, or buying something lightweight that folds the moment it meets a multi-level BOM.

Our first conversation with any manufacturer is about the production model, before a single vendor comes up. Roughly:

• Repetitive, fixed product lines: strong scheduling and inventory control, rarely complex BOM management
• Batch: multi-level BOM explosion, lot traceability, work order management
• Make to order: fast quoting, accurate job costing, scheduling flexibility
• Engineer to order: all of the above, plus BOM revision control during live jobs, because design and build overlap

Knowing which one you are before you open a pricing page saves months.

Features to evaluate, and how

Four functional areas matter: BOM management including multi-level and variant BOMs, production scheduling, inventory with real-time visibility, and shop-floor control.

What “included” means varies a lot between vendors. Some cover all four in the base licence. Others gate shop-floor control or advanced scheduling behind a higher tier, which changes your real cost per user once you add what you actually need.

When you demo, bring a real BOM from your own range, a sample works order and a realistic stock scenario. Ask them to run all four areas using your data. Vendors who do that confidently are worth shortlisting. Vendors who steer you back to their own tidy sample set are telling you something.

UK accounting integrations

For a UK manufacturer, syncing with Xero or Sage is not a bonus feature. It removes a double-entry job that gets worse as order volumes climb.

Several SME-focused platforms document Xero integration, MRPeasy among them. Sage connectivity is less universal across this market, so if you run Sage, confirm it early rather than assuming a connector exists. Check the current position with the vendor and on the Xero app listing rather than taking any article’s word for it, this one included.

Verify depth, not existence. A native two-way sync handling invoices, payments and inventory postings is a different thing from a one-way export you reconcile by hand. Ask for a live sync during the demo and get them to say which flows are automatic and which are not.

Cloud or on-premise

Cloud deployments for small manufacturers typically go live in two to four months, with the vendor handling hosting, updates and security.

On-premise is a different proposition: a one-off licence cost, six to twelve months to implement, and IT maintenance sitting with you.

For a manufacturer under 250 people without a dedicated IT function, cloud removes a lot of overhead and reduces first-year risk. It also scales with headcount and allows access across sites and devices, including rugged handhelds on the floor.

On-premise still has a case where you have plant-specific latency requirements, strict data residency obligations, or legacy equipment integrations that cloud connectivity cannot reach. Those are the exception in the SME market rather than the rule.

Four questions to put to every vendor

These separate credible suppliers from ones who oversell in the demo.

• BOM revisions mid-job. How does the system handle a BOM revision on an active works order? Does it update automatically or does someone intervene?
• Shop-floor access. Can operatives record progress and material consumption without holding a full named-user licence?
• Data migration. What does migration look like for a manufacturer coming off spreadsheets, and who actually does that work?
• Go-live timeline. What is typical for a manufacturer our size and order volume, and what most commonly causes delay?

Clear, specific answers are a good sign. Vagueness on migration or go-live is a reliable predictor that implementation support will be vague too.

Getting from shortlist to go-live

Define your production model and the capability level it needs before you open a vendor website. Then demo three or four systems with the questions above.

Run a pilot on a single product family before committing to a full rollout. That surfaces data quality problems and workflow gaps somewhere controlled, rather than mid go-live.

Plan the data migration before go-live day rather than during it. Clean BOMs, accurate opening stock and confirmed supplier lead times are what the system runs on. Every implementation we have seen struggle, struggled there first.

Three steps, not a feature comparison

Choosing MRP software comes down to three things.

Work out what the software has to do for your production model, whether that is multi-level BOM explosion for engineer-to-order work or lot traceability for food.

Match features and pricing to where you are now and where you will be in eighteen months, not to a theoretical future.

Verify the accounting integration and the implementation support before you sign, because those two decide how quickly you see any value.

The best system is the one your team will actually use, set up properly for how you manufacture.

If you want help building a shortlist around your setup, budget and team size, get in touch. We will start with how you make things, not with a demo. You can also see the sectors we work in and what our implementation support covers.