Guide
Brand Manager
Brand Manager as canonical brand source for storefront, packages, customer library, email, marketplace, support, and custom domains.
SoundSync
Brand field matrix
Only verified consumers are marked Yes.
| Brand field | Storefront | HISE | JUCE | Library | Marketplace | |
|---|---|---|---|---|---|---|
| Store name | Yes | Package/config when generated | Package/config when generated | Yes | Email footer/sender context | Yes |
| Tagline | Yes | Brand copy when package uses branding | Brand copy when package uses branding | Yes | Campaign templates where used | Yes |
| Primary/secondary/accent colors | Yes | Generated package/static branding when regenerated | Generated package/static branding when regenerated | Yes | Branded shell where used | Yes |
| Logo/icon/default product image | Yes | Generated package assets when regenerated | Generated package assets when regenerated | Yes | Email/logo where configured | Yes |
| Store slug/custom domain | Yes | Links/support context | Links/support context | Yes | CTA/link context | Yes |
| Reply-to/support email | Support/contact links | Support context | Support context | Customer help links | Reply-to/support footer | Developer profile support |
| Social links | Yes | No verified runtime dependency | No verified runtime dependency | No verified runtime dependency | No verified dependency | Developer profile |
Propagation rule
Dynamic storefront/library/email surfaces can read updated branding from platform payloads. Generated HISE/JUCE packages should be regenerated when package-embedded values or assets need to change.