Brand Manager, Domains, and SSL for Audio Software Stores
Brand Manager, Domains, and SSL
Your main domain or subdomain, managed SSL, and a consistent identity across storefronts, emails, and product packages.
Your main domain is supported
Use an apex domain such as example.com or a subdomain such as shop.example.com. A store/shop prefix is not required. You need control of the domain and access to its DNS records; SoundSync provides the hosted storefront connection and SSL certificate management.
Moving an apex domain can affect an existing website. Review current DNS records and preserve unrelated mail records. Domain ownership and DNS access do not authorize SoundSync to change unrelated services.
SoundSync
Connect the domain
-
Enter the hostname
Choose the apex or subdomain you actually want to publish.
-
Review provider guidance
The setup view detects available provider/nameserver information and presents the required records.
-
Add the exact records
Use the displayed targets and ownership-verification values in your DNS provider. Avoid publishing verification tokens in screenshots.
-
Verify ownership and routing
Check the step-by-step status until DNS and ownership requirements are met.
-
Wait for SSL readiness
The certificate and connection status determine readiness; DNS propagation has no universal completion time.
-
Check real pages
Visit home, catalog, product, cart, checkout entry, support, and customer sign-in on the intended host.
Related settings are not automatic
Storefront SSL does not verify an email sending domain. Optional GA4 tracking becomes ready on the verified custom host only when configured separately.
If verification fails, compare record name, record type, target, and proxy/provider guidance. Do not repeatedly replace unrelated DNS records or assume an SSL warning is safe to bypass.
SoundSync
Set the identity for each destination
| Setting | Where it belongs |
|---|---|
| Store name, tagline, and description | Your storefront identity and introductory copy |
| Developer display name and marketplace bio | Your public developer profile; review and apply separately from store copy |
| Main, light, and dark logos; icon | Appearance-appropriate identity across supported surfaces |
| Default product image | A fallback, not a replacement for product-specific artwork |
| Background, highlight, accent, and advanced colors | Brand defaults and supported semantic overrides |
| Support, reply-to, and social links | Customer contact and message identity; sending-domain verification is separate |
One source, several delivery mechanisms
Hosted storefront, Website Builder, checkout, customer library, and email identity reuse supported brand values. Product artwork remains product-specific. Plugin packages also carry generated configuration and bundled assets.
Dynamic retrieval and generated snapshots are different: a published web setting can update a web surface while an installed package still requires regeneration and a new binary. Review both after a brand change.
SoundSync
Set up the whole brand
-
Complete identity
Use the name and descriptions you want customers to see. Choose a stable store slug.
-
Prepare imagery
Upload suitable light/dark logos and default imagery; check transparency and actual placement.
-
Tune colors
Preview supported surfaces and maintain readable text, contrast, and focus indicators.
-
Configure support
Set the monitored inbox, help links, policies, articles, and optional form.
-
Connect domains
Use the exact DNS records in the guided domain view and wait for verified connection and SSL readiness.
-
Review emails and packages
Inspect the compliance footer and regenerate affected product packages where values are bundled.
SoundSync
Brand Manager in the developer dashboard
The Brand Manager workspace shows storefront identity, colors, support fields, domain readiness, email-domain state, and customer-facing brand propagation from one dark-theme dashboard surface.
Three workspaces, deliberate saves
Identity, Visuals, and Support have separate saved versions. Save the section you are editing without replacing unrelated settings. If someone saves a newer version, reload and review the conflict rather than overwriting it. Intentional clearing of supported fields stays cleared.
Review the currently public view and the proposed saved view. A page-level template override can take precedence over a brand default. Brand Manager does not promise to replace every page-specific choice automatically.
Support that fits your business
Choose the public support email, optional contact details, response guidance, and help content. Keep the form-delivery address private; it is not a public contact field. An enabled contact form needs a valid delivery route.
Draft help items stay unpublished. Published answers need content and can be reordered. Availability and response-time text describe the developer's support practice, not a SoundSync response-time guarantee.
From your main domain to the right colors
Use an apex domain, such as example.com, or a subdomain such as shop.example.com. You need the domain and DNS access; SoundSync guides the required records, verifies the connection, and provisions storefront SSL certificates. Provider guidance is not a promise of automated changes at every DNS provider or a fixed propagation time.
Website defaults, storefront themes, and plugin configuration use the applicable brand values. Generated HISE/JUCE packages may contain saved values: regenerate and rebuild when those change. Do not assume previously distributed plugins update every embedded setting instantly.
SoundSync
Inside SoundSync
