Replenishment Pull

Pattern: A named solution to a recurring problem.

Restock each supply-chain location from what was actually consumed, hold most protection at the highest useful aggregation point, and use buffer status to keep availability high without pushing excess inventory downstream.

Also known as: distribution/replenishment solution; TOC replenishment; replenishment solution.

Replenishment Pull is the supply-chain expression of the same logic that Drum-Buffer-Rope uses inside a plant: protect the system’s constraint, release work or stock from the signal that matters, and refuse local activity that raises inventory without raising Throughput. In distribution, the signal is actual consumption. A retailer sells a unit, a regional warehouse ships a unit, or a plant warehouse consumes from its finished-goods buffer; the upstream link replenishes what was consumed rather than what a forecast said might be consumed.

The counterintuitive move is where the protection sits. Conventional push distribution tries to place inventory close to the customer, then forecasts which item, at which location, at which time. TOC replenishment keeps smaller stock buffers at consumption points and places the larger protection at the plant warehouse or central warehouse, where demand variation is pooled across many locations. The downstream point still gets fast replenishment. It doesn’t carry the full uncertainty locally.

Context

Replenishment Pull fits a distribution or make-to-availability environment where customers expect immediate or near-immediate availability, but the replenishment time from production or upstream supply is longer than the customer’s tolerance time. A retailer, spare-parts distributor, regional warehouse network, or make-to-availability manufacturer all face the same operating question: how much stock should each location hold, and what should trigger the next replenishment order?

The pattern depends on four other ideas. Buffer Aggregation in Distribution gives the statistical reason for holding protection upstream. Make-to-Stock vs. Make-to-Availability explains why the operating commitment changes from “make to a forecast” to “maintain availability.” Buffer Management supplies the green, yellow, red, and black status readings. Subordination supplies the discipline: each link in the chain takes its signal from the system’s flow requirement, not from its local batch economics.

The TOCICO Dictionary calls the distribution/replenishment solution a pull method that sets stock buffer sizes, monitors buffer status, and replenishes inventory based on end-user consumption rather than forecast. Schragenheim’s TOC Handbook Ch. 11 is the canonical chapter-length treatment. It names the same six moves: aggregate stock at the plant or central warehouse, size stock buffers against demand and replenishment time, increase replenishment frequency, manage inventory through buffer penetration, use Dynamic Buffer Management, and set manufacturing priorities from the urgency in the plant-warehouse stock buffers.

Problem

Push distribution solves the wrong problem. It asks for a better forecast of local demand, then sends inventory downstream to match that forecast. The method looks reasonable because the customer can buy only what is physically available at the consumption point. But the forecast has to answer three questions at once: what item, where, and when. The more disaggregated the question becomes, the worse the variation becomes.

Schragenheim’s Handbook example makes the point without algebra. Demand for one item across 100 consumption points may be predictable in aggregate, but demand at any single location has a much wider range. If the distributor stocks every location against its local uncertainty, the system carries too much inventory and still stocks out in the wrong places. If it stocks every location against an average, it creates shortages at high-demand locations and excess at low-demand locations. Either way, the chain experiences the familiar contradiction: too much inventory and too many stockouts at the same time.

The standard response is to improve the forecast or add more planning detail. That doesn’t fix the structure. The problem is not only forecast error. It is the decision to place protection at the most variable point in the chain and to replenish from a prediction rather than from consumption.

Forces

• Availability is local, but variation is lower in aggregate. The customer buys from a specific location, yet demand is statistically smoother when many locations are pooled at a warehouse.

• Frequent replenishment looks expensive under cost-world measures. More shipments, mixed cases, and smaller batches can look inefficient even when they lower total inventory and protect sales.

• Forecasts improve with aggregation and degrade with disaggregation. The exact SKU-location-day forecast is the one push distribution needs, and it is also the one least likely to be reliable.

• A stock buffer is not a time buffer. TOC uses stock buffers in distribution and make-to-availability, while DBR uses time buffers in production. Treating the two as interchangeable creates the wrong priority signal.

• Local stock ownership pulls the chain back toward local optimization. Each retailer, warehouse, or planner wants protection in its own location; the chain needs protection where it reduces total uncertainty.

• The pattern needs fast replenishment to be credible. If the upstream link can’t replenish often enough, downstream buffers have to grow and the pattern loses much of its advantage.

Solution

Use actual consumption as the replenishment signal, and locate the largest useful stock buffer at the highest point in the chain that can replenish the downstream points quickly enough.

The operating design has five parts.

