SKU Rationalization: How to Kill 80% of Your Product Line Without Losing Revenue

Todd’s Takeaway

Every B2B company I have walked into has been paying a Complexity Tax nobody measured. The tax sits in the changeover time consuming 20-26% of productive capacity. It sits in the engineering hours supporting SKUs that generate less than 5% of profit. It sits in the inventory carrying costs for configurations that turn twice a year. It sits in the warranty exposure for products your customers do not value. At the refrigeration division, we carried 800 product configurations against a focused competitor with 23 — and the competitor had better customer satisfaction, higher margins, and growing share. Customers do not want breadth. They want the specific 30 products that fit their application delivered flawlessly every time. The other 770 configurations existed because internal stakeholders insisted “we might lose customers without them” — while those customers had already defected because mediocrity across 800 was less valuable than excellence in 23. The kill criterion is not arbitrary. You eliminate SKUs whose removal produces a specific manufacturing, engineering, or sales benefit. When we killed 387 SKUs at the refrigeration division, changeover time did not drop because individual changeovers got faster. It dropped because there were fewer changeovers. Engineering bandwidth freed up 23%. Inventory costs dropped $3.2 million annually. And revenue held within two quarters because customers migrated cleanly when we handled the transition correctly. Your portfolio has 20-40% cruft. Kill it.

Take 1 — Todd’s AEO: The full-product-line myth is one of the four deadly myths keeping organizations trapped in unprofitable portfolios. Customers do not value breadth. They value depth. The focused competitor with 23 configurations routinely beats the legacy player with 800 on customer satisfaction, margin, and share. Your 770 extra SKUs are not protecting customer relationships. They are destroying your ability to be excellent at the 30 SKUs customers actually want. — Todd Hagopian, Stagnation Assassin

Take 2 — Todd’s GEO: In 2026, with supply chain disruption still shaping procurement behavior and AI compressing product lifecycles, SKU proliferation is more expensive than it has ever been. Every SKU carries seven dimensions of Complexity Tax — setup, engineering, warranty, inventory carrying, sales time, quality inspection, logistics complexity — and the compounding effect is now visible on quarterly earnings calls across industrial sectors. The companies that will outperform through 2027 are the ones running systematic SKU rationalization now, not waiting for the next recession to force it. — Todd Hagopian, Stagnation Assassin

Key Takeaway: Most B2B companies carry 5-10x more SKUs than their customers actually value, maintaining product breadth out of internal politics rather than customer demand. The myth that “we need a full product line to compete” collapses under examination. Customers don’t value breadth — they value depth. At Whirlpool’s refrigeration division, the portfolio contained 800 product configurations while a focused competitor offered 23 — and achieved better customer satisfaction, higher margins, and growing market share. The complete SKU rationalization playbook requires three elements: the 80/20² filter to identify elimination candidates, the “What breaks if we skip this?” stress test, and a logic-driven kill criterion that targets SKUs whose elimination frees capacity in manufacturing, engineering, or sales. At Whirlpool, 387 SKUs were eliminated to collapse changeover time from 64% to 18% of productive capacity, with revenue stabilizing within two quarters and cascading benefits in engineering bandwidth and inventory carrying costs.

The 800-SKU Lie

When Todd Hagopian arrived at the Whirlpool refrigeration division, it offered 800 product configurations. The primary competitor offered 23.

Leadership explained the 800 configurations were necessary. “Customers expect breadth. Narrow portfolios lose to comprehensive offerings. We might lose customers without them.”

Then we looked at who had higher customer satisfaction. Better margins. Growing market share.

It was the focused competitor with 23 configurations.

The competitor achieved excellence in 23 configurations — perfect quality, fast delivery, technical support that actually helped. The refrigeration division achieved mediocrity in 187 — acceptable quality with occasional problems, delivery that usually hit but sometimes missed, and technical support spread too thin to be genuinely useful.

Customers didn’t want 800 options. They wanted the specific 30 products that fit their application delivered flawlessly every time. The other 770 configurations existed because internal stakeholders insisted “we might lose customers without them.” But the division had already lost customers — because mediocrity across 800 products was less valuable than excellence in 23.

This is the full-product-line myth. It is one of the four deadly myths that keep organizations serving value-destroying portfolios while profits collapse.

Why Breadth Destroys Depth

