A slow-selling product leaves a retailer with an awkward choice. Hold the price and risk ending up with stock nobody wants, or cut it and give away margin that might still have been earned.
So clearance pricing is about more than putting a red sticker on old stock. A good retail markdown strategy has to answer a harder question: what is the smallest price reduction that will move the inventory in the time available?
Mark an item down too early and the retailer loses margin it didn't need to lose. Wait too long and even a deep cut may not clear what's left before the product stops being relevant. For a retailer managing hundreds or thousands of SKUs, getting this balance right affects both inventory turnover and gross margin.
What is markdown pricing in retail?
Markdown pricing is a reduction in an item's selling price, usually made because the original price isn't producing the sell-through the retailer wants.
The reasons vary. Seasonal products approach the end of their selling window. A new model replaces an older one. One color or size sells more slowly than the rest of a range. Grocery items have limited shelf life left. In each case the inventory is worth less as time passes, and a markdown lets the retailer turn it into sales before its value drops further.
An inventory markdown is also a different thing from a promotion. A weekend promotion may aim to bring in traffic or increase basket size, while a clearance markdown usually has an inventory goal behind it. Shopify draws a similar line between markdown decisions on slow-moving or time-sensitive stock and broader promotional activity.
Why the discount percentage is the wrong starting point
Retail teams often open the markdown discussion with a number. Should this item be 10% off? Would 20% move it faster? Should the store go straight to 40%?
That starts the decision in the wrong place. Before choosing a discount, the retailer needs to understand the inventory problem behind it.
Take two jackets that have each sold 60% of their stock. On paper they look identical. The first has eight weeks of selling season left, the second only two. They shouldn't necessarily get the same markdown. The second has far less time to convert its remaining stock, and waiting another week could force a much deeper clearance later.
Effective markdown management usually looks at several variables together:
- current inventory
- recent sales velocity
- expected future demand
- remaining selling period
- product cost and margin
- store or regional performance
- incoming replacement inventory
- the retailer's target exit date
Modern pricing systems increasingly use these signals instead of applying one discount percentage across a whole category.
A better way to think about markdown timing
Waiting until an item is clearly dead stock feels safe, since full-price selling stays open for longer. In practice it can be expensive.
Say a store has 400 units of a seasonal product left with six weeks in the selling window, and at the current price it sells 40 units a week. If demand holds, about 160 units will still be on the shelf when the season ends.
The retailer could wait four weeks and then put a very deep discount on whatever remains. Or it could make a smaller adjustment now and try to lift sell-through while the product still matters to shoppers. Neither approach is universally correct, but the second one shows the principle: a markdown should reach an inventory target while giving up as little margin as necessary, and the biggest possible sales spike is not the goal in itself.
McKinsey notes that stronger markdown processes commonly use phased reductions, starting with a smaller cut and reviewing product performance before deciding whether another is needed. That makes markdown management an ongoing process rather than a single pricing event.
Blanket clearance pricing often wastes margin
Products respond differently to the same price change, and even one SKU can perform differently between stores. A winter coat may be moving slowly in one location and selling comfortably in another. A shoe style might be overstocked overall while one size is nearly gone.
Applying the same markdown everywhere creates two problems. In weak locations the cut may not be big enough to clear the stock. In strong locations the retailer may discount products that would have sold at full price anyway.
That is why markdown decisions increasingly need to work below the category level. McKinsey has pointed to the limits of a uniform pricing approach across products and locations, particularly when item-level and store-level performance differ. For a multi-store retailer, a workable retail clearance strategy starts with a more specific question than "Should we mark this SKU down?" It asks where this SKU actually needs a markdown.
Progressive markdowns can protect more margin
Many retailers use several markdown stages instead of going straight from full price to final clearance. A simplified sequence runs from full price to a first markdown, then a second markdown, then final clearance.
The percentages depend on category economics and demand, but the logic is simple. The first markdown tests whether a modest cut can speed up sell-through. If stock starts moving fast enough to meet the exit target, there may be no reason to cut again. If it stays weak, the next markdown comes in. Each step gives the retailer another chance to sell inventory without immediately giving up the maximum margin.
What matters is watching what happens after each change. A calendar that says "20% this week, 40% two weeks later and 60% at the end of the month" is still mostly a fixed schedule. A stronger approach compares actual sell-through with the target and adjusts the next decision to match. SAP's retail markdown planning model follows the same basic principle: retailers can compare planned and actual results and change the markdown plan as sales performance shifts.
Markdown decisions should have an exit target
Decide when the inventory needs to be gone. Without an exit date, teams tend to judge markdowns by whether sales went up, and higher sales after a discount don't automatically mean the strategy is working.
Suppose a retailer needs to clear 1,000 units over four weeks. After the first markdown, weekly sales rise from 100 units to 150. Demand did increase. But at that pace the retailer sells only 600 units in four weeks, so the markdown still falls short of the actual inventory objective.
An exit target makes the decision measurable. The retailer can ask how many units remain, how many selling days are left, what sell-through rate is now required, and whether the current price delivers it.
Clearance pricing is also an execution problem
Even a well-designed markdown can fail at store level. Head office approves a new price, the POS system receives it, the promotion appears online, and the shelf still shows yesterday's price. This gets harder when a retailer runs frequent markdowns across many SKUs or stores.
Paper labels add a physical step to every price change. Someone has to identify the affected products, print the labels, find the right shelf positions and swap them correctly. For an occasional clearance event that's manageable. When pricing changes by SKU, location and time, execution gets much harder, and the more granular the strategy becomes, the more the link between pricing decisions and the shelf matters.
Where electronic shelf labels change the equation
Electronic store labels don't decide which product should be marked down. That belongs to the retailer's pricing, merchandising or inventory systems. What ESLs change is the cost and speed of carrying out the decision in the store.
When an ESL system is integrated with the retailer's pricing environment, approved changes go out digitally and staff no longer have to replace individual paper labels. That makes more flexible markdown strategies practical. A retailer could, for example, reduce a product only in stores where inventory is building up, schedule a second markdown for a set time, or update a large group of clearance items without preparing hundreds of printed labels.
It also lets retailers make pricing decisions at a more useful level of detail without creating much extra work for store teams.
Keeping shelf price and selling price in sync
Retailers moving to more dynamic markdown processes should decide which system holds the authoritative price and how changes reach ecommerce, POS, shelf displays and other customer-facing channels. In ESL deployments this architecture deserves as much attention as the labels themselves, because fast updates only help when the price being sent is the right one.
