Policies and best practices

The supported clothing workflow uses merchant catalog import, a storefront script, and generated photo-based previews. It has no live store sync or merchant outbound webhook service. AI size recommendation is planned and is not currently available.

A preview does not guarantee physical fit, purchase outcomes, or a reduction in returns. Keep garment measurements, size charts, purchase controls, and return policies available to the shopper.

Starter, Growth, and Scale have published monthly allowances and billing amounts. Enterprise volume, support, and any SLA are defined by agreement. Read pricing, terms, and your checkout or contract for the applicable offer.

Any uptime, service-credit, maintenance, backup recovery, or support commitment must be specified in a current written agreement before you rely on it.

Explain the photo-processing experience before upload and use photos only with the necessary permission. The current widget accepts one JPEG, PNG, or WebP photo up to 10 MB; a separate shopper-profile workflow should not be treated as the widget's upload requirement.

The widget submits the selected photo as a base64 data URL; it does not accept a remote shopper-photo URL. The service uploads the photo into protected storage and gives processing a temporary signed access link. This processing flow is separate from public product photographs imported through the merchant catalog.

Review the privacy policy and any applicable account agreement for processing, storage, retention, and rights requests. Do not promise that photos are deleted immediately or never stored unless that is established for the actual service. Keep shopper images, result URLs, and account credentials out of public logs.

• Maintain a catalog owner and storefront-to-Closku product mapping.
• Review product imagery, variant labels, and category configuration before launch.
• Test desktop and mobile after changes to scripts, themes, or product data.
• Monitor submitted and completed previews separately from failures and purchases.
• Use a defined evaluation period and controlled comparison where possible, without treating every sales or return change as a result of try-on.

Use the owner account's billing portal or contact Closku for available changes. Effective dates, renewals, cancellation, and any adjustments follow the actual checkout or agreement. Do not assume that an upgrade resets recorded usage or that a downgrade has a penalty described by an outdated guide.