Create variant visuals from a verified record of each item and its approved source images. Keep the scene and layout rules consistent, but swap in the correct real variant rather than asking AI to invent a new color, capacity or package. Check the finished image against that variant's source, then verify that the correct file appears when the customer selects it.
- Define the actual variant set before making images
- Decide which differences must remain visible
- Assemble approved sources before using a common style
- Establish the shared visual rules without erasing differences
- Use Dreamina for a candidate with a defined identity boundary
- Build one controlled output per approved variant
- Compare the set twice: by item and by relationship
- Assign the images to the correct product options
- Troubleshoot the mismatch at its source
- Walk through a fictional three-variant set
- Deliver the variant set with its identity intact
- Questions about real product variants
Dreamina can help develop a shared campaign setting or a reference-led creative candidate. It does not determine which variants your business sells or verify that a generated color belongs to a real SKU. The workflow below keeps that identity relationship visible from planning through delivery; its sample variant records are fictional teaching examples.
Define the actual variant set before making images
Start with the product records, not the images already in a folder. Identify the exact options sold: color, size, capacity, finish, packaging, included accessories or another meaningful difference. Confirm which combinations exist. A blue product and a large product do not automatically imply that a large blue version is available.
Choose a stable identifier for each sellable combination. Use the existing SKU or another approved internal identifier when available. Record the displayed option names alongside it so that the visual file can be matched to what customers select.
A useful working table has six fields: variant identifier, option values, approved source, visible distinguishing features, required outputs and review status. It gives every image a defined destination before generation or editing starts.
For illustration only, imagine these three records:
These codes do not describe real stock, and the table is not a catalog test. Its point is the relationship: color and capacity are product facts. A generated “red version” of the blue cup is not sufficient evidence for the red SKU, and enlarging the smaller cup's picture does not establish the larger one's construction.
Decide which differences must remain visible
Two variants can be similar overall while differing in a detail that matters to the purchase. A matte and gloss finish may share the same silhouette. Two capacities may use different proportions or lid designs. A refill and a complete kit may have different included pieces.
Create a short check for each difference. Color needs comparison with an approved reference under sensible viewing conditions. Capacity needs the actual shape, proportions and any visible marking. Packaging needs its real artwork and configuration. Accessories need a clear record of what is included.
Do not depend on a filename or colored badge to compensate for a wrong product image. The picture itself should represent the selected item. Conversely, do not expect the photograph alone to explain every invisible specification. Keep accurate option text and product information alongside it.
Separate legitimate shared features from variant-specific ones:
This distinction prevents a style template from becoming a product template that overwrites meaningful differences.
Assemble approved sources before using a common style
For every variant, obtain a clear photograph or approved rendered asset that represents that exact item. Keep the whole product visible and important details readable. If the required view is unavailable, obtain it or choose an honest alternative view; do not assume a generator knows an unseen side of the product.
Keep source files separate from creative candidates and final exports. Record which source belongs to which variant. Similar filenames, nearly identical thumbnails and copied folders are common opportunities for mismatches, so include the stable identifier in the working relationship.
Inspect the source quality too. A heavy color cast, hidden label or cropped handle weakens later verification. Correct a capture problem or find a better source before using it to establish a supposedly faithful variant visual.
The label-and-shape preservation workflow explains how to retain authentic product artwork when scene changes could redraw it. Use that method for the source-preservation task, then return here to manage the whole variant set. A well-preserved image can still be assigned to the wrong SKU.
Illustrative asset map. The records and colored symbols are fictional; they are not photographs, generated products or evidence of available merchandise.
Establish the shared visual rules without erasing differences
Choose a representative layout and write the rules that should carry across variants: canvas size, background tone, camera direction, product baseline, margins and the treatment of supporting copy. Make those rules specific enough to reproduce.
Decide how size will be communicated. If two capacities appear together, their relative dimensions should be based on the real products. If separate listing images normalize product framing for easy browsing, do not present that normalization as a literal comparison of physical size. Provide a separate accurate size comparison when the purchase decision needs it.
Do not force every variant into identical geometry. A larger body, different handle or different package may need different framing to stay fully visible. Keep the presentation system stable while allowing the actual product to occupy it honestly.
Choose the reference for style carefully. A generated image containing one variant can unintentionally encourage later candidates to inherit that variant's cap, color or label. A background-only style reference or a written scene rule can be easier to separate from the exact product reference.
For a catalog covering different product categories, use the mixed-catalog style guide. This article concerns multiple real variants of a product family, where the specific option-to-image match is the central requirement.
Use Dreamina for a candidate with a defined identity boundary
When creative reconstruction is acceptable, Dreamina's image-to-image workflow provides a documented route: open AI Image, upload through +, add the change instruction, select Image 5.0 Pro by Seedream 5.0 Pro, choose available output settings, generate, review and download. Use the exact variant's reference for each candidate. Dreamina's image-to-image instructions
Keep the scene instructions consistent, but do not replace the real reference with the previous generated variant. Returning to the approved source helps prevent a small change in one candidate from becoming the next candidate's definition of the product.
An instructional, untested prompt could read:
Use the uploaded reference for this specific product variant. Keep its visible shape, color, finish, components and packaging markings as close to the source as possible. Place it in the approved pale studio setting with soft side light and the same framing convention as the campaign. Do not recolor the product, change its capacity, add accessories or invent new lettering.
Those words express the requirement. They do not prove it was met. Compare the candidate with the variant source, and keep a useful scene without accepting a redrawn product when exact representation matters.
If you need exact product identity, develop the background or composition separately and retain the approved product asset in the final layout. The creative operation can change the setting while the variant record remains tied to authentic artwork. That is a production choice, not a promise that every automatic cutout is already finished.
Build one controlled output per approved variant
Create a working layout for the shared style. Bring in the correct variant asset and verify it before refining the surroundings. Use the stable identifier in the product layer or working document name so that the relationship stays visible during editing.
When moving to the next variant, duplicate the layout structure and deliberately replace the product source. Clear any previous variant image that is no longer needed. A hidden old layer can later reappear during export or a last-minute correction.
Check the replacement at full view and close up. Confirm that the source is not merely a different crop of the previous variant. Inspect the details that distinguish this record, including components and packaging, before approving the shared treatment.
A common background may interact differently with each real color or finish. A dark product may lose its edge; a glossy version may show reflections absent from a matte one. Adjust the surrounding treatment within the approved style rather than recoloring the product to force a match.
Keep the sequence manageable: identity check, presentation adjustment, final export, then status update for that record. Do not produce a large unlabeled pile and try to determine later which candidate belongs to which SKU.
Compare the set twice: by item and by relationship
First inspect each final image against its own source. Check the actual variant's color, silhouette, proportions, label, packaging and accessories. This is the fidelity review.
Then arrange the final images together with their identifiers. Check whether the set follows the shared presentation rules and whether differences remain understandable. This is the set review. It cannot replace the first review: a beautifully consistent row can consist of three incorrectly recolored products.
Use the variant table to trace both directions. From a record, find its source and final file. From a final file, identify the corresponding record and source. If either direction is ambiguous, fix the mapping before delivery.
Pay particular attention to nearly identical variants. A changed small quantity marking, connector or package count may be easy to miss in a contact sheet. Review those features close up and check the supporting product information too.
Do not use a broad “looks consistent” approval for the entire set. State which records are accepted and which still need a source, correction or assignment check. That keeps one incomplete variant from inheriting the approval of its neighbors.
Assign the images to the correct product options
The visual work is incomplete until the image is matched to its intended option in the delivery system. Uploading all files into a gallery does not necessarily assign the right preview to each variant.
For a concrete example, Shopify documents Products > selected product > Variants, then the image icon beside the relevant variant. Select an existing image or add the correct file, choose Done, and Save. Its current help page says each variant has one assigned image; additional related images can sit in the product gallery. Shopify's variant-image instructions
That is a Shopify-specific example, not a claim that every commerce platform uses the same controls or automatically groups all related media. Follow the actual platform's assignment model and verify the selected result.
Preview the product page and select every available combination. Check that the option text, image and included-item information agree. A blue thumbnail beside a red selection is a delivery error even if both source images are accurate.
Check default selection behavior as well as changed selections. A page can open on the wrong image before any option is clicked. Where the theme or system handles additional gallery images, verify that behavior rather than assuming it follows the assigned preview.
Troubleshoot the mismatch at its source
Avoid fixing a mapping error by renaming the file to match whichever record happens to use it. Fix the source-to-record relationship. Avoid fixing a color error by repeatedly prompting until the output looks roughly like the option name; compare with an actual approved reference.
If the product information itself is uncertain, resolve that before generating a sellable visual. A design tool should not decide whether a capacity, color combination or accessory package exists.
Walk through a fictional three-variant set
Consider the fictional blue 350-ml, red 350-ml and blue 500-ml cups introduced earlier. The task is to prepare coordinated campaign images, not to create new merchandise.
Begin with three verified records and three approved sources. The first two share construction but differ in finish; the larger version has its own proportions. Record those differences before choosing a common warm-neutral presentation.
Develop the scene direction in Dreamina as a candidate and test the layout with one real source. Then apply the presentation to the other sources individually. If a generated red candidate changes the handle, reject that product depiction even if the color is attractive. If a shared crop clips the larger cup, adapt the framing rule rather than shrinking the source's body shape.
Place the three finals in a contact sheet with their identifiers. Compare each to its own source and verify the overall style. Export with identifiers that keep the files distinguishable, then assign them to the matching option records in the intended system.
Finally, select each option in the preview. The accepted outcome is three accurate, correctly connected visuals. No real SKU set was generated or tested in this example, and no business-performance result is implied.
Deliver the variant set with its identity intact
Provide the final files and a compact mapping table identifying the variant, source and approved outputs. Keep editable masters and source references available for corrections. Record any unresolved item rather than silently substituting another variant's visual.
Include the intended use of comparison images. If a group arrangement represents relative size, say which real dimensions informed it. If separate tiles use normalized framing, describe them as individual product views rather than a scale comparison.
Reopen the final exports and confirm that their contents match their filenames. Test the actual product-page selection or handoff destination. The image's correctness and its assignment must both pass.
Questions about real product variants
Can I generate every color from one photograph?
You can explore color concepts, but those outputs do not verify real sellable variants. Use approved references for the actual colors and construction, and keep concept images separate from merchandise representations.
Can I enlarge the small version to depict a larger capacity?
Only changing picture scale does not establish the larger product's proportions or components. Use the actual larger variant source. For a physical-size comparison, base the relationship on real dimensions.
Why does a consistent set still need individual review?
Style consistency can hide repeated mistakes. Each image must match its own variant, and each final file must be assigned to the correct option. Review both the individual product and the set relationship.
What if one variant has no approved photograph?
Mark it as awaiting source or use another approved representation of that exact item. Do not quietly substitute a generated interpretation or a neighboring SKU and label it as verified merchandise.