A growing company rarely drowns in one bad product. It drowns in too many decent ones.
More SKUs Usually Feel Rational at the Time
SKU proliferation does not usually start with bad thinking. It starts with opportunity.
A customer asks for a variation. A retailer wants an exclusive. Sales hears a gap in the market. A competitor launches something new. The founder has a product idea that feels obvious. One more SKU does not seem dangerous.
Then one becomes five. Five becomes twenty. The line expands across sizes, colors, flavors, bundles, pack formats, channels, and limited runs. Revenue grows, but complexity grows faster.
I have seen companies celebrate assortment expansion while margin, inventory turns, and team focus quietly deteriorated.
The trap is that every new SKU has a visible upside and a hidden operating cost.
The upside shows up in the forecast. The cost shows up in purchasing, planning, storage, quality control, customer service, fulfillment, marketing, sales training, data management, and cash tied up on the shelf.
Founders often approve products one at a time. The business pays for them as a system.
Revenue Is the Wrong First Test
A SKU can sell and still be a bad SKU.
That sounds harsh, but it is true. Revenue alone does not tell the full story. A product may generate orders while carrying weak gross margin, low velocity, high return rates, poor forecast accuracy, or heavy operational handling. It may distract the sales team from better products. It may require unique components that create purchasing risk.
When I review a product portfolio, I look beyond top-line sales. I want to understand contribution margin, velocity, inventory turns, minimum order quantities, stockout frequency, return or defect rate, channel fit, and support burden.
The surprises are usually in the middle of the assortment.
The best sellers are obvious. The dead products are obvious. The dangerous SKUs are the ones that appear acceptable. They sell enough to avoid scrutiny but not enough to justify their complexity.
One company I worked with had a long tail of SKUs that represented a modest share of revenue but a disproportionate share of inventory issues and customer service questions. None looked terrible in isolation. Together, they were draining cash and attention.
After cleaning the line, the company did not feel smaller. It felt sharper. Purchasing improved. Marketing became clearer. Sales had fewer stories to explain. Operations had fewer exceptions to manage.
Simplification created capacity for better growth.
Every SKU Needs a Job
I do not believe in cutting products just to make the spreadsheet look clean. A smaller assortment is not automatically better. The right assortment is intentional.
Every SKU needs a job.
Some SKUs are volume drivers. Some are margin builders. Some create entry points for new customers. Some support strategic retail placement. Some help with bundles or merchandising. Some exist because they serve a specific high-value segment.
But if nobody can explain the job clearly, the SKU is probably there because of history, emotion, or avoidance.
This is where founders need discipline. Product decisions can become personal. The founder may love the product. A large customer may have requested it years ago. The sales team may believe it needs every option to win. Operations may hesitate to challenge revenue.
The portfolio needs a common language.
I like assigning each SKU a role and then measuring it against that role. If a SKU is supposed to drive margin, margin must be real after all costs. If it is supposed to open a channel, that channel must be material. If it is supposed to create brand visibility, the company should be honest about whether that visibility is worth the working capital.
A product without a role becomes clutter.
Innovation Needs a Gate, Not a Wall
The answer to SKU proliferation is not to stop innovating. That would be a mistake. Growing companies need product development. Markets move. Customers change. Channels evolve.
The answer is a better gate.
Before adding a SKU, I want the team to answer practical questions. What customer problem does it solve? Which channel will carry it? What existing SKU might it replace? What margin does it need to hit? What operational complexity does it add? What minimum volume justifies keeping it? What will trigger a kill decision?
The last question is the one most teams avoid.
Launch decisions are easier than exit decisions. Teams like adding. They dislike removing. But every new SKU should come with a review date and a performance standard. If it misses the standard, the company should either fix the issue or discontinue it.
This protects innovation from becoming accumulation.
I have also found that replacement thinking helps. Instead of asking what can be added, ask what should be retired if this product enters the line. That one question changes the conversation. It forces the team to think about capacity, not just possibility.
Complexity Compounds in Operations and Cash
SKU growth has a way of hiding inside the balance sheet.
More SKUs usually mean more raw materials, more finished goods, more packaging types, more forecasting error, more warehouse locations, and more slow-moving inventory. Cash gets trapped in products that looked promising six months earlier. Finance sees it. Operations feels it. The founder wonders why growth is not turning into cash.
This is especially painful for companies moving from seven to eight figures. At that stage, working capital discipline matters. The business may have demand, but demand spread across too many products can create a cash crunch.
Complexity also slows the team. Marketing needs more assets. Sales needs more training. Customer service needs more answers. Fulfillment makes more mistakes. Purchasing loses buying power across fragmented components.
No single issue looks fatal. The system just gets heavier.
A clean SKU strategy gives the company room to scale. It makes the core easier to forecast, easier to sell, easier to produce, and easier to improve. It also creates a better foundation for real innovation because the team has the bandwidth to launch products properly.
The strongest product companies are not the ones with the most SKUs. They are the ones with the clearest reasons for every SKU they keep.
Growth does not require a bigger assortment; it requires a sharper one.