Executing portfolio price cuts: a category manager's playbook

Two weeks ago, Kroger told the market it wants to slash prices on thousands of products. Walmart pinned its tariff-refund windfall to a fresh round of price cuts. e.l.f. Beauty signalled it might cut prices on parts of its range. The headlines write themselves. The work does not. Every portfolio-wide price cut announced upstairs lands on the desk of a category manager who has to decide which SKUs, how deep, how fast, and what to offset. This is the playbook for the next sixty days.

The instinct, when the press release goes out, is to run a flat percentage cut across the SKUs that fit a loose criterion and call it done. That is how a third of these programs end up margin-dilutive. A "thousands of SKUs" announcement is a strategic posture. The thing the team actually executes is not flat. It is a redistribution.

Why "thousands of SKUs" is the wrong frame

The number on the slide is for investors. The number that matters on Monday morning is a much smaller one: how many SKUs in your assortment genuinely move basket behaviour when their price falls, and how many do not. In most mid-sized retail assortments the answer is somewhere between five and twelve percent. The rest of the SKUs you might cut will cost you margin without buying anything you can measure.

NielsenIQ's most recent print has inflation easing from 3.9 to 3.5 percent and 40 percent of global consumers still saying they are being cautious about spend. McKinsey's framing of the disinflationary era is blunt: the days when raising prices in line with cost was a guaranteed path to growth are over. The mirror image is also true. Cutting prices in line with a CEO promise is not a guaranteed path to volume.

The job is not to cut prices. The job is to redistribute margin so the cuts that get announced loudly are funded by raises that nobody notices.

The four-bucket SKU classifier

Before any number changes, every SKU in scope needs to land in one of four buckets. This takes a category manager less than a day if the data is in one place, and it is the single decision that separates a clean execution from a margin-leaking one.

Known-value items (KVIs). The 50 to 200 SKUs in your assortment that shoppers actually remember the price of. Milk, eggs, the headline branded soda, the entry-level white t-shirt, the on-shelf petrol. These carry your price perception. When the press release says "price cuts on thousands of products," KVIs are the SKUs the press release is actually about. Cut them visibly, telegraph the move on shelf and in flyers, and accept the gross margin hit because the perception lift is what you are buying.

Traffic drivers. The 5 to 10 percent of SKUs below KVIs that draw store visits or category clicks without being household-name comparators. Cut them moderately, two to four percent, and use them to extend the price-cut story across more shelves than KVIs alone would cover.

Margin anchors. The 15 to 25 percent of SKUs that carry the category's profit. Typically mid-tier branded items where shopper price sensitivity is moderate and private-label competition is weaker. Hold these flat. If the data supports it, raise them 1 to 3 percent inside the same window as the headline cuts. This is where the offset gets paid for.

Long-tail. Everything else. Low velocity, often low elasticity, often forgotten. Most of the assortment by SKU count, a fraction of it by sales. Leave alone or, where the data supports it, raise selectively. The shopper rarely notices. The P&L does.

The four buckets do not need a model. They need transactional sales data, a competitor price index, and a category manager who knows the assortment. Where the data is missing, the assumption is that the SKU is long-tail until proven otherwise.

The elasticity question most teams skip

Static price elasticity, the kind that says "a 10 percent cut yields 8 percent more units," is the right starting point and the wrong place to stop. Two reasons it misleads on a portfolio program.

The first is that cross-product elasticities matter more than own-product elasticities for any SKU with a credible substitute on the same shelf. Cut the price of the 1.5L cola and the 2L cola will lose units even though you did not touch it. If your offset plan was to raise the 2L cola, your offset is now smaller than your model predicted. The pairs that share a substitution edge need to move together, or they need explicit decisions to stay apart.

The second is that elasticity is not stable across price points. The SKU that pulls 8 percent more units at a 10 percent cut may pull only 3 percent more at a 20 percent cut, because at some point you cross a psychological threshold and the next unit of cut buys nothing. The team that ignores this overshoots the deepest cuts and undershoots the cheap ones.

The practical move, if you do not yet have a working elasticity layer, is to pilot. Two weeks, two to three regions, five to ten percent of the SKUs in scope. Measure unit lift, basket attach, and category margin contribution side by side with control regions. The pilot will not tell you the elasticity of every SKU. It will tell you whether the four-bucket classification was right.

The basket-level math

Unit economics is where most price-cut programs are still scored, and it is the wrong altitude. The number that decides whether a portfolio price cut funds itself is basket gross profit, not SKU gross profit.

A worked example. Cut the headline milk by 8 percent. Unit margin on milk drops from 18 to 10 percent. Volume lifts 6 percent. SKU-level, you are losing money on milk. Basket-level, the question is what else is in the basket. If milk baskets historically attach to cereal, bread, and coffee at a 78 percent rate, and those attached items are priced at their normal margin or, after this exercise, at a one-point lift, the basket gross profit improves even as the milk line bleeds.

