Brief multiple SKUs without mixing product details
By Drizzle team
1 min read
A batch becomes hard to review when prompts and reference photos cross between products.
Separate source sets
Give each SKU its own folder with the exact color, package version, and approved facts. Name every output with that SKU.
Reuse structure carefully
The shot pattern can repeat, but product construction checks must change. A strap count from one bag should never become a default for another.
Approve per item
Review each still and clip against its own source. Do not approve a batch because one attractive example passed.
A worked example
Suppose a seller needs clips for six tote colors. Keep six distinct source folders, each containing front, side, and interior images of that variant. A common shot list can save planning time, but review each output for its own color and stitching. Do not approve all six because the first tote looked right.
Decision check
Review the exact SKU, source imagery, current offer, and destination as one chain before using the asset. A generated scene can be visually persuasive while changing construction or availability. Save the accepted file with its product version and retire it when the physical item or terms change.