Numbers are indispensable in SKU rationalization, but they do not decide everything. Some products deserve protection even when their direct economics look modest. Others look important until the business forces itself to define what that importance actually is. This is where disciplined judgment matters. Without it, the company will either cut too aggressively and damage real sources of value, or protect too much and allow every stakeholder to label a favorite SKU “strategic.” This is the bridge between the quantitative analysis and the final management judgment.
This chapter explains how to identify legitimate keeper SKUs, how to account for brand and innovation effects without losing rigor, how to evaluate regulatory, contractual, and technical constraints, and how to incorporate field and customer input in a structured way. The objective is not to replace analysis with opinion. It is to make sure the final portfolio reflects the parts of the business that are real, but harder to measure.
11.1 Identifying Strategic Keeper SKUs
A good rationalization program does not require every SKU to justify itself on short-term economics alone. Some items matter because of the role they play in the broader portfolio, the customer relationship, or the capabilities of the business. The challenge is to distinguish true keeper SKUs from products that are merely protected by habit or vague claims of importance.
Strategic keeper SKU: an item that should be retained despite limited direct attractiveness because it performs a clearly defined strategic function that the business would struggle to replace quickly or cheaply. A SKU is not strategic because someone says it is. It is strategic when the company can explain what function it serves, why that function matters, and what would happen if the item were removed.
In practice, keeper SKUs usually fall into a few patterns. Some complete a size ladder, price ladder, dosage range, or configuration set that customers expect to see. Some are access items that help win with a major retailer, distributor, hospital system, or OEM even if the item itself is not especially profitable. Some are installed-based items. Service parts, legacy fitments, and compatibility products may generate modest volume but protect larger downstream revenue. Others are credibility items that help the company present itself as a full-line supplier in categories where customers prefer fewer vendors.
The discipline is to test each of these claims. If a SKU is said to complete the range, is that range actually important to the customer, or only to internal marketing logic? If it is required for a major account, is that requirement contractual, strongly preferred, or simply historical? If it supports an installed base, how large is that base and how fast is it declining? Strategy deserves respect, but it should still face scrutiny.
A useful principle is that a keeper SKU should have an identifiable consequence of removal. If the business cannot describe a credible consequence beyond “some people might be unhappy,” the strategic case is probably weak. The consequence may be commercial, technical, or architectural, but it should be concrete.
It is also useful to separate permanent keepers from temporary keepers. Some SKUs need to stay today because the organization is not yet ready to migrate customers, redesign the range, or satisfy a notice period. That does not make them permanent features of the portfolio. It makes them manage transition items.
11.2 Accounting for Brand, Innovation, and Halo Effects
One of the hardest parts of rationalization is dealing with the SKUs that seem to matter symbolically. Marketing teams often point to brand presence, innovation signaling, or halo effects when defending items that look weak on volume and margin. Sometimes they are right. Sometimes those arguments are broad enough to shelter almost anything. The right answer is not to dismiss these effects, but to force them into sharper definitions.
Halo effect: the indirect value a SKU creates by improving the performance, perception, or discoverability of other items in the portfolio. A halo SKU may attract attention, signal premium quality, reinforce innovation credentials, or make the broader range feel more relevant. In categories with strong consumer choice dynamics, that can be real value.
The problem is that halo claims are often asserted more easily than they are demonstrated. A company should therefore ask harder questions. Does the SKU genuinely draw traffic, trial, or brand attention, or is it simply admired internally? Does it have a visible role in advertising, digital search, retailer conversations, or category storytelling? Do customers mention it as part of why they choose the brand? Have past removals changed the performance of neighboring items? These questions do not make halo effects fully measurable, but they turn them from a vague concept into a testable argument.
Innovation raises a similar issue. Many companies overvalue the existence of newness and undervalue the discipline of exiting old, overlapping items. A launch may have been strategically important at one point because it signaled progress, defended a competitor move, or opened a new segment. But once the portfolio matures, the same item may no longer deserve immunity. Innovation should be treated as a portfolio function, not as lifetime protection for every launch.
Brand effects also need to be viewed at the right level. Sometimes one low-volume SKU is protected because leaders believe it contributes to the brand’s modern or premium image. That may be true, but the question is whether the image depends on that exact item or on the broader concept it represents. If the latter, the company may be able to simplify the range while preserving the brand signal through one better-executed SKU rather than several overlapping ones.
The broader principle is simple: intangible value counts, but it should not be unbounded. Teams should document the claimed effect, identify the mechanism by which the effect occurs, and decide whether the same benefit could be delivered with fewer or better-designed SKUs.
11.3 Evaluating Regulatory, Contractual, and Technical Constraints
Some SKUs cannot be rationalized on commercial logic alone because the company is constrained by outside rules, formal obligations, or technical realities. These constraints are often real, and ignoring them can create material risk. At the same time, they are frequently overstated. Teams sometimes use the language of regulation or technical necessity to defend items that are merely inconvenient to change.
Regulatory constraint: a legal, compliance, labeling, registration, or market-access requirement that limits the company’s ability to modify or discontinue a SKU without additional action. This is especially important in pharmaceuticals, medical products, food and beverage, chemicals, and cross-border categories.
Contractual constraint: an obligation created by a customer agreement, tender, service-level commitment, warranty, or supply contract that restricts the company’s freedom to change the offer. Contract constraints should be checked carefully rather than assumed. Many account teams speak as if an item is “required” when the real requirement is looser.
Technical constraint: a compatibility, performance, formulation, fitment, or qualification requirement that prevents one SKU from being replaced easily by another. This is common in industrial products, automotive parts, electronics, and medical devices. Two items may look similar to management but not be interchangeable in the field.
The key practice is to avoid binary thinking. Constraints are rarely just “yes” or “no.” A regulatory item may be removable after a filing. A contractual item may be renegotiable at review. A technical item may be replaceable after qualification testing or customer approval. In many businesses, the constraint does not eliminate choice; it changes the sequence and timing of action. For this reason, constrained SKUs should not all go automatically into the keep bucket. They should be classified by type of constraint, strength of constraint, time to resolve, and cost to resolve.
This approach improves portfolio management in two ways. First, it prevents reckless action where real obligations exist. Second, it exposes which “untouchable” items are actually candidates for phased simplification once the necessary work is done.
11.4 Incorporating Field and Customer Input
The final qualitative layer comes from the people closest to the market: sales teams, key-account leaders, customer service, technical support, distributors, and sometimes customers themselves. Their input is essential because data does not capture everything. It may not show why a retailer insists on a certain pack, why an installer prefers one component, or why a channel partner treats one SKU as a signal of seriousness. At the same time, field input can easily distort rationalization if it is collected casually.
Field input: structured insight from commercial and customer-facing teams about how SKUs are used, perceived, substituted, and negotiated in the market. The word “structured” matters. The company should not ask, “Which items do you want to keep?” That invites blanket protection. It should ask more disciplined questions. What specific customer need does this SKU serve? Which customers would object if it changed? What substitute would be acceptable? How much demand would likely transfer? What evidence supports that view?
The same principle applies to direct customer input. A small number of targeted conversations with major accounts, distributors, or representative users can be highly valuable, especially when the stakes are large. But these conversations should test specific hypotheses, not open the entire portfolio to renegotiation. The company is trying to understand risk, transferability, and requirements, not invite every customer to redesign the assortment. Used well, this input reduces surprise during implementation and improves confidence in transfer assumptions.
It is also useful to separate different types of field knowledge. Sales may understand account politics and negotiation leverage. Customer service may understand complaint patterns. Technical support may understand usage realities and failure consequences. No single voice sees the entire picture, which is why qualitative assessment should combine them rather than rely on whoever speaks most loudly.
A disciplined review process works best. Candidate SKUs are presented with their quantitative profile, likely substitute path, and preliminary recommendation. Field teams are then asked to confirm, challenge, or add context using defined criteria. Their input is documented, not just voiced in a meeting. When the rationale for an exception is captured explicitly, leaders can judge it consistently across categories and customers.
The point of field and customer input is not to override analytics. It is to complete them. A strong rationalization process respects market reality without becoming captive to anecdote. The company is no longer choosing between “the numbers” and “what the field says.” It is using both to make better portfolio decisions.
