How to organize product images and match them to SKUs

1. Introduction

Throughout this guide we follow a fictional manufacturer, Everlight Housewares, preparing images for three lighting SKUs, fixing a few misnamed files, and verifying the result in the product gallery. All company names, SKUs, filenames, and screenshots-style previews are fictional demo data.

The platform side of this workflow is Product Images: a central repository, SKU-linked images, and a per-product gallery.

2. Why SKU-based image organization matters

An image file and a catalog record are strangers until something connects them — and that something is the SKU, carried in the image filename. Organize images around SKUs and a thousand files match their products in one pass; organize them around photographer session names ("IMG_4482.jpg") and every file becomes a manual decision. The habit pays off downstream too: image files and catalog files stay two separate, clean inputs — products reference images by filename, and the platform joins them.

3. Review the product catalog first

Images match against the catalog you already have — so the catalog's SKUs are the source of truth. Before renaming a single file, confirm the catalog is imported and mapped (see mapping CSV columns) and skim the SKU column in Product Data Management. Renaming 500 images to SKUs that turn out to be formatted differently in the catalog is the most avoidable afternoon in this workflow.

4. Choose a consistent SKU naming convention

Whatever your SKU format is — Everlight uses ELH-LAMP-120-style codes — it must be identical in the catalog and in the filenames: same separators, same case discipline, same zero-padding. The same SKU-consistency rules that govern update files apply here (see the product-updates guide): whitespace, dropped leading zeros, and missing separators are what break matching.

5. Prepare image filenames

The filename carries the SKU — that's the whole trick. One widely used convention, shown here with Everlight's fictional SKUs:

The exact naming convention must match the image workflow configured for your account — confirm the expected pattern before renaming in bulk.

6. Handle primary and alternate images

Where primary and alternate images are supported, one common convention distinguishes them by suffix: the base SKU filename is the primary image, and numbered suffixes are alternates.

Again: this is one possible convention. The pattern your account actually uses is set by the configured image workflow — align with it rather than inventing your own suffix scheme.

7. Organize images into upload folders

Batch your files so an upload is reviewable: by brand, by category, or by photo-shoot delivery — whatever lets you say "this folder is done" with confidence.

The holding folder is the useful part: files you can't confidently name yet stay out of the upload instead of becoming mystery mismatches later.

8. Check image formats and dimensions

Use standard web image formats such as JPG or PNG, sized generously — a larger clean source beats an upscaled thumbnail. From what you upload, supported image outputs and dimensions may be generated according to the image workflow configured for your account; that doesn't promise every size every downstream channel might want, so if a partner needs an unusual spec, confirm it rather than assuming.

9. Remove unsupported or corrupted files

Sweep the staging folders before uploading: delete zero-byte and truncated files, convert files in unsupported formats, and pull out the things that aren't product images at all — logos, lifestyle collages, and the photographer's contact sheet. A corrupted file can't become a product image no matter how well it's named.

10. Upload images through the supported image workflow

Three supported paths bring images in — pick per batch:

11. Use the image repository

Uploaded images land in your image repository — the single pool your products draw from. One file serves every catalog that references its SKU: replace the file behind a filename and every product surface using it reflects the update, with no per-catalog copies to chase.

12. Match images to catalog SKUs

Matching connects filenames to products by SKU. It's mechanical, not magical: files whose names resolve to a catalog SKU link up; files whose names don't, land in the unmatched list for you to review — no matter how obvious the intended product looks to a human.

13. Review unmatched images

Unmatched files are almost always naming problems. Everlight's three:

Review this list after every upload — an unmatched image is a product silently missing its photo.

14. Correct filename and SKU mismatches

Fix the filename to the convention, and re-upload the corrected file:

If the mismatch runs the other way — the filename is right and the catalog SKU is wrong — fix the catalog record instead. Two sources of truth drifting apart is how the same mismatch comes back next upload.

15. Use the separate image URL importer where supported

When images live at remote URLs — a DAM, a supplier's server — the image URL importer is the supported route: a simple sheet pairing each target filename with its source URL, which the platform then fetches into your repository.

Two boundaries worth knowing. First, this is a separate import workflow — image-URL columns inside a normal catalog spreadsheet are not processed; catalog files reference images by filename only. Second, each URL must be publicly accessible and point to a supported image file — a URL that's blocked, expired, or serving an HTML page instead of an image won't import, so review the results the same way you review matching.

16. Verify primary and alternate image order

After matching, confirm each multi-image product leads with the right shot: the primary is what resellers see first everywhere the product renders. Everlight's renamed ELH-PENDANT-380-02.jpg should sit behind ELH-PENDANT-380.jpg — not in front of it. Spot-check the products that had suffix confusion in the unmatched review; those are where order problems hide.

17. Review images in the product gallery

The product gallery is the ground truth — what's actually attached, in what order:

Walk a sample: one single-image product, one multi-image product, and every product you corrected in section 14.

18. Reprocess corrected images where supported

Where supported, corrected or replacement files can be reprocessed so the repository and product galleries pick up the fix — re-upload the corrected file and confirm it lands on the right product. The verification habit is the same as everywhere else in this guide: check the result, don't assume it.

19. Share approved images with reseller catalog data

Images ride along with the catalog data resellers are permitted to see: a reseller browsing their portal view gets the images attached to the products your sharing setup grants them — products excluded by rule bring their images nowhere. Image verification belongs on your pre-share checklist: the full sharing workflow is in the catalog-sharing guide.

20. Common product-image mistakes

21. Product-image preparation checklist

Common questions