Markdown Waves That Don't Destroy Margin: A Fashion Pricing Playbook

Fashion is the only category in retail where a price decision made in week one of a 12-week season has irreversible consequences by week six. Every other category gets second chances - if a grocery item is priced wrong this week, the team fixes it next week, and the customer base mostly doesn't notice. In fashion, the wrong price in week one shows up as either lost margin or unsellable inventory four-to-six weeks later, after the natural sell-through curve has already done most of its work.

That asymmetry is what makes fashion markdown management uniquely hard - and uniquely high-value when it's run well. A fashion category running disciplined markdown waves typically holds two to four percentage points more total-season margin than the same category running reactive markdowns, on the same line plan and the same buy. The discipline isn't glamorous. It's the four pillars below, applied consistently across thousands of styles, every week, for a 12-week clock.

Why fashion is different from everything else

Three structural features of fashion pricing don't appear in other categories.

Time-limited shelf life. A fashion style has a life expectancy measured in weeks, not months or years. After the season window closes, the residual value of leftover inventory drops sharply - sometimes to zero, sometimes to whatever a clearance jobber will pay. That shape compresses the pricing window in a way grocery, hardware, or auto parts simply don't experience.

Size-curve asymmetry. A style isn't a single SKU - it's typically 5-8 size variants, and the variants don't deplete uniformly. By week four, the team often has zero M and L left, and a wall of XXL still on the shelf. A blanket markdown on the style wastes margin on sizes that would have sold at full price. A size-specific markdown is what the playbook eventually has to support.

Buy commitment ahead of demand signal. The buy decision was made months before the season, against a forecast that's now stale. Whatever the team learns about actual demand in weeks one-to-three has to be acted on in weeks three-to-six, because there's no way to reorder a style mid-season at the original cost. The markdown calendar is, in effect, the team's only lever to react to demand reality once the buy is committed.

These three features make fashion pricing a planning problem more than a tactical problem. The teams that win at it are the teams that have decided the markdown rules before the season starts, and apply them mechanically as the season unfolds.

The four pillars of a markdown calendar

The teams whose markdown calendars hold up over multiple seasons run the calendar against four explicit triggers. Each trigger is measurable, has a defined threshold, and produces a deterministic action. The combination is what produces consistency at scale.

Pillar 1: Sell-through rate. The percentage of original buy sold by a given week of the season. Each style is tagged with an expected sell-through curve at buy time (often "35% by week 4, 65% by week 8, 90% by week 11" for a typical 12-week season). Styles tracking below expected sell-through by week 3-4 are flagged for the first markdown wave. The threshold is explicit - say, 80% of the curve - and the same threshold applies across all styles in the category.

Pillar 2: Weeks-on-shelf. The age of the inventory. Even styles that are on-curve for sell-through trigger a calendar-based markdown at fixed points (often week 6 and week 9 of a 12-week season). The reasoning is simple - the remaining sell-through has to happen on a shorter clock as the season ages, and the marginal markdown earlier is cheaper than the deeper markdown later.

Pillar 3: Size-curve depletion. The distribution of remaining inventory across sizes. A style that's sold out of M-L but stuck with XXL doesn't need a 30% markdown across the whole style - it needs a 40% markdown on XXL and no markdown on the rest. The size-curve trigger is the pillar most teams skip because the operational complexity is real, and it's where the biggest margin recovery sits.

Pillar 4: Calendar boundaries. The hard end-of-season cutoff and the start-of-clearance boundary. Inventory still on the floor at the season cutoff transitions to a different pricing regime (clearance, outlet, jobber). The markdown calendar leading up to the cutoff has to deliver the target sell-through, because the cost of crossing the cutoff with leftover inventory is much higher than the cost of one extra wave.

A working markdown calendar is the combination of all four. Sell-through-only is too slow to react. Calendar-only is too blunt. Size-curve-only is impossible to implement without the other three running first. The discipline is to define the threshold on each pillar before the season, and then let the engine fire the action when the threshold trips.

Waves or rolling? The debate that doesn't matter much

Most pricing teams in fashion have a strong opinion on whether markdowns should run as discrete waves (every two weeks, the whole category gets reviewed and the qualifying styles get marked down) or as rolling triggers (each style hits its threshold independently and gets marked down the same day). Both approaches work; the gap between them is smaller than the gap between either of them and an unstructured approach.

Waves are easier to communicate to merchandising and easier for the consumer to anticipate. The cost is that a style that should have been marked down on week 5 sits at full price until the week 6 wave. Rolling triggers are more responsive and capture slightly more margin, at the cost of a less legible consumer-facing rhythm and more operational complexity in the team's workflow.