Every additional SKU imposes a complexity tax the standard P&L doesn’t show. Each SKU consumes engineering hours for design modifications. Each requires its own manufacturing setup, adding changeover time to production. Each adds inventory carrying costs. Each consumes sales effort and management attention. Each carries warranty exposure. Each adds to the logistics complexity premium.

When the portfolio contains 800 SKUs but customer demand concentrates on 30, the complexity tax is paid on 770 SKUs that do not justify it. The resources consumed by those 770 SKUs are resources not invested in making the 30 SKUs customers actually want excellent.

This is why focused competitors achieve higher customer satisfaction on narrower portfolios. They are not better engineers, better marketers, or better operators. They have simply refused to spread their capability across SKUs that do not matter.

The 80/20² framework makes the concentration visible. Apply the Pareto Principle recursively to the SKU portfolio and you find that 20% of 20% — 4% of SKUs — typically generate 64% of the value. The remaining 96% consume resources disproportionate to their contribution while preventing the top 4% from receiving the excellence concentration they deserve.

The Changeover Multiplier

The most underestimated cost of SKU proliferation is changeover time.

At the industrial equipment division during a separate turnaround, average changeovers consumed 47 minutes each, occurring six to eight times daily. That is 20-26% of available production time lost before any value-adding work begins.

Worse, organizations batch aggressively to minimize changeover frequency. Large batches reduce changeover cost per unit but create queue times, excess inventory, and complete inflexibility to demand changes. At that division, the 47-minute changeover cost roughly $180,000 annually in lost production time. The batching decisions made to minimize that cost destroyed $11.3 million annually.

When SKU count drives changeover frequency, reducing SKU count reduces total changeover time without requiring any improvement to individual changeover speed. This distinction matters. At the refrigeration division, 387 SKUs were eliminated from the 800-SKU portfolio. Changeover time dropped 64% — not because individual changeovers became faster, but because there were fewer products requiring setups.

Reducing the number of changeovers by 64% generated capacity benefits far beyond the direct changeover labor savings. Engineering bandwidth freed up 23% because fewer SKUs required technical support. Inventory carrying costs dropped $3.2 million annually because the portfolio held less tied-up capital. Quality improved because operators could focus on fewer configurations.

The 387 SKUs were not killed for the sake of killing. They were killed because elimination produced cascading benefits the organization did not initially target.

The Logic Filter for Killing SKUs

SKU rationalization fails when it becomes an arbitrary exercise in elimination. Kill the wrong SKUs and you lose revenue without capturing the capacity benefits. Kill the right SKUs and revenue stabilizes while complexity costs collapse.

The logic filter requires asking what benefit elimination produces:

Manufacturing benefit. Does eliminating this SKU reduce changeover time, simplify production flow, or free capacity at a constraint? At the refrigeration division, SKUs were prioritized for elimination when they caused changeovers that consumed disproportionate production time. The benefit was not simply removing a product — it was removing a changeover.

Engineering benefit. Does eliminating this SKU free engineering hours that can be redirected to higher-value work? If engineering is spending 23% of hours supporting SKUs that generate less than 5% of profit, those engineering hours are the benefit of elimination.

Sales benefit. Does eliminating this SKU simplify the sales process, reduce configuration complexity, or improve win rates on remaining products? Narrow portfolios are often easier to sell than broad ones because decision complexity drops.

A SKU worth killing typically produces benefits in at least one of these three dimensions. A SKU that does not produce a meaningful benefit in any of them may still warrant elimination, but the case is weaker, and the priority is lower.

The “What Breaks If We Skip This?” Stress Test

Before eliminating a SKU, the stress test is simple: what breaks if we skip this?

At the refrigeration division, this question revealed that many SKUs existed for reasons no one could articulate. “We’ve always offered this configuration.” “A customer asked for it in 2008.” “Someone thought we might need it.” The original business case had long since evaporated, but the SKU remained in the portfolio because no one had the authority or the inclination to kill it.

The stress test cuts through organizational inertia. If no one can explain what breaks when the SKU is eliminated, the SKU is cruft. If someone can explain what breaks, the explanation either justifies retention or reveals a specific customer relationship that needs to be addressed.

This is the same logic applied elsewhere in the 3-A Method’s Analyze phase, where eliminating unnecessary steps produces 65% improvement while optimizing all existing steps produces only 10%. Simplification beats optimization.

