Store setup
Set up Closku with a CSV product catalog and storefront script, then verify the merchant configuration, product mapping, and first try-on.
Reviewed by Closku documentation team ·
Prepare your store
Create a merchant account, choose the applicable plan, and import a small sample of your apparel catalog in Products. Review names, SKUs, images, variants, and active status. Use suitable clothing images and confirm you have the right to process the shopper photos used in testing.
Arrange an active widget configuration with an explicit allowed storefront origin. An empty origin list denies access in production. If the setting is not exposed in your dashboard, give support your merchant ID and the intended live and staging origins.
Install and map the storefront
Copy your merchant-specific script from SDK Config and insert it before the closing </body> tag on the intended product pages. The copied script contains your actual merchant slug or merchant ID.
<script src="https://closku.com/widget/YOUR_STORE_SLUG.js" defer></script>
<div data-product-id="CLOSKU_PRODUCT_UUID">
<!-- Product content -->
</div>Replace placeholders with real values. data-product-id must contain a Closku catalog product UUID. Store platform IDs and SKUs require explicit mapping; automatic button detection does not perform this translation.
Use Shopify theme setup or WooCommerce setup for platform context. Other storefronts need custom script support and a tested product mapping.
Launch checks
- Confirm configuration requests succeed from the intended storefront origin.
- Check that the correct product and image are used after clicking try-on.
- Test a shopper photo through completion and inspect a failure message.
- Check desktop and mobile behavior and make sure ordinary purchase controls still work.
- Review recorded usage and assign responsibility for future catalog updates.
Setup time depends on theme access, product mapping, and catalog quality. There is no fixed onboarding deadline promised by this guide.
Current integration scope
The supported workflow imports a CSV and adds the storefront script. It has no live catalog sync or merchant outbound webhooks. Read the widget endpoint reference before building custom interactions, and contact Closku for requirements beyond this flow.
Next steps
Review imported images and products.
Monitor launch activity.
Related pages
Read product mapping and request details.
Resolve setup and origin failures.