
Multi-Brand Design System and Design Tokens: A Solution for Managing 20 Brand Websites from a Single Source Code Repository
For diversified corporations in fast-moving consumer goods (FMCG), fashion retail, education, or pharmaceuticals, operating 10 to 20 websites simultaneously for different sub-brands is a common challenge. Each brand has its own distinct visual identity: Brand A targets dynamic young people with vibrant colors, large rounded corners, and modern fonts; Brand B targets the high-end segment with a minimalist, dark color palette, sharp lines, and elegant serif fonts. Traditionally, each time a corporation launches a new brand or refreshes its brand identity, the marketing department hires a separate web development company to build a completely independent website. The consequence after a few years is a chaotic "technical battlefield": 20 websites running on 5 different open-source platforms, and each time a security vulnerability in the navigation bar needs patching or a new shopping cart policy needs updating, the IT team has to repeat code fixes and testing up to 20 times. To put an end to this enormous waste, leading organizations are standardizing interface infrastructure using a Multi-Brand Design System that operates on Design Tokens at its core.
To understand the true nature of design, it's necessary to distinguish between a typical static UI Kit and a Design System that utilizes Design Tokens. In traditional CSS programming, developers often directly assign hard-coded values to the source code, such as background-color: #E63946 or border-radius: 8px. When changing the interface to a different brand with a dominant blue color and square corners, the technical team has to manually edit thousands of lines of CSS code, easily leading to errors or color distortion in secondary states such as hovering or disabling buttons. Design Tokens completely solve this problem by abstracting all atomic design decisions – from color, font size, spacing, shadows to animation duration – into platform-agnostic Name-Value pairs (Platform-agnostic JSON files according to the W3C Design Tokens community specification).
The true power of multi-brand architecture lies in its Three-Tier Token Architecture model . The first foundational layer is Primitive Tokens , acting as a repository of raw, uncontextualized color palettes and parameters (e.g., color.blue.600 = #1D4ED8, radius.md = 8px). The most important layer in the middle is Semantic Tokens, which define the intended use of the design rather than its appearance (e.g., color.action.primary points to the main brand color, color.surface.danger points to the error color, spacing.card.padding specifies the content frame padding). The top layer is Component Tokens , directly attached to specific details such as button.primary.background or input.border.focus.
Thanks to this tightly structured hierarchical system, all 20 websites of the corporation can share a single core component library (written in React, Vue, or Web Components) containing all the complex business logic such as product filters, shopping carts, form validation, and user support standards. The completely different aesthetics between the 20 brands are determined simply by swapping the Semantic Tokens mapping file (Theme Switching) at the configuration layer. The same <PrimaryButton/> button component, when paired with Brand A's Token, will automatically display a vibrant orange pill-shaped icon with a thick sans-serif font; but when paired with Brand B's Token, it will instantly transform into a sharp, black and gold rectangular frame with a classic serif font without needing to write any additional JavaScript logic.
To prevent this system from failing due to mismatches between the design and programming teams, high-tech corporations implement a continuous automation pipeline called the Design-to-Code Pipeline . All design variables are centrally managed on Figma. As soon as the Creative Director adjusts a primary color code or changes the font scaling system for Brand C on Figma and presses publish, an automated process (Webhook combined with GitHub Actions) extracts the standardized JSON structure, runs it through an intermediate compiler such as Style Dictionary . This compiler automatically translates common tokens into the correct format required by each platform: creating CSS variables (--color-action-primary) for websites, creating Swift files for iOS applications and XML/Compose files for Android applications, and then automatically opening a code merge request (Pull Request) to the source code repository. Any errors caused by programmers misinterpreting color codes are completely eliminated.
From a financial management and time-to-market perspective, the initial investment in a Multi-Brand Design System delivers exceptional return on investment. When a corporation acquires a new brand or needs to launch a large-scale microsite campaign during the holiday season, instead of spending three months designing and testing from scratch, the team only needs to create a new Token configuration file within a week to have a complete website, inheriting the corporation's proven performance, security, and conversion optimization capabilities. The Multi-Brand Design System represents a transformation from a "manual website outsourcing" mindset to a "large-scale, industrial-scale digital experience manufacturing" approach.