Risk Management

How to Prioritize Which SKUs to Protect When Disruption Risk Is High

Abstract visualization of ranked SKU risk prioritization in supply chain planning

When a disruption signal arrives, the first instinct for most planning teams is to pull everything forward: increase safety stock across the board, expedite as many orders as possible, and wait to see what actually arrives late. That instinct is understandable but expensive. It treats all SKUs as equally at risk and equally worth protecting, which is rarely true.

A 1,000-SKU catalog has enormous variation in revenue contribution, supply concentration, and customer impact from a stockout. Treating them uniformly means overspending on protection for low-impact items while under-resourcing the few SKUs where a stockout genuinely matters. During a disruption event, capital and procurement bandwidth are limited. SKU prioritization is how you allocate both to where they create the most value.

The Two Axes That Define SKU Risk Priority

SKU prioritization for supply risk is a two-dimensional problem. The axes are:

Revenue impact of a stockout: How much does this SKU contribute to revenue, and how do customers respond to a stockout? High-velocity SKUs with inelastic demand and no easy substitute command more protection than slow-moving SKUs where customers will backorder or switch without significant penalty. This axis also captures contractual obligations: a stockout on a product under a supply agreement with a penalty clause has a different impact profile than a stockout on a standard catalog item.

Supply risk exposure: How likely is this SKU to be affected by the current disruption signal? This is a function of supplier geography, lead-time variance, current inventory position relative to reorder point, and whether the supplier for this SKU is in the same geographic cluster as the disruption event. A SKU with a single-source supplier routed through the congested port has high exposure. A SKU sourced domestically with two qualified suppliers has low exposure even if you put it on your watch list.

The prioritization matrix plots these two axes and produces four quadrants: high impact, high exposure (protect immediately); high impact, low exposure (monitor, no immediate action); low impact, high exposure (accept the risk, do not burn capital); low impact, low exposure (ignore for now).

This sounds straightforward, but the data inputs to build the matrix correctly are not always assembled in one place.

Building the Revenue Impact Score

Revenue contribution per SKU is usually available from your ERP or order management system as average monthly revenue or gross margin. The adjustment factors that turn raw revenue into a stockout impact score are:

Demand inelasticity: How much of the demand transfers to an alternative product versus being lost? For specialty or sole-sourced products, lost demand is high. For commodity products with substitutes in your own catalog, it is lower.

Customer segment: A stockout affecting your five highest-revenue accounts has a different impact than the same stockout spread across many small accounts. If you have account-level revenue attribution in your ERP, use it. If not, use product categories as a proxy: products that go primarily to large accounts typically have higher per-unit impact from a service failure.

Stockout duration tolerance: Some customers will backorder with a 5-day wait. Others will cancel and place with a competitor. The category and relationship type matter here. In distribution businesses, commodity categories typically have low tolerance: the customer has alternatives. In specialized manufacturing, customers may wait because qualification of an alternative is expensive for them too.

The output of this scoring is a ranked list of SKUs by weighted revenue impact from a stockout. The top 10-15% of SKUs typically represent 60-70% of the total impact. These are your priority-1 protection list regardless of supply conditions.

Building the Supply Risk Score

Supply risk scoring per SKU requires connecting SKU-level procurement data to the current disruption signals you are monitoring. The inputs are:

Supplier-to-SKU mapping: Which supplier or suppliers can fill this SKU, and what fraction of volume comes from each? SKUs with a single supplier have maximum concentration risk. SKUs with two or more qualified suppliers have lower exposure.

Supplier geographic exposure: Is the primary supplier for this SKU in the affected region? If you are tracking a port congestion event in East Asia, SKUs sourced from East Asian suppliers are exposed. SKUs sourced domestically are not.

Current inventory position versus reorder point: A SKU at 4 weeks of supply above its reorder point is less exposed to a 2-week lead-time extension than a SKU already at its reorder point. The current buffer modulates the exposure: high geographic risk plus adequate buffer means you have time. High geographic risk plus near-reorder point means act now.

Lead-time extension estimate: Given the current signal severity, what is the estimated extension to lead time for the affected lane? Applying that estimate to SKU-level reorder points tells you which SKUs will trip an alert during the disruption window.

At Supplyverde, this supply risk score per SKU is calculated continuously and updates when signal conditions change. The output feeds into the alert ranking: when a disruption signal arrives, the SKUs that surface at the top of the alert list are those where high supply risk exposure overlaps with high revenue impact, not simply all SKUs served by the affected supplier.

A Worked Example: 18-SKU Priority Outcome

Consider a distributor with 340 active SKUs that gets a port congestion alert affecting three Tier-1 suppliers. Those three suppliers collectively provide inputs or finished goods for 87 SKUs in the catalog. Applying the prioritization matrix:

  • Of the 87 exposed SKUs, 23 are in the top quartile of revenue impact. These go on the immediate watch list.
  • Of those 23, 11 are currently within 10 days of their reorder point, meaning a 2-week lead-time extension would create a gap before stock arrives.
  • Of those 11, 5 have a single-source supplier in the affected region with no qualified alternative. These are the critical-action SKUs: either expedite freight, place an emergency buffer order, or escalate to the account team to pre-notify high-priority customers of potential delays.
  • The remaining 6 of the 11 have a secondary source that can partially cover volume, so the action is to qualify a shifted order split rather than emergency freight.
  • The remaining 64 of the 87 exposed SKUs either have low revenue impact, adequate buffer, or alternative sourcing. They get a weekly check but no immediate action.

Without the prioritization framework, the planner is looking at 87 SKUs with no clear ranking. With it, the decision set collapses to 5 critical actions and 6 secondary actions. That is a workable scope for a single planning day.

What the Framework Does Not Resolve

SKU prioritization tells you where to focus. It does not tell you whether to protect through buffer stock, emergency sourcing, or customer communication. Those are separate decisions that depend on cost, lead time of alternatives, and customer relationship context.

It also does not substitute for maintaining up-to-date supplier-to-SKU mapping and inventory position data. The framework is only as good as its inputs. If your ERP supplier mapping is out of date, or if your current on-hand inventory data has a 3-day lag, the prioritization output will have errors. The analytical discipline required to maintain clean data for this exercise is the same discipline that makes the rest of your planning process more reliable, which is why it is worth investing in even outside of active disruption events.

The goal is to avoid the scenario where a disruption response becomes a flat increase in safety stock and emergency freight across the board. That response costs more, delivers less targeted protection, and leaves you less informed about where your actual risk concentration is for the next event. Prioritization creates a structured response even when conditions are moving fast.