LineNow
Use CasesPartnersProcurementSuppliersResources
LoginBook a Demo
LineNow
  • Use Cases
  • Suppliers
  • Pricing
Login
Book a Demo
Line Now Logo
Procurement and supplier operations — simplified.Based in Seattle, WA

Products

  • Purchase order software
  • Purchase order tracking
  • Supplier management
  • Inventory replenishment
  • Procurement platform
  • Supplier catalogs
  • Pricing

Solutions

  • Restaurant purchasing
  • Manufacturing purchasing
  • Central purchasing
  • Dropshipping
  • Regulated purchasing
  • Supplier order intake
  • All purchasing use cases

Integrations

  • Shopify purchasing
  • Square purchasing
  • Lightspeed purchasing
  • QuickBooks Online
  • All integrations

Resources

  • Buying guides
  • Software comparisons
  • Buyer insights
  • All articles
  • Free purchasing tools
  • Free templates
  • Rollout checklist

Company

  • Why LineNow
  • Book a demo
  • Help Center
  • Contact
PrivacyTermsEditorial standards
© 2026 Line Now LLC
Home/Blog/Glossary/SKU Rationalization: When to Cut Products and the Math Behind the Decision
GlossaryProcurement encyclopedia

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

Compare item contribution with avoidable ordering and holding costs while retaining critical and complementary products.

Jainul Vaghasia/Published May 25, 2026/Updated September 4, 2026/5 min read

Use the definition

Turn procurement terms into an operating system.

This reference page should help you understand the concept first. When the term affects purchasing execution, LineNow connects it to live POs, supplier replies, receiving, and accounting handoff.

Retail Replenishment, Complete: From Reorder Points to Reconciled CostsInventory replenishment

Contents

  1. Quick answers
  2. The formula
  3. Measure the catalog rather than assuming a Pareto split
  4. Worked example
  5. Why most operators get rationalization wrong
  6. Apply this to a real purchasing record
  7. Related
Back to top

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):

Read before ordering

A dense operator briefing for teams that need sharper buying, cleaner supplier follow-up, and fewer expensive surprises.

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

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.

Revenue side:

  • Monthly gross margin: 3 × $14 = $42
  • Annual gross margin: $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

Net annual contribution: $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.

Why most operators get rationalization wrong

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

Apply this to a real purchasing record

LineNow's purchasing workflow connects purchase orders, supplier replies, receiving and accounting handoff. In a demonstration, inspect item-level sales or usage, purchase history and stock alongside a separately reviewed contribution analysis; verify any scenario model or automatic catalog recommendation before relying on it.

Use the result to agree the fields, decision owner and exception process. A linked purchasing record supplies evidence for this analysis; it does not by itself prove a particular dashboard, financial outcome or automatic approval policy.

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

Wondering which SKUs are quietly eating your margin? Book a demo to start your 90-day free trial.

SKU rationalizationSKU optimizationproduct rationalizationreduce SKU countSKU managementassortment optimization

Written by Jainul Vaghasia

Jainul Vaghasia builds LineNow, the purchasing and inventory platform for SMBs. He writes from operator interviews, customer implementations, and the live purchasing workflows LineNow runs for restaurants, retailers, and ecommerce brands.

Editorial standards and corrections

Recommended next

Continue with a relevant guide or purchasing workflow.

Explore the buying process, compare software, or see how a customer handles similar supplier work.

Retail Replenishment, Complete: From Reorder Points to Reconciled CostsConnect reorder policies, packs, supplier communication, physical receiving and cost review with current platform-specific guides and tools.Best Inventory Replenishment Software: Compare Planning and ExecutionCompare replenishment tools for retail, restaurants, stockrooms and manufacturing, with a worked order calculation and a repeatable forecast-and-receipt trial.Inventory replenishmentReview demand, supplier packs and outstanding orders before buying more stock.PricingCheck the trial, business-unit pricing and what is included.
Share on X