Three Brands, Three Platforms: The Infrastructure Cost

Running three ecommerce brands on three different platforms isn't usually a decision anyone made. It's what happens when each one was built or bought at a different time, by different teams, with different priorities. The problem is that three years on, you're still living with all of it.

Three years on, you've typically got three separate codebases, three sets of integrations to maintain, and a Friday afternoon job every quarter where someone has to pull all the numbers together before a board meeting. That's if things are ticking along fine. If they're not, you find out the hard way - usually when you try to do something that should be straightforward, like connecting a new payment provider or launching in a new market, and discover that what should be a week's work is actually a month's work done three times over.

The direct costs are obvious enough once someone adds them up. Platform licences, development retainers, agency relationships - all multiplied by the number of brands. Every security patch, every platform update, every technical audit gets done once per brand. When something breaks, it breaks everywhere, and you're dealing with it three times.

But the more expensive problem is that fragmented platforms make it genuinely hard to move forward.

What fragmentation actually costs

One of the first things I ask when we're talking to a multi-brand business is how long it would take them to pull a single performance view across all their brands right now. Not a board pack someone's assembled by hand - an actual live picture. The answers range from "a couple of hours" to "honestly, that would take most of the weekend" (the ones who say a couple of hours are usually being generous with themselves).

The reason is almost always the same. When you want to do something that touches more than one brand - a new payment provider, a loyalty programme, a data warehouse, connecting a PIM - the integration work multiplies. You're not building one connection, you're building three, across three different codebases with three different sets of technical debt and three different timelines. More often than not, that's the reason it just doesn't happen.

New site launches tell the same story. When each brand's tech is independent, spinning up a new regional site isn't a deployment - it's a project. I've had this conversation more than once with businesses who came to us after spending six months trying to get a new market live and still not being there.

There's a downstream consequence for marketing performance too, though it tends to get attributed to the wrong cause. Fragmented platforms mean fragmented data. Paid media teams can't share audiences across brands. Attribution models diverge between brands, making any cross-portfolio comparison meaningless. When the data lives in separate systems, any analysis of how the portfolio is actually performing is a manual exercise - and the decisions that come out of it are only as good as whoever did the spreadsheet.

Development teams feel it too. Good engineers don't want to spend their time rebuilding the same infrastructure across multiple codebases. The context-switching is wearing enough on its own; the sense that the work isn't accumulating into anything is what tends to finish it.

What a shared platform actually looks like

Brand experience and technical infrastructure are different things, and conflating them is where the expensive mistakes happen. You can have three completely distinct brand experiences sitting on a shared platform foundation - one codebase, modular by design, with each brand's experience sitting on top. From the customer's perspective, the brands look and feel like their own. What changes is everything underneath.

A new regional site launches from an existing framework rather than starting from scratch. Integrations get built once and inherited across every brand. The development team's time goes on what's actually different between the brands - the customer experience, the product logic, the things that matter - rather than reconstructing the same foundations repeatedly. And a live view of how the whole portfolio is performing stops being something you prepare for a board meeting and starts being something you can actually run the business on.

The usual concern is that consolidation means compromise - that putting multiple brands on a shared platform flattens what makes each one distinct. In practice that only happens if the architecture isn't built with brand separation in mind. A modular setup handles this without much difficulty. The harder problem is usually the migration itself, not what you end up with on the other side.

Horizon Global: what this looks like when it's done

Horizon Global is probably the clearest example I can point to of what the full version of this looks like. They're the business behind Witter Towbars, Westfalia Automotive and Rola - three distinct brands, part of a portfolio of closer to six in total. When we started working with them, each brand was running its own websites, its own ERP setup, its own PIM configuration, with their own warehouse operations spread across different regions on top. Not because anyone had designed it that way, but because that's how it had grown. Data couldn't travel between brands. Launching a new regional site was a months-long project every time. The team was spending more time managing the complexity of the setup than improving anything it produced.

We connected it all into one platform - a single codebase with a modular framework sitting across the brands, integrated directly with their ERPs and PIMs across every region. We also built Ixplore, a combined product brand that brought their full range together in one place. Product data, stock levels, customer information - all of it accurate and consistent without anyone manually updating it. A new regional site that previously meant starting from scratch can now be stood up from the existing framework in a fraction of the time.

"Data management and communication is infinitely better," said Mareike Müller, Head of eCommerce and Marketing at Horizon Global Europe. "Everyone can easily access and share data, enabling us to provide a quality service to our customers and expand worldwide."

What I found interesting about the Horizon work wasn't the technical complexity - the integration problems were solvable. It was that once the infrastructure was connected, the brands stayed completely distinct. Witter, Westfalia and Rola look and feel like their own. The thing that had been blocking the business's ability to grow turned out to be sitting underneath the brands, not inside them.

When this tends to come up

In my experience this conversation rarely happens proactively. It tends to get forced - an acquisition that introduces a platform nobody knows how to connect to anything else, an expansion plan that stalls because standing up a new market turns into a six-month project, a board that asks for a consolidated performance view and gets a spreadsheet three days later.

For PE-backed and acquisitive businesses it tends to come to a head faster. If the investment thesis involves adding brands to a portfolio, the platform infrastructure either scales with that or it doesn't. A collection of independently chosen tech stacks, each of which made sense at the time, isn't a foundation that scales. The consolidation work at that point is harder than it would have been earlier - though by then the commercial case is a lot easier to make.

We work with multi-brand businesses on this at different stages - some who want to get the architecture right before it compounds, some where it's already compounded and the fix is more involved. The question tends to be the same either way: at what point does the cost of the current setup outweigh the effort of sorting it?

We run a structured platform audit for multi-brand ecommerce businesses that maps the current stack honestly: what it's costing to maintain, where it's blocking growth, and what a consolidated architecture would actually look like for that specific business. It's a diagnostic, not a sales process. If you're running more than one brand and the platform setup has grown by accumulation rather than design, it's usually worth a proper look.

R3 is a full-service digital agency. We help multi-brand businesses consolidate their ecommerce platforms, connect their data infrastructure and build technology that scales with their portfolio.