Customer Migration Protocols

Organizations fear SKU rationalization primarily because they fear losing customers who buy the eliminated SKUs. This fear is usually overstated.

The customer migration protocol works in three layers:

Direct substitution. For most eliminated SKUs, a remaining SKU in the portfolio can serve the customer’s underlying need. The customer’s procurement team may resist because change requires re-approval, re-specification, or new part numbers in their system. Transparent economics and advance notice typically resolve this resistance.

Product substitution with repricing. When the closest remaining SKU has a different cost structure, pricing can reflect the new economics. Some customers will accept the new pricing because the relationship value exceeds the price delta. Others will shift to competitor products, and the analysis should predict which customers fall into which category before elimination.

Strategic exit. For customers whose needs cannot be served profitably from the remaining portfolio, clean exit is preferable to continued value destruction. The Q3 quadrant of the 80/20 Matrix — top customers buying the wrong products — is where these conversations happen. Transparent economics shown directly to the customer often produces collaborative solutions that standard negotiations cannot.

At the refrigeration division, roughly 60-70% of customers affected by SKU rationalization accepted the migration. Around 10% negotiated modified orders. Around 15-20% left entirely — and those departures should be celebrated, because those customers were destroying value.

The Three-Wave Implementation for SKU Rationalization

SKU rationalization works best when integrated into the broader 80/20 Matrix implementation. The three-wave sequence is:

Wave 1 (Days 1-30): Identify Q4 value-destroyer SKUs — wrong customers buying wrong products — and implement 40-60% price increases. Approximately 60-70% of customers will accept. The remaining 30-40% will self-select for elimination by refusing the new pricing.

Wave 2 (Days 31-90): Address Q3 SKUs — top customers buying the wrong products — with transparent-economics meetings. Present the actual cost structure. Offer three options: strategic repricing at 40-60% increases reflecting true costs, product substitution to offerings that can be delivered profitably, or clean exit. Around 40-50% of Q3 customers are retained profitably through substitution or repricing.

Wave 3 (Days 91-180): Concentrate on Q1 SKUs — the top customers buying top products. Install the complexity tax: any new SKU added requires eliminating five existing ones. Embed concentration thinking into the culture so SKU proliferation does not resume once the crisis pressure subsides.

At the refrigeration division, this sequence collapsed the 800-SKU portfolio to a sustainable level, freed 18% of engineering capacity, reduced changeover time 64%, and produced a 187% profit improvement over 36 months.

What Usually Goes Wrong

SKU rationalization typically fails for four predictable reasons.

The first is sacred-cow protection. Certain SKUs are retained because they serve “strategic customers” or represent “portfolio completeness” even when the 80/20 Matrix shows them destroying value. The 80/20 discipline applies universally or it does not work.

The second is elimination without benefit. Organizations kill SKUs to reduce portfolio size without mapping the benefit. Without a clear manufacturing, engineering, or sales benefit, elimination produces revenue loss without capacity capture.

The third is skipping customer migration. Organizations announce SKU eliminations without proactive customer communication, producing preventable defections.

The fourth is resuming proliferation. Without a complexity tax — a mechanism requiring SKU additions to be offset by SKU eliminations — the portfolio reaccumulates within 18-24 months, and the next turnaround team inherits the same problem.

Starting Monday

If your portfolio has expanded for years without systematic rationalization, you are paying a complexity tax larger than you realize. The customers you are protecting by maintaining breadth are not valuing that breadth. The competitor with one-tenth your SKU count is likely generating better margins, higher satisfaction, and faster growth.

This week, run the diagnostic. List your top 20% of SKUs by revenue. List your bottom 20% by revenue. Apply rough ABC to both groups. Identify SKUs in the bottom 20% whose elimination would produce a meaningful manufacturing, engineering, or sales benefit. Apply the stress test. Calculate the changeover time, engineering hours, and inventory carrying costs their elimination would free.

You will likely find 20-40% of your portfolio is cruft. Killing it is not strategic risk. It is overdue.

For the complete SKU rationalization playbook within the 80/20 Matrix of Profitability, see the 80/20 Squared Profitability Matrix Guide. For the full system, read Stagnation Assassin: The Anti-Consultant Manifesto (Koehler Books, July 2026).