Show the outfit,
not just one item.

For agencies: one client, one reviewable proof

Choose one fashion client with separate tops, bottoms and shoes that shoppers could plausibly combine. Share your agency website and the client's public store address, then identify the specific three products in the note. A useful brief describes the intended customer question, such as whether a new jacket can anchor a complete office outfit. It does not need a catalog export, live theme access or a customer photograph.

The agency remains the primary adviser and keeps the client relationship. Private Try-On supplies a bounded synthetic-model concept and notes the generation limits. Review the original items and the concept together before proposing wider work. A private proof does not establish that a client-branded, white-label or native-platform integration is ready to sell. Referral, resale and hosted-integration terms require a separate written scope after the proof and required production path have been reviewed.

For a client presentation, keep the product links beside the output and describe the discrepancies plainly. A missing shoe, changed print or altered jacket cut should remain visible in the discussion. Do not convert one attractive image into a claim about conversion lift, fewer returns or consistent performance across an entire collection. The first useful decision is whether the example answers the client's styling question well enough to justify a separately scoped next step.

For stylists: a discussion aid for an existing service

Start from a public style board, an existing package or three current product references. The first proof uses a synthetic adult model, so you do not need to send a client photograph. State the occasion and the visual question: a stronger contrast under a jacket, a quieter shoe choice or a more coherent relationship between the top and trousers. The proof gives a client one complete-look direction to react to while your styling judgment remains central.

Keep your original recommendations, product links, measurements and retailer guidance with the concept. If the generated view changes the garment shape, explain that change before asking for feedback. A client may like a feature the model invented; separate that preference from a claim about the actual product. One bounded retry applies when a required piece is missing or the provider fails. Further concepts follow the confirmed service scope and current offer, with payment requested only after the products and written terms are agreed.

Use the selector below to choose a store, agency or stylist request. It changes the relevant form instructions while keeping the same no-access, no-customer-photo boundary for the initial proof.

Independent virtual try-on QA for a public product route

The QA route is for teams reviewing an existing virtual try-on experience. It is separate from generating a store styling proof. Agree a public route and synthetic adult inputs, then record the exact journey, source references, visible result and conditions needed to reproduce a finding. The review needs no customer photos or production account access. Results stay private; the linked sample is illustrative and is not a customer result.

First-use journey

Follow entry, upload, garment selection and generation. Record unclear requirements, dead ends, failure messages and any state that appears to promise a result the user has not received.

Identity and body

Compare the source with the output for face drift, body-shape changes, extra limbs and other visible changes that the user did not request.

Garment fidelity

Inspect missing pieces, altered color, changed silhouette and invented details against the submitted references. Keep the source and output together so the finding can be checked.

Output stability

Repeat only the agreed cases within the test limit, noting inconsistent pose, background, composition and failure handling. A repeat is evidence about those runs, not a guarantee about future outputs.

A useful finding records what happened and what was expected, the input set, route, desktop or mobile viewport, and the observed result. Pair a visible issue with a passed check where the tested route supports both. If a route cannot be tested or no issue is observed in the bounded sample, state that limit instead of inventing a defect. Visual QA does not certify physical fit, fabric behavior, sizing or sales performance.