The SKU Rationalization Cut List

Cut a bloated SKU catalog

cut a bloated sku cataloge-commerce / retailtool-agnosticecommerceskuoperationsmargincatalogintermediate
Entry PT-0251 · full text · stolen 0 timesReceived

Our catalog has too many SKUs: [FULL SKU LIST WITH 12-MONTH REVENUE, MARGIN, INVENTORY ON HAND, STORAGE COST, WHICH SKUS EXIST FOR ONE BIG CUSTOMER]. Build the cut list: the revenue-versus-complexity score for each SKU, the bottom tail that costs more to keep than it earns, the customer-dependent SKUs that need a conversation before a cut, the wind-down plan (sell-through, discount depth, bundle-it-out), and the catalog promise going forward so it does not creep back.

Inputs needed

  • SKU P&L data, inventory, storage cost, dependencies

What good output looks like

Scored cut list; customer-dependent SKUs flagged; wind-down plan; anti-creep rule

Test it in SynthAnswers →

The stream (0)

Reading the room…

Same drawer