The pattern is predictable. An enterprise with multiple brands announces a "unified platform." The technical team designs a shared backend, a component library, a single deployment pipeline. Eighteen months later there are three platforms: the "unified" one plus two brand-specific forks that sprouted when stakeholders couldn't agree.
The shared backend worked. The disagreement was about who owned what.
Each brand or business unit believes its customer journey is unique. The belief has some basis: brand identity, pricing strategy, regulatory context, and customer expectations do vary. It is also usually overstated. The underlying commerce operations (cart, checkout, inventory, fulfillment) are mostly identical across brands.
The engineering team sees the overlap and designs for reuse. The brand leadership sees the difference and refuses to compromise. The project stalls between the two.
The architecture has to solve the political problem first, by giving brand leaders something they visibly own so they stop blocking the shared backend.
At Volkswagen, five car brands (VW, Audi, Skoda, Seat, Porsche) needed to sell directly to consumers on a single commerce platform, with a million-plus users across five markets. What each brand's leadership needed was proof, in their own reporting, that the shared platform served their brand. So the platform reported brand by brand: order intake, stock, and delivery on common definitions, so a brand lead could see their own numbers on the same basis as everyone else's. Underneath, one commerce backbone handled cart logic, payment processing, inventory, and order fulfillment for all five.
Each brand's leadership could point to results that were unambiguously theirs, and engineering maintained one backend.
Architecture is necessary and not sufficient. The second requirement is that every stakeholder can point at something in the platform and call it a win. The platform team has to design for political legibility: naming conventions, dashboards, reporting structures, and governance models that give each stakeholder visibility and credit.
If your unified platform has a single dashboard that shows "platform metrics" without brand-level breakdowns, you've already lost. Each brand needs to see its numbers, in its context, presented as its success.
Your multi-brand platform architecture has to survive a stakeholder who hates it. If it can't, you have a proposal, and the forks are already being planned.
The stakeholders who can fork, delay, or kill the project have to see their interests reflected in the design. Without that, a unified platform rarely makes it past its first year.