Do You Actually Need an MRP System? An Honest Take for Growing Manufacturers

An MRP system (material requirements planning system) calculates which materials and components you need, in what quantities and by when, so that planned production can go ahead. It starts from demand for finished products, breaks that demand down through each bill of materials, nets it against stock and open orders, and proposes purchase and production orders timed by lead time.

The calculation itself is well understood. The practical problem is that an MRP system can only plan from the records it is given. If bills of materials, stock figures, lead times or demand are wrong, it produces precise but unreliable plans, and buyers and planners quickly stop trusting it. This guide explains how MRP works, where it fits, where it struggles and how to decide between MRP inside an ERP, a standalone tool or a focused custom system.

MRP nets future requirements against the stock you hold and the orders already placed. Illustrative photograph, not an OpsMavix client site.

Image credit: Tiger Lily, Pexels License. Resized for web, no other edits.

Key Takeaways

• An MRP system turns demand for finished items into timed requirements for components and materials.
• Its core steps are explosion through the BOM, netting against stock and receipts, lot sizing and lead-time offsetting.
• The output is only as reliable as the BOMs, stock records, lead times and demand it uses.
• MRP plans materials; capacity, scheduling and finance usually need further functions or systems.
• MRP fits repeatable products with stable BOMs better than highly variable one-off work.
• Choose between ERP, standalone MRP, configuration or a custom system by testing your real products, not by feature lists.

In this guide:

• 1. Understand What an MRP System Does
• 2. Know the Inputs MRP Depends On
• 3. Work Through the MRP Calculation
• 4. Separate MRP, MRP II, ERP and Scheduling
• 5. Recognise Where MRP Works and Where It Struggles
• 6. Check the Data Before You Trust the Plan
• 7. Compare the Available System Approaches
• 8. Pilot MRP on a Real Product Range
• Frequently Asked Questions
• How OpsMavix Can Help

1. Understand What an MRP System Does

Start with the question it answers

An MRP system answers one planning question: given what we expect to make, what must we buy or build, how much and when? It does this for every component in the product structure, not just the finished item.

Microsoft’s documentation for Business Central describes the purpose of MRP as providing “timed, formal plans to supply the appropriate quantity of the item at the appropriate time and location” (Microsoft Learn). That is a fair summary of the concept across most systems.

Distinguish independent and dependent demand

Demand for a finished product comes from customers or forecasts. This is independent demand. Demand for the parts inside that product is dependent demand, because it follows from the decision to make the finished item.

The master production schedule (MPS) states how many finished items you plan to make and when. MRP then works out the dependent demand for components. Business Central, for example, calculates MPS for end items with forecasts or sales order lines and MRP for the other items (Microsoft Learn).

Know what it does not decide

MRP proposes orders. A person still decides whether to release them, change quantities or challenge the demand behind them. Treat the output as a recommendation that needs review, particularly while data quality is being proven.

2. Know the Inputs MRP Depends On

List the records the calculation uses

Every MRP calculation depends on a small set of master and transactional records. If any one is weak, the plan inherits the weakness.

Understand the role of the BOM

The bill of materials defines the parent-child relationships MRP explodes through. A multi-level BOM lets MRP plan sub-assemblies and the parts within them in the right sequence. For the structure itself, see our guides on what a bill of materials is and how to set up a multi-level BOM.

Treat lead time as a measured number

MRP offsets every requirement by lead time to decide when to release an order. A lead time that is too short releases orders late; one that is too long ties up cash early. Measure it from your own purchase order and goods received dates, as explained in our supplier lead time guide.

3. Work Through the MRP Calculation

Follow the four core steps

1. Explode: multiply planned production of each parent by the quantity per unit in the BOM to get gross requirements for each component.
2. Net: subtract projected stock and scheduled receipts to find the net requirement in each period.
3. Size: apply the lot-sizing rule, such as lot-for-lot or a minimum order quantity.
4. Offset: move the planned order release earlier by the item’s lead time.

