Why Hitting Your Revenue Target Can Hide a Serious Inventory Problem

A few years ago, a brand we know was doing everything right on paper.

Market leader in their category. Strong retail presence. A product that had been on shelves for years with loyal customers. Revenue tracking to plan.

And yet every single month, their operations team was missing the forecast by 10 to 20 percent. About three million dollars a month, consistently, for months.

Nobody could explain it. The revenue numbers looked fine. The brand was healthy. The promotions were running. So where was the miss coming from?

The answer was in a number nobody was watching.

What the price increase actually did

The year before the misses started, the brand had done two things. They reformulated the product — a cost-saving measure that changed the product in ways consumers could feel. And they took a price increase.

On the revenue plan, the price increase looked like growth. If you're selling a million units at ten dollars, you're doing ten million dollars. Raise the price to eleven dollars and — on paper — you're doing eleven million. Growth of ten percent. Progress.

What the revenue plan didn't ask was: will consumers keep buying at eleven dollars?

Some did. Some didn't. Some tried the reformulated product at the new price, noticed it felt different, and didn't come back. They posted about it. They told people. The signal was there in reviews, in social comments, in the quiet slowdown of repeat purchases. But none of that was in the revenue plan.

Here's what was happening in units: velocity was declining. Consumers were buying less frequently. Retailers were seeing slower movement at shelf. But because the price was higher, the dollar number wasn't falling as fast as the unit number. Revenue looked approximately fine. Units were not.

The team kept building the plan around the dollar target. The dollar target kept looking approximately okay. And the unit reality kept drifting further from it every month.

Why dollar planning hides this so effectively

The math is straightforward but the implication catches people off guard.

Take a price increase of 8 percent. If your volume stays exactly flat, revenue goes up 8 percent. Looks like growth.

Now say volume drops 5 percent because some consumers pushed back on the new price. Revenue goes up roughly 3 percent — still positive. Still looks fine. The P&L says the business is growing.

But you needed to manufacture, ship, and distribute 5 percent fewer units to satisfy that demand. If your inventory plan was built on the dollar forecast — which implied growth — you produced more than you needed. That excess sits in a warehouse, or worse, in a retailer's back room that they're now trying to clear before they reorder.

The price increase that looked like growth was actually masking a volume problem. And the longer you plan in dollars, the longer that problem runs undetected.

What it looked like from inside the business

The team wasn't ignoring the misses. They were responding to them — just in the wrong way.

Every month there was a new explanation. The promotion didn't drive the expected lift. The retailer was slow to reorder. The season was soft. Each explanation was plausible. Each one kept attention on the external environment rather than on the internal plan.

Nobody said: our forecast is built in dollars and our volume assumptions are wrong.

Because in dollars, the assumptions didn't look wrong. The dollar plan absorbed the price increase and reflected modest growth. It was only when someone finally asked how many cases they needed to ship — not how many dollars they needed to generate — that the real picture emerged.

The unit forecast, when they finally built one, showed something the dollar forecast had been hiding for months: volume was declining. Not collapsing, but declining. Steadily. In a direction that made the dollar plan increasingly unrealistic as each month passed.

The compound problem: assumptions stacked on assumptions

The other thing that made this hard to catch was how the forecast had been built in the first place.

It wasn't just the price increase. The team had layered in promotional lifts, seasonal assumptions, and retailer program estimates — all in dollars. Each assumption sounded reasonable on its own. Back to school would drive demand. A major retailer was running a feature. A holiday set was planned.

But some of those assumptions cancelled each other out in ways nobody tracked. Two retailers running promotions at the same time don't produce double the lift — the same consumers shop both stores. A seasonal spike that happened in dollars because of the price increase wasn't actually a spike in units at all.

When you build a forecast by adding dollar assumptions on top of dollar assumptions, each one adds confidence to the number without adding accuracy. The plan looks more certain with each layer. It isn't.

What the fix required

The team eventually did two things that broke the cycle.

First, they rebuilt the forecast in units. They stripped out every dollar assumption and started over with a simple question: how many cases do we actually expect to ship, by SKU, by month? They let the historical unit data generate the baseline. Then they added assumptions back — one at a time, in units, with a reason for each one.

The number was lower than the dollar plan had implied. Significantly lower. Leadership wasn't pleased. But it was real.

Second, they got retailer inventory data. Not their own shipments to retailers — what was sitting in retailer warehouses unsold. That data confirmed what the unit plan was suggesting: the channel was overstocked. Retailers weren't reordering because they were still working through what they had.

Once they had that picture, the path forward was clear. Stop shipping into an overstocked channel. Work with retailers on a plan to move through the existing inventory. Rebuild the demand plan from a real baseline rather than a dollar-inflated one.

It took a quarter to right-size. It would have taken less time if they'd caught it earlier — which they would have, if the plan had been in units from the start.

The question worth asking now

If your demand plan lives primarily in revenue, try this: take your forecasted revenue for next month and divide it by your average selling price.

That's your implied unit forecast.

Now compare it to what you actually shipped last month in units. And the month before.

If the implied units in your dollar plan are growing while your actual unit shipments are flat or declining — you're looking at the same gap. The dollar plan is telling you things are fine. The unit data is telling you something different.

One of them is right.

If you'd like help rebuilding your demand plan in units and understanding what your current dollar forecast might be hiding, we're happy to take a look.