Product Images Template

Common Angles

1. 1Identify product - AI analyzes the image to determine what product is shown and generates a descriptive name.
2. 2Detect SKU/barcode - If visible in the image, extracts SKU codes, barcodes, or product IDs.
3. 3Determine image angle - Recognizes the photo angle (front, side, detail, lifestyle, etc.).
4. 4Apply counter - Numbers multiple images of the same product sequentially.

E-commerce teams routinely manage 50–500 images per SKU across multiple product variants, colorways, and platforms. When every image is named IMG_4521.jpg or DSC_0042.jpg, finding the front shot of item ABC123 means opening dozens of thumbnails. A consistent convention like sku_name_angle_counter puts the answer in the filename itself.

Standardized names also enable automated DAM (Digital Asset Management) ingestion. Most enterprise DAM systems accept structured filenames as metadata — SKU becomes the product identifier, angle becomes the asset type, and counter becomes the sort order. Batch uploads that would otherwise require hours of manual tagging complete without human intervention.

Finally, meaningful filenames prevent client delivery mistakes. When you hand off a folder of 300 product images to a marketplace or agency, a name like WD5000_wooden-desk_front_01.jpg is self-documenting. The recipient can verify completeness and placement without an accompanying spreadsheet.

The default pattern works for most product catalogs. These variants suit specific workflows:

1. 1Agree on angle taxonomy before processing — Inconsistent angle names ("front" vs "front-view" vs "front-shot") create duplicates when sorting and break DAM filters. Define your list — front, back, side, top, detail, lifestyle, white-bg, package — and stick to it.
2. 2Lowercase and hyphenated slugs only — Underscores separate fields; hyphens separate words within a field. "blue-sneakers" not "Blue Sneakers" or "BlueSneakers". This makes the delimiter logic unambiguous when parsing filenames programmatically.
3. 3Process images in product groups and reset the counter per SKU — Running the entire catalog in one batch mixes products. Group by SKU so counter starts at 01 for each product, giving you clean sets for marketplace bulk upload.
4. 4Use "lifestyle" for in-context shots and "white-bg" for studio shots — These are industry-standard terms recognized by most marketplaces and DAM systems. Using them consistently means your angle field doubles as a shot-type filter.
5. 5Add platform suffix only for single-channel assets — If the same images go to multiple platforms, omit the platform field to keep files reusable. Add it only when you're producing platform-exclusive variations (e.g. Amazon requires white background, Instagram allows lifestyle).
6. 6Always include the counter, even for single images — Using _01 on a solitary product shot makes future bulk additions consistent. When you add a second image later, _02 slots in naturally without renaming the existing file.