Forecasting retail demand by product category and setting budget against it

The short answer

Demand gets forecast per category or collection from patterns already sitting in past launches, so the budget commitment happens before sell-through data exists rather than after. The split is built in Cassandra from the brand's own comparable prior launches and categories, not a number set by feel or a rule chosen once and never checked.

Applies to

EcommerceBrand
Retail demand forecasting by product categoryforecastactual, scoredPINNED BEFORE, SCORED AFTER
The prediction is pinned before the outcome is known, then scored against what actually happened.

Where this comes up

Committing category budget before any sell-through data exists

The business runs as a sequence of collection launches, media works mainly in the first window of each one, and budgets have been reduced enough that every allocation now matters. Spend commits per collection before any sell-through data exists, while the read that would say whether the last one worked arrives many months later, well after the next launch decision has been made. Every allocation becomes an irreversible bet, graded afterward against numbers nobody could see when the call was made.

A pre-launch read built from the brand's own history of prior collections and categories informs the bet before it is placed rather than judging it only after. The evidence moves to before the commitment, where it can still change the decision. The grading stops being on bets nobody had a way to inform.

Forecasting category demand by hand because no formal function does it

Every planning cycle someone asks what the demand looks like for each product category, and the answer comes from forecasting search volume by hand, because no function in the business actually does this formally. The category split that comes out of that process is treated as fixed once it is written down, even though it is movable and has no justified data behind it. Now external retail-media advertisers are asking the same question of those category splits, and intuition gets defended as if it were analysis to a second audience with its own money on the line.

A category demand forecast built from patterns in the business's own sales and media history replaces one assembled by hand under deadline. A split stands ready to defend as reasoned rather than felt. And one answer works for internal planning and external retail-media conversations alike.

What changes

Setting a category split by feel gives way to committing budget against a read the commercial team can see before the season locks.

What this does not do

This forecasts at category or collection level, not per SKU, and it is a strategic planning input rather than a live inventory or pricing tool. It needs enough history across comparable launches or categories to build a credible split; a genuinely new category with no comparable precedent gets a wider range rather than a confident number, and that range is the honest answer, not a gap to be hidden. It informs the commitment; the final call on how much to bet stays a commercial decision.

Who this is for

This matters most to retail and publishing brands whose year runs as a sequence of category or collection launches, where media budget commits before a single unit has sold. It is most relevant where the category split is produced by hand because no function formally owns demand forecasting, and where external retail-media advertisers are starting to ask about the same splits.

Questions

What is category demand forecasting?

Category demand forecasting is estimating how much revenue a product category or collection will generate before it launches, using patterns from comparable past launches rather than waiting for sell-through data. The output feeds a category-level budget split, made before spend commits rather than justified after the fact.

How does category demand forecasting work without sell-through data?

By comparing the new category or collection against past launches with similar characteristics, using the sales and media pattern those launches actually produced. The read draws on the business's own history, comparable past launches and categories in its own data, rather than on a number set by feel.

What is the difference between a category demand forecast and a category budget?

How much revenue a category is expected to generate, based on comparable history, is the forecast. How that expected revenue translates into a media spend split across categories is the budget, and the two are related but distinct decisions: a category can be forecast to perform well without automatically justifying a large budget increase.

Which brands need to forecast category demand before committing budget?

Retail and publishing brands whose business runs as a sequence of category or collection launches, where budget has to be committed before any sales data exists for that specific launch. It is most useful where enough comparable prior launches exist to build a credible pattern, rather than for a genuinely first-of-its-kind category.

When does this not apply?

When the category or collection is genuinely new with no comparable history to draw on, when the decision needed is at SKU or individual-product level rather than category level, or when the forecast is being used to set a live price rather than a media budget. In those cases the honest output is a wide range or a recommendation to wait.

The product behind it