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 catalog that better serves demand and operating requirements; the result need not be fewer SKUs in every category.
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. The incremental burden depends on shared suppliers, consolidated orders, storage constraints and the item’s role in the assortment.
How does rationalization connect to ABC analysis? ABC analysis can prioritize the review using a chosen measure, such as annual usage value. The class proportions depend on your data and thresholds. Low-ranked items are review candidates, not automatic deletion targets. Oracle’s ABC documentation explicitly makes the valuation criterion a choice.
When should you rationalize? Set a review cadence for the assortment and buying cycle. Useful triggers include: 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
Illustrative SKU result after assigned costs:
SKU result = Gross profit − Assigned ordering, holding and other costs
where:
- units sold × margin per unit — gross profit 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
A negative result is a review signal. Separate avoidable costs from allocated overhead that would remain after discontinuation, and count each cost once. Lost basket sales or a critical operational use can change the decision.
Measure the catalog rather than assuming a Pareto split
Calculate each item’s revenue, gross profit, stock investment and incremental ordering burden. Low usage value does not automatically mean an item should be removed: critical spares, assortment commitments and complementary products may justify their place.
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.
Gross profit:
- Monthly gross profit: 3 × $14 = $42
- Annual gross profit: $504
Cost side:
- Carrying cost, excluding costs allocated separately below: assumed average inventory of 8 bottles × $22 cost × 25% annual rate = $44/year
- Procurement cost: unique supplier, minimum order 12 bottles, 3 orders/year × $35 ordering cost = $105/year
- Receiving/storage: 3 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 + $105 + $60 + $20 = $229
Annual result after assigned costs: $504 − $229 = $275
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 — may reduce separate ordering work and free shelf space, depending on supplier overlap and how much demand transfers for a higher-GMROI item. The question is not whether each SKU earns $275, but whether the catalog configuration maximizes total portfolio return.
Estimate the effect of discontinuing a SKU
An allocated loss does not prove that dropping the item saves money. Compare the future keep and discontinue scenarios over the same period:
Change from discontinuation = Avoidable cost savings + Contribution from transferred demand
− Lost contribution − Exit costs
Use consistent contribution definitions and count each cost once. Existing inventory may need selling, returning or writing down. Shared rent, software and staff costs may remain even if the item disappears. Released shelf space has value only if there is a useful alternative or an avoidable expense.
For a separate fictional example, an item generates $500 annual contribution before SKU-specific costs. Dropping it saves $150 of genuinely avoidable annual costs, transfers $300 of contribution to substitute products and incurs a one-time $40 exit cost. The first-year change is $150 + $300 − $500 − $40 = −$90. Under these assumptions, discontinuing it worsens the result despite reducing catalog size.
Test demand transfer rather than assuming it. A niche item can complete a customer’s basket, satisfy a contract or keep a critical process running. Seasonal items need a relevant comparison period, and low recorded sales during stockouts do not establish low demand.
Make the decision operational
Document the item, reason, decision owner, affected locations, replacement and review date. Check outstanding POs and supplier commitments before stopping reorders. Decide how existing stock and returns will be handled, then update the catalog and replenishment rules consistently.
Monitor what happens after the change: substitute sales, lost baskets, remaining stock and purchasing workload. Review the actual outcome against the assumptions rather than treating fewer SKUs as proof of success.
Connect the review to purchasing
Use LineNow’s purchasing workflow to inspect a candidate item’s orders, supplier replies, receipts and remaining commitments alongside your sales and contribution analysis. A living purchase order helps identify a delivery or obligation that a catalog decision must account for.
Demonstrate any required assortment model or automatic discontinuation rule explicitly; the contribution decision still needs the buyer’s commercial context.
Related
- Procurement Software
- Purchase Order Software
- Supplier Management Software
- ABC Inventory Analysis: How to Classify and Prioritize SKUs
- Carrying Cost: What It Really Costs to Hold Inventory
- Slow-Moving and Dead Stock: The SLOB Problem
- GMROI: Gross Margin Return on Inventory Investment
- Inventory Turnover: Formula, Benchmarks, and How to Improve