Skip to content

How it works

How the Integration Works

The SDK loads on your page and sits between your storefront and the 3D component. Your site tells the component what to show. The component tells your site what the shopper did.
ZolakYour storefront

Your Site Drives the 3D Component and Keeps the Cart

 
 

Your storefront

Zolak

Product controls

Your own selectors, or Zolak’s sidebar

Cart and checkout

Your code adds the item
Checkout stays as is

Zolak JS SDK

Runs on your page
Client-side API: methods + events

3D component

Hosted iframe
Renders the product, applies SKU + materials

Zolak CMS

Products, materials, access token

 methods
methods
events
3D content
 
 Add to Cart event
SKU + materials
Step by step

One Integration for the Whole Catalog

The same integration works for every product you set up in Zolak. Adding a product to the configurator is a content task in Zolak CMS, not a new integration: your site just passes its SKU.

It works with either common catalog structure: one SKU per variation, or a base SKU with a material assigned to each part.

01
Your storefront

Your Site Sets the Product

Pass a Product SKU, and materials if you use them, from your own controls or on page load.

02
Zolak

The Component Reports Back

Events fire when the shopper changes the product or adds it to the cart.

03
Your storefront

Your Cart Takes Over

Your code adds the selected SKU and materials to the cart. Checkout runs as it does today.

Control models

Use Our Options Panel or Your Own UI

One component, two control models. The difference is who shows the options and where the shopper clicks Add to Cart.
ZolakYour storefront
 
Add to cart
Product name$1,240
SKU + materials
Zolak options panel

Shoppers Configure Inside the Component

The 3D model, the options and Add to Cart all live in the Zolak component. When a shopper adds a configuration, your site gets an event with the Product SKU and selected materials and adds the item to your cart.

Choose it when: you want a full configuration experience with little UI work. With its built-in render gallery, it can replace your image slider.

 
API call
Option Add to cart
Your own UI

Your Controls Drive the 3D View

Swatches, selectors and Add to Cart stay in your storefront. When a shopper picks an option, your code passes the new SKU or materials to the API, and the 3D model updates. The cart works as it does today.

Choose it when: your product page already has a variant picker. The viewer can replace the main image or open from a 3D button in your gallery.

Both can sit inline on the product page or open in a popup from a button.

Choosing between them for your product pages?

See how it fits
Roles

How the Integration Work Is Split

Your checkout stays yours. When a shopper adds a configuration to the cart, your site gets the SKU and selected materials and adds the item through your existing cart. Zolak doesn’t place orders.

The integration work can be done by your developers or by Zolak’s integration team as a separate project.

  Zolak platform Integration work
3D Hosts and renders the 3D component Adds a container to the page
Product setup Products, variations and materials in Zolak CMS Keeps SKUs and material IDs in line with the store
Controls Built-in options panel, if you use it Your own selectors, if you use the viewer model
Sync Methods to change the product, events for every change Calls the methods, handles the events
Cart The final configuration: SKU and materials Adds the item to the cart; checkout stays as is

Need 3D models? Zolak can build them from product references or your existing 3D files.

Case study

How Cut Throat Knives Added 3D to Their Wix Store

Cut Throat Knives
Blade Lab

Cut Throat Knives

Every Cut Throat Knives knife is made to order, so customers commit before the product exists. Blade Lab, the brand’s configurator, lets shoppers choose the blade, handle, pins and liner and see that exact knife in 3D, right on their existing Wix store.

Own controls drive the 3D
How it was integrated

Cut Throat Knives wanted shoppers to build a knife without leaving their Wix store. We kept everything they already had - products, prices, cart and checkout - and added the 3D on top. Our interface is hidden, so shoppers only see the brand’s own options and loader. When a new knife is ready, the client adds it to the configurator themselves.

Herman Malyshev
Integration Engineer, Zolak
Client

The team at Zolak were fantastic to work with. Every step of the way they were responsive, amenable to changes and clearly communicated pricing. I couldn't be happier with the service that they've provided and look forward to working with them well into the future.

Aidan Mackinnon
Aidan Mackinnon
Director, Cut Throat Knives
Before you start

What You Need to Go Live

01

Products in Zolak

GLB models and PBR materials set up in Zolak CMS and linked to your SKUs.

02

Access Token

An access token for your company account, issued in Zolak CMS.

03

A Control Model

Zolak’s panel or your own UI, inline or popup.

04

SKU Mapping

One SKU per variation, or a base SKU with materials.

05

Cart Integration

Cart integration, built by your developers or by Zolak, if shoppers add configurations to the cart.

06

A Modern Browser

The component renders with WebGL 2.0 and supports current versions of Chrome, Safari, Firefox and Edge.

The Configurator API runs in the browser and controls what shoppers see. Product names, prices, descriptions and availability sync through a separate server-side Public API. 3D models and materials are managed only in Zolak CMS, where content managers check every product visually.

On Shopify, Magento or WooCommerce? See platform integrations.

FAQ

Is the Configurator API a REST API?
No. It’s a client-side JavaScript API that comes with the Zolak SDK and runs on your storefront. Product names, prices and availability sync through a separate Public API.
Do I need a developer?
Not necessarily. Embedding the configurator with Zolak’s panel takes a script, a container and one initialization call. For your own controls and cart integration, your developers can do the work, or Zolak’s integration team can build it for you.
Can I use my own variant picker instead of Zolak’s panel?
Yes. Turn off the built-in panel and drive the component from your own controls. The 3D model updates as shoppers change options.
Can the configurator change product dimensions or add modules?
The configurator switches materials and colors on each part of a product. Geometry changes, such as sizes or modular layouts, aren’t part of the standard configurator. Talk to us about custom options.
Do I need to change my existing SKUs?
Usually not. Zolak supports one SKU per variation and a base SKU with materials. The IDs in Zolak just need to match the ones in your store.
How does a configuration get into my cart?
The component sends your site the Product SKU and selected materials. Your code adds the item to your existing cart, so checkout doesn’t change.
Does it work with headless storefronts?
Yes. The component runs in an iframe and adapts to the size of its container, so any frontend that can load a script and render a container element can host it.
Can I run more than one configurator on a page?
Yes. The SDK supports several independent instances on the same page.
Does it support AR?
Yes. Turn on AR in the initialization options, and shoppers on ARCore or ARKit devices get an AR button in the component.
Can I track configurator interactions in analytics?
Yes. You can subscribe to every component event at once and pass them to your analytics.

Plan Your Integration with Our Team

Show us your storefront and how your catalog is structured. We’ll work out the right control model, SKU mapping and cart handoff, and whether your team builds the integration or we do.