Virtual try-on can help shoppers consider a garment's appearance before purchase. It does not guarantee fewer clothing returns. To assess whether Closku helps your store, compare completed purchase and return outcomes over a defined period while accounting for product mix, traffic, and the time customers have to return orders.
Closku provides photo-based visual previews. Read how a preview differs from a size recommendation. Keep the experience alongside accurate size charts, fit notes, garment photos, and clear return information.
Identify the return reasons you can influence
Separate wrong-size, unexpected appearance, fabric preference, damage, late delivery, and change-of-mind returns in your own order data. A clothing preview may inform appearance expectations; it will not fix shipping delays or damaged inventory. Size guidance has a different purpose from a visual preview.
Start with garments for which shoppers ask about fit or appearance and for which you have usable return-reason records. Keep notes on the affected SKU, size, image, and customer question so you can make a specific improvement.
Place try-on at the purchase decision
Put the entry point near the garment and purchase controls, then verify that it works on mobile. Let shoppers compare the generated preview with the actual product photography. Generated images can differ from physical fabric, color, drape, and dimensions; do not describe a render as fit proof.
Use Shopify setup or WooCommerce setup for CSV import, script placement, and product mapping. The category guide explains different try-on and sizing approaches.
Define a comparison before collecting results
- Choose the included garments, audience, exposure period, and outcome definitions.
- Record which shoppers were offered try-on, not just which shoppers chose to use it.
- Use a randomized comparison when your storefront measurement setup supports it.
- If comparing time periods, record changes in promotions, traffic sources, pricing, and product mix.
- Allow orders in each group the same delivery and return-window follow-up.
- Report sample sizes and uncertain results alongside any apparent difference.
Comparing people who voluntarily tried on with people who did not can confuse product benefit with shoppers' existing intent to buy. A before-and-after comparison can also reflect seasonality or a promotion. These are reasons to record your method, not to assign a universal Closku improvement percentage.
Track purchases and matured returns separately
| Measure | Definition to record | Interpretation |
|---|---|---|
| Try-on use | Opens, submissions, and successful results for the included products. | Shows whether the experience is being used and completing. |
| Purchase conversion | Purchases divided by eligible visitors under the same attribution rules. | Evaluate shoppers offered the feature, accounting for comparison design. |
| Return rate | Returned eligible apparel orders divided by eligible fulfilled apparel orders. | Use the same return-window follow-up and unit of analysis for each group. |
| Return cost | Shipping, handling, restocking, and retained value using your own cost records. | Helps compare operating benefit with subscription and usage cost. |
Pick order-level or item-level measures and keep them consistent. Do not mix partially returned orders with item counts, or count fresh orders as successful non-returns before their return window closes.
Document what worked before expanding
Keep the store, included products, dates, visitor and order counts, completed return counts, exposure method, and other changes in one evaluation note. Report results for the evaluated catalog and audience rather than extrapolating to every merchant. A customer case study needs the merchant's permission and that underlying evidence.
If try-on use is low, first review entry-point placement and mobile behavior. If results are unclear, collect enough comparable outcomes before changing the whole catalog. If return reasons point to fabric or delivery, improve that information or operation directly.
Start with one garment
Import a small catalog, connect the correct Closku product IDs, and validate a controlled product page before broader rollout. Current integration uses CSV plus a storefront script, with no automatic catalog sync. See the documentation and product walkthroughs.
Starter costs $49/month for 145 try-ons; current plans are listed on pricing. Contact hello@closku.com to discuss the catalog and storefront requirements for your evaluation.
