Retail Markdown Strategy: How to Reduce Markdown Risk Without Killing Sell-Through

Markdown decisions are uncomfortable because both sides of the decision can be expensive.

Wait too long and you can end up sitting on seasonal inventory with three weeks left to sell it. Move too early and you give away margin on merchandise that might have sold perfectly well at full price.

That is why markdown strategy should not start with a question like, “Should we take 20% or 30%?”

The better question is: What inventory problem are we trying to solve?

That requires looking at demand, sell-through trajectory, weeks of supply (WOS), inventory depth, location, size availability and how much selling time remains.

McKinsey points to several common markdown failures: retailers discount products that are still performing, go deeper than necessary on some items, and use discounts too shallow to clear genuinely weak ones.

Most of those mistakes have something in common. The inventory problem was either diagnosed incorrectly or diagnosed too late.

Markdown Risk Starts Before Merchandise Goes on Clearance

A markdown is the visible event. The problem usually started earlier.

Maybe the initial demand forecast was too optimistic. Maybe the buy was heavy. Maybe the total buy was reasonable but allocation put too much inventory into the wrong doors. Replenishment may have continued after demand started slowing. Or the chain bought the right style but the wrong size curve.

The sequence is fairly straightforward:

Forecast → Buy → Allocation → Actual Demand → Inventory Position → Markdown Exposure

By the time a planner is discussing clearance depth, several of those decisions have already happened.

That is why markdown management needs to be an in-season inventory process rather than an end-of-season pricing exercise.

At minimum, planners should be comparing actual performance against the original plan throughout the selling period. Sell-through versus plan matters, but it is not enough by itself. Rate of sale, WOS, inventory age, remaining units and remaining selling weeks all add context.

Consider a fashion retailer carrying the same dress across 40 stores.

At chain level, the style might look acceptable. Sell-through is a little behind plan, but nothing alarming. Dig into store and size inventory, though, and the story changes. Several stores may be carrying six or seven weeks of supply while another group is still selling through steadily. The size curve may also be broken, with core sizes moving well and fringe sizes accumulating.

A chain-wide markdown would treat all of those inventory positions as the same problem.

They aren't.

McKinsey recommends comparing current-season item performance against the original sales plan rather than treating markdowns as an afterthought. Oracle's lifecycle pricing approach similarly incorporates changing sales and inventory information into ongoing pricing decisions, with recommendations updated as conditions change.

The earlier the imbalance becomes visible, the more choices a merchant has. Transfer inventory. Slow replenishment. Adjust allocation. Promote selectively. Hold price where demand remains healthy.

Wait another six weeks and the list of choices gets considerably shorter.

Decide What Actually Needs a Markdown Before Deciding the Discount

One of the easiest ways to lose margin is to confuse “behind plan” with “needs to be marked down.”

Suppose two SKUs are both 15 percentage points behind their planned sell-through.

SKU A has ten productive selling weeks remaining, reasonable weekly velocity and inventory concentrated in stores where the category is still performing.

SKU B has three weeks remaining, declining velocity and substantial inventory sitting in low-demand locations.

On a weekly exception report, they might both show up red. Operationally, they are nowhere near the same situation.

The question is whether the current inventory can reasonably sell through at an acceptable price before the selling window closes.

That means looking at the indicators together: actual versus planned sell-through, current rate of sale, WOS, units remaining, weeks remaining and projected terminal inventory.

The last one is particularly useful. Where are we going to finish if nothing changes?

Diagnose the Inventory Problem Before Using Price to Fix It

Price should not be the first tool pulled out every time sales disappoint.

Ask why the SKU is behind.

Is underlying demand weak? Is the product simply sitting in the wrong stores? Is ecommerce selling through while stores are long? Did replenishment keep feeding locations after their demand slowed? Has the size curve broken?

Apparel and footwear teams know this problem well. A sneaker can appear overstocked at style level while the most demanded sizes are already gone. Marking down the whole style does not fix the size break. It just discounts the few desirable sizes you have left along with the inventory you actually need to clear.

Sometimes the right action is a transfer rather than a markdown. Sometimes it is holding full price in one group of stores and taking action elsewhere.

A useful operating classification is:

Hold at full price. Rebalance. Promote. Markdown.

That is much more useful than dropping every underperforming style into a clearance bucket.

McKinsey specifically recommends looking at item and store-level performance rather than taking a uniform, “peanut-butter” approach to clearance.

Markdown Timing Matters as Much as Markdown Depth

Retail teams tend to spend a lot of time debating percentage off.

Timing deserves at least as much attention.

Holding full price for another month can feel like margin protection. Sometimes it is. Sometimes you are simply burning four of the best remaining selling weeks.

Seasonal inventory has a clock attached to it.

Imagine a retailer carrying a seasonal outerwear style that is clearly tracking toward excess inventory. There is still meaningful customer demand and enough time left in the season to influence the outcome.

A modest markdown now may create enough incremental velocity to exit cleanly.

Wait until demand has naturally collapsed and the same units may need a much more aggressive reduction. The retailer technically “protected” full price for longer, but ended up sacrificing more gross-margin dollars to clear the inventory.

The practical question is:

How many units need to sell, and how much viable selling time is left to sell them?

From there, you can work backward from a desired terminal inventory position.

If current demand is likely to get you there, leave the price alone.

If it will not, intervention is warranted.

