A practical SKU-by-SKU system for deciding which views to capture, why each image exists and what must be checked before upload.
A product photography shot list is not a list of attractive angles. It is a written answer to a more useful question: what must a buyer see before they can judge this exact SKU with confidence? When the list is organised around buyer uncertainty, the shoot becomes easier to approve, variants stay consistent and the final gallery does a clearer selling job.
This guide extends GPTWala’s AI product photography guide for Indian businesses. It focuses only on shot planning. Use it before the phone-to-approved-image workflow, not as a replacement for image quality, product-truth or marketplace checks.
What an ecommerce product photography shot list must decide
A useful shot list connects five things: the SKU, the buyer question, the required view, the intended channel and the approval rule. If any one is missing, the team may produce a beautiful image that cannot be used.
| Decision | Question to answer before shooting | Output |
|---|---|---|
| SKU coverage | Which exact product, size, colour and pack is being captured? | One row per sellable variant or approved shared asset |
| Buyer need | What can the buyer not verify from copy alone? | A named image purpose |
| View | Which angle, crop or context proves that point? | A capture instruction |
| Channel | Will this be a main image, gallery image, ad or catalogue asset? | Background and composition rule |
| Approval | What must remain accurate? | A measurable QA note |
Turn buyer questions into images
Begin with the questions your sales team repeatedly answers on WhatsApp, at the counter or during returns. These questions are often better inputs than a competitor gallery because they reflect your product, your customers and your fulfilment reality.
Use four sources of uncertainty
- Identification: Is this the right model, colour, size, finish or pack?
- Inspection: What are the texture, stitching, ports, closure, ingredients, markings or included parts?
- Scale and fit: How large is it, how does it sit, and what can it hold?
- Use and outcome: How is it assembled, worn, applied, stored or used safely?
Write each uncertainty as a buyer question. Then decide whether photography can answer it truthfully. If the answer depends on a measurement, specification or policy, keep that information in the copy or a labelled diagram rather than implying it through perspective.
The core ecommerce image sequence
There is no universal magic number of photographs. The right count is the smallest complete set that lets a buyer identify and evaluate the product. Google Merchant Center supports one main image and additional images, and notes that different angles can help purchase decisions. Its current product-image guidance also requires the image to represent the actual product and the correct variant. See the official Merchant Center image-link guidance.
| Sequence | Image purpose | Typical capture | Do not hide |
|---|---|---|---|
| 1 | Immediate identification | Clean three-quarter or front hero | Overall shape, colour and sellable unit |
| 2 | Complete inspection | Front, back and important sides | Closures, controls, labels or rear construction |
| 3 | Material/detail proof | Macro or close crop | Texture, weave, edge, finish or connector |
| 4 | Scale | In-hand, on-body, beside a neutral reference, or dimension graphic | True proportion |
| 5 | Use | Product in one realistic context | How it is held, worn, opened or positioned |
| 6 | What is included | Lay-flat of box contents or bundle | Every included and excluded component |
| 7 | Variant distinction | Separate approved image per colour or configuration | SKU-specific colour, pattern and attachment |
For marketplace main images, use the relevant channel rules as the final authority. GPTWala’s Google, Amazon, Flipkart and website image-rules guide explains the difference between a clean main image and supporting gallery assets.
Add category-specific modules
The core sequence is a base. Add modules only where the product creates a specific buying risk.
| Category | Extra views worth planning | Accuracy risk |
|---|---|---|
| Apparel | Front, back, side, fabric close-up, closure, on-body fit and movement | Do not reshape fit, length, drape or print placement |
| Jewellery | Face, side profile, clasp, setting, scale on body and hallmark where relevant | Do not enlarge stones or remove construction details |
| Food and packaged goods | Front pack, back label, ingredients/nutrition, seal, pack contents and serving context | Keep label copy and pack quantity legible and current |
| Tools or appliances | Controls, ports, accessories, operating position, size reference and safety labels | Do not show accessories that are not included |
| Furniture or decor | Front, side, back, material detail, dimensions, room context and assembly points | Perspective must not exaggerate size |
| B2B components | Multiple faces, connector/thread detail, dimensional drawing, finish and packaging | Revision, tolerance and material claims must match the data sheet |
Reusable ecommerce shot-list template
Create one row for every required output. Do not write “take all angles”. A photographer, editor and approver should interpret the instruction in the same way.
| Field | Example |
|---|---|
| SKU / variant | JAR-750-AMBER / 750 ml / amber |
| Buyer question | What does the lid and sealing ring look like? |
| Shot ID and purpose | JAR-750-AMBER-04 / closure proof |
| Capture instruction | Top-down close-up with lid removed and ring visible |
| Background / styling | Neutral light surface; no unrelated props |
| Channel and placement | Website gallery image 4; WhatsApp catalogue optional |
| Required truth | Ring colour, lid thread and finish must match approved sample |
| Crop / delivery | Square master plus 4:5 derivative; keep full product inside safe area |
| Approval owner | Product manager |
If several variants share construction, record exactly which asset may be shared. Never use a convenient image of one colour for another colour variant.
Plan the production day from the shot list
Group by setup, not only by SKU
Capture all products that need the same light, lens, background and camera position before rebuilding the set. However, keep a physical “to shoot / captured / approved” lane so grouped production does not cause variant mix-ups.
Lock the reference before volume capture
Photograph one representative SKU, edit it to the proposed standard and obtain approval. That reference should define crop, background tone, shadow, colour handling and naming. The approach mirrors the sample-first control in GPTWala’s product-accuracy checklist.
Reserve time for proof shots
Details, contents and labels often take longer than hero images because the product must be cleaned, opened or repositioned. Put them on the plan; do not leave them as optional shots at the end of the day.
Adapt the shot list by channel
Capture a truthful master set first, then derive channel crops. A marketplace main image, a website gallery, a WhatsApp catalogue tile and a Meta ad do different jobs.
- Marketplace main: clear product identification under the platform’s current rules.
- Website gallery: full evaluation sequence, including detail, scale, contents and context.
- WhatsApp catalogue: instant identification on a small screen, with simple composition.
- Advertising: attention and context, while preserving the actual SKU and claims.
Avoid composing every shot too tightly. Leave safe space in selected masters so your team can create square, portrait and landscape crops without cutting the product.
Approval checklist before files leave production
- Match the physical sample to the SKU and variant row.
- Confirm every required shot ID exists and no duplicate file is pretending to be another view.
- Check colour, material, shape, label, included parts and scale.
- Inspect edges, dust, reflections, stitching, clasps, ports and text at 100%.
- Confirm the main image and supporting images follow the target channel’s current rules.
- Verify crop derivatives against their safe areas.
- Rename, export and place files in the approved SKU folder.
Common shot-list mistakes
- Copying a competitor’s gallery: it may not answer your buyers’ questions or fit your product.
- Planning by angle only: “front, side, back” says nothing about the purpose of each image.
- Using one list for every category: a jar, kurta and machine component have different proof needs.
- Ignoring variants: colour and configuration errors create a product-truth problem.
- Shooting for one crop: tight framing can make a useful master impossible to adapt.
- Leaving approval until the end: one early reference approval is cheaper than reworking a full catalogue.
Frequently asked questions
What should be included in a product photography shot list?
Include the exact SKU or variant, buyer question, image purpose, capture instruction, background, channel, crop, product-truth check and approval owner for every required output.
How many product photos should an ecommerce listing have?
Use the smallest complete set that lets a buyer identify the product, inspect important details, understand scale or fit, see what is included and distinguish the correct variant. The number varies by product risk and channel.
Which product angles reduce buyer uncertainty?
A clear hero plus the hidden or decision-critical sides usually matter most. Add detail, scale, use, contents and variant views where they answer a real purchase question.
Should every colour variant have separate photos?
Yes when colour, pattern, finish or another visible attribute changes. A shared construction detail can be reused only when it is genuinely identical and the listing does not imply it represents another variant.
Can AI generate missing shots?
AI can help with approved backgrounds or derivatives, but it should not invent an unseen side, accessory, label, material or construction detail. Capture missing product evidence from the real item.
Who should approve the shot list?
The product owner should approve factual coverage, while the channel or marketing owner checks placement and format. Assign one final decision owner to avoid conflicting feedback.
Leave a Reply