RETAIL

APPAREL

Markdown Optimization at Scale

How a €620M European apparel retailer recovered €7.8M of margin across 320 stores — by replacing calendar-driven markdowns with sell-through-driven optimisation.

€620M Revenue

320 Stores

16 Week Engagement

5 Countries

EU Apparel

€7.8M

Margin Recovered (annualised)

+4.2 pts

EOS Gross Margin

−31%

Deep Markdown Units

2 seasons

To Steady State

Illustrative case based on engagement patterns from European apparel retail. Specific business details, names, and exact figures have been adapted to preserve client confidentiality.

The Challenge

A €620M European apparel retailer operating 320 stores across five countries had been running calendar-based markdowns for fifteen years. The schedule was uniform: week 6 = 20% off, week 9 = 30%, week 12 = 40%, week 14 = 50% — applied uniformly across assortment, stores, and regions, with manual merchant override authority rarely used at scale.

End-of-season margin had deteriorated for four consecutive years. The CFO’s seasonal P&L review consistently showed markdown destroying 17–20% of season-start gross margin. The number had become accepted as the cost of doing business in apparel retail. Merchandising teams pushed back on changes, arguing the calendar provided commercial predictability for next-season planning.

The CEO commissioned a strategic review with two questions: was the markdown spend recoverable, and could the recovery happen without disrupting the planning rhythm the merchandising team needed?

Diagnosis

Calendar-driven markdown was producing systematic over-markdown

A retrospective analysis of two prior seasons showed that approximately 37% of styles received their first markdown more than 4 weeks after their sell-through trajectory had clearly indicated they would need one. Those styles ended up requiring deeper markdowns at week 12–14 than they would have needed at an earlier intervention.
Conversely, approximately 24% of styles received markdowns on the calendar even though their sell-through trajectory predicted they would have cleared at full price within the season. These markdowns were direct margin loss with no commercial rationale.

Pan-store markdown was masking regional variation

When sell-through was decomposed by store cluster (defined by region, customer demographic, and historical sell-through pattern), substantial intra-style variation emerged. The same winter coat that sold cleanly at full price in northern stores was sitting in southern stores at 40% sell-through by week 8. The pan-store 25% markdown applied at week 9 was insufficient to clear the southern inventory and unnecessary to clear the northern inventory.

The data infrastructure was workable

The retailer’s ERP and merchandising systems contained: style-week-store sales, weekly inventory positions, regional weather, marketing-promotion calendar, and competitor markdown observations from a third-party tracking service. The data was structured, current, and — critically — already feeding into the existing markdown calendar logic. The required transformation was not a data infrastructure project; it was a decision-logic project on top of existing data.

What the diagnostic suggested

A markdown optimisation programme that triggered on sell-through projection rather than on calendar position, differentiated by store cluster, with merchant override authority preserved — was implementable in a single season cycle and would produce material margin recovery without disrupting the merchandising team’s next-season planning rhythm.

Approach

Workstream 1 — Demand Projection

Style-level end-of-season sell-through projection under current price, using recent trajectory, historical style matching, weather, and category seasonality. Output refreshed weekly with confidence intervals.

Workstream 2 — Markdown Response Curves

Per category, store-cluster level estimate of how sell-through responds to markdown depth. Historical events with counterfactual controls to calibrate lift curves.

Workstream 3 — Sequential Optimisation Engine

Model that recommends markdown depth and timing to minimise total margin sacrifice while achieving target end-of-season inventory clearance per style × store-cluster.

Workstream 4 — Merchant-in-the-Loop UI

Workflow embedded into existing merchandising system: sell-through trajectory, model projection under no-action vs recommended action, override logging and feedback loop. 22% override rate, preserving merchant expertise.

The Numbers

Metric	Before	After (2 seasons)	Change
End-of-season gross margin	44.6%	48.8%	+4.2 pts
Margin recovered (annualised)	—	€7.8M	+€7.8M
Stock units in 50%+ markdown	Index 100	Index 69	−31%
Avg first-markdown timing (weeks from launch)	Week 7.4	Week 6.1	−1.3 wks
Merchant override rate	—	22%	—
Season-end inventory carry-over	Index 100	Index 91	−9%

The 4.2-point margin improvement came from two structural changes: earlier first-markdown intervention (week 7.4 → week 6.1) reduced necessary depth, while store-cluster differentiation stopped unnecessary markdowns where styles were selling at full price. The 31% reduction in stock units reaching 50%+ markdown was strategically more important — it meant the model flagged troubled styles earlier and cleared them at shallower depths, reducing next-season inventory drag.

Key Lessons

Calendar-based markdown is structurally over-marking.

The two structural waste patterns — marking what would have cleared at full price, and marking too late so the eventual markdown is deeper — together account for most of the margin recovery available from optimisation. Both waste patterns are invisible in the calendar discipline. Both are visible the moment sell-through projections are computed at style level.

Store-cluster differentiation produces 1–3 points of margin even alone

Merchant adoption is the real implementation risk

The value compounds across seasons

Inventory carry-over reduction is the second-order benefit

Related Case Studies