ETAM Partners with commercetools to Modernise Commerce Platform

What happened

ETAM has partnered with commercetools to modernise the digital commerce foundation behind its online operations. The platform supports a set of brands that includes Maison 123.

The announcement frames the work as a rebuild of the underlying commerce infrastructure rather than a change to a single storefront. The reporting available to us does not set out the scope, timeline or technical detail of the programme, so those points should be checked against the original announcement before they are relied on.

Why it matters

Replacing the foundation beneath several brands is a different kind of decision from redesigning one site. It determines how product data, pricing, inventory and checkout logic are shared across channels, and it sets the limits of what teams can change quickly later. For organisations running multiple brands on shared systems, the platform layer often decides whether customer experience improvements can be delivered at scale or have to be rebuilt brand by brand.

The story also illustrates a wider pattern in retail technology: commerce stacks are being reorganised into modular, service-based components so that brands can be launched, adjusted and integrated without a full rebuild. That shift changes the operating model as well as the technology, since merchandising, engineering and customer service teams need to work from the same data and the same rules.

The Renascence take

Most coverage of a platform partnership focuses on the vendor and the technology choice. The more useful question is what customers will notice, and when. A modernised foundation pays off only if it removes friction that shoppers actually feel, such as inconsistent stock information, slow checkout or mismatched promotions across brands.

Platform modernisation is rarely a technology story; it is a decision about which customer journeys the business is willing to stop breaking. Behavioural economics suggests shoppers judge an entire brand by the first point where a promise fails, so consistency across brands on a shared stack matters more than any single feature. Operators in this position should map the top five journeys by abandonment or complaint volume before choosing components, and use those findings to set the migration order. If the foundation changes but those moments stay the same, the programme will have modernised the plumbing without improving the experience.