Match storefront products to Closku
Map each storefront product to its active Closku product and verify the garment image.
Reviewed by Closku documentation team ·
Understand the identifiers
- Your store product ID identifies an item in your commerce system.
- Its SKU is a business identifier, which may also appear on variants.
- Neither is automatically a Closku product UUID.
- The Closku product ID identifies an active product in the widget catalog.
- A Closku variant ID identifies a color or size entry within that product.
For example, store product shirt-42 with SKU SHIRT-BLUE might map to Closku product 11111111-1111-4111-8111-111111111111. Store product dress-19 with SKU DRESS-RED needs its own Closku UUID, for example 22222222-2222-4222-8222-222222222222. These UUIDs are illustrative only.
Find and apply the mapping
- Ask the store team to add products manually or import a CSV, then confirm each is active and has a usable garment image. Neither method provides live store sync.
- Find the public merchant UUID using the installation script. From an authorized storefront, request the widget products endpoint with the public merchant ID. Match name and SKU to the store record and record its
id. InspectprimaryImageandvariants; an active product can have a null image. - Render that UUID as
data-product-idon the appropriate template target. Check two different pages to catch accidental ID reuse. - Complete a real try-on for each sample and confirm the intended garment appears. A button alone does not prove the mapping.
If you replace or reimport a product, inspect the resulting record and update its mapping to the current UUID. Check for duplicates before retrying an import.
Understand variant images
The standard widget passes the product ID, not the shopper's selected storefront color or size. It does not automatically synchronize variants. A custom API flow can explicitly submit a Closku variantId with its product ID.
For a matching variant with a usable image, the service prefers that image. Otherwise it tries the product's primary image and then a usable variant image. Verify the actual preview rather than assuming a variant image was selected. The active product response does not filter variants by activity.