How to organise clothing images for multiple colour variants
Keep generated product images connected to the correct garment and colour variant. Build a clear source, review and publication workflow for collections with similar-looking items.
Begin with a variant list
Write down the product references and colour variants that need images before starting generation. Use the same identifiers that the person publishing the catalogue recognises. A colour name alone may not distinguish two similar products, and a product name alone may not identify the intended version. Keep both pieces of information together throughout the workflow.
Record the image roles required for each variant. One item may need a main product view, a styled secondary image and a close-up of a distinctive feature. Another may already have useful real photographs and need only a supporting scene. Defining the missing assets avoids generating a large folder of images without knowing which gaps they are supposed to fill.
Keep the list modest and practical. It can be a simple table or a clearly structured document, provided that it identifies the item, the variant and the status of each required asset. Avoid adding fields that nobody will maintain. The purpose is to make the next decision clear and prevent a similar-looking file from being assigned to the wrong listing.
Match each source photograph to the actual variant
Use a source photograph of the variant you intend to represent whenever possible. A generated colour change does not establish that the resulting shade, trim or pattern matches another physical item. Different variants may also differ in details that are not obvious from the product name. Check the source against reliable product information before creating the working set.
Inspect the photographs for accidental ambiguity. A dark navy item and a black item may appear similar under poor lighting, while a warm colour cast can shift the appearance of a neutral garment. Label the files from verified references rather than guessing from the image alone. If the distinction remains unclear, resolve it before producing more candidates.
Keep the original files separate from any adjusted working copies. An edit that makes a photograph look more appealing may alter the very colour you need to preserve. Retain enough context to understand how the working source was prepared. If another person joins the project, they should be able to locate the original reference without asking which edited copy came first.
Use a consistent naming pattern
Choose a filename pattern that puts the stable product reference first, followed by the variant and image role. Add a version marker for working candidates. The exact punctuation matters less than consistency. A name should help someone identify the file without opening every image, but it should not be treated as proof that the visible garment is correct.
Separate working versions from approved delivery files. A folder full of names ending in final, revised-final and newest-final creates avoidable uncertainty. Use a clear status in your working list and keep only the selected delivery copies in the publication folder. Preserve the useful earlier candidates elsewhere when they explain a review decision or a correction.
Avoid embedding unnecessary personal information in filenames. A catalogue image normally needs product and workflow references, not private customer details or a reviewer's contact information. Use a shared naming convention that the team can understand. If the catalogue already has a reliable identifier system, extend it rather than creating a competing set of informal names.
Define what should remain consistent across the set
A collection benefits from a coherent presentation, but consistency does not mean every image must be identical. Agree on broad rules for framing, background treatment and the space around the garment. Keep those rules connected to the image role. A square collection card and a taller detail view may need different crops even for the same product.
Choose one reviewed reference image as a visual direction for the set. Use it to compare camera distance, garment visibility and background tone. Do not assume that a generation setting will reproduce the same pose or garment details for every item. Check each output independently, particularly when a print, fastening or sleeve shape differs between variants.
Make exceptions deliberate. A pale garment may need more separation from a light background, and a long item may need a different crop to remain fully visible. Record the reason for a useful exception rather than forcing a rule that makes the product difficult to inspect. Consistency should make comparison easier for the shopper, not hide important differences.
Generate a small batch and review it together
Start with a manageable group of variants. Produce the required candidates, then review them as a set as well as individually. A group view can reveal inconsistent scale, background colour or framing that is less obvious when each file is inspected alone. Keep the product references visible during the comparison so that visual similarity does not lead to a mistaken assignment.
Check the garment against its own source. It is not enough for all the generated images to match one another if they share the same incorrect detail. Compare colour, print placement, fastenings and the outline of the item. Keep actual product photographs available for features that need precise evidence, and reject a scene that changes a defining characteristic.
Record a short decision for each required asset. Some variants may be ready for publication while others need a clearer source or a different approach. Do not mark the whole batch approved because most images look acceptable. A per-variant status makes it possible to continue useful work without allowing an unresolved item to slip into the delivery folder.
Prepare a clear publication handoff
Deliver approved files with a small manifest. Include the product reference, variant, image role and selected filename. Add the intended order when several images belong to one product. If alternative text has been prepared, keep it matched to the specific file rather than attaching one generic description to every colour option in the collection.
Explain any limitations that affect the publisher's decision. A scene may be approved as a secondary styling view while a real photograph remains the main product image. Another file may be suitable for an internal campaign concept but not for a listing. These distinctions should be explicit so that the publication step does not depend on interpreting a reviewer's informal comment.
Use the destination platform's normal product-media tools to upload and assign the assets. Check the relevant product and variant in the preview after each small batch. A correct manifest can still be applied incorrectly through a mistaken selection. Keep the previous live files available until the new presentation has been checked and accepted through the team's usual process.
Check the storefront after assignment
Open the product as a shopper would and move between the available variants. Confirm that the displayed image corresponds to the selected option and that the gallery order remains understandable. Check both a narrow layout and a larger view. A theme can crop or arrange media differently across layouts, which may affect whether the garment is shown clearly.
Read the visible product information alongside the image. Colour names, descriptions and photographs should describe the same item. If a generated scene uses lighting that makes a variant ambiguous, include a clearer real view or choose a more suitable candidate. Do not expect the customer to resolve a contradiction between the image and the option they selected.
Record any publishing correction against the same product reference used during preparation. This closes the loop between generation, review and the live catalogue. If a file is replaced, update the manifest so that an older version is not uploaded again during a later edit. Keep the record focused on the information needed to maintain the published asset set.
Maintain the collection when products change
Recheck images when a supplier changes a material, trim, print or colour description. A photograph that was suitable for an earlier version may no longer represent the item being sold. Keep the product update connected to the image review instead of treating the media folder as permanently correct. Even a small construction change can matter to a buyer.
Archive obsolete delivery copies through the team's ordinary file-management process, while preserving the history needed to understand previous publications. Do not remove the only useful source reference before the replacement has been checked. A clear current folder and a separate archive are easier to use than one large directory containing every version without status.
When a new person takes over the catalogue, give them the naming convention, the current variant list and the approval criteria. They should be able to identify the source, approved master and live delivery copy for a product. A workflow that another person can continue is more reliable than one that depends on the original editor remembering every exception.
Variant image checklist
- List the product reference, variant and required image roles.
- Verify the source photograph for each actual colour option.
- Keep originals, working candidates and approved files separate.
- Apply consistent framing rules while allowing useful exceptions.
- Review every garment against its own source image.
- Deliver approved files with a simple product and variant manifest.
- Check the storefront after assigning the media.
- Revisit the image set when the physical product changes.
Use the photo studio to prepare candidates, then follow the generated-image review guide before assembling the publication folder. Generation, approval and catalogue assignment are separate stages. Keeping their statuses clear helps a small team avoid preventable mistakes without requiring a complicated asset-management system.
Frequently asked questions
Can I use one generated image for every colour variant?
Only use an image where it accurately represents the relevant item and its intended role. A generated recolour does not verify the shade or details of another physical variant. Use reliable source photographs and check the visible result. Keep real product views where precise colour or construction information is important.
What should a variant image filename include?
Use a stable product reference, the variant and the image role, with a version marker for working candidates. Keep the naming pattern consistent and avoid unnecessary personal information. Pair the filenames with a simple approval record so that the publisher can distinguish a selected delivery file from an unfinished concept.
Why should I review the images as a group?
A group view can reveal inconsistent framing, garment scale or background treatment. It does not replace checking each garment against its own source. Both views are useful: the individual review protects product accuracy, and the group review helps the collection remain clear and coherent for a shopper.
What happens when the supplier changes the garment?
Review the relevant source and published images again. A new trim, fabric or print can make an earlier asset unsuitable even when the product name stays the same. Update the variant record and delivery manifest so that an obsolete file is not accidentally reused during a later catalogue edit.