Bottom-Up vs Top-Down Forecasting: Which to Use

The bottom-up vs top-down forecasting debate usually gets framed as a religious war, and it shouldn't be. They're two ways of cutting the same cake, each with a failure mode, and the right answer for most $100M–$1B manufacturers is to use both and reconcile. I learned this the hard way at a $250M manufacturer where finance forecasted top-down by revenue and demand planning forecasted bottom-up by SKU. The two numbers were 9% apart, every quarter, and nobody owned closing the gap. Production planned to one, finance reported the other, and the obsolete reserve ate the difference.

Here's how each method actually works, where each one breaks, and how to combine them so you stop planning against two truths.

What Each Method Actually Does

Bottom-up forecasting builds the total from the bottom: forecast every SKU at every location, then sum up. It's granular, it's what operations needs to plan production and replenishment, and it's how demand planners naturally think.

Top-down forecasting starts with the aggregate — total company revenue, or a product family's annual target — then allocates down to SKUs using historical mix. It's how finance and the board think, and it's fast.

The core trade-off is this: bottom-up is accurate where it matters (the SKU you actually ship) but noisy in aggregate, because thousands of small errors accumulate and the long tail is mostly guesswork. Top-down is stable in aggregate but blind at the SKU level — it'll tell you the family will do $4M and have no idea which of the 60 SKUs in it customers actually want.

Where Bottom-Up Wins

• Replenishment and production. You can't build "the family." You build a specific SKU at a specific plant. Bottom-up is the only forecast operations can execute against.
• High-volume, low-variability A items. When a SKU has clean, stable history, its individual forecast is reliable and worth doing precisely.
• Capturing real SKU-level signal. A promo on one SKU, a new customer for another — bottom-up captures it where top-down smears it across the whole family.

Where bottom-up breaks

The long tail. If 70% of your SKUs are low-volume, high-variability C items, their individual forecasts are barely better than noise, and summing 3,000 noisy guesses gives you a shaky total. Bottom-up also drifts in aggregate — each planner's small optimism compounds into a company number that's systematically high.

Where Top-Down Wins

• Aggregate accuracy. It's a statistical fact that forecasting at a higher level of aggregation is more accurate in percentage terms — errors cancel out. Your total-company forecast from the top is usually tighter than the sum of SKU forecasts.
• Speed and the financial plan. Finance can set a defensible revenue number in an afternoon. The board cares about the family and the quarter, not SKU 40231.
• Imposing a reality check. When sales' bottom-up forecast sums to 30% growth and the market is growing 4%, top-down is the gut check that says "prove it."

Where top-down breaks

Mix. Top-down allocates by historical share, so it assumes next quarter's mix looks like last year's. The moment a SKU is launching, dying, or shifting, the allocation is wrong at exactly the SKUs where being wrong is expensive. Top-down will keep replenishing a dying SKU because its historical share says to.

Side-by-Side

The Answer: Middle-Out Reconciliation

The method that actually wins isn't picking one. It's middle-out — forecast at the level where the signal is strongest (usually product family or product-line), then disaggregate down to SKU for execution and aggregate up to total for the financial plan. You reconcile in both directions.

Here's the workflow that fixed our 9% gap:

1. Forecast at the family level statistically — this is where you get the best accuracy-to-effort ratio.
2. Disaggregate to SKU using a mix model, not flat historical share — bias the mix toward what's growing and away from what's dying.
3. Let planners override at the SKU level for known events (promos, launches, lost accounts), then re-aggregate.
4. Reconcile the bottom-up sum against the top-down total. When they diverge more than a tolerance — we used 5% — that's a meeting, not a rounding error. The gap is information.
5. Lock one number that feeds both production and the financial plan.

The reconciliation step is the whole point. A divergence between bottom-up and top-down isn't a problem to average away — it's the early-warning system. When sales' bottom-up was 9% above finance's top-down, one of them was wrong, and finding out which prevented either a stockout or a warehouse full of dead stock.

Tooling Makes or Breaks This

Middle-out is painful in spreadsheets. You're disaggregating, overriding, re-aggregating, and reconciling across thousands of SKUs every cycle, and the moment finance and demand planning work in separate files you're back to two truths. This is exactly what an integrated planning platform like Pigment is for — one model where the family-level forecast, the SKU disaggregation, and the financial roll-up are the same object, so reconciliation is automatic instead of a quarterly fight. When demand and finance plan against one live model, the 9% gap doesn't get a chance to form.

Stop Planning Against Two Numbers

If your bottom-up SKU forecast and your top-down financial plan don't tie out, you already have stranded inventory or stockouts hiding in the gap — you just haven't measured it. We'll run a free planning-maturity and stranded-inventory teardown to find where the two numbers diverge and what it's costing you in trapped cash. Book a call and we'll reconcile your forecast together.