Use Progressive Markdowns, but Reforecast After Every Price Change

Progressive markdowns make sense because you do not need to commit to the deepest possible discount immediately.

The mistake is turning them into a rigid calendar.

First markdown in week one. Second markdown four weeks later. Final clearance three weeks after that.

That sequence ignores the most valuable piece of information you receive: what customers did after the first markdown.

If a modest reduction produces enough additional unit velocity to hit the exit target, there may be no reason to go deeper.

If sales barely move, waiting another four weeks because the calendar says so is hard to justify. You now have evidence that the first price change was insufficient, and every week of delay compresses the remaining clearance window.

McKinsey's markdown framework treats timing and frequency as decisions to be tested and revisited rather than fixed assumptions. Oracle's pricing workflow also evaluates markdown decisions on a recurring basis rather than treating pricing as a one-time event.

This is where forward-looking inventory monitoring becomes much more useful than another spreadsheet full of historical sell-through. A planning platform such as Flagship can help surface where current demand is taking an SKU before the inventory problem becomes obvious on a clearance report.

The planner still makes the commercial call. The advantage is making it while there are options left.

Choose Markdown Depth Based on the Inventory Outcome, Not a Standard Percentage

“Start at 20%” is not a markdown strategy.

Twenty percent is useful only if it changes demand enough to produce the inventory outcome you need.

The required depth depends on several things: current inventory, remaining selling time, expected full-price demand, desired sell-through, prior price response and the margin economics of the item.

Products also respond differently to price.

Some items get a meaningful lift from a relatively shallow reduction. Others barely respond until the price reaches a very different value point.

So the decision is not simply whether 20%, 30% or 40% sounds appropriate. It is what each price is expected to do to unit demand and terminal inventory.

Take the same seasonal SKU in two situations.

With eight selling weeks remaining and moderate excess inventory, a shallow intervention may be enough. There is time for the additional weekly units to accumulate.

With two weeks remaining, that same excess position is far more serious. The required demand lift is much larger because there are fewer selling days left. A deeper markdown may now be economically rational even though it would have been unnecessarily destructive six weeks earlier.

There is also a useful distinction between promotion and markdown. A promotion is temporary. A markdown is generally a permanent price reduction associated with lifecycle or clearance management. Oracle makes that distinction explicitly in its lifecycle pricing documentation.

The objective is not maximum sell-through regardless of cost.

It is to move enough inventory while protecting as many gross-margin dollars as the situation still allows.

Protect Margin by Making Markdown Decisions at the Right Level

Chain-wide numbers can hide surprisingly different inventory realities.

A jacket might be badly overstocked in warmer markets while still selling at full price in colder locations. Ecommerce might be absorbing inventory faster than stores. A footwear style might look slow because sizes 5 and 12 are piling up while sizes 8 through 10 are effectively sold out.

Applying one markdown to all of that inventory is convenient.

Convenience can be expensive.

Before reducing price everywhere, planners should ask whether inventory can be rebalanced toward locations or channels where full-price demand still exists. Transfers have costs, of course. Freight, handling, store labor and the amount of remaining selling time all matter. Moving four units across the country to avoid a small markdown may make no economic sense.

But neither does marking down hundreds of units because some of them happen to be in the wrong stores.

The same principle applies to size-level planning.

Once core sizes disappear, the demand curve for the remaining inventory changes. Looking only at style-level WOS can give a false sense of inventory health or risk. For apparel and footwear retailers in particular, size-level forecasting can expose markdown risk that aggregate style metrics miss.

There is a practical limit to granularity. Stores cannot execute an infinitely complex pricing strategy. Signage, ticketing, systems and customer experience matter. The goal is not a different price for every unit.

It is enough precision to avoid dragging healthy demand pockets into clearance unnecessarily.

Both McKinsey and Oracle's frameworks recognize that markdown decisions can differ by item and location or price zone rather than being applied uniformly across an assortment.

Measure Whether the Markdown Worked and Feed the Result Back Into Planning

A 95% sell-through rate does not automatically mean the markdown strategy worked.

You can get to 95% by giving away too much margin.

The opposite is also true. Protecting gross-margin percentage while carrying obsolete seasonal stock into the next season is not a victory.

Measure the actual inventory and financial response: incremental unit velocity, sell-through versus target, markdown dollars, gross-margin dollars, WOS, ending inventory and the response after each markdown event.

Then use that information upstream.

If a category repeatedly needs aggressive clearance, investigate the original forecast and buy.

If the same store cluster consistently ends the season long while another cluster stocks out, allocation deserves attention.

If core sizes repeatedly disappear early while fringe sizes accumulate, the size curve needs to change.

If the first markdown consistently produces almost no demand response, question the timing, depth and assumptions about price sensitivity.

That creates the loop retailers actually need:

Plan → Monitor → Diagnose → Markdown → Measure → Replan

McKinsey describes markdown management in similar terms: set targets, segment merchandise, optimize clearance decisions, execute, track the result and adjust. Oracle likewise describes lifecycle pricing as an ongoing process informed by updated sales and inventory information.

A good markdown strategy is not the one with the fewest markdowns.

It is the one that identifies inventory risk early enough to preserve choices.

Because once you are sitting on twelve weeks of supply with three weeks left in the season, you are not really optimizing anymore. You are clearing inventory.

The work that protects margin happens before you get there.