Deep dive · Premium brand manufacturer
One platform for 39 locales, live in 8 months
How we replaced a monolithic commerce platform with a composable stack for a premium brand manufacturer, and kept it at 99.99% uptime with a small internal team.
Our client for more than 6 years
At a glance
Key facts
Client
A premium brand manufacturer. Our client since 2020.
Company size
A medium enterprise as part of a larger enterprise group.
Markets
24 country versions plus an international version, in 39 locales.
Channels
Brand site and online shop, plus a dealer network of thousands of specialist dealers worldwide.
Platform and main systems
Contentful for content, commercetools for commerce, AWS for hosting. Customer accounts sit in the CRM.
Project period
8 months from decision to first go-live. The relationship is still running.
Starting point
A monolithic shop and a small team
The brand ran its online shop on a monolithic commerce platform, while selling through a large network of specialist dealers worldwide.
What was broken: The old shop system handled a classic storefront and nothing more. We could not match its look and feel to the brand, it had no proper CMS for engaging content, and the digital experience fell short of what premium buyers expect.
Why it mattered: A premium brand could not give its buyers a premium digital experience. The shop looked like everyone else's, and without a CMS the team could not publish engaging content around the product.
Constraints: We had to integrate a number of backoffice systems, some of them very legacy. Otherwise the client aimed for a complete relaunch from the start, with few restraints.
Approach
How we approached it
Discovery
We started with a dedicated planning phase built around a series of workshops. One of them was an Event Storming workshop, which pays off in complex projects with many moving actors and parts.
Three architecture decisions
Separate systems for content, commerce and hosting. We replaced one monolith with a composable stack, so each part can be changed or replaced on its own. Rejected alternative: relaunching on the existing monolith, because its limitations were among the core reasons for the relaunch.
Customer accounts in the CRM, not in the shop. Decoupled from the shop, the commerce engine can be replaced without a rebuild. Rejected alternative: accounts inside the commerce engine, which ties every customer record to one engine.
An automated translation workflow. At 39 locales, hand-offs per locale stop scaling. Rejected alternative: manual translation per market.
Integrations
We connected the business systems behind the shop by type: ERP, CRM and marketing automation. CRM and e-commerce stay in sync, with nearly 500,000 contacts between them.
What we built
The main capabilities
We took over the design after go-live, and the current design is mostly ours.
One storefront, many markets
24 country versions plus an international version, in 39 locales.
Content by segment
Content tailored to three user segments.
Automated translations
Translations run through an automated workflow instead of manual hand-offs.
Dealer locator
Covers thousands of specialist dealers worldwide.
Dealer landing pages
Hundreds of dealers have their own landing page on the website.
CRM and shop in sync
Nearly 500,000 contacts synced between CRM and e-commerce.
After launch
Running and evolving it
We host, monitor and continuously optimize the custom platform, and we keep changing it. Bug fixes reach production within hours.
We replaced several backend systems, including ERP and marketing automation, without downtime.
We delivered a redesign of the website and shop without downtime.
New countries go live in days instead of months.
The original launch was a single cutover: we replaced the old platform from one day to the next, in one clear event where we retired the legacy platform.
Results
Measured on the platform, then on the business
Platform figures come first. Internal IT involvement in e-commerce operations is measured in hours per year, and the site carries 80,000+ pages in Google’s index. Business figures follow, each with its comparison period.
- Uptime since launch
- 99.99%
- Months from decision to first go-live
- 8
- To launch a new country
- Days
- From bug fix to production
- Hours
- Lighthouse, all four categories
- 90+
- E-commerce team growth, 5 years
- +1
- Orders, 2025 vs 2019
- +377%Online shop
- Revenue, 2025 vs 2019
- +519%Online shop
- Orders, 2026 outlook vs 2019
- ~6xOnline shop
- Revenue, 2026 outlook vs 2019
- >8xOnline shop
Today
What the client can do now
Launch a country in days
New markets go live on the same platform in days instead of months.
Ship fixes within hours
Bug fixes and change requests reach the production platform within hours.
Swap systems without downtime
ERP and marketing automation were replaced, and the site redesigned, while the shop stayed live.
I have been in this business for a long time, and I have never had such a good collaboration with a technical agency.
Questions
What technical buyers ask about this project
Talk to a senior engineer about your platform
A senior engineer joins every first call. Tell us about your stack and your markets.