Walkthrough
Storefront Embed Walkthrough
Complete storefront embed walkthrough with configuration, expected results, and recovery guidance.
SoundSync
Storefront Embed Walkthrough
-
Choose the package
Decide between full commerce and a standalone supported surface.
-
Generate
Use the saved store's current installation code.
-
Install
Preserve required assets and references without exposing developer tokens.
-
Navigate
Check direct product URLs and browser back/forward.
-
Customer access
Test the supported session, cart, checkout return, and library.
-
Responsive check
Review mobile/desktop layout and brand values on the actual host.
Install the package that matches the job
Use the full commerce embed when the host needs product navigation, cart, checkout handoff, and customer access together. Use a standalone page embed for a supported individual surface. HISE or JUCE in-plugin Store/My Products is a separate integration, not the same web embed pasted into a plugin.
Save the storefront and generate its current installation code. Keep the supplied script and store references together on the host page. Do not put a developer JWT, private product secret, signed delivery URL, or customer library token in public HTML.
Test navigation on the real host page
Open the embedded catalog on desktop and mobile, select a product, use back/forward, and test direct links. Review the inherited logo, appearance, colors, and product images rather than assuming an editor preview proves the published host works.
Use a permitted customer identity to test the cart and return from the intended checkout environment. Inspect owned-product access separately from public browsing. If the embed is blank, check that the current script loads, the store reference matches, and the host permits the generated installation. Avoid stacking multiple old package versions on the same page.
SoundSync
Contract and detailed settings
Read the full guide
Field definitions, permissions, and current limitations.
Test safely
Use permitted test identities and the intended environment. Inspect allowed and rejected outcomes. Keep private customer data, serials, credentials, payment details, and verification links out of published examples.
