The SKU Rationalization Framework That Survives Q2
Every FMCG operator has sat in this meeting. Once a year, a conference room fills up with brand managers, a finance lead, and someone from supply. A spreadsheet appears. Each brand manager defends their SKUs in turn.
11 min read · 1 April 2026

The SKU Rationalization Framework That Survives Q2
The Annual Review Lie: Why Brand Managers Always Win
Every FMCG operator has sat in this meeting. Once a year, a conference room fills up with brand managers, a finance lead, and someone from supply. A spreadsheet appears. Each brand manager defends their SKUs in turn. Numbers get debated, feelings get bruised, and at the end of the afternoon, perhaps two or three obvious losers go on a watchlist. Almost nothing dies.
This is the standard SKU rationalization framework most $1M-$10M brands inherit, and it is engineered to fail.
Look at what scale players actually do when they get serious. P&G consolidated around 100 brands over two years to focus on its top 80-90 product lines. Those discarded brands were contributing only about 6% of total profit. Read that again. A Fortune 50 company found that a meaningful slice of its portfolio could be deleted with almost zero profit impact.
Now ask yourself how many SKUs you would cut if you ran the same exercise this Friday.
The annual review meeting fails for one structural reason. It lets each brand manager defend their items in isolation, with no shared overhead loaded against the SKU under review. Trade spend stays in the marketing P&L. Slotting fees stay buried in retail accruals. The 3PL pick rate, the spoilage on slow movers, the warehouse cube cost; none of it sits next to the SKU being argued for. So every defence sounds reasonable, because the true cost of keeping the item is hidden across four other ledgers.
A practitioner explainer from Cin7 puts the hidden cost figure at 15-40% additional cost for low-demand SKUs, once cost-to-serve is fully loaded. That number does not appear in any single brand manager's spreadsheet. So the meeting concludes that everything is roughly profitable. The tail survives.
The real damage is what happens next. Forecast accuracy degrades because demand planners are modelling thousands of low-velocity items with noisy data. Trade promotion budgets get spread thinly across SKUs that generate no incremental volume. Sales reps spend retail conversations defending facings for items that move four units a week. And the brand manager who keeps her tail SKUs alive is not punished, because she has hit her gross revenue target.
This is what Bain calls the complexity penalty, and the firm makes a point most operators miss. Value-category SKUs are pure cost; only premium-category SKUs are allowed to fund choice. Most $1M-$10M FMCG brands have the proportions inverted.
The SKU Pruning Blueprint: A Four-Axis Cull Scorecard
The SKU Pruning Blueprint replaces the annual defence meeting with a quarterly cross-functional cadence, a four-axis scorecard, and a single named owner with kill authority. I have run a version of this with Australian FMCG operators whose tail was visibly eating warehouse cube and contribution margin. Two cycles in, the bottom-quartile SKUs were gone, forecast error had fallen by double digits, and trade spend had been reconcentrated on the items that actually compounded.
The Blueprint has three components, and they only work together.
The first component is the four-axis scorecard. Every SKU is rated on contribution margin per unit, velocity (units per outlet per week), strategic role (gateway, halo, profit, or hygiene), and fully-loaded cost-to-serve. Cost-to-serve is the axis that breaks the old meeting. It loads trade spend, slotting fees, 3PL pick rate, spoilage, returns, and retailer-specific compliance costs back onto the SKU that incurred them. Most ERP systems will not produce this number out of the box. You build it once, in a spreadsheet, with help from finance.
The second component is the single cross-functional owner. One person, named, with kill authority. Not a committee. Not "the leadership team." Not a vote. Specright's frame on cross-functional ownership puts this bluntly: rationalization stalls every time the decision is distributed, because every stakeholder has a reason to delay. The owner is usually the COO, the head of supply chain, or a dedicated portfolio director. They are not the brand manager whose items are on the table.
The third component is the quarterly cadence, replacing the annual meeting. Quarterly is the right interval because trade promotion calendars and retailer buying cycles run on quarters, not years. Run the cull less often than that and stale data corrupts the decision. Run it more often than that and the supply chain cannot react.
Tellius makes the case for why a flat Pareto chart misses the real story: cross-SKU substitution and shelf cost. The four-axis scorecard handles both. Strategic role flags substitution effects (a hygiene SKU defends a category position even at low margin), and cost-to-serve absorbs shelf cost into the per-unit math.
This is not pack-price-architecture work. The Blueprint deals with item-level deletion and variant consolidation, full stop. If the question is "should this SKU exist?" you are in scope. If the question is "should this 250g version become a 200g version at a different price point?" that is a different project.
Phase 1: The Cross-Functional Cadence and Data Spine (Days 0-30)
Phase 1 is unglamorous. You are not killing anything yet. You are building the data spine that makes every future cull defensible.
Start by naming the owner. This needs to happen in a conversation with the founder or CEO, because the role carries authority over brand managers. The owner role has a job description: chair the quarterly meeting, own the four-axis scorecard, and have a final vote on every kill, keep, or re-engineer decision. I have watched founders try to skip this step and run rationalization "as a team." It does not work. Six months later the same SKUs are still on the watchlist.
Next, build the data spine. The minimum viable scorecard pulls four data sources:
- Sales and margin data from your ERP or Shopify, by SKU, last 13 weeks rolling
- Trade spend from finance, allocated to SKU level (this is usually the hardest pull)
- 3PL pick rate and storage by SKU, expressed as cents per unit shipped
- Returns and spoilage by SKU, as a percentage of units shipped
For most $1M-$10M operators, the trade spend allocation is where Phase 1 stalls. Finance has it as a lump sum. Marketing has it spread across campaigns. Neither view sits at SKU level. The fix is pragmatic. Pick a 90-day window, take the largest five trade promotion line items, and allocate them by units sold of the promoted SKUs over that window. It will not be perfect. It will be 80% directionally correct, which is enough to cull the obvious losers in Phase 2.
While you are building the spine, draft the meeting cadence. The first meeting is held at Day 30. Every brand manager presents their portfolio against the four-axis scorecard, not against gross revenue. The owner sets the rule: any SKU that scores in the bottom quartile on three of the four axes goes onto the kill list automatically, with no defence permitted unless a documented strategic role applies.
Bring sales, marketing, ops, and finance into the cadence by Day 14, before the first scorecard is finished. Each function provides one input. Sales provides retailer feedback on SKU strategic role. Marketing flags any SKU with active brand-building investment. Operations flags SKUs with supplier contract minimums. Finance flags any SKU with deferred costs that need to be amortised before deletion.
By Day 30, you should have one named owner, one populated scorecard, four functional inputs documented, and the first meeting on the calendar. You have not killed a single SKU yet. That comes next.
A note on the data spine for operators with no formal cost-to-serve model. You do not need a six-figure consulting engagement to get this right. A spreadsheet with five tabs (sales, trade spend, 3PL, returns, scorecard) and a junior finance analyst running the numbers for two weeks gets you to a defensible v1. The accuracy gain over the year-one baseline is easily 40 percentage points, which is more than enough to anchor the first cycle's kill decisions. You can refine the cost-to-serve methodology in cycle three, once the obvious tail is gone and the marginal calls need tighter inputs.
Phase 2: The Kill, Keep, or Re-Engineer Meeting (Days 31-60)
This is the meeting that breaks the old habit. Every SKU gets one of three verdicts: kill, keep, or re-engineer.
Kill means the SKU is discontinued at the next natural break, typically the end of the current trade cycle or when existing stock runs out. The brand manager loses defence rights. The supply team builds the run-out plan. Sales communicates to retailers using a script that the owner has approved.
Keep means the SKU stays, but with conditions. The condition is usually a measurable performance threshold over the next 90 days. If velocity does not improve, contribution margin does not lift, or strategic role does not justify the cost-to-serve, the SKU automatically moves to kill at the next quarterly meeting. No re-debate.
Re-engineer means the SKU has commercial logic but the cost structure is broken. This category usually accounts for 10-15% of the portfolio. Re-engineering means changing pack format, consolidating variants, switching to a lower-cost manufacturer, renegotiating slotting, or moving the SKU from retail to a DTC-only channel. It is a different project, not a deferral. The owner assigns a 60-day deadline and a measurable target.
The HBR canonical case on Clorox is the playbook here. The Clorox SKU cuts study describes a formal kill process that boosted both margin and sales, against the intuition that cutting SKUs would hurt revenue. The mechanism is consolidation. When a slow-moving SKU gets killed, customers who bought it most often migrate to a faster-moving variant in the same brand. The brand keeps the revenue and sheds the cost.
Three rules make the meeting work.
First, the four-axis scorecard is binding. If a SKU sits in the bottom quartile on three axes, the default verdict is kill. The brand manager can argue for a re-engineer verdict, but they cannot argue for keep without documented strategic role.
Second, the owner has the final vote. Brand managers can disagree, but the kill list does not require consensus. This is the same principle that EisnerAmper's mid-market CPG guidance emphasises. Rationalization decisions stall when they require unanimity. Authority must sit with one role.
Third, every kill verdict has a documented rationale tied to the scorecard. If a SKU gets killed, the rationale lives in the meeting minutes, with the four-axis scores attached. This matters for Phase 3, when retailers ask why specific SKUs are being delisted. You need a defensible written record.
Most first cycles produce a kill list of 20-30% of SKUs. That sounds aggressive. It is consistent with what Circana describes in its growing-brands rationalization playbook on protecting margins by cutting tail-SKU drag. The brands that protect margin are the ones that cut hard once, not the ones that cut a few SKUs every year forever.
Phase 3: Institutionalising the Quarterly Cycle (Quarter 2 and Beyond)
Phase 3 is where most SKU rationalization frameworks die. The first cycle works because everyone is energised and the data is fresh. The second cycle is harder because the obvious tail is gone and the marginal calls are tighter. The third cycle is hardest because brand managers have learned the scorecard and are now positioning their SKUs to look better on the four axes.
This is fine, as long as the cadence holds.
The quarterly cycle has a fixed rhythm. Week 1 of the quarter, the owner refreshes the scorecard with the previous quarter's data. Week 2, brand managers review their portfolios and flag any SKU launches or retirements that have already occurred. Week 3, the owner consolidates the scorecard and circulates the watchlist. Week 4, the meeting runs. Then the run-out plans, retailer comms, and re-engineer projects kick off in the following quarter, while the cycle starts again.
The trade press case on P&G's collaborative commerce strategy is instructive on the cadence question. P&G runs continuous SKU trimming, not as an annual event but as a routine cross-functional decision. The trimming logic is tied to retail partner planning cycles. Smaller operators do not need P&G's scale, but they need the same rhythm.
Two anti-patterns kill Phase 3.
The first is letting brand managers re-pitch killed SKUs in subsequent quarters. The owner must hold the line. A killed SKU can return only as a re-engineered new SKU, with a different code, a documented commercial case, and a 90-day proof window. Re-pitches without re-engineering get rejected at the door.
The second anti-pattern is letting cost-to-serve drift out of the scorecard. As the tail gets cut, trade spend, slotting, and 3PL costs concentrate on the surviving SKUs. The cost-to-serve numbers shift. If the scorecard is not refreshed, the marginal SKUs from cycle one start looking like the kill candidates of cycle three. That is the system working as designed; embrace it.
By the end of cycle two (typically month 6), well-run brands see two outcomes that justify the whole exercise. Tail SKUs are down 25-40%, freeing working capital and shelf attention. And forecast accuracy improves by 10-15 percentage points, because the demand planning team is no longer modelling thousands of low-velocity items with noisy data.
The forecast accuracy gain is the one most operators do not anticipate. It pays back the entire rationalization project on its own.
The New North Star: Forecast Accuracy as the Rationalization Scorecard
Most FMCG operators measure SKU rationalization success by the count of SKUs cut. That is a vanity metric. It tells you nothing about whether the cuts were good cuts.
The right north star is forecast accuracy at the portfolio level, measured as MAPE (mean absolute percentage error). When you cull a low-velocity SKU, you remove a noisy signal from the demand plan. When you keep a SKU that should have died, you keep that noise. So MAPE moves directly with the quality of the rationalization decisions.
Track it monthly. Compare quarter over quarter. Tie the owner's accountability to MAPE improvement, not to SKU count. This single change is what separates brands that run two good cycles and stop, from brands that run the cull as a permanent operating discipline.
There is a second-order benefit most operators miss. As MAPE improves, safety stock requirements drop, working capital tied up in slow-moving inventory shrinks, and the supply team gets faster at flagging real demand shifts versus modelling noise. A 10-point MAPE improvement on a $5M FMCG portfolio typically frees six-figure working capital inside two cycles. That released cash funds the launches that compound, which feeds the next round of contribution margin growth. The cull is not a one-time cleanup. It is a flywheel that pays back every quarter, but only if the cadence holds and the owner has authority.
The before-state is familiar. Annual reviews, defended SKUs, gross-revenue dashboards, and a tail that quietly eats margin while everyone agrees the portfolio is healthy. The after-state is uncomfortable for brand managers in cycle one, freeing in cycle two, and routine by cycle three. The same conference room that used to host the defence meeting now hosts a quarterly cull decision that takes 90 minutes and produces a kill list with documented rationales.
Two cycles in, you will have cut 25-40% of your SKUs, lifted forecast accuracy by 10-15 points, and freed enough working capital to fund the launches that actually compound. That is what The SKU Pruning Blueprint is built to deliver.
The annual review meeting is not a SKU rationalization framework. It is a ritual that protects the tail. Replace it.
Unit Economics Calculator
Contribution margin per order after COGS, shipping and fees — the number scaling actually depends on.
Product Portfolio Optimisation for FMCG Margin Recovery
Line Extension Strategies That Don't Destroy Parent Margin
Demand Forecasting for FMCG That Beats the 60% Wall
Fixing the New Product Introduction Process for FMCG Brands
Rolling Forecast Implementation: Retire the Zombie Budget
The Budget vs Actual Analysis Framework Operators Need
Newsletter
The Uncommon Insights Letter
Practical FMCG & eCommerce growth playbooks — margins, retention and scaling tactics, straight to your inbox.
Turn fmcg strategy into profit you can see
Get a hands-on operator to turn the frameworks above into results — book a free audit call.