Skip to main content
Question

Multi-brand design system: how to structure master components vs brand theming?

  • January 20, 2026
  • 0 replies
  • 15 views

Dmytro No

Hi folks, looking for advice from people who’ve built or scaled multi-brand / white-label design systems.

 

We have a large master design system and need to support multiple brands on top of it.

 

What we’re trying to achieve:

 

  • One single source of truth for components

  • Ability to evolve master components (add variants, change structure, etc.)

  • All brands should inherit those updates automatically

  • Colors, images, and other visual styles should come from brand-specific configs

  • Avoid component duplication and version drift

 

The mental model we’re aiming for:

 

  • Structure & behavior → master design system

  • Visual identity / theming → brand level

 

Questions:

 

  • Have you done something similar?

  • What worked best for you: tokens, variables, nested libraries, overrides?

  • Any major pitfalls or things you wish you’d done differently early on?

 

Real-world experience or links to solid write-ups would be much appreciated 🙌