Decathlon — Sports Retail Smart Warehousing

01The Core Tension in Multi-Site Rollouts

Every country Decathlon operates in presents different constraints. Ceiling heights vary from 8 to 18 meters. Some facilities are greenfield builds designed around robots from day one; others are brownfield retrofits where automation coexists with manual processes during a months-long transition. Labor regulations, electrical standards, and ambient temperature ranges differ site to site.

The temptation is to custom-design each facility from scratch. That works for site one. By site five, you have five different WES configurations, five integration playbooks, and an operations team that cannot transfer staff between facilities without weeks of retraining. We learned early that the deployment framework matters more than any individual site design.

Our solution: standardize three layers — the WES software core, the integration methodology, and the RFID data pipeline — while customizing two: robot type selection and physical layout. That split let Decathlon scale from a handful of sites to 25+ without project management overhead growing at the same rate.

02Why RFID Beat Barcodes for This Use Case

Decathlon committed to RFID across its supply chain years before the automation program started. That existing investment changed the architecture in ways a barcode-based operation could not replicate.

In a barcode system, inventory state updates only at scan points. Between scans, a tote is a black box. RFID eliminates that assumption — as totes pass through portals on conveyors, at robot handoff points, and at picking stations, every item inside is read without stopping the flow.

The practical impact: accuracy above 99.8%, continuous cycle counting instead of periodic shutdowns, and shrinkage detection in real time instead of quarterly audits. At Decathlon’s volume, the gap between 99% and 99.8% translates to thousands of fewer mispicks monthly.

Retailers evaluating barcode vs. RFID should consider the compounding effect. RFID tagging has a per-item cost, but paired with robotic handling through a unified hardware ecosystem, the gains pay back faster than most finance teams expect.

03Building a Repeatable Deployment Template

After the initial pilot, we documented every decision — robot selection criteria by facility profile, racking rules based on ceiling height and SKU mix, conveyor routing patterns by building footprint, and WES parameter sets by throughput tier. New sites start from this template and adjust only what local conditions require.

Deployment timelines shortened by roughly 30% between the first wave and recent sites. The operations team manages the entire network from a single platform because every site runs the same WES core. Staff transfers between facilities require days of orientation, not weeks.

The Li-Ning case study shows what a single high-complexity site looks like, while the YKK case demonstrates unmanned operations. Our solutions page outlines how we structure programs across verticals and scales.