Place the main protection at the plant or central warehouse. In a manufacturer-owned chain, the plant warehouse is the finished-goods aggregation point. In a distributor-owned chain, the central warehouse is the hub. That upstream buffer sees the pooled demand of many consumption points, so the same total protection covers more demand variation than separate large buffers at each location. Regional warehouses may sit between the central point and the consumption points when transportation time is too long, but the logic stays the same: buffer at the point that can replenish many downstream locations, then pull from actual consumption.

Size each stock buffer against demand, supply, and replenishment time. A stock buffer target is the “order up to” level for a SKU at a location. The Dictionary’s rule is maximum expected consumption during average replenishment time, adjusted for unreliability in that replenishment time. The target is intentionally approximate. Schragenheim’s implementation guidance is to get a reasonable initial target in place, then let Dynamic Buffer Management adjust it against real consumption. Being approximately right quickly is better than spending months calculating a target that will be wrong as soon as demand shifts.

Replenish frequently and in mixed quantities. The pattern works by shortening the time between consumption and replacement. A daily mixed replenishment order can replace what each downstream location sold yesterday, instead of waiting for a batch-economic reorder point. Transportation cost may rise in some cases, but the decision is read in Throughput Accounting terms: lower inventory releases cash, better availability protects sales, and the extra variable cost of shipping is compared against both.

Use buffer status as the priority signal. In distribution, buffer penetration is the fraction of a stock buffer that is missing. A SKU with most of its target still available is green. A SKU that has consumed enough of the buffer to need attention is yellow. A SKU at risk of stockout is red. A stockout with actual demand is black. The color determines the action: order, investigate, expedite, or order immediately. The signal applies separately to each SKU at each location, so a production order or transfer order can be prioritized by the buffer it protects rather than by its due date alone.

Adjust buffers from the pattern of penetration. Dynamic Buffer Management reads “too much green” as an oversized buffer and “too much red” as an undersized or disrupted buffer. The common rule of thumb is to adjust the target by one third, then let the system settle before adjusting again. The adjustment is not a forecast. It is a feedback loop based on the combined effect of demand flowing out and supply flowing in.

Do not turn pull into forecast push: The pattern fails when a team keeps the vocabulary but returns to forecast-driven ordering. A buffer target is not a forecast quantity frozen into the system. It is a protection level that changes when buffer readings show that the chain is carrying too much or too little protection.

How It Plays Out

A consumer-goods distributor with 100 stores. A distributor stocks a popular item at 100 retail points. Under push distribution, each store receives inventory from a SKU-level forecast. The aggregate forecast for the whole region is fairly stable, but the store-level forecasts are noisy. Some stores run out, others carry excess, and the central planner responds by raising inventory everywhere. Under Replenishment Pull, the central warehouse holds the larger buffer, each store holds a smaller local buffer, and each store replenishes daily against what it actually sold. The central warehouse sees the pooled signal, while the store sees fast replacement. The total stock falls because the chain no longer protects each store against its own worst local variation.

A make-to-availability manufacturer. A manufacturer commits to immediate availability for a chosen family of repeat items. The plant warehouse holds finished-goods stock buffers for each SKU. When customers consume units, the plant warehouse buffer status creates the next production order and sets its priority. A red buffer for Item A outranks a green buffer for Item B even if the Item B order was created earlier. The production floor doesn’t need to know whether the order came from a retail sale, a regional warehouse, or the plant warehouse itself. It needs the buffer color and the percent of target remaining.

A regional warehouse network. A central warehouse serves three regional warehouses. Each regional warehouse replenishes from actual consumption, and each central-warehouse replenishment decision reads the virtual status of downstream stock and stock in transit. A shipment already on the road counts as protection for the downstream buffer. If a region is red but a shipment will arrive today, the transportation manager expedites the shipment; the central warehouse doesn’t duplicate the order blindly. The useful visibility is not “how much did the forecast say?” It is “how much protection is missing, and where is the replacement?”

Consequences

Benefits:

• Availability rises while total inventory falls. The pattern moves protection from many high-variation local points to fewer aggregation points, then restores local availability through frequent replenishment.

• The chain gets a single priority language. Green, yellow, red, and black buffer status can prioritize production orders, transfer orders, purchase orders, and expedites without a separate due-date argument for each one.

• Forecast dependence drops. Forecasting still matters for capacity, seasonality, and unusual demand spikes, but the daily replenishment order comes from consumption and buffer status.

• Cash is released from the wrong inventory. The chain stops carrying large local cushions that don’t earn their keep, which improves inventory turns and frees cash for variety, capacity, or genuine constraints.

