Decision situation

When the shelf is crowded, every SKU needs a reason to stay.

When a range is under pressure, the lowest-volume SKU is only one suspect. Some small items protect a role; some large ones quietly add complexity.

Fictional FMCG shelf range under portfolio rationalisation pressure
When this is for you

Build a decision rule before arguing SKU by SKU.

First define the jobs the range must do: recruit buyers, defend the price ladder, protect premium trade-up, serve key occasions, or meet retailer needs. Then individual SKUs can be judged against those jobs.

The goal is to decide which items deserve defence, which need a different job, and which can be removed without creating a bigger problem.

Use this when

  • The long tail is absorbing margin, attention, or shelf space.
  • The retailer is asking for rationalisation.
  • Teams disagree on which SKUs are strategic.
  • You need a defend, fix, simplify, or cut view that can survive scrutiny.
Where the risk sits

The dangerous shortcut is a sales ranking.

A ranking tells you what is big and small. It does not show cannibalisation, strategic role, or what disappears from the range when an item goes.

Performance is read too narrowly

Volume alone can hide margin, cannibalisation, shopper role, retailer dependency, and price-ladder contribution.

Internal politics protects clutter

Every SKU has a history and usually an owner. The decision needs a market view strong enough to get past attachment.

The retailer frames the cut

If the brand cannot explain which SKUs earn their space, the retailer will bring its own logic. That logic may not protect your strongest future role.

Evidence worth checking

  • SKU role beyond volume: reach, incrementality, loyalty, margin, and trade-up.
  • Where variants overlap, substitute, or serve distinct buyer needs.
  • Which items are retailer-critical versus internally protected.
  • Which SKUs support the price ladder, shelf block, or usage architecture.

What you should decide

  • Which SKUs deserve active defence.
  • Which SKUs need a different role, price, pack, or channel logic.
  • Which SKUs can be cut with limited damage.
  • Which cuts would create a bigger commercial problem than they solve.
Output example

Recommendation: remove the duplicated mid-tier variant, not the smaller niche SKU. The mid-tier item adds volume but mostly steals from the core. The niche SKU is smaller, but it protects a distinct usage occasion and gives the retailer a reason to keep the premium block intact.

This can start with Markt.Scan when the pressure needs diagnosis, or move into Markt.Lever when the question is where the range should be adjusted first.

Book a free briefing See other decision situations