What is MRP?

Material Requirements Planning (MRP) is a production planning and inventory control methodology that calculates the materials, components, and sub-assemblies required to meet a production schedule. It answers three questions simultaneously for every item in the bill of materials:

MRP answers:
What do we need? (which materials, which quantities)
How much do we need? (net of what we already have in stock)
When do we need it? (offset by manufacturing and purchasing lead times)

MRP was originally developed by Joseph Orlicky at IBM in the 1960s and formalised in his 1975 book Material Requirements Planning. It became the dominant manufacturing planning framework of the 1970s and 1980s and remains the backbone of most ERP systems' production planning modules today.

The three core MRP inputs

Additional MRP parameters

How MRP Calculates

MRP works by exploding the master production schedule through the bill of materials, level by level, to generate planned orders for every component and raw material. The calculation sequence is:

Step 1: Gross requirements

From the MPS, MRP determines the gross requirement for each finished product in each time period (week or bucket). It then explodes through the BOM to calculate the gross requirement for each sub-assembly and component — multiplied by the quantity per parent and the number of parents required.

Step 2: Net requirements

For each item, MRP subtracts available stock (on-hand inventory + scheduled receipts) from the gross requirement to determine the net requirement — the quantity that actually needs to be produced or purchased.

Net Requirement = Gross Requirement − Projected On-Hand Inventory − Scheduled Receipts + Safety Stock

Step 3: Planned order generation

For each period where a net requirement exists, MRP generates a planned order — either a production order (for manufactured items) or a purchase requisition (for bought-out items). The order is offset backwards by the item's lead time so that the material arrives exactly when it is needed.

Step 4: BOM explosion cascade

The planned orders for parent items become gross requirements for their components — cascading down through every level of the BOM. A product with four BOM levels will trigger four successive rounds of calculation, each level's orders becoming the next level's requirements.

Example MRP calculation

Period Week 1 Week 2 Week 3 Week 4
Gross Requirement (from MPS) 0 200 150 300
Scheduled Receipts 100 0 0 0
Projected On-Hand 120 20 (120+100-200) −130 → 0
Net Requirement 0 0 130 300
Planned Order Receipt 0 0 130 300
Planned Order Release (lead time = 1 wk) 0 130 300 0

Opening on-hand = 20 units, safety stock = 0 for simplicity. Week 3 requires releasing an order in Week 2 to arrive in Week 3.

MRP Limitations

MRP is a powerful framework but it was designed in an era of relatively stable manufacturing — and it carries assumptions that cause well-known problems in more complex or volatile environments.

Infinite capacity assumption

Classical MRP assumes unlimited production capacity. It will generate planned orders for whatever quantities the net requirements dictate, regardless of whether the shop floor, machine centres, or labour pool can actually deliver them. When the resulting production plan is infeasible, planners manually adjust it — a time-consuming and error-prone process. MRPII (Manufacturing Resource Planning) extended classical MRP to include capacity requirements planning (CRP), addressing this limitation partially.

Fixed lead time assumption

MRP uses a single fixed lead time for each item — the same offset is applied regardless of current shop floor load, supplier condition, or order size. In practice, lead times vary significantly. A supplier running at full capacity may deliver in 6 weeks instead of 3; a shop floor with a backlog takes longer per order than a lightly loaded one. This variability is invisible to classical MRP.

Plan nervousness

MRP re-explodes the BOM every time the MPS changes. In environments with frequent forecast updates — which is virtually every modern consumer goods or retail supply chain — MRP generates a constant stream of plan changes, expedite and de-expedite messages, and revised planned orders. This "nervousness" erodes trust in the system and leads planners to ignore recommendations, defeating the purpose of the system.

No handling of demand uncertainty

MRP treats the MPS as a deterministic plan. It does not natively model the probability that the forecast will be wrong, or dynamically adjust safety stock based on forecast error. Adding safety stock to an MRP system is typically done as a manual parameter rather than as a statistically derived calculation.

Disconnection from distribution

Classical MRP sees demand as a single input at the factory gate — usually the MPS, which may have been calculated with little or no visibility into what is happening in the distribution network. The gap between what distribution actually needs and what MRP believes is required is where supply chain misalignment lives.

