Marcus Andrey Study
Ler em português Library

Design Systems · Step 7 · 6 min read

Multi-brand and multi-product systems

One system for several brands and products, without forking it. What a brand is allowed to change and what it never touches, how a brand layer of tokens works next to modes, and how to split a shared core from what belongs to one product.

A second brand is the moment you find out whether your system has layers or just a lot of components. Tidewater is launching Skiff, a budget ferry brand, on the same booking app. If every Harbour component hard-codes Tidewater blue, Skiff means copying the library and keeping two forever. If the components only know semantic tokens, Skiff is a new set of values and a few weeks of checking.

What you'll be able to do after reading:

  • Decide what a brand can change and what it can't
  • Add a brand layer to tokens that already have modes
  • Split a shared core from product-specific parts
  • Plan the checks a new brand needs before launch

1. See it switch

Brand
Mode
TIDEWATERSKIFF

Harbourside → Gull Island

Today, 08:40 · 55 min · from €24

Book a seat

button.primary.background → color.action.primary → color.blue.600 #1F5FAE, white text 6.35:1 color.action.primary → color.blue.400 #5B95DB, ink text 5.32:1 color.action.primary → color.teal.600 #0E6F68, white text 6.01:1 color.action.primary → color.teal.300 #4FB8AE, ink text 6.92:1

One component, two brands, two modes: four results from the same markup. Only the bottom of the token chain changes; the component and its semantic token never do. Skiff also changes radius.control to a pill. Contrast ratios measured with the WCAG formula.Live demo: Marcus Andrey, CC BY 4.0. CSS only, no script.

The card is the same markup in all four states. The component asks for button.primary.background, which points to color.action.primary, and only what that semantic token points to changes with the brand and the mode. That's the whole trick, and it only works if it was built in from the start (see Token tiers).


2. What a brand may change, and what it may not

Write this down before the second brand arrives, because every brand team will push on it.

A brand can change A brand can't change
Colour values behind semantic tokens Which semantic tokens exist, and their meaning
Type families, within the type scale The type scale's steps and minimum sizes
Corner radius, within a set of options Component structure, properties and slots
Illustration, photography and icon style Behaviour, keyboard support and focus
Voice and tone of the content Contrast minimums and target sizes

IBM Carbon defines a token as a role-based identifier that assigns a value to a theme, and says tokens "are universal and never change across themes"; only the values do (Carbon, Themes). Atlassian puts it the same way: themes switch styles everywhere "using a single set of tokens", and the right column above is why they tell people to pick tokens by meaning, not by how the colour looks today (Atlassian, Design tokens).

A brand that needs something from the right column is asking for a new component or a new pattern, and that goes through the normal contribution path (see Contribution models).


3. A brand layer next to modes

Semantic tokenTidewater lightTidewater darkSkiff lightSkiff dark
color.action.primaryblue.600blue.400teal.600teal.300
color.text.on-actionwhite · 6.35:1ink.900 · 5.32:1white · 6.01:1ink.900 · 6.92:1
color.text.defaultink.900sand.50ink.900sand.50
color.surface.pagesand.50ink.900mint.50ink.900
radius.controlradius.md 8pxradius.md 8pxradius.pill 999pxradius.pill 999px
font.family.displayThe brand serifThe system sans
The brand and mode layer of Harbour as one table: rows are the semantic tokens every component uses, columns are the four contexts. Every text pair was measured and passes WCAG AA (4.5:1). Components never see the columns, only the row names.Example: Marcus Andrey, CC BY 4.0. Ratios computed with the WCAG 2.2 relative-luminance formula.

Brand and mode are two independent axes. Tidewater and Skiff both need light and dark; the console also needs compact density. Don't write every combination by hand: two brands × two modes × two densities is already eight files that must stay in step.

The Design Tokens Community Group's resolver module, published with the first stable version of the format in October 2025, is built for this. A resolver document lists sets that are always included and modifiers with named contexts, such as brand: tidewater | skiff and mode: light | dark; a tool picks one context per modifier and resolves the result. The number of possible results is the product of the contexts, so you describe the axes, not the combinations (DTCG Resolver Module 2025.10).

