For a supported BigCommerce storefront, add the supplied allyWay snippet through Script Manager and select the intended storefront and page scope. Preserve its loading settings and required initialization, avoid duplicate copies, save and test your live product, category and content pages. A headless storefront needs an integration appropriate to its separate frontend. No dedicated allyWay BigCommerce app is required or promised.

You need permission to manage storefront scripts, or a store administrator or developer who can add the snippet for you. Product-editing access alone is not enough. For Stencil storefronts, Script Manager is the standard integration path; legacy Blueprint themes do not support it. Catalyst or other headless frontends need a method suited to that frontend, including checks during client-side navigation. For multiple storefronts, verify the script configuration and loading on each intended storefront and domain. Keep security protections enabled and allow only the required script and connection sources where a Content Security Policy applies.

The snippet loads asynchronously. Preserve its loading settings and check your store’s performance after installation, especially if you already use several apps or external scripts. Avoid adding the same snippet through both Script Manager and your theme. Test loading with your storefront’s existing optimization and consent settings; do not disable security protections to make the script run.

allyWay works on storefront pages where its snippet loads and security settings permit it. Test product options, menus, cart updates, app forms and dynamically loaded content. The script’s selected page scope does not guarantee compatibility with every theme or app. BigCommerce checkout and order-confirmation pages have additional script requirements, so verify their support and the complete purchase journey separately. External iframe content and payment-provider screens cannot be adjusted by the surrounding page’s snippet.

allyWay is developed in Europe and processes data in line with the GDPR. The widget does not set tracking cookies on your visitors’ devices. When adding the snippet, choose the script consent category according to its actual purpose and your store’s privacy setup. Test loading with your configured consent choices; do not bypass visitor consent or label the script as essential solely to force it to load.

No single tool can do that. allyWay fixes supported issues, offers visitor controls and monitors storefront content. Your theme, apps, product content and purchase journey still need review. Read about the European Accessibility Act for context.

Remove only the allyWay entry from Script Manager, or the integration from the theme or separate frontend where it was added. Check every affected storefront and domain and test the live store after the change. Leave unrelated apps and scripts in place. Your products, categories and content pages stay unchanged.