THE CHALLENGE
Overcoming technical debt at a massive scale
Decathlon is universally known as a sports retailer, but it has also grown into a major technology operator, with nearly 4,000 people working at its digital hub in Lille, France, where it develops and maintains tools that power the organization’s growth.
One of these platforms is an internal pricing builder designed to centralize retail prices and maintain a single source of truth for global commerce. It’s a system that needs to track and account for standard prices, discounts, multiple currencies, and often strict legal regulations.
“The advantage of centralized pricing is that we can also centralize compliance with pricing laws, of which there are many, depending on the country,” explained Julien Lampin, Solutions Architect at Decathlon. “In France, for example, it is forbidden to sell at a loss except during sales. We are not pricing decision-makers, but if someone sets a price too low, we are obligated to raise it to be compliant.”
It’s an important business process, but Decathlon’s eight-year-old legacy system, Masterprice, which was built on a PostgreSQL database, was buckling under the weight of severe technical debt, burdensome data stores, and a series of critical paradigm shifts. These include local ‘subsidiarity’, which allows over 600 stores in France to adjust their own prices, as well as the launches of AI-driven dynamic pricing and a new third-party marketplace. As a result, the business’s daily data volume skyrocketed, reaching up to 1 million dynamic prices and 4 million marketplace prices.
“Mechanically, it generated a huge load increase,” added Lampin. “In France alone, we have around 1 million references. Multiply that by 600 stores, and that potentially creates 600 million timelines.”
Masterprice’s PostgreSQL database also suffered from unpurged, compressed timeline data and heavily duplicated tables, which slowed momentum and feature delivery. Decathlon needed a new platform that could scale seamlessly to support future models without creating infrastructural bottlenecks.
“Masterprice was holding up, but we didn’t know how long for,” Lampin noted. “We had a vast amount of unpurged data, and scalability wasn't perfect. We needed a clear strategy for handling massive loads over the coming years.”