What is DRP?

Distribution Requirements Planning (DRP) is a time-phased planning methodology that calculates inventory replenishment needs across every node in a distribution network. Where MRP looks backwards into production and procurement, DRP looks forward into the distribution chain — from the retail shelf back to the factory gate.

DRP was developed in the 1970s as a logical complement to MRP for companies managing multi-echelon distribution networks. The insight was simple but powerful: the same time-phased net requirement logic that works for components in a factory also works for finished goods moving through a network of warehouses.

A multi-echelon distribution network

Most manufacturing and retail supply chains involve multiple stocking levels between the factory and the end customer — a structure called a multi-echelon network:

Factory → Central DC → Regional DC → Local DC / Retail Store → End Customer

Each level in this network holds inventory, serves demand from below, and places replenishment orders on the level above. DRP calculates the optimal replenishment plan for every node in this network simultaneously, taking into account demand forecasts, current stock levels, safety stocks, lead times, and order quantities.

DRP inputs

How DRP Calculates

DRP uses the same net requirement logic as MRP, but applied across the distribution hierarchy rather than the production BOM hierarchy. The calculation flows from downstream to upstream.

Step 1: Calculate requirements at the retail/consumer level

Starting at the most downstream point — the retail store or customer location — DRP applies the demand forecast to calculate gross requirements by period. It nets against current on-hand stock and planned receipts to determine the net requirement, then generates planned replenishment orders offset by the store-to-DC lead time.

Step 2: Aggregate to regional DC level

The planned orders generated for each store supplied by a Regional DC become gross requirements at that Regional DC. DRP nets these against the DC's on-hand stock and in-transit inventory to determine the Regional DC's net replenishment requirements, then generates planned orders offset by the Central DC-to-Regional DC lead time.

Step 3: Aggregate to central DC / factory level

The planned orders for all Regional DCs aggregate to the Central DC level. The total planned order quantity at the Central DC represents the demand that the factory needs to plan against. This is the DRP-to-MRP interface — the output of DRP becomes the demand input for the master production schedule.

Why this matters: the aggregation effect

One of the most powerful features of DRP is that aggregating orders from many downstream locations to the factory level smooths out demand variability. A regional demand spike that would have caused a large spot replenishment order in an unplanned system is absorbed by the planned DRP calculation — reducing the bullwhip effect that typically amplifies demand variability as you move upstream in a supply chain.

Network Level DRP Input DRP Output Feeds into
Retail / Point of Sale POS forecasts, on-hand stock Planned store replenishment orders Regional DC requirements
Regional DC Store orders aggregated, DC stock Planned DC replenishment orders Central DC / national requirements
Central DC Regional DC orders aggregated, CDC stock Planned factory replenishment orders Master Production Schedule (MPS)
Factory (MRP) MPS from DRP aggregation Planned production & purchase orders Shop floor, suppliers

DRP Limitations

DRP is a significant improvement over ad-hoc distribution replenishment, but it is not without its own constraints.

Forecast dependency

DRP is only as good as the demand forecasts that feed it at the downstream end. Poor forecast accuracy — particularly for slow-moving, high-variability, or seasonal SKUs — propagates errors through every level of the DRP calculation. A forecast that is 30% wrong at the store level generates 30%-wrong replenishment signals all the way back to the factory.

Parameter maintenance burden

DRP requires accurate, up-to-date parameters at every node: safety stock targets, lead times, lot sizing rules, and forecast overrides. In a large network with thousands of SKU-location combinations, maintaining these parameters is a significant and ongoing workload. Stale parameters silently degrade DRP output quality without generating any obvious error signal.

Handling of promotional and irregular demand

Standard DRP calculations assume relatively smooth, forecastable demand. Promotional events, new product launches, and end-of-life inventory create spikes and step changes that require manual overrides and judgement-based adjustments above and beyond what the algorithm handles. Organisations running many promotions typically need a dedicated promotional planning layer on top of base DRP.

Inter-network dependency

In a global supply chain with multiple factories and distribution networks, DRP calculations in one region can create conflict with those in another if they are both drawing on the same constrained production capacity. Resolving these conflicts requires either a supply planning layer above DRP or an APS system that can optimise across the entire supply-demand network simultaneously.

