Product photography workflow: approve clothing images

A useful product photography workflow ends with a specific file approved for a specific use. Keep the source, review the output, record any product discrepancy and name the destination before publishing. A saved generated image is ready to inspect; it is not automatically ready for a customer-facing product page.

The jeans example makes the distinction practical. Two retained Fotogenic AI results work as supporting campaign images. A third scene was rejected because it changed the fly. The record below shows how to carry that decision into the publishing handoff.

Define what approval allows

Use the complete source to establish the visible product. For these dark-indigo jeans, the reference shows one waistband button and a zip fly. A reviewer can compare that closure with the returned scene without guessing from a thumbnail.

Write the intended use beside the image: supporting campaign, main product view or factual construction detail. Approval for a styled street scene does not approve the same file as proof of fit or exact textile construction.

If the missing view needs a real photograph, use the clothing shot plan before commissioning another scene.

Review saved images in Fotogenic AI

1. In WordPress, open Fotogenic AI → Studio. For an image-only review workflow, choose Media source and select your complete clothing reference.
2. Continue to Generate Images. In Configure → Results settings, check that this Media source task saves new images to Media Library for review. This keeps this Media source task separate from applying images to a store product.
3. After generation, open Summary. When the result is Saved, choose Open image and compare the full-size file with the original reference. Inspect the garment before judging the background.
4. Record your decision and permitted use outside the image before handing it to the publisher. Keep rejected results out of the approved selection; do not rely on their download order.

For the retained set shown here, the creative direction is warm autumn street styling around dark denim. The full-length portrait supplies outfit context; the closer view gives the waistband visual emphasis. The separate review decision determines where each is useful.

Follow the WordPress walkthrough for configuration screens and scene instructions. Saved confirms file delivery, not a built-in product-approval decision.

Use a filled approval record

Give the publisher the source, selected result, decision, allowed placement and next action. These three decisions come from the retained jeans set.

Full-length street portrait: accept for styling

Source: dark-indigo jeans front reference. Result: walking outfit with rust knitwear and coat. Decision: accept as a supporting campaign image. The visible single-button closure and wide-leg silhouette remain recognizable. Next action: check the final placement crop before publishing. Do not describe the generated person as a measured fit model.

Seated café portrait: reject

Source: the same jeans reference. Result: seated café outfit. Decision: reject because the output introduces an exposed multi-button fly. Next action: exclude this file from the publishing selection. A strong setting does not resolve a changed fastening; a filename or crop cannot make that version approved.

Waistband close-up: accept for campaign detail

Source: the same jeans reference. Result: a closer street view of the waistband and pocket. Decision: accept for a supporting campaign detail. Next action: keep a real garment close-up for factual textile or construction claims. The two accepted results appear together at the end.

Source and version: [your garment reference]. Result and version: [selected file]. Decision: [accept / revise / reject]. Allowed use: [specific placement]. Reason: [one concrete observation]. Publisher: [responsible person]. Next action: [publish / revise / exclude].

Fill every field before sending the record. “Looks good” leaves the destination unclear; “accepted for the product-page styling slot” tells the publisher what the decision covers.

Hand off a reversible image replacement

Before replacing an existing image, record its file and current position. Keep it available until the replacement has passed a live check. The approval record should identify the exact new file, intended product and permitted slot, so a publisher never has to choose between similar downloads.

For the jeans, the full-length result belongs in a styling role. The closer result may accompany it as campaign detail. Neither decision authorizes replacing a reliable front or back product photograph with a generated interpretation.

After the publisher applies the selected file, reopen the actual product on desktop and mobile. If the wrong variant appears, the crop loses the approved garment detail or the image fails to load, return to the retained previous selection while resolving that specific issue. Record the result of the check beside the decision.

Use the WooCommerce image workflow or the Shopify guide below for the actual store controls.

The Shopify image and variant guide covers product and variant assignment. This approval record is a manual handoff, not a new store integration.

Let the review reason choose the next action

A product change means the candidate is rejected for that use. A sound garment with the wrong campaign mood needs a revised creative direction. A correct file on the wrong product needs a publishing correction. Keeping those reasons separate prevents another generation from being used to solve a file-assignment mistake.

For a later composition or lighting change, see Image Variations. Compare the garment again after the change; the earlier approval applies to the earlier file.

For the broader capture, editing and delivery sequence, read Shopify’s photography workflow guide.