SKU rationalization
SKU rationalization is the periodic review of every active SKU in a catalog against sales velocity, margin, and carrying cost, ending in a decision to keep, consolidate, or discontinue each one. The goal is concentrating merchandising, inventory, and data-quality effort on the SKUs that earn it, instead of spreading it evenly across an assortment where a small share of items drives most of the revenue.
What drives a rationalization decision
The usual inputs: sales velocity and inventory turns, gross margin after all-in cost, carrying cost (ordering frequency, receiving labor, storage space, cycle counts), and overlap with a near-identical SKU already in the catalog. Every active SKU carries a fixed maintenance cost independent of how often it sells — a slow mover with thin margin can cost more to keep listed and stocked than it returns.
How it connects to product data quality
Long-tail SKUs, the low-volume items sitting in the bottom band of a catalog by sales, are usually the ones with the thinnest, stalest attribute data, because enrichment effort follows revenue and gets spent on top sellers first. That makes rationalization and enrichment two sides of the same resourcing decision: deciding what to cut, consolidate, or keep before investing effort enriching everything equally is usually a better use of a data team's time than enriching a catalog uniformly and rationalizing later.
Rationalization also surfaces duplicate and near-duplicate records — the same physical item listed under two SKUs from a merger, a re-platform, or inconsistent supplier onboarding — that product matching and golden record work would otherwise need to catch anyway.
Doing it without breaking availability
The risk isn't cutting a slow mover — it's cutting one a single account still depends on for a service contract or a repair. Before discontinuing a SKU: check whether it's a component inside a kit or bundle SKU that would break if it disappeared, and if it's being replaced rather than dropped outright, publish the mapping as a part number cross-reference so a buyer searching the old part number lands on its replacement instead of a dead page.
A basic rationalization cadence
Most programs run this quarterly or annually, aligned to catalog planning cycles: segment SKUs by velocity and margin (an ABC or ABC/XYZ analysis), flag candidates against a threshold rule (zero orders trailing 12 months is a common floor), and route flagged SKUs to a decision — keep, consolidate into a near-duplicate, or discontinue with a cross-reference to whatever replaces it, rather than a silent removal that leaves the buyer's search with nothing.
Frequently asked questions
How often should a catalog be rationalized?
Quarterly or annually is typical, tied to broader catalog and inventory planning cycles. Fast-moving or seasonal categories sometimes review more often; slow-moving industrial catalogs often run it annually.
Does rationalization mean deleting the SKU everywhere?
Not usually. It more often means discontinuing new orders and hiding the SKU from active search while keeping the historical record for support and reordering, and redirecting the product page to a replacement via a part number cross-reference rather than deleting it outright.
What's the risk of over-rationalizing?
Cutting a SKU that looks like a low-velocity long-tail item in aggregate data but is contractually required for a specific account, or is the only compatible replacement part for equipment still in the field.
How does rationalization relate to enrichment?
Rationalization decides which SKUs are worth the enrichment investment in the first place. Running enrichment uniformly across a catalog before rationalizing it usually means spending effort on items that are about to be discontinued anyway.