Troubleshoot your store
Start with the symptom, check the expected result, and collect useful details if you need help.
Reviewed by Closku documentation team ·
No try-on button
Open the intended product page and ask the installer whether the correct script is present. Check that the product:
- Is active.
- Has an image.
- Is mapped to the matching Closku product.
The expected result is a control on the intended page; its presence alone does not prove the mapping or live rendering works. See installation and product mapping.
If it remains missing, record the page URL and browser and contact support.
Wrong garment or domain denied
For the wrong garment, compare the mapped Closku product ID with the active catalog and its image. A storefront SKU is not necessarily a Closku ID. Correct the mapping, then run a real test for the intended garment.
For a domain error, have the owner check Store domains in Your Widget. Save each exact HTTPS origin, including separate www, staging, and production hostnames where used. Retry on the saved origin. See domains and access; contact support if the correct saved origin is still denied.
Photo rejected or generation fails
For a rejected photo, select a JPEG, PNG, or WebP file no larger than 10 MiB, shown as 10 MB in the widget. Check the photo notice and submit only a photo you have permission to use. A valid file should proceed to processing.
If processing fails or stalls, record:
- The message.
- The page.
- The time.
- Any job reference.
Check subscription and capacity before another intentional test. If the problem persists, contact support; do not send shopper photos or signed result links. Integrators should follow errors and retries rather than automatically repeating an uncertain submission.
Limit reached or subscription not recognized
Open Usage & Limits and check included allowance. If you intend to spend beyond it, check that extra try-ons are enabled and the purchased balance covers the request. Adding balance alone does not enable extra try-ons. See usage and limits.
Have the owner check Billing for an eligible subscription. If checkout completed but Billing does not reflect it, follow billing guidance and contact support with the safe details of the purchase. Do not send payment details.
Import or analytics looks wrong
After an import, inspect the resulting products, variants, and images, even if some products were reported as imported. Correct the source or missing data before retrying; blindly reimporting can create duplicates. See CSV import and product management.
If Analytics shows no activity, check the selected date range and whether a real widget journey occurred in that period. An unavailable dashboard is not proof of zero activity. See analytics and contact support if the expected activity remains absent.
Cannot sign in
Use the sign-in page's password recovery option and check the email associated with your account. For a new account, open the confirmation email or request a new link on the verification page. If access still fails, see account access or use the public contact options in Contact support.
Integrator diagnostics
On the affected page, use browser developer tools to check whether the installation script loads and whether widget requests report a domain, product, or capacity error. Compare the active catalog response and mapped product ID, then follow errors and retries for the relevant operation. Share with support if the checks do not resolve the issue:
- The page URL.
- The safe error code.
- The job reference.
Exclude:
- Credentials.
- Photos.
- Signed result links.