DDMRP: what it is, how buffers are calculated and how to apply it without changing your ERP

Almost every distribution business lives the same contradiction: it has too much stock and still runs out. The warehouse is full, working capital is trapped, and yet there are shortages every week. The usual answer is to buy more of everything, which makes the problem worse and hides its cause.

DDMRP is a planning methodology that attacks exactly that contradiction. In this article we look at what it is, why traditional MRP fails with erratic demand, how the three zones of a buffer are calculated with concrete numbers, and how it is implemented on the ERP you already have.

1. Why the traditional approach falls short

1.1 The forecast as the only source of truth

Classic MRP works like this: demand is forecast, exploded against available inventory and replenishment times, and orders are issued. The whole system depends on the forecast being reasonably accurate.

In high-variety distribution — thousands of SKUs, customers with irregular behaviour, promotions that distort the series and imported suppliers with variable lead times — SKU-level forecasting fails structurally. Not because of poor execution, but because the phenomenon being predicted is not predictable at that granularity.

1.2 The bullwhip effect

When every link in the chain rounds up to cover itself, the variation in real demand is amplified at each step. A 10% fluctuation at the point of sale can turn into 40% variation in the order to the supplier. The result is the familiar sequence of overstock followed by stockout followed by panic buying.

1.3 System nervousness

Every MRP recalculation moves dates and quantities on dozens of orders because of minor changes in the input data. The planner ends up ignoring the system's suggestions and buying on their own judgement, which is the clearest sign that formal planning has stopped working.

1.4 The cost of treating every SKU the same

A high-turnover SKU with a short lead time and an imported, seasonal, low-frequency one cannot be planned with the same logic. Most operations apply a single rule — the famous "two months of stock" — and the result is predictable: excess on the fast movers and shortage on the critical ones.

2. What DDMRP proposes

DDMRP, Demand Driven Material Requirements Planning, inverts the premise. Instead of trying to predict better, it proposes building decoupling points in the chain that absorb variability, and planning against real demand rather than against the forecast.

2.1 The five components

1. Strategic inventory positioning: deciding on which SKUs and at which point in the chain it is worth holding a buffer. Not all of them need one.
2. Buffer profiles and levels: sizing each buffer according to variability, lead time and consumption.
3. Dynamic adjustments: moving the size of the buffer in the face of seasonality, trend or known events.
4. Demand-driven planning: generating orders according to the buffer's position, not the forecast.
5. Visible and collaborative execution: prioritizing by colour, not by date.

2.2 The central idea: decoupling

A decoupling point is a place where stock is deliberately held to cut the propagation of variability. Upstream of that point, the supplier sees stable demand. Downstream, the customer sees immediate availability. The buffer absorbs the difference.

That also cuts the bullwhip effect: the supplier stops receiving erratic orders and starts receiving regular replenishments, which improves their own delivery performance and over time makes it possible to negotiate better terms.

3. How a buffer is calculated

The buffer is divided into three zones, and each answers a different question.

3.1 Green zone: how often and how much do I order

It determines order frequency and size. It is calculated as the greatest of three values:

• Average daily consumption × lead time × lead time factor
• The supplier's minimum order quantity (MOQ)
• Desired order cycle × average daily consumption

Example: a SKU with consumption of 100 units a day, a 20-day lead time and a factor of 0.3 gives 100 × 20 × 0.3 = 600 units. If the supplier has an MOQ of 1,000, the green zone is 1,000.

3.2 Yellow zone: covering the cycle

This is the heart of the buffer, and it covers consumption during the replenishment time:

Yellow zone = Average daily consumption × Lead time

Following the example: 100 × 20 = 2,000 units.

3.3 Red zone: protection against variability

This is the equivalent of safety stock, and it has two parts:

• Red base = Daily consumption × Lead time × Lead time factor
• Red safety = Red base × Variability factor

