Skip to content

Build Not yet confirmed elsewhere1 publisher 3 min read Published

Decathlon swapped weekly DeepAR retraining for a six-month fine-tune of Chronos-2

The retailer benchmarked several time series foundation models over 101 rolling cutoffs of its own catalogue, and the one it shipped now covers both the 12-week and 52-week horizons that two separate models used to split.

The Engineer · Build desk

How we use AI Send a correction

Illustration accompanying Decathlon swapped weekly DeepAR retraining for a six-month fine-tune of Chronos-2
Generated illustration

What happened

  • Decathlon evaluated multiple time series foundation models against its production baseline and selected Chronos-2 as a core component of its demand forecasting stack, in a post co-written with AWS.
  • The system runs weekly across supply zones including Europe, India, China, South East Asia and Latin America, with up to 25,000 products in each and the Middle East and Africa still to come.
  • From 2021 to 2024 the stack paired SageMaker AI DeepAR for weeks 1 to 16 with Holt-Winters for weeks 17 to 52, and DeepAR was retrained every week to track recent trend shifts.
  • The bake-off ran 101 rolling cutoffs from week 48 of 2022 to week 44 of 2024, scoring 12-week and 52-week forecasts primarily on weighted absolute percentage error.
  • Decathlon reports that Chronos-2 in zero-shot mode matched or surpassed its fully trained production baseline, and that several other foundation models approached or exceeded it too.

Why it matters

  • cost Scheduled training drops from about 52 runs a year to two, so the spend and the on-call surface move from a retraining pipeline to inference and evaluation, where a quietly degrading week is harder to notice.
  • capability Usable zero-shot accuracy is what lets a new supply zone forecast before it has enough local history to train on, which is precisely the extra engineering that made each region its own project.
  • decision With one model covering both horizons, the week-16 handoff between two model families disappears, and so does the fault isolation it provided: one bad run now touches supplier orders and capacity plans together.
  • exposure Teams copying this choice from the AWS write-up are trusting a summary, because the model-by-model comparison sits in Decathlon's separate Medium analysis rather than in the post making the recommendation.

Start with the retraining cadence, because that is where the operational bill changes. DeepAR was retrained every week specifically to adapt to recent trend shifts [8]. Chronos-2 is fine-tuned once every six months [16], which is roughly 26 weeks between weight refreshes [22]. That moves the job of tracking a trend break out of the training loop and into the context the model is handed at inference time. Under the old design, a demand shift in March was in the weights by the following Monday. Under the new one, it has to be read off the recent history of the series. That is a reasonable trade if the model reads context well, and it is the behaviour I would regression-test hardest before putting it in front of purchase planners.

The second structural change is the seam. From 2021 to 2024 the stack ran DeepAR for weeks 1 to 16 and Holt-Winters for weeks 17 to 52 [8], so the 12-week replenishment forecast that feeds supplier orders [4] sat entirely inside the deep model, and the 52-week capacity view [5] came from something else. Covariates only enter the story in 2024, with Temporal Fusion Transformer for long-horizon accuracy [9]. One model now spans both horizons at weekly frequency [13].

The evaluation is the part worth copying. Week 48 of 2022 to week 44 of 2024 is about 100 weeks, and Decathlon ran 101 rolling cutoffs across it [11], so the cutoffs sit one week apart and the backtest replicates the production cadence rather than sampling convenient dates [21]. About 25,000 products appear per cutoff against 39,000 unique series over the full window [12]. That difference is roughly 14,000 series entering or leaving, about 56 percent of a single cutoff's panel [20]. Catalogue churn on that scale is exactly why the zero-shot result matters: new products arrive with no history, and weights refreshed twice a year will not have seen them [15]. At least five named supply zones at up to 25,000 products each is up to 125,000 series per weekly run [23].

For the numbers to transfer, your baseline has to look like theirs. Decathlon's production comparator was a global deep model retrained weekly [8], not a per-SKU statistical fit, so a shop still running per-item exponential smoothing is not reading its own bake-off here. WAPE is volume-weighted [14], which means high-volume lines dominate the headline figure and a long tail of single-store items can be badly wrong without moving it. Weekly frequency, strong seasonality across more than 80 sports [18], and horizons of 12 and 52 weeks are the shape of the workload the result was measured on.

The AWS post says fine-tuned Chronos-2 beat every other evaluated model at both horizons and that fine-tuning cut error by several percentage points [1][24], but the model-by-model figures sit in Decathlon's own analysis on Medium [17]. For a decision that ends in supplier orders, that is one hop further from the evidence than I would like.

What to watch

  • Whether Decathlon publishes per-model WAPE deltas at 12 and 52 weeks rather than 'several percentage points'.
  • Whether the Middle East and Africa zone goes live zero-shot or waits for a fine-tune, which tests the portability claim directly.
  • Whether the six-month fine-tune interval survives a season with a sharp trend break in a major sport.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence52
Adoption58
Hype gap+22
Incentives85
Confidence56
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    In Decathlon's published benchmark results, fine-tuned Chronos-2 consistently outperformed all other evaluated models across both horizons.

    Reported Supported Source: Decathlon, via AWS blog2 sources— create a free account to open themView cited source
  2. [2]

    After evaluating multiple time series foundation models, Decathlon selected Chronos-2 as a core component of its forecasting stack.

    Reported Supported Source: AWS Machine Learning Blog, co-written with DecathlonView cited source
  3. [3]

    The AWS blog post describing the deployment was co-written with Vianney Bruned, Filippo Giruzzi, Belkiss Saidi and Carlos Ramirez of Decathlon.

    Reported SupportedView cited source

Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.

Add to ChatGPTAdd to Claude

Sources

1 independent publisher whose own reporting we read for this story.

  1. aws.amazon.com

    1 article · August 28, 2026

    How Decathlon runs demand forecasting at scale with Chronos-2

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

  • Retail Demand ForecastingFollow
  • Retraining Cadence And ML OperationsFollow
  • Supply Chain Machine LearningFollow
  • Time Series Foundation ModelsFollow
  • Benchmarking On Private Production DataFollow

Entities

Loading related stories