SKU count rarely looks like a problem until the P&L starts lying.
At first, more products feel like progress.
A customer asks for a variation. Sales wants a new size. Marketing sees a seasonal opportunity. A retailer requests an exclusive. The founder has a product idea that makes strategic sense in isolation. Each new SKU has a reason. Each one feels small.
Then the business gets heavier.
Forecasting becomes harder. Inventory spreads across too many bets. Purchasing loses scale. Operations deals with more changeovers, more packaging, more quality checks, more exceptions. Sales has more to explain. The website gets cluttered. Finance sees revenue, but margin becomes harder to trust.
This is the SKU proliferation trap. Growing companies fall into it because product expansion feels like customer responsiveness. Sometimes it is. Often it is complexity disguised as growth.
Every SKU Makes a Promise to the Business
A SKU is not just an item for sale.
It is a promise to forecast it, buy it, store it, market it, sell it, fulfill it, service it, and eventually decide whether it deserves to stay. That promise consumes attention and capital even when the SKU is small.
I have seen companies add products without ever calculating the full burden. The launch conversation is exciting. The maintenance conversation is ignored.
What is the minimum order quantity? How much working capital gets tied up? Does the SKU require unique packaging? Does it create operational inefficiency? Does it confuse the sales team? Does it fragment demand from a stronger product? Does it earn enough contribution margin after the full cost to serve?
Those questions are not meant to kill innovation. They are meant to protect it.
Good product strategy creates room for the right bets by refusing to carry too many weak ones. When every idea becomes a SKU, the company loses the ability to support the products that actually matter.
Revenue Can Hide Weak Product Economics
One of the most dangerous phrases in a growing company is that a SKU sells.
Selling is not enough.
A product can generate revenue and still weaken the business. It may have low margin, slow turns, high return rates, high support burden, poor repeat purchase, or operational requirements that disrupt better products. It may be loved by a small customer group but too costly to manage at scale.
I once reviewed a product portfolio where leadership believed the long tail was valuable because it represented meaningful annual revenue. After looking at contribution margin, inventory turns, pick complexity, and discounting, the picture changed. Several SKUs were tying up cash and warehouse capacity while contributing very little profit. Worse, they were distracting the team from the top products that drove repeat demand.
The decision was uncomfortable. Some customers liked those products. Sales worried about losing options. The founder had history with a few of them.
But the business needed focus.
Cutting underperforming SKUs improved inventory quality, simplified operations, and made the sales story cleaner. Revenue dipped slightly in a few pockets. Profitability and execution improved.
That is the trade-off founders need to understand. Product discipline may reduce visible variety while strengthening the company underneath.
Innovation Needs Gates, Not Gut Feel
Founder instinct is valuable in product development. It should not be the only gate.
As a company scales, product decisions need a simple but firm path from idea to launch. Not corporate bureaucracy. Just enough discipline to stop emotional or opportunistic launches from overwhelming the system.
I like clear gates.
The first gate is strategic fit. Does this product reinforce the position of the company, or is it a distraction chasing short-term revenue?
The second gate is customer evidence. Is there real demand, or only internal enthusiasm and anecdotal feedback?
The third gate is economic logic. Can the SKU hit margin, velocity, and working capital requirements that make sense?
The fourth gate is operational readiness. Can the business produce, buy, store, ship, and support it without damaging the core?
The fifth gate is exit criteria. What has to be true after launch for the SKU to stay?
That last gate is often missing. Companies decide how to launch products but not how to judge them. Without exit criteria, every SKU becomes permanent through neglect.
A launch should come with a review date. If the SKU does not hit the agreed thresholds, it gets fixed, repositioned, or cut. That is not harsh. That is responsible portfolio management.
The Best Assortments Are Edited
Great product companies are not just creative. They are editorial.
They know the role each SKU plays. Some products drive acquisition. Some drive margin. Some drive retention. Some support a key channel. Some create brand heat. But each SKU needs a job.
When a product has no clear job, it becomes clutter.
This is especially important in omnichannel businesses. A SKU that works online may fail in retail. A retail exclusive may create supply chain complexity. A premium variation may raise average order value but slow fulfillment. A low-priced item may bring in customers but dilute brand perception.
The answer is not fewer SKUs by default. The answer is intentional assortment design.
I want to see the product portfolio mapped against margin, velocity, customer role, channel fit, and operational complexity. That view makes decisions clearer. It shows which products deserve investment, which need repositioning, and which are living on borrowed time.
Founders often resist pruning because every SKU has a story. I respect that. The first version of a product may have opened a door. A niche variation may have helped win an account. A seasonal item may have created a strong moment.
But history is not strategy.
The portfolio has to serve the company the business is becoming, not only the company it used to be.
More products can create growth, but only if the organization can support them with focus, margin, and operational control. Otherwise, the assortment becomes a tax on every function.
The strongest product strategy is not adding more; it is knowing what deserves to stay.