SAP’s documentation describes the same netting idea: the system “checks whether it is possible to cover requirements with the plant stock and fixed receipts already planned”, and creates a procurement proposal where there is a shortage (SAP Help).

Hypothetical worked example: netting one component

A hypothetical manufacturer assembles a steel shelving unit. Each unit uses 4 uprights. Planned assembly starts over six weeks are 0, 30, 0, 50, 0 and 40 units. Uprights are bought in with a 2-week lead time. There are 150 in stock, 100 are due from an open purchase order in week 2, safety stock is zero and the rule is lot-for-lot.

In week 2, 150 in stock plus 100 received, less 120 required, leaves 130. In week 4, 130 available against 200 required leaves a net requirement of 70. In week 6, nothing is left, so the full 160 is needed. Offsetting by 2 weeks, the buyer should place orders for 70 in week 2 and 160 in week 4.

See how lot sizing changes the answer

Now assume the supplier has a hypothetical minimum order of 250 uprights. The week 4 requirement of 70 becomes an order for 250, leaving 180 after week 4. Week 6 needs 160, leaving 20, so no second order is needed in the horizon.

Neither answer is automatically better. The minimum order reduces ordering effort but holds more stock. For the trade-off between ordering and holding costs, see our economic order quantity guide.

4. Separate MRP, MRP II, ERP and Scheduling

Compare the scope of each term

These labels are often used loosely. Agree what each means before comparing products.

Check how capacity is handled

Many MRP calculations assume infinite capacity. Business Central’s documentation states that its planning worksheet entries “assume infinite capacity” and that work centre and machine centre capacity is not considered when it develops those schedules (Microsoft Learn). A material plan can therefore be correct while the production schedule it implies is not achievable.

If capacity is your main constraint, read our guides on capacity planning and manufacturing scheduling software alongside this one.

Understand regenerative and net change planning

Some systems recalculate the entire plan each run; others replan only items affected by changes. Business Central offers both a regenerative plan, which deletes and replans all planned supply orders, and a net change plan, which considers items whose demand, supply or planning parameters have changed (Microsoft Learn). Ask any supplier how often their plan runs and what triggers a replan.

5. Recognise Where MRP Works and Where It Struggles

Match the method to the product profile

MRP works best when products repeat, BOMs are stable and lead times are reasonably predictable. It is harder to apply when every job is designed to order or when the BOM is not known until engineering is complete.

For engineer-to-order work, long-lead purchasing is often better tracked against the project. Our engineering PO tracking guide covers that approach.

A material plan still has to be achievable on the machines and with the people available. Illustrative photograph, not an OpsMavix client site.

Image credit: EqualStock, Unsplash License. Resized for web, no other edits.

Know the common limitations

• Nervousness: small demand changes can trigger many rescheduling messages across lower levels.
• Infinite capacity assumptions: the material plan may ignore bottlenecks.
• Fixed lead times: real lead times vary, and MRP usually plans with a single value.
• Data dependency: missing issues, scrap or BOM changes flow straight into the plan.
• Review effort: someone has to act on exception messages every planning cycle.

Decide whether you need MRP or a simpler method

Items with steady, independent demand can often be managed with reorder points or min/max levels. MRP adds most value where component demand is lumpy because it is driven by planned production. Compare the methods in our guides to reorder point systems and time-phased order point.

6. Check the Data Before You Trust the Plan

Hypothetical example: the cost of one stock error

Return to the shelving example. Suppose the system shows 150 uprights, but 60 were used on rework and never booked out, so only 90 are physically available. MRP still plans from 150 and recommends ordering 70 in week 2.

The calculation was correct. The input was wrong. The shortage appears in week 4, after the 2-week lead time has made it too late to order normally.

Run a data readiness checklist

