MRP (Material Requirements Planning)

MRP (Material Requirements Planning) is a management method that calculates precisely which inputs a plant needs, in what quantity and at what time to meet a production plan. Instead of buying "just in case," MRP translates finished-goods demand into specific purchase and production orders, sequenced over time.

It works by combining three inputs: the master production schedule (what will be made and when), the bill of materials or BOM (which components go into each product) and the inventory status (what is in stock and what is already on order). With that, it prevents two costly, opposite problems: the stockout that halts the line and the excess inventory that ties up capital.

As a core practice of industrial planning, MRP falls within the scope of Manufacturing, where coordination between purchasing, production and inventory determines the margin.

MRP was born in the 1960s as one of the first applications of computing to factory management, and it is still the logical core of almost every industrial planning system. Its premise is simple but powerful: demand for materials is not independent, but derived. Nobody buys screws "just because"; they buy them because they are going to make a certain quantity of a product that uses those screws. MRP formalizes that reasoning and automates it at the scale of hundreds or thousands of components.

How it works, step by step

The MRP calculation, known as the materials explosion, follows a logical sequence that starts from the finished product and works down to the last input:

• Independent demand: the master production schedule sets how many units of each end product are needed and by what date.
• BOM explosion: for each product, the system walks through the bill of materials and multiplies to get the dependent demand for each component and subcomponent.
• Net requirements calculation: from that gross demand it subtracts available stock and what is already on order, leaving only what actually still needs to be sourced.
• Lead time offsetting: it places each order backward on the calendar according to the supplier's lead time or the manufacturing time, so the material arrives exactly when it is needed.
• Order suggestions: the result is planned purchase and production orders, with quantity and date, ready for a planner to review and release.

Why it matters for the business

Applied well, MRP reduces the capital trapped in inventory, lowers the frequency of shortages that stop the line and gives purchasing early visibility to negotiate better with suppliers. At a small metalworking company in Greater Buenos Aires, for example, moving from spreadsheet planning to MRP usually means no longer discovering a sheet metal shortage on the same day the order starts, and instead seeing it weeks in advance. That advance warning is the difference between calmly renegotiating a delivery date and paying for rush freight.

MRP, MRP II and ERP: how they differ

The term has evolved, and it is worth not confusing it with its relatives:

MRP is the materials calculation module; MRP II adds capacity planning (do I have the machines and the hours to make it?); and ERP integrates all of that with the rest of the company. Today, when people talk about "the MRP," they almost always mean the planning module inside a broader system.

Common mistakes

MRP is only as good as its input data. The most frequent pitfalls are an outdated BOM (which miscalculates requirements), inventory balances that do not reflect what is actually in the warehouse, and optimistic lead times that generate orders that arrive late. Another typical mistake is treating suggested orders as automatic decisions: MRP proposes, but the planner's judgment (minimum lot sizes, seasonality, plant capacity) remains essential. Without a well-defined safety stock, on top of that, any variation in demand ends in a shortage.

In modern industrial practice, MRP coexists with lean manufacturing approaches and pull systems such as kanban. They are not opposites: MRP plans the horizon and triggers long-term purchases, while kanban regulates the fine-grained flow on the shop floor. Combining them well is what separates a reactive operation from one that produces predictably.