MRP vs DRP: Direct Comparison

Dimension MRP DRP
Full name Material Requirements Planning Distribution Requirements Planning
Scope Factory / production planning Distribution network / inventory replenishment
Primary question What to make and what to buy, and when What to move where, and when
Core input Master Production Schedule + Bill of Materials + Inventory Demand forecast at downstream points + Inventory by location + Lead times
Core output Planned production orders + Purchase requisitions Planned replenishment orders across the distribution network
Structure BOM hierarchy (multi-level product structure) Distribution hierarchy (multi-echelon network)
Direction of explosion Top-down: finished goods requirements → component requirements Bottom-up: retail demand → regional DC → central DC → factory
Demand origin MPS (often driven by forecast or customer orders) Actual or forecasted demand at the point of consumption
Primary users Production planners, materials managers Distribution planners, inventory managers, supply chain analysts
Key dependency BOM accuracy, MPS quality, lead time data Forecast accuracy, safety stock parameters, lead time data
Integration point Receives demand signal from DRP; outputs to shop floor and suppliers Receives factory supply as a constraint; outputs demand to MPS

Integrating MRP and DRP

In an integrated supply chain, MRP and DRP are not alternatives — they are complementary systems covering different parts of the planning horizon. The integration between them is the most important and most commonly neglected aspect of supply chain planning architecture.

The DRP-to-MRP interface

The cleanest integration model works as follows:

  1. DRP runs first — calculating replenishment requirements across the entire distribution network from downstream demand forecasts
  2. DRP output feeds the MPS — the aggregated planned orders from the central DC (or the last stocking point before the factory) are converted into a demand signal for the Master Production Schedule
  3. MRP runs on the MPS — exploding requirements through the BOM to generate production and purchase orders
  4. Factory planned output feeds back into DRP — as available supply, constraining what the distribution network can plan to receive

In practice, this loop runs in a weekly (or more frequent) S&OP cycle, with planners reviewing and adjusting at each interface point.

Common integration failures

The most frequent reason that MRP and DRP systems fail to deliver their promise is poor integration between the two:

The role of S&OP in MRP/DRP integration

The Sales & Operations Planning (S&OP) process is the governance mechanism that closes the loop between MRP and DRP. The monthly S&OP review should explicitly address the interface: does the factory plan generated by MRP match what DRP says the distribution network needs? Where there are gaps, S&OP is the forum for resolving them — adjusting the production plan, the distribution targets, the safety stock parameters, or the demand forecast.

When to Use MRP, DRP, or Both

Business Profile Use MRP? Use DRP? Why
Manufacturer selling direct (no distribution network) Yes No Multi-level BOM is the planning challenge; no multi-echelon distribution to manage
Pure distributor (no manufacturing) No Yes Multi-location inventory replenishment is the planning challenge; no BOM to explode
Vertically integrated manufacturer-distributor Yes Yes Both manufacturing and distribution planning needed; integration is critical
High product complexity (deep BOM) Critical Depends on network Without MRP, component-level planning is unmanageable at scale
Wide geographic distribution network Depends on manufacturing Critical Without DRP, replenishment across many DC nodes becomes inconsistent and reactive
Highly seasonal or promotional demand With caution With caution Both MRP and DRP struggle with demand volatility; supplementary planning layers needed

Companies that genuinely need both

Any company that manufactures its own products and distributes them through a multi-tier network needs both systems integrated. This includes most consumer goods manufacturers (FMCG), pharmaceutical companies, industrial equipment manufacturers with dealer networks, and food producers supplying retail chains. The absence of either system — or, more commonly, the absence of integration between them — is one of the most frequent root causes of forecast bias, inventory imbalance, and planning instability in these industries.

Modern Alternatives: APS and DDMRP

Classical MRP and DRP were designed for the computing and business environment of the 1970s–1990s. The planning challenges of the 2020s — higher demand volatility, shorter product life cycles, more complex global networks, and real-time data availability — have driven the development of more sophisticated planning methodologies.

Advanced Planning Systems (APS)

