SKU Rationalization: When to Cut Products and the Math Behind the Decision

SKU rationalization is the systematic process of evaluating every product in your catalog to determine which SKUs to keep, consolidate, or discontinue — using contribution data rather than intuition to reduce procurement complexity and redirect capital toward items that actually earn their shelf space.

Quick answers

What is SKU rationalization? SKU rationalization asks a simple question of every item in your catalog: does this SKU generate enough margin to justify the procurement, storage, and management cost of keeping it active? SKUs that don't are candidates for consolidation (merging similar variants) or discontinuation (dropping entirely). The goal is a smaller, higher-performing catalog.

Why does SKU count matter for procurement? Every active SKU carries a procurement cost: ordering frequency, receiving labor, storage space, carrying cost, cycle count time, and system maintenance. These costs exist whether the SKU sells 500 units per month or 2. More SKUs means more complexity — more supplier relationships, more purchase orders, more chances for error — with diminishing returns on the margin side.

How does rationalization connect to ABC analysis? ABC analysis provides the data input. C-items — the ~50% of SKUs contributing ~5% of inventory value — are the primary rationalization targets. Not every C-item should be dropped (some are strategically necessary), but every C-item should be justified.

When should you rationalize? At minimum, annually. Better triggers: when catalog size exceeds the team's capacity to manage it, when inventory turnover is declining despite stable revenue, or when warehouse/storage space constrains growth.

The formula

SKU contribution margin (net of procurement overhead):

net SKU contribution = (units sold × margin per unit) − (procurement cost + carrying cost + allocated overhead)

where:

units sold × margin per unit — gross margin generated by the SKU per period
procurement cost — ordering cost allocated to this SKU (PO processing, receiving labor, quality checks)
carrying cost — average inventory value × carrying cost rate, for this SKU
allocated overhead — shelf space, system maintenance, and management attention proportional to this SKU

If net contribution is negative, the SKU is destroying value.

The long tail distribution

Catalog segment	% of SKUs	% of revenue	% of procurement time	Typical action
Top performers	10–15%	60–70%	15–20%	Protect and optimize
Solid contributors	20–30%	20–30%	25–30%	Maintain
Long tail	50–70%	5–15%	45–55%	Rationalize

The long tail is where procurement labor accumulates. Each tail SKU requires the same ordering cycle, the same receiving process, and the same inventory tracking as a top performer — but generates a fraction of the margin. The rationalization question is not "does this SKU sell?" but "does this SKU earn more than it costs to keep active?"

Worked example

A specialty food retailer with 400 active SKUs runs a rationalization review. They identify a flavored olive oil that sells 3 bottles per month at $14 margin per bottle.

Revenue side:

Monthly gross margin: 3 × $14 = $42
Annual gross margin: $504

Cost side:

Carrying cost: average inventory of 8 bottles × $22 cost × 25% annual rate = $44/year
Procurement cost: unique supplier, minimum order 12 bottles, 4 orders/year × $35 ordering cost = $140/year
Receiving/storage: 4 receiving events, dedicated shelf space allocated at $60/year
Cycle count time: included in quarterly counts, allocated at $20/year

Total annual cost to maintain SKU: $44 + $140 + $60 + $20 = $264

Net annual contribution: $504 − $264 = $240

This SKU is marginally positive. But if the operator has 80 similar SKUs with the same profile, the aggregate management burden is significant. Consolidating three similar olive oil variants into one — the best seller — eliminates two supplier relationships, two sets of ordering cycles, and frees shelf space for a higher-GMROI item. The question is not whether each SKU earns $240, but whether the catalog configuration maximizes total portfolio return.

Why most operators get rationalization wrong

Emotional attachment. "We've always carried this." "One customer loves it." Dropping a SKU feels like losing a customer. But keeping 50 low-performers because each has one loyal buyer means subsidizing those buyers with procurement labor that could serve the other 95% of customers better.
Looking at revenue instead of contribution. A SKU with $6,000 in annual revenue and $5,800 in total cost (COGS + procurement + carrying) contributes $200. A different SKU with $3,000 in revenue and $1,500 in total cost contributes $1,500. Revenue alone misleads.
Not counting procurement overhead. Operators calculate margin as revenue minus COGS and stop. The ordering, receiving, tracking, counting, and storing costs are real and SKU-specific. Ignoring them makes every SKU look profitable.
Rationalizing without data. Dropping items based on gut feel ("this doesn't sell well") misses SKUs that sell slowly but at high margin, and preserves SKUs that sell briskly but at negative net contribution after overhead.
One-time exercise. Catalogs grow naturally — new products are easy to add, rarely reviewed for removal. Rationalization must be periodic, or the tail regrows within two quarters.

How LineNow handles SKU rationalization

Computes net SKU contribution by combining POS-derived margin data with procurement frequency, carrying cost, and allocated overhead per item — surfacing items where total cost exceeds total margin.
Ranks SKUs by GMROI — gross margin return on inventory investment — so operators can see which items generate the most margin per dollar of average inventory held, and which are earning less than the cost of capital.
Flags rationalization candidates automatically: items below configurable thresholds for velocity, margin contribution, and inventory turnover, weighted by ABC class.
Models consolidation scenarios — if three similar SKUs are candidates, LineNow estimates the demand transfer to the surviving variant and recalculates the portfolio impact of discontinuing the other two.
Tracks catalog growth over time, alerting when total active SKU count is growing faster than revenue — a leading indicator that the tail is expanding and rationalization is overdue.