Try-on usage and results
A try-on submission requests one clothing preview for one product and shopper photo. Review recorded activity, completed results, and failures in your account.
Reviewed by Closku documentation team ·
How activity is recorded
A shopper selects a mapped product and uploads a photo. The widget creates a session and submits a rendering job. That submission records a try-on creation event before the render completes. Repeating a submission can create another job and record another event.
The dashboard's monthly activity is based on recorded creation events since the start of the calendar month. It is an operational usage view; do not assume it equals completed renders, purchase orders, or a provider invoice. Check your account and agreement when reconciling billing.
Included monthly usage
Published plans include the following monthly allowances. Enterprise volume is agreed separately.
| Plan | Included monthly try-ons |
|---|---|
| Starter | 145 |
| Growth | 340 |
| Scale | 750 |
| Enterprise | Custom agreement |
Monitor dashboard usage and review plan changes or eligible extra credits before a busy period. The current widget contract checks subscription access and reports HTTP 402 when entitlement is unavailable; it does not promise a 429 response when a displayed usage allowance is reached.
Rendering results
The shopper's photo and catalog garment image are processed into a visual preview. The widget polls until the job is completed or failed, or until its client waiting limit is reached. Completion time depends on processing availability and inputs; an estimated time is not a guaranteed deadline.
The widget reads the selected photo into a base64 data URL, uses an unexpired session for the merchant, and uploads the photo for processing through a temporary signed access link. Remote shopper-photo URLs are not accepted. Use the returned preview link rather than treating it as a permanent public asset.
If the render fails, check the mapped product ID, garment image, and photo before retrying. Keep failed activity separate from completed previews when assessing your launch.
Separate previews from fulfillment
A try-on result does not place a purchase order, manage stock, ship a garment, or guarantee its physical fit. Your ecommerce platform remains responsible for checkout and fulfillment. AI size recommendation is planned and unavailable currently; maintain the product size chart and return policy alongside the preview.
Next steps
Review plan amounts and billing.
Investigate missing or failed previews.
Related pages
Read rendering states.
Keep the right product images available.