Storefront launch checklist#
Use a preview theme or staging storefront to verify the complete journey, then repeat the critical checks on the published site.
Shop and product data#
- Confirm Shop ID and Publishable Key belong to the intended shop.
- Open Dashboard → Settings and confirm Allowed Origins (CORS) includes the published storefront origin customers actually visit (for example,
https://www.example.com). Add preview or staging origins when needed, separate multiple origins with commas, and click Save. See configuration steps. - Verify the test product is ready and its storefront identifier matches the catalog.
- For batch uploads, inspect the final job status and individual failures.
Storefront behavior#
- sdk.js loads successfully and the page does not contain duplicate loaders.
- Eligible products show the intended button in the intended placement.
- Unmapped products do not show an actionable button for the previous product.
- Selecting another variant updates the product shown in the Viewer.
- Product cards, quick views and client-side navigation behave correctly where used.
- Test a narrow mobile viewport, keyboard navigation and your store's supported browsers.
Production checks#
Publish the platform customization, then use a fresh browser session to repeat the customer journey. Check the console and network panel for blocked scripts, origin errors or stale cached assets. Verify any storefront consent and script-loading rules with your own site configuration.
Rollback and support#
Keep the previous theme or deployment available. Remove the SDK loader and its target customization to roll back; do not delete products or credentials simply to hide the storefront button. Record the failing page, selected SKU, browser and approximate time for troubleshooting.