DNS Setup
Custom Domains and Managed 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
Identity and presentation
| Area | Values and purpose |
|---|---|
| Identity | Store/developer display name, tagline, short description, marketplace description, and store slug |
| Logos and imagery | Main, light/dark, icon and banner assets, plus default product imagery |
| Palette | Primary, secondary, tertiary/accent values and supported semantic overrides; preview contrast before saving |
| Appearance | Light/dark appearance and supported background/highlight values |
| Social links | Supported profile destinations; publish only links you control |
| Contact identity | Support inbox, reply-to, contact label, business address, response guidance, and availability |
| Domains | Apex or subdomain storefront, DNS ownership verification, and SSL status |
| Support content | FAQ/articles, policy and documentation links, contact-form configuration |
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
Inside SoundSync
