Home

All InsightsDiscovered Thu 18 Jun

Halden & Rowe · Womenswear · Supply

Womenswear markdowns follow a replenishment lag of nine trading days — we are discounting stock the warehouse would have solved.

The correlation between markdown decisions and prior replenishment lag is tight enough to change how the trading committee sequences its Monday meeting.

EstablishedAna · Digital Retail Analyst

Observation

The pattern.

What Ana has read in the trading data — described in the language a senior analyst would use with the CEO.

Reading markdown events against distribution-centre dispatch times over the last six months, 74% of Womenswear markdowns were preceded by a replenishment lag on the same SKU of nine trading days or more. In the matched cases where the lag was closed inside seven days, the SKU cleared without markdown in 61% of instances. The relationship is one-way — markdowns without prior lag are rare, and lags without subsequent markdown are common — which points to supply timing as the trigger, not the noise.

Evidence

What Ana is reading.

Five to six pieces of supporting evidence. Each line is a signal, its measurement, and — where useful — a caveat.

  • Markdowns preceded by replenishment lag

    74% (≥9 trading days)

    Trailing six months, all Womenswear SKUs above minimum volume

  • Clearance without markdown when lag closed

    61% of matched cases

    Lag closed inside seven days

  • Preserved margin per avoided markdown

    £6,400

    Current Womenswear mix, gross of storage cost

  • Directional cleanliness

    Markdowns without prior lag are rare (12%)

    So lag is a cause, not correlation

  • DC concentration

    Two DCs account for 68% of the lag events

    Named separately in the Ops review

  • SKU concentration

    Cross-references the same three suppliers as the margin concentration Insight

    See supplier-margin-concentration

Why this matters

What changes if leadership takes this on board.

The business consequence, framed for a board conversation rather than a metric review.

Three in every four Womenswear markdowns are a warehouse problem being solved with the retail price. Every markdown avoided by moving the dispatch-lag conversation ahead of the price one is worth roughly £6,400 in preserved margin — and the lever is a Monday-morning sequencing change, not a system programme and not a headcount request.

Commercial framing

The order of magnitude.

An honest sizing of the pattern, with the methodology stated so the number can be argued with.

Order of magnitude

£380K

margin preserved by closing avoidable markdowns · next 12 months

How Ana arrived at this number

£6,400 × the trailing 12-month rate of markdown-with-prior-lag events, held at 61% avoidability.

Counter-evidence

The reasons the pattern might not generalise.

The caveats Ana would raise before an executive commits an Insight to a decision. Included by design — an Insight is only useful when its limits are known.

  • Seasonal SKUs

    Markdowns there are demand-driven, not supply-driven

    The relationship weakens on end-of-season SKUs (≤4 trading weeks left)

  • DC data quality

    The 9-day threshold is conservative for that reason

    Dispatch timestamps on one DC are known to lag by 6–12 hours

Linked across the platform

Where this Insight already touches your operating rhythm.

Missions the Insight informs, Opportunities and Prompts it reframes, and Decisions that were shaped by the same evidence.

Ana's commentary

How Ana would present this in the room.

Ana · Digital Retail Analyst

The two Insights on Rachel's desk this quarter — the supplier concentration and the replenishment lag — both point at the same three suppliers. That is a stronger signal than either Insight alone, and it argues for a single supplier-review programme rather than two parallel workstreams.

Recommended monitoring

What Ana will keep watching.

The signals whose movement would either confirm the pattern is holding or tell us it has stopped.

  1. 01

    Markdown-preceded-by-lag rate, weekly — a rise above 80% signals a DC issue, a fall below 60% suggests the sequencing change has stuck.

  2. 02

    Time between lag detection and DC ticket close — the actionable window is under seven days.

  3. 03

    Category read on the two named DCs, so the lens does not stay Womenswear-only.

Insights inform decisions. When you are ready to act, the Prompts and Opportunities linked above are the surfaces to move to.

Back to Insights