GPTWala

Tag: Shot List

  • Product Video Shot List: A Scene-by-Scene Template for Small Teams

    GPTWala Business Hub · Practical video systems

    A production-ready worksheet that turns a script into exact shots, product actions, crops, audio cues and approval checks.

    Updated 23 August 2026 · Guide for Indian product businesses

    A product video shot list converts the approved script into a capture plan. It tells the team exactly what to record, in which product state, from which framing, for which crop and with which factual check. Without it, small teams often discover missing close-ups, mismatched variants or unusable vertical crops during editing.

    This article sits between the product video script templates and GPTWala’s AI product video workflow. It is a production tool, not a list of cinematic camera moves.

    Script versus shot list versus edit plan

    Document Main question Owner Typical unit
    Script What must the viewer understand and hear/read? Marketing plus product owner Scene or line
    Shot list What exactly must be captured to prove it? Producer/photographer Shot
    Edit plan How will approved shots become each final version? Editor Timeline and deliverable

    Adobe describes a shot list as the detailed plan of what needs to be captured, including framing and production information. Its shot-list overview is a useful general production reference. A product-business list adds SKU, variant and product-truth controls.

    Required fields for every product-video shot

    Field Purpose Example
    Shot ID Unique handoff reference JAR-A750-07
    Script line / viewer question Connects shot to the communication job Show how the seal is removed
    Exact product state Prevents continuity errors Amber 750 ml jar, lid open, seal fitted
    Action Defines what happens Hand removes seal slowly and replaces it
    Framing and camera Makes coverage predictable Top close-up, locked camera
    Light/background/props Controls look and factual context Neutral table, soft side light, no extra accessories
    Duration / handles Gives editor usable time Action plus two seconds before and after
    Target crops Protects vertical, square or horizontal delivery 9:16 primary; 1:1 safe
    Audio Plans dialogue, natural sound or silence Capture latch click separately
    Truth/approval check Defines acceptance Seal colour and lid construction match approved SKU

    Reusable scene-by-scene shot-list template

    Shot ID Scene job Product/action Frame/movement Crop/audio QA
    01 Identify problem Old container leaks during tilt Medium close-up; fixed 9:16 safe; natural sound Do not imply competitor brand
    02 Identify exact solution Approved jar enters frame Clean hero; slow push only if stable All crops; text space above Correct 750 ml variant
    03 Prove mechanism Four latches close in sequence Top close-up; locked 9:16/1:1; capture clicks All latches visible and functional
    04 Show scale Measured contents placed inside Three-quarter view Horizontal secondary No unverified capacity implication
    05 CTA 500 ml and 1 litre variants beside labels Wide locked shot All crops; clean voice-over Correct names and destination

    Core product-video coverage modules

    Identification module

    Capture a stable hero, label/name, front/back/important sides and the exact variant. This footage supports openings, transitions and thumbnails.

    Mechanism or use module

    Record the complete action in a clear master shot, then details from angles that explain contact points, controls or sequence. Do not use only fast cutaways that hide whether the product works.

    Scale, fit or installation module

    Use a familiar and truthful reference, dimension overlay or on-body/in-space view. Lock perspective so the product is not exaggerated.

    Contents and compatibility module

    Show every included item separately from props. Capture model numbers, connectors or fit points where they help the buyer verify compatibility.

    Texture and finish module

    Use controlled light and movement to reveal material. For reflective products, plan the environment using GPTWala’s reflection-control workflow.

    Choose an efficient shoot order

    The published story order is rarely the fastest capture order. Group shots by product state, setup, lens, background and talent. Capture the clean, unopened item before it is assembled, filled, worn or marked. Record destructive or messy demonstrations last.

    Shoot order Why Continuity record
    Clean hero and all sides Product is untouched Reference photos of labels and orientation
    Detail and macro Setup remains clean and controlled Lens, distance and product state
    Assembly/use Product may change state Step photos and included parts
    Lifestyle/talent Needs separate blocking and releases Wardrobe, hand, location and consent
    Messy/destructive tests Cannot easily reset Test conditions and result

    Plan multiple aspect ratios at capture

    Mark the primary composition and the safe secondary crops. A wide product held near the edge may fail in vertical delivery. Capture selected wide, medium and detail versions rather than expecting automatic reframing to solve every scene.

    • Keep critical product detail and labels inside the planned safe area.
    • Leave room for captions, platform controls and CTA overlays.
    • Capture clean plates when approved composites may be needed.
    • Record a vertical-native take for hand actions that feel awkward when cropped.

    Use the current format matrix in GPTWala’s product video sizes and aspect ratios guide before production.

    A phone-first production setup

    Clean the lens, stabilise the phone, disable beauty/scene filters, lock exposure and focus where possible, and record with consistent light. Put the shot list where the operator can check it without touching the set. Capture one reference clip and review it at full size before completing the batch.

    When using stills instead of motion, the still-photo demo workflow helps plan pans, crops and truthful sequence.

    Continuity and product-truth controls

    • Use a physical SKU card at the beginning of each take, then remove it before the usable action.
    • Photograph the product state after each approved setup.
    • Track fill level, cap position, cable routing, hand orientation and included parts.
    • Never substitute a convenient variant when colour, size, finish or mechanism differs.
    • Label AI-generated or composited elements in the production register.

    Editor handoff and shot-list QA

    Rename clips with shot ID and take number, keep camera originals, and mark approved takes without deleting alternatives. The editor should receive the script, shot list, claims sheet, product reference, logo/fonts, music and talent rights, crop matrix and final delivery list.

    1. Every script line has at least one usable proof shot.
    2. Shot IDs, filenames and product variant agree.
    3. Core actions are complete, not hidden by cuts.
    4. Audio, releases and licensed assets are documented.
    5. Primary and secondary crops keep critical elements safe.
    6. Product-truth notes survive the edit handoff.

    Add a take log so the editor does not guess

    The shot list says what to capture; the take log records what actually happened. During production, mark the best take, technical problem, product-state change and any approved deviation. A 20-second note can save an editor from reviewing several almost-identical clips or choosing a take with the wrong variant.

    Shot/take Status Production note Editor instruction
    03/T1 Reject Second latch did not fully close Do not use, even as a cutaway
    03/T2 Approved Complete action; clean sound Primary demo master
    03/T3 Approved detail Tighter crop; no beginning handle Use only after T2 establishes action

    Record reshoots as new takes rather than overwriting files. Keep a copy of the final shot list and take log inside the project archive with the product reference and claims sheet. That makes future versions, translations and corrections easier to audit.

    Frequently asked questions

    What is a product video shot list?

    It is a capture plan that turns each script line or buyer question into a defined product state, action, frame, crop, audio need and approval check.

    What should be included in a video shot list?

    Include shot ID, scene job, exact SKU/variant, action, framing, movement, light, background, props, duration, crop, audio and product-truth QA.

    How do I create a shot list for a product video?

    Break the approved script into proof needs, choose the clearest master and detail shots, record product state and crop requirements, then group capture by setup.

    Should the shot list follow the final edit order?

    Not necessarily. Capture in the safest efficient order, such as clean product first and messy demonstrations last, while using shot IDs to restore story order in editing.

    How do I plan one shoot for vertical and horizontal video?

    Mark a primary crop, protect critical elements in shared safe areas, and capture separate vertical-native or wider takes where reframing would weaken the action.

    Can AI generate missing shots after production?

    It should not invent an unseen product side, action, accessory or result. Recapture missing factual evidence; use AI only for approved non-product elements under review.

    Sources and further reading

  • Ecommerce Product Photography Shot List: A Buyer-Question Template

    GPTWala Business Hub · Practical ecommerce systems

    A practical SKU-by-SKU system for deciding which views to capture, why each image exists and what must be checked before upload.

    Updated 23 August 2026 · Reading guide for Indian product businesses

    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.

    The one-line rule: every planned image should either identify the item, prove a detail, explain scale or use, differentiate a variant, or remove a purchase objection.
    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

    1. Match the physical sample to the SKU and variant row.
    2. Confirm every required shot ID exists and no duplicate file is pretending to be another view.
    3. Check colour, material, shape, label, included parts and scale.
    4. Inspect edges, dust, reflections, stitching, clasps, ports and text at 100%.
    5. Confirm the main image and supporting images follow the target channel’s current rules.
    6. Verify crop derivatives against their safe areas.
    7. 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.

    Sources and further reading