APS (Advanced Planning and Scheduling) systems extend beyond MRP's infinite capacity assumption to simultaneously optimise production plans against capacity, material availability, and financial constraints. Where MRP generates a plan and leaves capacity conflict resolution to the planner, APS solves the constrained optimisation problem algorithmically. SAP APO, Kinaxis, o9 Solutions, and Blue Yonder are examples of APS platforms.

APS covers the same scope as MRP + capacity planning + DRP in an integrated optimisation model — making the MRP/DRP integration challenge easier, because a single system owns the full planning horizon from factory to shelf.

Demand-Driven MRP (DDMRP)

DDMRP is a planning methodology that deliberately breaks from classical MRP's forecast-driven, nervousness-prone approach. Instead of exploding a forecast through the BOM, DDMRP positions strategically placed inventory buffers (decoupling points) in the supply chain. These buffers absorb variability and decouple production and procurement from the noise of day-to-day demand fluctuation.

DDMRP generates production and replenishment signals based on actual consumption of buffers rather than on forecast projections — making the plan more stable and reducing the expediting and de-expediting cycles that plague classical MRP implementations. It is particularly effective in high-mix, high-variability, or short-lead-time manufacturing environments.

Which approach to choose

Condition Recommended Approach
Standard, stable manufacturing with predictable demand Classical MRP within ERP (SAP, Oracle, Microsoft D365)
Manufacturing with complex capacity constraints MRPII or APS with capacity requirements planning
Multi-echelon distribution, medium to large network DRP module within ERP, or standalone supply chain planning tool
High variability, high-mix manufacturing DDMRP (as a replacement or complement to classical MRP)
Large, complex, multi-country supply chain APS platform integrating production, distribution, and financial planning

Frequently Asked Questions

What is the difference between MRP and DRP?

MRP calculates what materials need to be produced or purchased to meet a production schedule, working backwards through a bill of materials from the master production schedule. DRP calculates what inventory needs to be moved or replenished across a distribution network to meet demand at each location, working backwards from downstream demand forecasts. MRP operates inside the factory; DRP operates across the distribution chain. In integrated supply chains, DRP output drives MRP input — the aggregated distribution plan tells the factory what to produce.

Does MRP still work in modern supply chains?

MRP remains a valid and widely used planning framework for manufacturing environments structured around bills of materials. Most ERP systems — SAP, Oracle, Microsoft Dynamics — use MRP as their core production planning engine. However, classical MRP has known weaknesses: it assumes infinite capacity, uses fixed lead times, and generates plan nervousness in volatile environments. These limitations have driven the development of APS and DDMRP for more complex situations. For stable, predictable manufacturing, classical MRP remains entirely appropriate.

What is the master production schedule and how does it connect to MRP?

The Master Production Schedule (MPS) is the top-level plan that defines what finished goods will be produced, in what quantities, and in which time periods. It is the primary input to MRP — the MPS is what MRP explodes through the BOM to calculate component requirements. The quality of the MPS directly determines the quality of MRP output. In integrated supply chains, the MPS should be driven by DRP output — the aggregated distribution replenishment needs flowing up from the network to the factory gate.

What is the bullwhip effect and how do MRP and DRP relate to it?

The bullwhip effect is the amplification of demand variability as signals move upstream through a supply chain — small fluctuations at the retail level become large swings in factory orders. MRP is vulnerable to the bullwhip effect because it re-plans based on every MPS change, generating cascading order changes through the BOM. DRP can reduce the bullwhip effect by aggregating many downstream demand signals before they reach the factory — smoothing out local variability that would otherwise propagate upstream. However, poorly configured DRP with high safety stocks at every level can itself amplify variability through what is called the "inventory explosion" effect.

What is DDMRP and how is it different from MRP?

Demand-Driven MRP (DDMRP) is a planning methodology that replaces the forecast-driven, BOM-explosion approach of classical MRP with a buffer-based, consumption-driven approach. Instead of forecasting requirements and exploding them through the BOM, DDMRP positions strategically placed inventory buffers at decoupling points in the supply chain. Production and purchasing are triggered by actual buffer consumption, not forecasts. This makes the plan dramatically more stable — fewer expedite messages, less nervousness, and lower inventory across the chain — particularly in high-variability, high-mix environments where classical MRP generates constant plan changes.