Define what the missing photograph was supposed to establish
A shopper supplies a face-only selfie, while a proposed try-on workflow expects a visible torso. The missing body region is not simply an inconvenient crop. Decide whether the experience needs a synthetic styling representation or evidence of that person's real body and pose. Those requirements call for different input policies.
FASHN documents Face to Model as an Experimental endpoint that extends cropped headshots or selfies into upper-body avatars. Its optional prompt can guide appearance or body shape; without it, shape is inferred from the face image. Inference is not measurement. The output may be a candidate for a visual try-on pipeline, but the source does not establish the person's real dimensions.
Choose an honest admission path
| Experience requirement | Possible next action | Claim to hold |
|---|---|---|
| Synthetic styling illustration | Evaluate an authorized avatar route and disclose its role | That the generated torso is a measured body |
| Real pose or visible body reference | Request a suitable authorized photograph | That unseen pose details were captured |
| Size recommendation | Use a separately supported sizing method | That selfie expansion establishes fit |
| No permitted face-image processing route | Offer a suitable alternative experience | That the image may be sent to any provider |
Walk through a fictional cardigan request
A hypothetical customer wants to preview a cardigan and supplies an adult headshot. The merchant's proposed service can offer either a clearly described generated styling avatar or a route using an appropriately supplied real photograph. It should not silently invent a torso and then label the result “your exact fit.” No real person, customer image or provider request is involved in this example.
If the avatar route is chosen, preserve the distinction between uploaded face source, generated avatar and final garment visualization. Give each stage a separate identity in the authorized production record. Review facial resemblance and garment accuracy separately, and allow an unsuitable avatar to fail without treating the customer's actual body as the problem. Do not infer demographic, medical or body measurements from the photograph.
Keep the interface promise aligned with the pipeline
Explain the generated representation before asking a user to rely on it. A face image's presence does not authorize sharing it with an unrelated service; the merchant needs its actual permitted processing and data-handling arrangement. This guide does not implement that arrangement or create a shopper upload widget.
The fit-evidence guide addresses unsupported body and size claims. The seller versus shopper workflow guide distinguishes creative assets from a storefront feature. Here the earlier admission decision is whether missing body pixels can appropriately be synthesized for the promised experience.
Approve each stage separately
Close input admission only when the chosen route matches the actual user-facing purpose and permitted source use. Review the avatar before forwarding it into garment generation, then inspect the actual garment result against its source. Passing the first stage does not approve the second. CartVisual's own workbench capabilities must be checked separately; documentation of this FASHN endpoint does not establish a CartVisual shopper integration.