Get started with integration
Plan a storefront integration, collect access, and hand a verified installation back to the store owner.
Reviewed by Closku documentation team ·
Before you start
The standard integration combines a Closku product catalog with one storefront script. The integrator installs and maps it; the owner can prepare products and authorize domains.
- Obtain approved workspace access or ask the owner for the installation line and active product details.
- Identify exact storefront and staging origins and obtain product-template access.
- For a real try-on, confirm an eligible subscription and available allowance, or enabled extra try-ons with sufficient balance.
Find the merchant UUID in the installation script; the store slug is a different identifier. Merchant and product IDs are public installation identifiers, not secret API keys. The standard widget does not use a secret key.
Build and check the integration
- Ask the owner to add products manually or by CSV and inspect the active products and images. This is not live catalog sync.
- Have the owner save the exact origins in Store domains.
- Match each storefront product to its Closku product UUID.
- Install the script and complete a real try-on on the authorized storefront.
Hand the result to the owner
Share the following:
- The tested URL.
- Authorized origins.
- The product-to-Closku ID mapping.
- The real try-on result using the intended garment.
Agree who maintains the template and catalog. A visible button establishes placement, not successful mapping or rendering.
Use troubleshooting if needed. For custom work, review the widget API and retry rules after understanding the standard path.