Most SKU rationalization efforts begin with the visible economics of the portfolio: volume, revenue, and margin. That is necessary, but it is rarely enough. Many SKUs that appear harmless in sales reports create a disproportionate burden across planning, sourcing, production, storage, and fulfillment. Because that burden is spread across functions and often buried in overhead, companies routinely underestimate the true cost of variety.
This chapter explains how assortment complexity creates cost beyond standard product margin, how to measure the operational load imposed by individual SKUs, how to assess inventory and working-capital effects, and how to build a practical view of complexity cost at the SKU level. The goal is to make hidden complexity visible in a form that leaders can act on.
8.1 Understanding the Hidden Cost of Assortment Complexity
Assortment complexity: the cumulative burden created when a company carries more variants, pack types, configurations, or customer-specific items than the operating model can support efficiently. The key word is cumulative. A single additional SKU rarely looks expensive on its own. It is one more line in a forecast, one more bill of material, one more production run, one more pick location, one more replenishment rule. But when these effects multiply across hundreds or thousands of items, the cost becomes material.
What makes complexity difficult to manage is that much of its cost sits in shared resources. Standard product costing usually captures direct materials and direct conversion, but it rarely attributes enough of the added burden created by low-volume or high-variability SKUs. Planners spend more time managing exceptions. Buyers place more small orders. Manufacturing absorbs more changeovers and shorter runs. Warehouses maintain more pick faces and slower-moving inventory. Customer service handles more order issues and substitution questions. None of these burdens is always charged back to the SKU that causes it.
The effect is that portfolio complexity is often funded invisibly. A business may believe a tail SKU is profitable because it clears a standard gross margin hurdle, even though it consumes an outsize share of support effort. In many organizations, the core portfolio cross-subsidizes the tail. High-volume items carry the fixed cost base efficiently, while slow and fragmented items erode that efficiency without showing their full impact in product-level reporting.
Complexity also has a nonlinear effect. The tenth variant in a family may add little burden if the system is already designed to handle it, but the hundredth may push the business into more schedule instability, more stockouts, more obsolete inventory, and more manual intervention. This is why companies that tolerate continuous SKU additions often feel operations become harder to run long before they can see the full cost in the P&L.
The first discipline in cost-to-serve analysis is therefore conceptual. Leaders must accept that complexity cost is real even when accounting systems do not isolate it neatly. The task then becomes practical: identify the activities most affected by SKU proliferation, measure them consistently, and connect them back to the portfolio in a way that supports decisions.
8.2 Measuring Operational Burden Across Planning, Sourcing, Manufacturing, and Logistics
Operational burden: the workload, variability, and inefficiency that a SKU creates across the operating model. Measuring it requires looking beyond finance reports and into the activities that teams perform to keep the item available. The right question is not simply, “What does this SKU cost?” It is, “What does the organization have to do because this SKU exists?”
In planning, burden often shows up as forecast difficulty and exception management. Low-velocity SKUs generally have noisier demand, which weakens forecast accuracy and forces planners to intervene more often. A practical measure is to examine demand variability, order frequency, forecast error, and the number of manual planning touches. A SKU that requires repeated overrides, special review, or frequent rescheduling is usually more expensive to manage than a similar-volume item with stable demand.
In sourcing, burden appears through supplier fragmentation, small order quantities, and special components. Some SKUs require unique materials, labels, inserts, or packaging formats that can only be purchased in inefficient lots. Others depend on niche suppliers with longer lead times or stricter minimum orders. Useful metrics include component uniqueness, supplier count, lead-time length, minimum-order mismatch, and the frequency of urgent buys or order changes.
In manufacturing, the most important burden drivers are usually changeovers, short runs, and line complexity. A SKU that forces frequent setup changes or requires dedicated cleaning, tooling, or quality checks can be expensive even at healthy sales levels. Measures such as setup time, run length, line efficiency, scrap, and schedule disruption help show which SKUs are absorbing disproportionate plant capacity.
In logistics, the burden usually sits in storage, handling, and service execution. Every SKU may need a location, a replenishment rule, carton logic, transportation planning, and order handling. Low-volume items often take more touches per unit sold because they move less efficiently through the network. Good indicators include warehouse slot usage, pick frequency, case-break handling, shipment fragmentation, expedited orders, and service exceptions.
The objective is not to build an encyclopedic library of metrics. It is to identify the few drivers that explain most of the cost in the business. Operational burden analysis should reflect the real economics of the operating model, not a generic template. The right model is the one that explains where friction really comes from.
8.3 Assessing Inventory Implications and Working Capital Effects
Inventory is where SKU complexity becomes cash. Every active SKU usually requires some combination of cycle stock, safety stock, in-transit inventory, and reserve stock for uncertainty. As portfolios expand, the business does not simply divide the same inventory across more items. It often has to hold more total inventory because demand is spread more thinly and less predictably. That makes replenishment less efficient and increases the risk that stock will sit for too long in the wrong place.
Working capital effect: the cash impact created by holding inventory, funding longer procurement cycles, and absorbing write-offs tied to slow or unstable items. Tail SKUs are often the biggest offenders because they require disproportionate stock coverage relative to their sales velocity. The business may carry months of supply for an item that sells only occasionally, simply because procurement minimums, production economics, or service expectations make smaller replenishment impractical.
Safety stock is especially sensitive to complexity. When demand is fragmented across many similar SKUs, each individual item becomes harder to forecast, and the company often compensates by holding more buffer inventory. If demand could be concentrated into fewer substitute items, the total stock required to serve the same market need would often fall sharply. This is one of the clearest financial arguments for rationalization.
Obsolescence is another major effect. Low-velocity items are more likely to age into write-offs when packaging changes, specifications are updated, or customer demand moves on. A good analysis therefore looks not only at current inventory levels, but also at age, turns, excess and obsolete balances, and historical write-off patterns.
Working-capital analysis should also examine network implications. A SKU stocked in multiple warehouses or service locations ties up more cash than the same SKU held centrally. Customer-specific variants can be especially costly because they may need dedicated inventory positions with little pooling benefit. When viewed this way, inventory becomes a portfolio design issue, not just a planning parameter.
8.4 Quantifying Complexity Cost at the SKU Level
The final step is to translate these burden drivers into a usable SKU-level estimate. This does not require perfect activity-based costing. What matters is building a method that is consistent, directional, and credible enough to change decisions.
Complexity cost: the incremental cost imposed by a SKU beyond its direct product cost, including the added burden it creates in planning, sourcing, manufacturing, logistics, and inventory. There are two common ways to estimate it. The first is a driver-based model. In this approach, the business identifies the major burden drivers, such as setup time, unique components, forecast error, stocking locations, or days of inventory, and assigns cost rates or relative weights to them. The second is a scoring model, in which SKUs are ranked on those drivers and grouped into low-, medium-, and high-complexity tiers.
The best method usually combines the two. Where the data is strong, cost rates can be applied directly. For example, the business may know the approximate labor and lost-capacity cost of a changeover, the carrying cost of inventory, or the handling cost of an additional stocking position. Where the data is weaker, the team can use weighted complexity scores to distinguish problematic SKUs from healthy ones. The result is not a statutory accounting view. It is a management view designed to expose which items are consuming hidden resources.
It is important to avoid false precision. If the model claims that one SKU creates exactly $18,742 of annual complexity cost, leaders will often challenge the estimate and miss the larger point. It is usually better to show ranges or indexed comparisons. A clear message such as “this SKU sits in the top decile of complexity burden while contributing only marginal profit” is often more actionable than a fragile point estimate.
The output should support decisions, not just analysis. Each SKU or family should be visible through a combined lens: commercial value, margin quality, complexity burden, inventory effect, and likely transferability. When those elements are brought together, patterns become obvious. Some SKUs are commercially important and operationally healthy. Some are small but acceptable niche items. Others are classic rationalization targets: low demand, weak economics, high complexity, and easy substitutes. That combined view is what turns complexity analysis into action.