With a lead time factor of 0.3 and medium variability of 0.5: red base = 100 × 20 × 0.3 = 600, red safety = 600 × 0.5 = 300. Total red zone = 900.

3.4 The result

Top of buffer = green + yellow + red = 1,000 + 2,000 + 900 = 3,900 units. Reorder point (top of yellow) = 2,900 units.

The lead time and variability factors are not universal: they are assigned by SKU profile. A long lead time implies a lower factor; high variability implies a higher safety factor. That is where the planner's judgement comes in, and it is the part worth reviewing quarterly.

3.5 The available-flow equation

The decision to buy is not taken on physical stock but on the buffer's position:

Available flow = Stock on hand + Orders in transit − Qualified demand

Qualified demand includes overdue orders, today's orders and known future spikes above a threshold. If available flow falls into the yellow zone, replenish to the top. If it falls into red, it is urgent.

3.6 Prioritize by colour, not by date

This is the most noticeable practical difference day to day. The planner opens a screen where SKUs are ordered by buffer penetration: deep reds first, then reds, then yellows. Nobody argues about what is a priority, because the colour says so.

Compared with a list of suggestions carrying dates that change with every run, the difference in adoption is enormous.

4. Implementation in the real world

4.1 Not every SKU carries a buffer

The first job is segmentation. An ABC analysis by revenue is combined with an XYZ by demand variability, and the criterion of commercial criticality is added. The AX and AY items are clear buffer candidates. The CZ items — low turnover, high variability — are generally best handled to order or with simple rules. That connects directly to purchase planning and to each product's lifecycle, because a product in decline should not have a growing buffer.

4.2 The data you need

Historical consumption per SKU with at least 12 months, real lead times per supplier (not the promised ones, the delivered ones), MOQ and purchase multiples, and a calendar of known events. The data that is almost always missing is the real lead time, and its variability matters as much as its average.

4.3 Dynamic adjustments

The buffer is not fixed. For known seasonality, a factor is applied to daily consumption before the season arrives, not during it. For launches or discontinuations it is adjusted manually. That capacity for anticipatory adjustment is what separates a living implementation from a frozen spreadsheet.

4.4 On top of the existing ERP

DDMRP does not require replacing the ERP. Buffer calculation, flow position and colour prioritization can be built as a layer that reads the item master, the movement history and the open orders, and returns a replenishment suggestion. The order is still issued in the same system as always.

4.5 What to expect

Well-executed implementations tend to show a reduction in total inventory alongside an improvement in service level, which is the counter-intuitive result that makes the methodology attractive: it is not about having more stock but about having it distributed where it protects. The effect on working capital is direct and shows up in the first quarter, and the complementary work on what is already in excess sits in reducing excess inventory.

Frequently asked questions

Does DDMRP replace forecasting? It does not eliminate it, it demotes it. The forecast still serves to size capacity, negotiate with suppliers and anticipate seasonality. What it stops doing is triggering every purchase order.

Is it useful for a small distributor? Yes, and sometimes more so, because there is less process inertia. What determines viability is the number of SKUs and the variability, not revenue.

How long does an implementation take? The initial buffer calculation on historical data takes weeks. Real adoption — the planner buying by colour rather than by their own judgement — takes a few months and depends more on change management than on the tool.

How is it different from a classic reorder point? A reorder point is a fixed number reviewed sporadically. A DDMRP buffer adjusts with real consumption, distinguishes lead time from variability, incorporates known future qualified demand and prioritizes by penetration rather than by a binary threshold.

How nBlock applies DDMRP to your operation

nBlock's Purchasing block builds demand-driven planning on top of your current ERP:

• DDMRP buffers per SKU, calculated on your consumption and your real lead times.
• A forecast with seasonality for the dynamic adjustments.
• A replenishment suggestion rounded to the pallet or to the purchase multiple.
• Colour prioritization, with buffer penetration visible on a single screen.

---

Want to see how your buffers would look with your own data? Book a demo.