Fashion Ecommerce Product Photography Shot List: 7 Image Jobs Every SKU Should Cover

Build the shot list around buyer questions

A useful shot list is not a list of fashionable angles. It is a product-information plan. Each frame should answer a question the hero cannot answer: what is the exact variant, how is the garment constructed, what does the back look like, how does it sit on a body, and which detail could change a purchase decision?

Begin with the product record and destination channels. For every SKU family, record the required image job, view or crop, product details that cannot change, background and styling rule, file name, delivery format and reviewer. This creates a stable definition of done before anyone shoots, generates or retouches an image.

The seven image jobs to consider for every fashion SKU

Treat these as seven jobs, not seven mandatory files. A front-facing hero can sometimes perform two jobs. A technical garment may need several detail frames. Footwear may need outsole and profile views, while a simple accessory may need fewer on-model images and more scale information.

Adapt the list by fashion category

Do not copy one master list across every category. Keep a shared catalogue standard, then add category rules where product behaviour and buyer questions differ. The result should still look like one visual system even when the required views change.

Separate the master product set from channel derivatives

The master set should preserve the strongest approved product information. Channel derivatives should be named outputs from that source: marketplace square crops, retailer-specific aspect ratios, mobile PDP crops, thumbnails, paid-social variants or regional files. Do not treat each derivative as an unrelated production job if one governed master can supply it safely.

Google Merchant Center requires a main image and supports additional product images. Its guidance asks sellers to show the correct variant, keep the product clear and use additional views for information that does not fit the main image. Google also notes that images can be automatically cropped, so important product information should not depend on a fragile edge composition.

• Name the channel and purpose for every derivative.
• Record aspect ratio, dimensions, background, crop and file format.
• Keep stable image URLs for live commerce feeds unless the image itself changes.
• Map every output back to the correct SKU and variant.

Add product-truth and AI provenance rules before production

Whether the route is physical, AI-assisted or hybrid, the shot list should identify product details that cannot drift: colour, print placement, branding, trim, closure, texture, proportions and variant identity. Mark the views that require a real reference. If the back of a garment is not visible in any approved input, a generated back view is an invention risk, not a routine deliverable.

For generative-AI product images used in Google Shopping data, retain the required IPTC DigitalSourceType TrainedAlgorithmicMedia metadata. Include provenance and metadata checks in the delivery specification so a later export or compression step does not silently remove them.

Turn the shot list into a review checklist

The shot list and QC checklist should refer to the same image jobs. That connection prevents a common failure: production creates the requested files, but review checks only whether each image looks attractive. Ecommerce review must also confirm completeness, product fidelity and delivery readiness.

Use a representative pilot before scaling the list

Test the shot list on a small but representative group of products, including normal difficult cases: reflective trims, complex prints, dark materials, layered garments, unusual closures or incomplete source packs. Measure missing views, corrections, held inputs, review time and channel-preparation work.

Change the list when the pilot exposes a repeated information gap. Do not add frames simply because another retailer uses them. Every additional image increases production, review, storage and maintenance work, so it should earn its place by resolving a buyer, channel or operational requirement.

When a traditional shoot is still the better route

Traditional production remains preferable when the team must discover how a new product behaves on set, capture complex physical interaction, verify difficult materials or create views for which no reliable source information exists. AI production can extend or standardise a defined product record; it should not be used to conceal missing product truth.

A hybrid route is often practical: capture the product information that must be physically resolved, then use a controlled AI-human system for approved extensions, variants or recurring channel delivery. The shot list should state which method owns each image job.