Skip to main content

How do I test my first Looksy try-on?

Open a representative product page on the theme where Looksy is enabled. Look for the Try On button over the main product image, use a clear photo of one person, complete the same flow a shopper will use, and record anything unclear or incorrect.

1. Choose the test product

Use a product with current images, complete information, and representative variants. Confirm the intended variant before opening Looksy.

2. Use the button on the product image

Check that the Try On button is visible over the main product image, does not hide important product details or gallery controls, and explains what will happen next.

3. Provide a test image

Follow the current on-screen instructions. Test both an accepted input and a failure case so the retry guidance can be reviewed.

4. Review processing and output

Check that progress is clear, errors are actionable, the result corresponds to the selected product, and the generated preview appears in the same product-image area. The shopper should still be able to return to the correct product and variant. The generated result is a visual preview and visualization aid, not an exact fit prediction. Continue to show sizing, materials, colours, delivery, and return information. After a successful photo try-on, verify the result actions as well. Depending on the browser, shoppers can try again, share or download the image, return to earlier photo results on the same device, and clear the current result. A configured Find my size action can appear separately when that product has an available size chart. See Result Actions and Previous Try-Ons for browser and storage details.

5. Repeat on other devices and products

Test representative mobile and desktop browsers, camera permission and existing-image selection, slower connections, product templates, and variants.

Pre-launch checklist

  • Try On button is visible over the main product image
  • Generated preview appears in the same image area
  • Correct product and variant are used
  • Accepted input completes successfully
  • Failure and retry states are clear
  • Product controls still work afterward
  • Mobile and desktop layouts are usable
  • Performance is acceptable
  • Unsuitable products are excluded
Do not infer broad compatibility from one successful try-on. Test a representative set before launch.

Choosing Products

Build a useful validation set.

Common Issues

Diagnose a failed step.