Make the filename point to the right product.

Choose a convention before the export batch

Agree on product identity, variant, image role and revision with the person receiving the files. A pattern such as SKU-variant-role-r01.jpg can make these fields easy to scan. It is a local team convention, not a universal platform requirement. Use your actual inventory identifiers and keep an explicit mapping when an editor-friendly slug differs from the original SKU.

Avoid changing the meaning of a field between products. If “front” means a factual front view, do not assign it to a generated lifestyle scene. Reserve clear roles such as detail or lifestyle, and keep camera originals outside the exported-deliverables folder.

Describe what the view adds — Use image-role examples to write meaningful alternative text.

Keep image selection tied to a revision — Use a contact sheet to approve direction without confusing source and final files.

Keep variant identity and origin visible

Name the photographed color or package from the real SKU, then compare the export with that source. Renaming a generated recolor does not make it an accurate photograph of another stocked variant. A text-only product concept belongs in a concept record and should not be handed off as inventory photography.

The filename cannot carry the whole review. Maintain a small manifest with the original identifier, normalized name, file revision, image role, source type, approval status, owner and destination. Keep origin metadata checks in the manifest as well when a channel requires them.

Plan a manual product batch — Approve a pilot, track exceptions and keep each source SKU with its outputs.

Check whether a product image can be discovered — Audit the image URL, page markup and surrounding product information separately.

Record the destination mapping separately

A store may need product identifiers, image position, variant-image assignment and a working image URL. Shopify’s CSV guide treats these as separate fields, and it says product image filenames are final after upload. Read the current import specification and test a small sample in your actual workflow before a catalog-wide operation.

This page only prepares a filename and a manual record. It does not generate a valid Shopify import, host images or assign variants. Do not assume a platform reads SKU or role from a name automatically. If an import is part of the project, keep its schema, preview and observed mapping as separate evidence.

Plan a real product-spin sequence — Record views and publish a real sequence when shoppers need to rotate the item.

Deliver the approved revision with a short audit

Check for duplicate names, missing variants, stale revisions and files whose extension does not match the actual format. Separate approved exports from candidates on hold. A reviewer should be able to trace each delivered file back to the real reference and the approval decision.

Open a sample from each product family and verify the selected option in the destination. Retain the approved revision even if the live platform changes the served filename. Fayvoro has no bulk catalog mapping or automated store import; generate and review one scene before deciding whether it belongs in the batch.

Match each option to the right photo — Test the selected option, image and cart against a real SKU mapping.