The right answer for most mid-market fashion retailers is a hybrid - rolling triggers for the size-curve depletion pillar (it has to be responsive) and biweekly waves for the sell-through and calendar pillars (the consumer-facing rhythm and the team's review cadence both benefit from the regularity). The right tool surfaces the recommendations either way and lets the team decide on a case-by-case basis.

The regret math

One framing helps fashion pricing teams more than any technique. Every markdown decision is a tradeoff between two regrets: the regret of marking down a style that would have sold at full price (margin regret) and the regret of holding a style at full price that ends up on clearance at a deeper discount (sell-through regret).

The mid-market reality is that sell-through regret is almost always larger than margin regret, because the residual value of unsold inventory at season end is materially below the marked-down price. A style sold at 25% off in week 6 contributes more than the same style sold at 60% off in week 14, and the latter is the alternative path for inventory the team held too long. The math favors marking down a little too early on a little too much inventory, not the reverse.

This framing changes the operating posture. Teams that internalize the regret math tend to set sell-through-rate thresholds slightly looser (mark down at 80% of expected curve rather than 70%), apply markdowns slightly earlier in the season (week 4 instead of week 6), and accept that they'll occasionally mark down styles that would have sold at full price. The aggregate margin outcome over a season is consistently better than the aggregate margin outcome of a team trying to optimize each individual style.

This is also where rules-based pricing actually pays for itself in fashion - the discipline of applying the same threshold consistently across thousands of styles, without exception, is what produces the season-level margin lift. Human teams, asked to mark down a specific style they had high hopes for, almost always wait a week longer than the framework would have. That delay compounds across the catalog.

Size-curve depletion in practice

The size-curve pillar is the one most teams skip, and it's worth being specific about why and how to do it.

The reason teams skip it is that the operational complexity is real. Setting a single markdown price on a style is one decision; setting six prices on the same style (one per size) is six decisions, with the visual-merchandising and consumer-perception complications that come with displaying multiple prices for the same item. Most ecommerce platforms can handle size-level pricing technically; most consumer-facing UX choices around it are awkward.

The way that works in practice is to set the markdown on a small number of sizes rather than every size, and only when the size-curve depletion is genuinely lopsided. A style with 85% sell-through on M-L and 20% sell-through on XXL is a candidate for an XXL-only markdown. A style with relatively uniform depletion across sizes isn't - mark it down at the style level or not at all. The threshold for triggering a size-specific markdown should be deliberately high (say, 50 percentage-point gap between best- and worst-selling sizes), so that the team isn't constantly running size-specific markdowns the consumer can't make sense of.

For the styles that do qualify, the size-specific markdown is one of the highest-margin recoveries available in fashion pricing. The XXL inventory that would otherwise go to clearance gets cleared at a manageable discount; the M-L inventory holds full margin.

Full-price to sale transitions

The other inflection point in fashion pricing is the transition from full-price retail to sale - the moment a style stops being part of the current season and starts being a clearance asset. Most teams under-invest in this transition, and the cost shows up as margin leakage on either side of the line.

The two failure modes are mirror images. Transition too early, and the team is signaling "this whole season is on sale" to the consumer, which depresses margin on styles that were still selling at full price. Transition too late, and the cliff at season end is steeper because the inventory is older and the residual value is lower.

The discipline that works is to make the transition explicit and bounded - a defined week of the season, a defined depth, and a defined product scope. Styles transitioning to sale this week get a specific markdown depth (often 30-40%) and a clear shelf or page placement that signals "sale" without contaminating the still-current part of the assortment. The styles staying at full price retain their original presentation and pricing.

This is where the explainable side of agentic pricing matters most. Every style at the transition boundary should be a deliberate decision the team can defend - which styles are going, which are staying, what the depth is on each, and why. The audit trail is the difference between a season the team can debrief and a season they can only describe.

An explainable playbook

Pulling the four pillars together into a season playbook:

• Pre-season (week -2 to 0): Set sell-through curves per style at buy time. Define markdown wave dates and depths. Set size-curve depletion thresholds. Publish the season pricing policy internally.
• Weeks 1-3: Hold full price. Let the demand signal develop. Monitor sell-through against the curve. Flag styles trending more than 20 percentage points below curve for the first wave.
• Week 4 (first wave): First markdown wave on flagged styles. Typical depth 15-20%. Re-baseline sell-through expectations.
• Weeks 5-6: First check on size-curve depletion. Flag styles with 50+ percentage point size-curve gaps for size-specific markdowns.
• Week 7 (second wave): Second markdown wave. Typical depth 25-30%. Size-specific markdowns applied to qualifying styles.
• Weeks 8-9: Calendar-trigger review. Styles still on the floor with low remaining-weeks margin get the third wave - 35-40% depth.
• Week 10: Full-price-to-sale transition for designated styles. Clear visual separation.
• Weeks 11-12: Final clearance push. Whatever's left at the season cutoff transitions to outlet, jobber, or carryover.

The depths and timings vary by category - jackets and outerwear run different cadences than t-shirts and basics - but the four-pillar structure stays the same. The cadence is the protection against the human tendency to wait a week longer than the framework would have.

For a deeper view of how the markdown workflow runs in the Retailgrid workspace - sell-through tracking, wave planning, size-curve depletion, and full audit trail - see the markdown and clearance use-case page. For the broader fashion-pricing capability set, including the in-season grid, see Retailgrid for fashion retailers.

Want to see what the markdown engine looks like on a sample fashion dataset? Talk to the Retailgrid team - we'll run a real 12-week season simulation against your line-plan structure.