Check your store before launch
Confirm that a shopper can obtain a real preview on each production storefront hostname.
Reviewed by Closku documentation team ·
Before you start
The owner needs workspace access and an eligible subscription with available allowance or enabled extra try-ons and sufficient purchased balance. The installer needs storefront template access. Use a suitable photo you have permission to submit; each real test uses available capacity.
The Appearance preview shows an example result. A preparation percentage or completed tour does not verify installation either.
Check the setup
- In Products, check that the test garment is active and has an image. Expected result: the intended garment is ready for try-on. See products.
- Have the owner check Store domains in Your Widget. Expected result: each production origin is saved separately, including distinct hostnames such as the apex and
www. See domains and access. - Ask the installer to check the installation line on the product template. Expected result: the correct store script loads on the intended page. See installation.
- Check the product mapping against the active Closku catalog. Expected result: the page identifies the intended Closku product, not merely a similar SKU. See product mapping.
- Open Billing and Usage & Limits. Expected result: an eligible subscription and capacity for the test are available. See billing and usage.
Test the shopper journey
- Open the mapped page on every production hostname in representative desktop and mobile browsers. Expected result: the try-on control appears. A button alone does not prove the mapping is valid.
- Complete an intentional real try-on on each hostname and device. Expected result: the shopper can submit an accepted photo and see a completed preview of the intended garment.
- Check the result controls. Expected result: Download and Try another are available.
If a check fails, record the page, device, expected result, and observed message. Use troubleshooting before contacting support.
Hand off for sign-off
The integrator should return the following to the owner:
- The tested hostnames.
- Product-page URLs.
- Mapped product identities.
- Devices.
- Observed results.
The owner can then confirm the intended garment, subscription, and capacity before promoting the feature. A staging result does not prove a different production hostname works.