• The POOGI signal becomes visible. Repeated red events at the same SKU, supplier, lane, or warehouse identify where the chain’s next improvement effort belongs.

Liabilities:

• Replenishment time is the governing constraint. If transportation, order processing, or production lead time can’t be shortened enough, downstream buffers must grow and the inventory advantage shrinks.

• The pattern can be misread as kanban. Both are pull systems, but Replenishment Pull is a chain-level stock-buffer design with central aggregation and Dynamic Buffer Management. A local card loop doesn’t supply that logic.

• Seasonality and sharp demand changes still need judgment. Schragenheim is explicit that Dynamic Buffer Management can lag a sudden demand change. Short, large spikes may require planned buffer adjustments or a crude forecast.

• The accounting frame will argue against the operating frame. Frequent replenishment, smaller shipments, and non-local stock protection can look worse under cost-world measures even when the T-I-OE effect is better.

• The chain needs shared visibility. If downstream locations hide consumption, in-transit stock, or buffer status, the upstream link cannot distinguish a real shortage from a local ordering habit.

The pattern is not a promise that inventory disappears. It is a claim about where inventory earns its keep. Inventory held at the aggregation point protects many downstream locations at once; inventory pushed into every location protects each local manager from blame while raising total system exposure. Replenishment Pull makes that distinction operational.

Corrupted by: Cost-World Thinking — Cost-world thinking resists frequent small replenishments, central stock buffers, and visible non-constraint slack because each looks wasteful under local cost measures.

Depends on: Buffer Aggregation in Distribution — Buffer aggregation supplies the statistical reason a central stock buffer can protect many consumption points with less total inventory than local safety stocks can.

Depends on: Throughput Accounting — The pattern is defended in T, I, and OE terms: availability protects throughput, while aggregation and frequent replenishment cut inventory.

Enables: Supply-Chain Collaboration — Cross-company collaboration extends replenishment pull across organizational boundaries by sharing buffer status and replenishment priorities.

Enforces: Subordination — Every link in the chain subordinates to the consumption signal and the central buffer status rather than pushing inventory downstream to protect local measures.

Implements: Make-to-Stock vs. Make-to-Availability (MTS vs. MTA) — Make-to-Availability is the operating policy that turns replenishment pull into a market commitment: reliable availability at chosen stock points with minimum inventory.

Prevents: Local Optimization — The pattern prevents each location from optimizing its own stock level at the expense of total chain availability, inventory, and flow.

Supported by: Procter & Gamble Distribution — The Procter & Gamble distribution case is the field's scale example for applying TOC replenishment principles to consumer-goods distribution.

Uses: Buffer Management — Replenishment pull uses buffer status, buffer penetration, and dynamic buffer management to decide what to order, what to expedite, and when to resize a stock buffer.

Sources

• Cox, TOCICO Dictionary (2nd ed., 2012), entries “distribution/replenishment solution,” “make-to-availability,” “buffer target,” “buffer status,” “buffer penetration,” “aggregation of variability,” “replenishment lead time,” and “stock buffer” — the certification-grade definitions this entry cross-checks against. The Dictionary is distributed through TOCICO membership and does not carry an Open Library record.

• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 11 (Schragenheim, “Supply Chain Management”) — the canonical six-step treatment of the TOC distribution/replenishment solution: aggregate at the plant or central warehouse, size stock buffers, increase replenishment frequency, manage by buffer penetration, use Dynamic Buffer Management, and set manufacturing priorities from plant-warehouse buffer urgency.

• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 10 (Schragenheim, “Managing Make-to-Stock and the Concept of Make-to-Availability”) — the production-side companion that explains why make-to-availability changes both planning and execution rules, and why buffer status rather than due date sets priority for stock replenishment orders.

• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 12 (Smith and Ptak, “Integrated Supply Chain”) — the actively synchronized replenishment treatment that bridges TOC replenishment with complex MRP-dependent material environments and explains strategic inventory positioning, dynamic buffers, and visible execution priority.

• Schragenheim, Dettmer, and Patterson, Supply Chain Management at Warp Speed (2009) — implementation-grade treatment of TOC replenishment in supply chains; the companion source cited by the Handbook chapters for distribution, make-to-availability, and S-DBR at the supply-chain boundary.

• Goldratt, Isn’t It Obvious? (2009) — the popular business-novel exposition of TOC distribution and retail replenishment, useful for seeing how the buffer-status and availability logic is taught outside the Handbook’s formal chapter structure.