Procter & Gamble Distribution §

Case: A specific real-world TOC implementation that practitioners across the field repeatedly cite.

Procter & Gamble’s field-cited distribution work, best read as a consumer-goods scale case for TOC replenishment, aggregated stock buffers, frequent replacement from consumption, and the source discipline needed when VMI and TOC claims are repeated together.

P&G matters because consumer-goods distribution makes the inventory-availability conflict visible. A store can carry too much stock overall and still miss the item the customer came to buy. TOC practitioners cite Procter & Gamble because the company sits at the right scale for that question: many products, many consumption points, large retailers, and enough operational sophistication that “try harder at forecasting” can’t be the whole answer.

Context §

In supply-chain practice, the P&G story sits beside Replenishment Pull, Buffer Aggregation in Distribution, Make-to-Stock vs. Make-to-Availability, and Supply-Chain Collaboration. It tests whether the mechanism survives when production, central warehousing, retailers, transportation, promotions, and category management all press on the same flow.

The operating problem is familiar. Retailers want high shelf availability and low inventory. Manufacturers want stable production, low expediting, and reliable replenishment. The traditional answer pushes stock downstream from forecasts, lot-size economics, trade promotions, and local service-level targets. The TOC answer changes the protection point and the signal: hold most protection where demand variation is lower, replenish downstream stock from actual consumption, read buffer status frequently, and use that signal to decide what to order, ship, expedite, and resize.

Procter & Gamble is often discussed near Vendor-Managed Inventory (VMI), but that proximity can obscure the TOC lesson. VMI by itself means the supplier has access to the customer’s inventory data and is responsible for maintaining the customer’s required inventory level. TOC replenishment asks a sharper question: does actual consumption and buffer status drive the replenishment action, or has the forecast merely moved from the retailer to the supplier?

The evidence boundary is part of the case. In this cycle’s local source pass, the canonical TOC library supplied strong sources for the distribution mechanism and for VMI’s boundary, but it did not supply a detailed primary P&G rollout record with baseline inventory, availability, locations, dates, and sustained after-state. A careful reader should treat P&G as a field-cited scale case and keep hard company-specific outcome claims out unless the cited source supplies them.

What Was Tried §

The defensible TOC reading of the P&G case has four moves.

Move protection upstream. The TOC distribution/replenishment solution keeps larger stock buffers at the plant warehouse or central warehouse, where demand from many downstream points is pooled. Smaller downstream buffers protect local availability, but they don’t carry every location’s full uncertainty. Schragenheim gives the statistical reason: demand variation is lower at the aggregation point than at each retail point taken alone.

Replenish from consumption. A sale or withdrawal at the downstream point creates the replenishment need. The quantity is not “what the forecast says next week might need.” It is the buffer target minus on-hand stock and open supply, adjusted when Dynamic Buffer Management shows that the buffer is too large, too small, or temporarily distorted by a supply or demand event.

Increase replenishment frequency. The case is usually cited for frequent small replenishments rather than large forecast-driven pushes. Under a cost-world reading, smaller and more frequent shipments can look worse because each shipment carries visible handling and transportation cost. Under a throughput-world reading, the comparison includes protected sales, lower total inventory, fewer obsolete items, and less cross-shipping or expediting.

Share the operating signal. A consumer-products replenishment system cannot work from a private signal at one node. Retailer consumption, stock already in transit, central-warehouse status, production availability, and promotion timing all affect the buffer. The collaboration pattern is a shared priority language: green, yellow, red, and black buffer readings tell each party which SKU-location flow deserves attention now.

What Worked §

The case works first as a scale answer. Many supply-chain readers accept replenishment pull in a small demonstration but distrust it in a real consumer-goods network. P&G is the field’s shorthand for the larger claim: the logic is not confined to a classroom distribution game or to a single manufacturer-owned warehouse.

The second useful feature is the VMI distinction. VMI can be a win-lose arrangement in which a large customer shifts inventory responsibility to a supplier without changing the underlying forecast-push logic. Schragenheim’s Make-to-Availability treatment is explicit on this point. TOC replenishment becomes interesting when the supplier and customer use consumption data to replenish and manage the buffer, not when the supplier simply holds forecast stock on behalf of the customer.