{
  "version": "2025.10",
  "sets": {
    "core": { "sources": [{ "$ref": "primitives.tokens.json" }] }
  },
  "modifiers": {
    "brand": {
      "contexts": {
        "tidewater": [{ "$ref": "brand/tidewater.tokens.json" }],
        "skiff": [{ "$ref": "brand/skiff.tokens.json" }]
      },
      "default": "tidewater"
    },
    "mode": {
      "contexts": {
        "light": [{ "$ref": "mode/light.tokens.json" }],
        "dark": [{ "$ref": "mode/dark.tokens.json" }]
      },
      "default": "light"
    }
  },
  "resolutionOrder": [
    { "$ref": "#/sets/core" },
    { "$ref": "#/modifiers/brand" },
    { "$ref": "#/modifiers/mode" }
  ]
}

In Figma, the same idea is one collection per axis, each with its own modes: a Brand collection with Tidewater and Skiff, a Mode collection with Light and Dark (see Themes and modes). The resolver spec is new; check that your token tool supports it before you depend on it.

Measure every pair. Each new brand multiplies the colour pairs you have to check. Harbour's four action colours were all measured with the WCAG formula: white on Tidewater #1F5FAE is 6.35:1, white on Skiff #0E6F68 is 6.01:1, and the dark-mode pairs are 5.32:1 and 6.92:1, all above the 4.5:1 that text needs (W3C, Understanding 1.4.3).


4. Many products: a core and its edges

Brands change how things look. Products change what people do. Tidewater's booking app and staff console share buttons, fields and notices, but only the console needs a dense table for a sailing's manifest, and only the app needs a seat picker.

  • Core: what at least two products use, held to the full bar. Brad Frost's advice applies: name patterns by their structure, "card" rather than "product card", so they travel (Atomic Design, chapter 5).
  • Product layer: components and patterns that one product owns, built with core tokens and components, documented in the same place, with a clear owner.
  • Promotion: when a second product needs something from a product layer, it moves to the core through the contribution path.

The product layer is what stops a core from filling with things one team needed once, and stops that team from building outside the system altogether.


5. Before a brand launches

  1. Every semantic colour has a value for every mode of the new brand.
  2. Every text and control pair is measured, not eyeballed.
  3. Components are checked in the new brand: long names, bigger radius, a font with different widths.
  4. Images, icons and illustration have the brand's style guide (see An image style guide in your design system).
  5. Nothing was forked. If a component had to be copied to make the brand work, that's a gap in the system to fix.

6. Common mistakes

  • Components that use primitives (color.blue.600) directly, so a brand can only be added by editing every component.
  • A brand that changes component structure "just for us", and becomes a fork.
  • Writing every brand × mode combination by hand, then fixing one and forgetting the others.
  • Checking contrast in the first brand only.
  • Putting one product's specific patterns in the core, where every other product has to carry them.

7. Vocabulary

Term Meaning
Brand layer The tokens that change per brand: values, families, radius options
Theme A full set of values for the same token names; often brand × mode
Modifier, context In the DTCG resolver: an axis such as brand, and its options such as Tidewater or Skiff
Core The part of the system every product shares
Product layer Parts owned by one product, built with the core
Fork A copy of the system, or of a component, that drifts away from it

8. Try it (no tools needed)

  1. Take one screen of your product and imagine a second brand with a different main colour and rounder corners.
  2. List what would change on the screen, and where that value lives today: a token, a component, or a hard-coded value.
  3. Count the hard-coded ones. That's your work before a second brand.

Reflection questions: Which of your components would a brand team most want to change structurally, and what's the need behind it? What in your core is used by only one product?


9. If you already practise

  • Keep a "brand contract" page: the two columns of section 2, signed off by brand and product leads.
  • Run your visual regression tests in every brand × mode combination, not only the default.
  • Review the product layers once a year and promote what two products now use.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Themes and modes · Token tiers · Naming tokens · Colour and contrast · An image style guide in your design system · What a design system is

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close