commercetools Integration
Bring 3D configuration, 360° viewing and app-free AR to your composable commercetools storefront — rendered by the Thridify JS SDK in your own frontend.
How it integrates
commercetools is headless, so your frontend owns the product page. Build your 360° viewer, configurator and AR experience once in Thridify and publish it, then mount it in your commercetools storefront with the Thridify JS SDK — passing the product ID your frontend already resolves. AR runs in the browser — no app for your shoppers.
Install: Thridify JS SDK in your headless frontend
Create the 3D viewer, configurator or AR experience for your product and publish it — each gets a stable ID.
In your commercetools frontend, call the Thridify SDK with the product ID your storefront already resolves.
The SDK renders the live experience in your own UI — customers explore in 3D and view the item in their room, app-free.
Install guide
commercetools is headless: it has no storefront templates for a snippet to go into. Thridify is added to your own frontend, whatever it is built with, and talks to commercetools only through your code.
The Thridify viewer is a browser component, so load it after hydration. In Next.js, for example, use next/script with the afterInteractive strategy on the product page.
import Script from "next/script";
<Script id="thridify-data" strategy="afterInteractive">
{`window.thridifyData = Object.assign({ accountId: "YOUR_THRIDIFY_ACCOUNT_ID" }, window.thridifyData || {});`}
</Script>
<Script src="https://viewer.thridify.com/floating-icon.js" strategy="afterInteractive" />Use a stable identifier as the Thridify product reference. The product key works well because it does not change between environments. Expose the current variant’s SKU through window.thridifyCommerce, and Thridify uses the binding published for that SKU.
<div data-thridify-page-product-id={product.key} />
window.thridifyCommerce = {
getVariantContext: () => ({ sku: selectedVariant.sku }),
onConfigurationChange: (change) => syncVariantPicker(change),
addToCart: async (req) => addLineItem(selectedVariant.sku, req),
};When addToCart is defined, the viewer offers its own Add to cart button. Your handler adds the line item with your own price and can keep the shopper’s configuration on it.
What you get
Composable stacks demand a clean embed, not a plugin. Thridify’s SDK drops a 3D experience into your commercetools frontend without owning your product page.
The SDK mounts a drag-to-spin 3D viewer inside your commercetools storefront — you keep full control of the layout.
Shoppers swap finishes and options in real time with live pricing, driven by the product data your frontend already holds.
One tap places the product at true scale in the buyer’s space from your composable storefront — no app to install.
The impact
FAQ
The questions commercetools merchants ask most.
Yes. Because commercetools is headless, Thridify mounts a published 3D viewer, configurator or AR experience in your own frontend using the JS SDK and the product ID your storefront resolves.
Publish the experience in Thridify, then call the Thridify SDK in your frontend with the product ID. The SDK renders the live experience inside your UI — you keep control of the page.
No. AR runs in the browser on any modern smartphone, so shoppers place products in their room in one tap — no app download.
The SDK is framework-agnostic JavaScript, so it mounts in React, Vue, Angular or plain JS storefronts built on commercetools.