Finalize Product Image Variations: Approve, Name and Archive

Updated November 6, 2026

Finalize the set by publishing only individually approved listing assets. Keep the source master, approved exports, and rejected files in separate locations. Every active gallery image should have a recorded approval, an intended channel, and an alt-text purpose; a file does not become publishable simply because it exists in the shoot.

Separate the master, derivatives, and rejected files

Use three clear buckets:

Source master: Preserve the original blue-jar file for future derivatives and rollback. Keep it out of the active gallery.
Approved derivatives: Export specific views from the master only after a human confirms the variant, label, image purpose, and channel suitability.
Rejected archive: Retain the wrong-label version for reference, but keep it out of any active or publishable folder.

This separation prevents a useful source image from being published by default and prevents a rejected label from returning through a later export. The mapping record should identify the source file and version behind every derivative, so the team can replace an approved image without searching through unrelated assets.

Worked example: six files for one blue-jar SKU

In this illustration, a reviewer confirms that four derivatives show the correct blue variant. The source remains internal, while the wrong-label file is rejected. “Marketplace gallery” is a placeholder for the actual destination channel.

Filename	Source	Version	Status	Intended channel	Approval reference	Alt purpose
`BJ-001-BLUE-SOURCE-v01.tif`	Original blue-jar source set	v01	Source master—not active	Internal source store	—	Preserve master and rollback source
`BJ-001-BLUE-CUTOUT-v01.png`	`BJ-001-BLUE-SOURCE-v01.tif`	v01	Approved derivative—active	Marketplace gallery	APR-BJ-014	Show the product outline
`BJ-001-BLUE-HERO-WHITE-v01.jpg`	`BJ-001-BLUE-SOURCE-v01.tif`	v01	Approved derivative—active	Marketplace gallery	APR-BJ-014	Primary product view
`BJ-001-BLUE-CONTEXT-v01.jpg`	`BJ-001-BLUE-SOURCE-v01.tif`	v01	Approved derivative—active	Marketplace gallery	APR-BJ-014	Show the product in its setting
`BJ-001-BLUE-DETAIL-v01.jpg`	`BJ-001-BLUE-SOURCE-v01.tif`	v01	Approved derivative—active	Marketplace gallery	APR-BJ-014	Show a verified close detail
`BJ-001-BLUE-WRONG-LABEL-v01.jpg`	`BJ-001-BLUE-SOURCE-v01.tif`	v01	Rejected—archive only	None	APR-BJ-014 (reject)	Do not publish

Use stable filenames and complete mappings

The filename pattern should remain consistent: SKU, view, and version. If a detail image changes, create a new version rather than overwriting the previous export. Keep the name descriptive without adding repeated keywords merely to fill a presumed length allowance. There is no universal 50- or 60-character filename rule to satisfy.

Each active derivative should also retain its source filename, version, approval reference, intended channel, and alt purpose in the mapping record. Extensions and exports should match the destination’s actual format requirements. Requirements for image format, dimensions, and resolution vary by platform, so confirm the current specification for each channel instead of assuming that a large white-background image works everywhere.

Write alt text for the actual image purpose

Alt text should describe what the particular image communicates. If the files match the views above, examples include:

Cutout: “Front view of the blue jar.”
White hero: “Front view of the blue jar against a white background.”
Context: “Blue jar shown on a kitchen counter,” but only if that is the setting actually visible.
Detail: “Close-up of the blue jar’s lid and upper body,” but only if those are the features shown.

Do not claim a material unless it has been verified. Decorative images may use empty alt text, while a functional image should describe its action. For long or complex information, provide the details near the image rather than forcing them into alt text. Do not apply an arbitrary 125-character limit, and do not replace useful descriptions with generic marketing phrases.

Run the final gallery check

A practical sequence for this set is white hero, cutout, context, then detail, subject to the channel and the images’ purposes. Before release, confirm that:

Every active file is marked approved in the mapping.
Each image shows the actual blue-jar variant selected by the customer.
Visible labels match the product being sold.
The export resolution, format, and dimensions meet the chosen channel’s current requirements.
The rejected wrong-label file remains outside the active gallery.
The source master and prior approved versions are recorded in a known rollback location.

The example is an asset-management record, not a complete gallery for every marketplace. If an Etsy item requires a real, unedited photograph, include that qualifying listing image alongside permitted edited supporting images. Keeping the archival master private does not waive the unedited-photo requirement.

Continue with the next task

Sources and scope

Documentation checked November 6, 2026. Rewarx is the publisher. Covers are MiniMax-generated editorial concepts, not measured products or outputs of the tool discussed. Native diagrams and worked examples are labeled illustrations. No customer conversion result, physical product test, live marketplace transaction or hands-on provider benchmark is claimed.

https://www.rewarx.com/blogs/finalize-keep-product-image-variations-ecommerce

Finalize Product Image Variations: Approve, Name and Archive