The third lesson is the inventory-availability contradiction. Conventional distribution treats the pair as a tradeoff: more inventory buys more availability; less inventory lowers cost but creates stockouts. TOC’s claim is different. If protection is aggregated at the right point and replenishment time is short enough, total inventory can fall while local availability improves.

The fourth contribution is measurement. The decision cannot be defended by local freight cost, local inventory dollars, or a retailer’s local service-level number alone. The P&G story is a Cost-World vs. Throughput-World Thinking test because the recommendation often looks wrong until it is read in T, I, and OE terms.

What Did Not §

The public TOC source trail does not expose enough P&G-specific detail for a certification-grade reader to quote hard results responsibly from the present source set alone. The available local sources support the mechanism and the VMI boundary. They don’t establish, in this pass, which P&G product families, retailers, regions, dates, stock reductions, shelf-availability shifts, or sustainment results should be treated as verified.

The case can also be overread as “P&G invented VMI.” It didn’t. VMI is broader than TOC and often operates in ways TOC practitioners criticize. The Handbook’s VMI discussion says the supplier may hold inventory for a client under an arrangement that still depends on forecast and customer orders. The TOC version is narrower: the customer passes daily consumption data, replenishment follows actual use, and the buffer status decides priority.

The third weakness is transfer. A giant consumer-products company can negotiate data sharing, replenishment cadence, packaging changes, freight practices, and retail relationships that a smaller supplier can’t. The transferable lesson is the operating logic: place protection where variation is lower, replenish what was consumed, make buffer status visible, and judge the change by the system-level T-I-OE effect.

What Practitioners Draw From It §

For Replenishment Pull, P&G is the “has this been tried at scale?” example. The useful answer is careful: practitioners cite it as a scale case for TOC distribution, but the claim should stay tied to replenishment mechanics rather than vague supply-chain excellence.

For Buffer Aggregation in Distribution, the case turns a statistical claim into an operating claim. Aggregation changes where stock sits, how replenishment is triggered, and which local manager loses the right to protect their location by hoarding inventory.

For Make-to-Stock vs. Make-to-Availability, P&G is a boundary case. The customer-facing promise depends on availability, but the promise fails if it is implemented as ordinary VMI with the same forecast-push assumptions. The distinction between “supplier-managed forecast stock” and “consumption-driven buffer replenishment” is the point.

For Supply-Chain Collaboration, the case shows why collaboration needs an operating signal. Retailer data, manufacturer production, in-transit stock, and central buffer status have to mean something actionable. Without buffer status, shared data is a larger report, not a better priority system.

For Local Optimization, P&G is the warning. Every link can defend its local behavior: full trucks, local stock cushions, stable production batches, retailer shelf coverage. TOC asks whether those choices improve the chain’s availability, inventory, and flow together. If they don’t, the local optimum is the problem.

Disputed Lessons §

How much of the public P&G story is TOC, and how much is broader VMI or supply-chain management? The terms are often repeated together. That does not make them identical. A reader should ask which signal governed replenishment: actual consumption and buffer status, or supplier-held forecast inventory.

Which outcomes are safe to quote? The TOC distribution literature reports strong average effects for distribution/replenishment implementations: higher sales, lower inventory investment, and higher turns. Those are mechanism-level or consultant-experience claims. They should not be silently converted into P&G-specific numbers unless a P&G-specific source supplies them.

What survived after rollout? A distribution redesign can work during a pilot and then erode when local measures, promotions, retailer pressure, or freight economics pull the system back toward push behavior. The P&G case needs sustainment evidence before it can carry a durability claim comparable to cases with clearer published after-state records.

Was the constraint the retailer, the consumer, the supplier, cash, shelf space, or data latency? Consumer-goods distribution can bind at different points. The TOC Dictionary’s distribution core conflict treats the client as the constraint in the distribution environment. A P&G-specific analysis still has to identify the operative constraint for the product family and relationship in question.

Related Articles §

Sources §