Assets & tasks / QUESTION GUIDE
How do you detect mixed product revisions in a supplier photo folder?
Check whether every source photograph shows the same current product revision. A supplier folder can mix older packaging, a changed connector and a new color name under one SKU. Resolve those conflicts before generation; the system should not be asked to average different physical products into a plausible hybrid.
Find the revision evidence
Ask the product owner for the current SKU, packaging revision and relevant change record. Compare each photograph with those identifiers. File dates alone may reflect download or export time rather than when the product was manufactured. Use actual construction and approved records to establish the current version.
For an illustrative desk device, one image may show the old rear connector while another shows the new control layout. Both can look professionally shot, but they do not form a consistent source set.
Create a source reconciliation table
| Photo | Visible revision cue | Status |
|---|---|---|
| Front A | Current label confirmed | Use |
| Rear B | Older connector | Hold |
| Detail C | Current control | Use |
| Scene D | Variant uncertain | Ask supplier |
Record uncertainty instead of choosing whichever photograph best fits the desired scene. If the supplier cannot resolve a critical difference, obtain a new photograph of current stock.
Generate from the reconciled set
In the relevant CartVisual workbench, upload only the approved current references and describe the exact variant. Keep the held files out of the submitted set. A detailed requirement cannot reliably repair contradictory source evidence after the fact.
Inspect the candidate for hybrid construction, such as a new front with an obsolete rear port. This manual source decision must come from the product owner’s actual record; a generated candidate is not a revision-database check.
Preserve the source decision
Keep the reconciliation table with the generation record and final asset. When another team member asks why a high-quality image was excluded, the revision reason should be available. If a product update arrives later, repeat the comparison rather than appending new photographs to the old set.
Use replacement planning for already released assets and source tracing for the record. The output of this guide is a coherent source set, before any creative candidate exists.
Fictional SKU D keeps the same sale name through revisions R1 and R2. The product owner’s R2 record confirms a changed rear connector and unchanged front wordmark. Folder file F1 shows that front, R1-rear shows the old connector, and S1 hides the rear entirely. A later download date on R1-rear does not make it an R2 photograph.
| Source | What is established | Intake decision |
|---|---|---|
| F1 front | Wordmark matches both revisions | Use only for the confirmed front facts; it does not establish the rear |
| R1-rear | Old connector visible | Hold from the R2 generation set |
| S1 scene | Rear cannot be inspected | Do not infer the missing connector from the file name |
| New R2 rear request | Evidence not yet supplied | Obtain a same-edition photograph before depicting that side |
Exclude held sources from the actual input set, not just from the written brief. If the current edition cannot be resolved, narrow the requested view or wait for evidence. After the product changes, the replacement-plan guide handles published placements; this intake step prevents a mixed source set before generation. No supplier folder or physical unit was tested here.
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.
- CartVisual: editorial scope and evidence policy · Review date not separately recorded
- Photoroom: product image realism and accuracy · Reviewed
Frequently asked questions
Does the newest file date prove the latest product?
No. Verify the physical revision and approved records.
Should I upload conflicting photos for more context?
Resolve the conflict first; do not create a hybrid source set.
Can a polished generated image settle a supplier revision conflict?
No. Resolve the actual product record and source photographs first.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in CartVisual.
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