The category manager who measures only at SKU level will reverse the cut after four weeks. The category manager who measures at basket level will hold it and find more like it.

Three numbers worth instrumenting before the cuts go live: basket gross profit on baskets containing the cut SKU, attach rate of cut SKUs to margin-anchor SKUs, and category gross profit by store. If the team only has time for one, it is the second one. A KVI cut that does not change attach rate is a KVI cut that did not work.

What to offset, and where it is dangerous

Three places offset can come from in a category, in declining order of safety.

The safe place is the long-tail raise. Pick the 30 to 50 percent of SKUs in scope with the lowest velocity and the lowest competitor price exposure. Take one to three percent on each. No shopper has a price memory of these. Competitors do not benchmark them. The aggregate margin recovery is meaningful, and the risk of perception damage is close to zero.

The moderate-risk place is the margin-anchor raise. The mid-tier branded SKUs that carry category profit can usually absorb a one-to-two-point lift if the headline KVIs have just been cut. Shoppers comparing across the category see lower prices on the prominent SKUs and assume the rest moved with them, which they did not. This works for one cycle. Two cycles in a row and the perception breaks.

The dangerous place is the private-label raise. It is tempting because private label is the highest-margin part of most categories and the brand owner is internal. It is dangerous because private label is the place shoppers are trading down to during disinflation. NielsenIQ's own data has private-label units up 1 percent against branded units down 2.2 percent, with premium store-brand growth in the high teens in the UK, Poland, and Italy. Raising private-label prices while cutting branded headlines reads to shoppers as a bait-and-switch the moment they notice it, and they will notice it. If the offset has to touch private label, touch it on the long-tail SKUs only, never the headline lines.

What this playbook doesn't fix

Three honest limits worth saying out loud, because the slide deck will not.

A portfolio-wide price cut does not fix a structural cost-of-goods disadvantage. If you are buying chicken at 12 percent over your nearest competitor's landed cost, no amount of clever bucketing will close that gap. The cut buys you a perception window. The window closes if the underlying gap does not.

It does not reset competitor perception in ninety days. Price-perception data, measured properly, moves on quarters and years, not weeks. The team that expects a brand tracker spike six weeks after the cuts will not see one. The win is in basket size and traffic, both of which move faster.

And it is not the right play if gross margin is already below the sector median. Cutting from a structurally thin base is how mid-market retailers stop being able to fund the operating expenses that keep the doors open. If the CFO has not modelled a downside case where elasticities come in 30 percent below plan and the cuts hold for a full year, the program is under-modelled.

A five-step workflow for the next sixty days

One way to land the plan inside a single category, on a clean weekly cadence.

1. Week 1 - classify and instrument. Drop every SKU in scope into one of the four buckets. Wire the three basket-level metrics so that week-two reads have a baseline. Agree the offset list before the cuts list.
2. Week 2 - pilot. Move five to ten percent of the in-scope SKUs in two to three regions or store clusters. Use the regions you would defend in front of the executive committee, not your weakest ones.
3. Weeks 3 to 4 - read and refine. Read the pilot at basket level, not SKU level. Re-bucket the SKUs the pilot got wrong. Confirm the offsets are not eroding.
4. Weeks 5 to 8 - wave the rollout. Three waves, each one bigger than the last, with a week of read between waves. Do not roll the whole assortment at once. The team that does cannot diagnose what fails when something fails.
5. Weeks 9 to 10 - lock in the offsets and rewire the rules. If the offset SKUs are holding their new prices and basket gross profit is up, encode the rule into the pricing engine so the next time costs shift, the offsets move automatically with them. The cuts then stop being a campaign and start being how the category is run.

The category managers who land these programs well do two things differently. They classify before they cut, and they measure baskets, not SKUs. The category managers who do not land them well skip the classifier, run a flat percentage across the in-scope set, and reverse half of it inside the quarter when the SKU-level margin report goes red.

This is the moment where pricing software, used well, pays its keep. Rules-based pricing maintains the four-bucket logic automatically as costs and competitor prices move. An optimization layer on top adds elasticity-driven recommendations on the SKUs where the four buckets are not crisp. Together they replace the spreadsheet that the category manager would otherwise be rebuilding every Monday for the next sixty days. The companion piece on weekly cost-letter triage covers the upstream half of this same workflow.

If you are walking into a portfolio price-cut program in the next quarter, the four metrics worth tracking from day one are basket gross profit on the cut baskets, attach rate of cut SKUs to margin anchors, category gross profit by store, and the velocity-weighted price index against your two closest competitors. Get those four wired before the first SKU moves. The rest of the playbook follows.