1. Stock accuracy for planned items is measured by regular cycle counts.
2. Every issue to production, scrap and return is recorded against an item.
3. BOMs have an owner, a revision and an effective date for changes.
4. Open purchase and works orders are closed when complete or cancelled.
5. Lead times are reviewed against recent receipts.
6. Lot-sizing and safety stock settings are set per item, not left as defaults.
7. Demand and the master schedule have a named owner and review cycle.

Assign ownership of exceptions

MRP produces exception messages: expedite, defer, cancel or new order. Decide who reviews each type, how quickly and where the decision is recorded. Without that routine, a correct plan still leads to late or excess stock.

7. Compare the Available System Approaches

Match the approach to the gap

Check how packaged MRP behaves

Packaged systems vary in how they plan. Odoo’s Master Production Schedule, for example, is enabled in the Manufacturing app settings, suggests quantities that users then turn into manufacturing and purchase orders, and should not be combined with reordering rules for the same product because they conflict (Odoo documentation). Details like these matter more than a feature tick list. Our Odoo for manufacturing guide covers that product in more depth.

Compare the full operating cost

Include implementation, data cleansing, integration, training, licences or hosting, support and the planner time needed to act on the output. A capable system that nobody has time to maintain will drift back to spreadsheets. For a UK buying perspective, see manufacturing ERP systems in the UK.

8. Pilot MRP on a Real Product Range

Choose representative items

Pick a product family with a multi-level BOM, at least one bought-in long-lead component and some open orders. Load the real stock, open orders and lead times rather than clean demonstration data.

Agree acceptance tests

1. The BOM explosion matches a manual calculation for one order.
2. Netting uses current stock and open orders correctly.
3. Lot sizes and minimum order quantities are applied as configured.
4. Planned releases are offset by the correct lead time.
5. A demand change produces sensible exception messages.
6. A stock correction changes the plan as expected.
7. Planned orders convert to purchase or works orders with the right references.
8. Buyers and planners can explain why each proposal appeared.

Expand only when the plan is trusted

Run the pilot alongside your current method for a few planning cycles. Compare proposals with what experienced buyers would have ordered, and investigate every difference. Expand once the team trusts the output and the data routines are working.

Frequently Asked Questions

What is an MRP system in simple terms?

It is software that works out which materials and components you need, how many and when, based on what you plan to make. It uses your BOMs, stock, open orders and lead times to propose purchase and production orders.

What are the main steps of an MRP calculation?

Explode demand through the BOM to get gross requirements, net those against stock and scheduled receipts, apply lot sizing, then offset by lead time to find when orders should be released.

What is the difference between MRP and ERP?

MRP plans materials. ERP connects wider processes such as finance, sales, purchasing, stock and production, and many ERP systems include MRP as one function.

Does MRP consider machine capacity?

Often not by default. Many MRP calculations assume infinite capacity, so capacity planning or finite scheduling is needed to check whether the plan is achievable.

Do small manufacturers need an MRP system?

It depends on the products. A small business with repeat products and multi-level BOMs can benefit; one with mostly one-off work or simple bought-in stock may manage with reorder points and job tracking.

Why do MRP plans go wrong?

Usually because of inputs: inaccurate stock, outdated BOMs, unrealistic lead times or stale open orders. The calculation is mechanical, so input errors pass straight through.

Can MRP work with high-mix, low-volume production?

Partly. It can plan known components and common parts, but jobs whose BOM is defined late may need project-based purchasing and tracking alongside it.

Can OpsMavix build an MRP system?

Yes. OpsMavix can build focused planning and tracking applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.

How OpsMavix Can Help

OpsMavix can map how demand, BOMs, stock and purchasing connect in your business, then define the planning scope needed to make material requirements reliable.

That may involve improving your current system’s setup, connecting it to your stock records through an inventory automation system, adding manufacturing production tracking so issues and scrap are recorded at source, or developing a full custom ERP.

Contact OpsMavix with one recent shortage, the BOM and stock records behind it and the point where the plan diverged from reality. We can use that evidence to define requirements and a practical pilot.