Itemlume
Sign inCreate account

PRODUCT CREATIVE / PRODUCTION AND HANDOFF

Why Did FASHN Replace My Entire Outfit When I Only Wanted to Try On a Top?

Check the garment reference and category setting first. In FASHN Try-On v1.6, category=auto can interpret a full-body on-model garment reference as a complete outfit. If the intended replacement is only a top, evaluate an explicit tops category instead of relying on automatic classification.

01 / WHY DID FASHN REPLACE MY ENTIRE OUTFIT WHEN I ONLY WANTED TO TRY ON A TOP?

Identify Which Image Defines the Clothing

The garment_image represents the clothing being transferred. The model_image represents the target person who will wear it. These inputs have different responsibilities, even when both photographs contain people.

When category is auto, a full-body on-model garment reference defaults toward a full-outfit swap. Upper- or lower-body-focused references can lead to corresponding clothing categories. Flat-lay references follow a separate automatic classification path. Do not conclude that a full-body target model photograph alone causes full-outfit replacement.

02 / WHY DID FASHN REPLACE MY ENTIRE OUTFIT WHEN I ONLY WANTED TO TRY ON A TOP?

Set the Replacement Scope Before Production

Record which clothing must change and which existing clothing must be reviewed for unintended changes. If the garment reference shows a full outfit but the merchant wants only a top, evaluate an explicit tops category rather than relying on auto.

For this API workflow, the official request uses model_name="tryon-v1.6". Put model_image, garment_image and category inside inputs; category is not a top-level request field. This states the documented request structure, not an executed request or a guarantee that unrelated pixels remain identical.

  1. Identify the actual model_image and garment_image and save their file/version references.
  2. Read the submitted inputs.category. For a top-only brief, record whether it is auto or explicitly tops before deciding on a new request.
  3. If a candidate is produced, compare it with both sources: first check replacement scope, then garment details and unrelated clothing. Record each problem separately.

Check field placement and category behavior against the FASHN Try-On v1.6 input definitions.

Before choosing the garment reference, prepare garment photos for virtual try-on so the intended variant and necessary details are visible.

03 / WHY DID FASHN REPLACE MY ENTIRE OUTFIT WHEN I ONLY WANTED TO TRY ON A TOP?

Illustrative Exercise: Two Garment References

Illustrative exercise, not an executed request: use the same target model with either a full-body outfit reference or an upper-garment-focused reference. For a jacket-only brief, the full-body reference calls for checking auto classification and evaluating explicit tops; the focused reference still needs scope review. The table summarizes the decision, while the worksheet is left for actual inputs and observations.

Fictional garment referenceMerchant intentDecision
Full-body outfit photographReplace only the jacketEvaluate explicit tops rather than relying on auto
Upper-garment-focused photographReplace the upper garmentReview automatic classification against the brief
04 / WHY DID FASHN REPLACE MY ENTIRE OUTFIT WHEN I ONLY WANTED TO TRY ON A TOP?

Review the Intended and Unintended Changes

Keep three references in the approval record: the garment source, the original target model, and the generated result. Compare the new upper garment against the garment source while checking whether unrelated clothing changed.

If the result replaces trousers despite an upper-garment-only brief, record a scope failure separately from fabric-detail inaccuracies. These require different investigations.

Do not repeatedly change unrelated creative instructions before confirming the category and input roles. The documented Stable v1.6 behavior, released June 25, 2025, supports this diagnostic branch but does not establish a guaranteed outcome for any merchant photograph.

05 / WHY DID FASHN REPLACE MY ENTIRE OUTFIT WHEN I ONLY WANTED TO TRY ON A TOP?

Garment scope and submitted-category record — complete with actual observations

Save a copy of this record and enter actual inputs, actions and observations. Keep incomplete checks pending; do not prefill success.

RecordActual value to complete
Task/SKU and approved replacement scope
Actual model_name
model_image file/version
garment_image file/version and framing
Submitted inputs.category and request-record location
Other submitted settings relevant to the comparison
Candidate identifier
Unintended clothing changes and problem locations
Garment-detail mismatches and problem locations
Unresolved issue and review status

Download review worksheet (CSV)

Published by ItemlumePublished Updated Evidence and editorial policy
SOURCES & SCOPE

Sources and further reading

Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.

QUESTIONS, ANSWERED

Frequently asked questions

Does a full-body model_image automatically trigger full-outfit replacement?

No. The documented automatic classification concern here is the on-model garment reference. Distinguish garment_image from the target model_image.

Will explicitly setting tops guarantee that trousers remain unchanged?

No. It specifies the intended clothing category, but the resulting image still requires inspection for unintended changes.

PREPARE ASSETS FOR YOUR NEXT STEP

Create supporting product assets in Itemlume.

Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.

Explore asset creation tools Check pricing and credits