← Back to Insights

Product & Innovation · August 10, 2026

Why A Bigger Catalog Rarely Means A Stronger Company

By Axel D'Addario

The easiest way to make a growing company feel innovative is to add SKUs.

More Products Can Hide a Weaker Core

I have watched strong companies create real drag by saying yes to too many product ideas. A customer asks for a variant. Sales wants something fresh for a key account. A founder has a smart concept. A retailer wants an exclusive. Marketing wants a seasonal drop. Nobody wants to be the person who says no to growth.

At first, it feels productive. The catalog expands. Revenue has more ways to show up. The team can point to launches as evidence of momentum.

Then the costs arrive.

Forecasting gets harder. Inventory fragments. Minimum order quantities create cash pressure. Production changeovers increase. Sales loses focus. Customer service has more exceptions to explain. Finance struggles to understand true contribution by product. The warehouse carries slow movers that nobody wants to own.

The company thinks it has a product strategy. In reality, it has accumulated decisions.

SKU proliferation is rarely one bad call. It is usually dozens of reasonable decisions made without a strong enough filter.

Revenue Is Not the Same as Contribution

The first discipline I install is a clear view of SKU-level economics.

Founders often know the heroes and the obvious dogs. The problem lives in the middle. Products that sell enough to avoid scrutiny, but not enough to justify the complexity they create. Products with decent gross margin before freight, storage, spoilage, obsolescence, customer-specific handling, or operational disruption. Products that matter to one account but distract the entire company.

A SKU can generate revenue and still weaken the business.

I want to see contribution after the real costs are considered. Not perfect accounting. Practical truth. What does this item require from purchasing, production, inventory, sales, marketing, customer service, and cash? Does it earn that burden?

At one company, a long tail of low-volume products looked harmless because each item had a positive gross margin. Once the team accounted for small production runs, higher waste, extra storage, and sales time, the picture changed. The long tail was not supporting growth. It was taxing the products that actually carried the business.

The answer was not a reckless cut. It was a disciplined review by revenue, margin, velocity, strategic value, and operational burden. Some SKUs stayed because they opened important doors. Some were repriced. Some were moved to made-to-order. Some were discontinued.

That is product management for a scaling company. Not taste. Not politics. Economics plus strategy.

Every SKU Needs a Job

A healthy product portfolio has roles.

Some SKUs are traffic drivers. Some are margin builders. Some support strategic accounts. Some create entry points for new customers. Some defend shelf space. Some test future demand. Some deserve to exist because they strengthen the brand, even if their direct economics are not perfect.

The issue is not that every SKU must perform the same job. The issue is that every SKU must have a job.

When I ask why a product exists and the answer is history, preference, or a single loud customer, I know the portfolio needs work.

This is where founders can get emotionally attached. Products carry stories. The original version. The first big customer request. The item the founder fought to launch. The seasonal product everyone loves internally. I respect that. I also know nostalgia can occupy warehouse space.

A growing company cannot afford a catalog built on sentiment.

The portfolio should be reviewed with enough rigor to separate strategic value from emotional residue. That does not mean cutting everything that is not a top seller. It means naming the reason each product earns a place and measuring whether that reason still holds.

Launches Need Gates, Not Enthusiasm Alone

The best way to fix SKU proliferation is to prevent it.

I like launch gates. Simple, practical gates. What customer problem does this product solve? Which channel will sell it? What volume is required to justify it? What margin is expected after real costs? What inventory risk is created? What existing SKU might it replace? What operational constraints are introduced? Who owns the post-launch review?

If those questions feel heavy, the company is probably launching too casually.

A launch gate does not kill creativity. It protects it. The team can still test, but tests are designed with exit criteria. If a product misses the threshold, it gets changed, paused, or removed. It does not drift into the permanent catalog because everyone got busy.

Post-launch reviews are especially important. Many companies approve products with discipline and then fail to inspect them after market reality arrives. The forecast was wrong. The margin changed. The retailer did not reorder. The customer use case shifted. Nobody wants to reopen the decision.

That is how the tail grows.

A launch is not complete when the product ships. It is complete when the company knows whether the SKU deserves to stay.

Pruning Is a Growth Move

Founders sometimes treat SKU rationalization as retreat. I see it as a growth move.

Pruning frees cash. It improves forecast accuracy. It gives sales a clearer story. It reduces operational noise. It helps purchasing negotiate better on fewer inputs. It improves service levels on the products customers actually want. It gives product development more room to focus on meaningful innovation instead of maintaining clutter.

The key is to prune with a plan. Customers need transition paths. Sales needs talking points. Operations needs timing. Finance needs to quantify the benefit. The founder needs to hold the line when exceptions appear.

There will always be a reason to keep one more SKU. A customer might complain. A sales rep might worry. A manager might argue the product just needs more time. Sometimes they are right. Often they are defending complexity because the cost is spread across the company.

That is why portfolio governance matters. Not once a year. Quarterly at minimum for a growing product business. The catalog should be managed like an asset, not inherited like a family attic.

More SKUs are not proof of innovation. A stronger portfolio is.

The trap is believing every new product adds growth when many only add weight.