Why material still gets written off despite mature CPFR programs

Collaborative Planning, Forecasting and Replenishment was built to make sure you never run out. It was never designed to make sure you never end up with too much. For Life Sciences and perishable-goods companies, the second problem is where the money is leaking.

In a rush? Here are the 3 key takeaways

👉 CPFR was designed to solve one half of the material equation making sure you never run out. The other half, too much of the wrong kind, was never in scope. That's where pharma and perishables companies are losing money.

👉 CPFR is stockout-first by design. The metrics reward fill rate, the scope ends at trading partners, and the assumptions are shelf-stable none of which hold for batch-locked, expiry-bound materials in Life Sciences.

👉The fix isn't a replacement. A second layer material risk orchestration extends CPFR's collaborative spirit to the post-replenishment world. CPFR-mature companies are best positioned to adopt it.

If your company has a mature CPFR program, you already know what it's good for. In-stock rates are higher. Stockouts are rarer. Forecasts between you and your trading partners actually line up. The 9-step process agreement, joint plan, sales forecast, exception resolution, order forecast, order generation has done what it was designed to do since Walmart and Warner-Lambert piloted it in 1995. The Listerine case is the textbook one: in-stock moved from 87% to 98%. The methodology works.

And yet, almost every Life Sciences and perishable-goods company we talk to with a serious CPFR program is also sitting on growing write-offs.

How does both happen at the same time?

Because CPFR was designed to solve one half of the material equation. The other half was never in scope.

Two halves, one balance sheet

There are really only two ways material hurts a company. You don't have enough of it, or you have too much of the wrong kind. The problem is that most organizations lack a systematic process for managing material risk once inventory enters the supply chain : I would move that near the top.

CPFR is, structurally, a stockout-prevention discipline. Every step in the 9-step process is oriented toward making sure the right product is on the shelf at the right time. Exception management in CPFR means "the forecast looks wrong, let's align." It does not mean "this batch is going to expire in six weeks, who owns the disposition, what's the chargeback path, and how do we reconcile the reserve."

Those questions live in a different operating model entirely and CPFR doesn't pretend otherwise. The original methodology ends at generate the orders. What happens to material after it lands, ages, gets stranded, or becomes obsolete is somebody else's chapter.

For shelf-stable retail goods, that gap is manageable. For pharma, CDMOs, and perishable goods, it's where the P&L damage actually concentrates.

Three things CPFR was never built to fix

It's worth being specific about where the gap lives, because "CPFR isn't enough" by itself is too vague to act on.

1. Stockout-first optimization. Every metric CPFR rewards fill rate, in-stock %, forecast accuracy points in one direction. None of them measure excess, expiry exposure, or recovery cycle time. A CPFR program can score green on every dashboard while material in the warehouse quietly ages past usable shelf life. The system isn't blind by accident. It's blind by design.

2. Two-party scope. CPFR coordinates between a retailer and a supplier, or a manufacturer and its trading partners. It does not coordinate between planning, procurement, quality, manufacturing, and finance inside your own four walls. When a deviation appears, the question of which internal function owns the disposition — and how the decision gets routed, documented, and reconciled sits entirely outside the methodology. In a pharma site or a CDMO, that internal fragmentation is exactly where weeks of cycle time get lost.

3. Shelf-stable assumptions. CPFR was built on retail. It assumes that if demand drops, you can mark down, redirect, or hold. In Life Sciences and perishables, that assumption breaks. You can't redirect API that's batch-locked to a customer program. You can't hold expiring vaccine adjuvant indefinitely. You can't mark down a controlled substance. Every disposition path is bounded by regulation, contract, and time. CPFR's exception-management toolkit doesn't have a place for any of that.

The second layer

What's needed isn't a replacement for CPFR. It's a complementary discipline that picks up where CPFR ends.

Call it material risk orchestration. Same collaborative spirit shared data, joint decisions, exception management but applied to the post-replenishment world. The moment a forecast shifts, a program scales down, a batch fails, a spec changes, or an expiry window closes in, the work starts on its own: affected materials identified, liability owner named, disposition options surfaced, the right internal stakeholders routed in, financial reserve updated when the decision closes.

This isn't a different philosophy than CPFR. It's the same philosophy extended to the part of the lifecycle CPFR's authors didn't get to. Where CPFR coordinated between two companies on what would be ordered, material risk orchestration coordinates between five internal functions on what to do with stock that's already in the system and no longer behaving the way the plan assumed.

For a CDMO managing customer-owned WIP across programs, this is the difference between absorbing silent liability and enforcing contract terms in the quarter the event occurred. For a pharma site managing expiry exposure across a portfolio, it's the difference between a quarter-end write-off surprise and a real-time view of recoverable working capital.

Why CPFR-mature companies are best positioned for this

There's a counterintuitive point worth ending on. The companies that should find this second layer easiest to adopt are the ones that already have CPFR running well.

They've already built the data discipline. They've already established cross-partner trust. They've already accepted that exception management is a continuous, collaborative process and not a quarterly fire drill. Adding a second orchestration layer one that handles the excess-and-obsolete side of the equation rather than the stockout side is an extension of muscle they've already built, not a culture change.

If your organization has mature forecasting, planning, and CPFR processes but still struggles with daily material chaos common versus customer-specific material, customer-owned versus company-owned materials, inventory reserves, aging stock, expiring lots, write-offs, and questions around who owns the risk and who should take action the problem may not be your planning process.

The problem is that most organizations lack a systematic process for managing material risk once material enters the supply chain.

Planning systems help determine what should happen. But when demand changes, customer programs are delayed, materials age, products expire, specifications change, or material becomes stranded, companies need a way to understand the impact, assign accountability, evaluate recovery options, and coordinate actions across functions.

That's the problem Traceflow was built to solve.

Traceflow helps manufacturers identify material risk, understand why material is at risk, determine the highest-value recovery path, and orchestrate the actions required to recover value before material becomes a write-off.

CPFR made sure you'd never run out.

The next problem is making sure you don't drown.