Salesforce B2C Commerce 24.7 > Storefront Toolkit

Storefront Toolkit Tips and Limitations

For best results, configure your system for optimal Storefront Toolkit performance and make sure you’re aware of toolkit limitations.

  • If you redirect the browser to use an unencrypted HTTP version of the page, the Storefront Toolkit sometimes doesn’t work correctly. As a best practice, don't redirect the browser to use HTTP. To eliminate potential issues related to unencrypted pages completely, enable the global security preference Enforce HTTPS. In Business Manager, go to Administration > Global Preferences > Security. On the Access Restrictions tab, select Enforce HTTPS and click Apply.
  • Make sure that you’ve correctly configured the HTTPS host and that the hostname aliases point to the correct instance using DNS.
  • Page Designer pages are not connected to the Content preview on either the old or new Storefront Toolkit.
  • Make sure that all of your certificates are valid. If you have an invalid certificate, a user must first open the storefront and allow an exception. Then the user can open the Storefront Toolkit.
  • For cookies, you must use the Secure attribute and set the SameSite attribute to None.
  • The Storefront Toolkit uses an iframe to display your storefront. Avoid JavaScript that accesses the window.top or window.parent elements of the iframe. Make sure your code doesn’t write to parent in the global scope.
  • Don’t use ClickJack Protection or Anti-ClickJack scripts, which can cause errors. Use the appropriate HTTP headers instead. For more information, see Troubleshoot the Storefront Toolkit.
Related reference
Hostname Aliases

Infocenter Retirement: On June 30, 2023, the Infocenter was retired, and documentation currently hosted on the Infocenter will be published to Salesforce Help, Commerce Cloud Developer Center, and Salesforce B2C Commerce Developer Documentation Resources. For more information, see the release note.