Product readiness

Readiness is calculated by Aabhas; it is not trusted from an imported ready column.

A customer-facing product needs:

• A usable barcode or supported product identifier.
• A product title for staff, search, TV, and result labels.
• A mapped category.
• An approved garment image.
• Required runtime configuration and preparation state.

Staff can see products in incomplete states so they can resolve missing data. The customer try-on search exposes only tryon_ready products.

Reusable garment images

A central registry image is a reusable product or garment asset, not a generated VTON result. First-time use for a store product requires store approval. Approval must occur before the image makes the product customer-ready.

Prepared garment media can be cached using the organization, asset kind, source content hash, and preparation version. A changed source image or preparation version causes preparation to run again.

Preparation reuse in Store and mall journeys

For configured two-step journeys, the customer-photo preparation step and garment preparation are separate. An already prepared customer photo can be passed into the try-on step rather than cleaned again. Eligible garment preparation is reused through the same content-and-version cache used by synchronous template execution.

This requires compatible template preparation slots and version metadata; it is not automatically enabled for every template. An existing approved garment image is not necessarily an existing prepared-cache entry. Product approval and customer-facing readiness checks still apply.

Changing the original garment bytes or effective preparation version requires new preparation. Changing a title alone does not change the image bytes. Customer-photo retention remains subject to the organization’s storage policy, and no_store does not retain customer preparation in the server cache.

Before rolling out a template, test a first try-on, a second try-on using the same garment, and a changed garment. Confirm preparation reuse with your template administrator; a working final result alone does not prove a cache hit. See Prepared-image caching for identity rules, response diagnostics, versioning, and privacy limits. Its request examples are for server API integrations, not requests that Store operators need to send manually.

Configuration and mapped values

A saved ready status does not prove live media availability, remaining usage or generation health. When catalog fields are mapped to a workflow, the selected product must also supply valid values. A missing mapped value can block generation even when its image was previously prepared. Complete a real phone/TV trial before launch.