Product-photo filenames: a scheme based on SKUs and views
Associate images, variants and views without relying on folder order or names such as final-final.

A visually consistent catalog can still be hard to manage when filenames do not identify products. Names primarily help people and processes associate images with the right reference. They replace neither image verification nor quality review.
Choose a stable identifier
Start with the SKU or code used by your system. Preserve variant distinctions where variants have separate codes. Avoid basing identity on a commercial title that changes during the season.
Add a recognizable view
One possible scheme is SKU-variant-view-version, such as BAG042-OLIVE-FRONT-V02. This is an organizational example, not a Centyr-required format. Agree on a short vocabulary: FRONT, BACK, SIDE and DETAIL. If numbers define gallery order, document their meaning.
Make versions unambiguous
Assign a number or date to deliveries. Separate sources, working files and approved outputs into different folders. Calling every output “final” becomes confusing when color is revised or a channel requests a different format.
Check the mapping before delivery
- The SKU exists in the catalog.
- The image shows the correct variant.
- The view matches the filename.
- The file is complete and readable.
- Approved versions are separate from tests.
For larger batches, a reference table can connect source names with delivered names.
Account for workflow transformations
Do not assume every tool preserves filenames or every gallery sorts alphabetically. Test an actual upload and download. Manage this scheme within the team process; it does not imply automatic renaming or SKU association in Centyr.

