GPTWala

Tag: Ecommerce Video

  • 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

  • Product Video Script Templates: 7 Formats for Ecommerce and WhatsApp

    GPTWala Business Hub · Practical video systems

    Seven fill-in frameworks that connect buyer questions, truthful product proof, scenes, words and calls to action before production begins.

    Updated 23 August 2026 · Guide for Indian product businesses

    A product video script is not only a voice-over. It is a decision document that says what the buyer needs to understand, what must appear on screen, which words are safe to use and what action follows. A strong script keeps the product truthful before filming, editing or AI generation begins.

    Use this guide with GPTWala’s complete AI product video guide. Choose one format for one job rather than combining a demo, testimonial, explainer and sale announcement into a crowded 20-second video.

    Start with a one-line video brief

    Complete this sentence before writing scenes: After watching, [specific audience] should understand/believe/do [one outcome] because they saw [specific proof].

    Brief field Weak answer Useful answer
    Audience Everyone Retail buyers comparing 500 ml and 1 litre food-storage jars
    Outcome Know our product Understand how the lid locks and choose the right capacity
    Proof Looks premium Close-up of hinge, seal, open/close action and measured capacity label
    Destination Online Product page or WhatsApp enquiry for the exact SKU
    Guardrail Make it viral No invented claim, accessory, result, size or testimonial

    Write the script in four production columns

    Separating the plan prevents the editor from guessing what a line means visually. Adobe’s current video script guidance and templates also emphasise defining purpose and organising the script before production.

    Time Picture/action Spoken words or sound On-screen text
    0–2 sec Lid slipping from an overfilled container “Still fighting this every morning?” Lunch-box leak?
    2–6 sec Exact product opened; seal and latch shown “This model uses a four-side latch and removable seal.” Show the real closure
    6–11 sec Measured quantity placed inside “Choose 500 ml or 1 litre for your routine.” 500 ml / 1 litre
    11–15 sec Two SKUs beside their labels “Check dimensions and order the right size.” View sizes

    Write only what the shot can prove or what approved product data supports. The visual and words should agree.

    Seven product video script templates

    1. Buyer problem to product mechanism

    Hook: Name a specific, recognisable friction. Proof: Show the product feature operating. Meaning: Explain the practical difference without guaranteeing a universal outcome. CTA: Invite the next verifiable step.

    Template: “If [specific situation] keeps happening, look at [feature]. Here is how it [visible action]. Check [specification/fit condition], then [CTA].”

    2. Three-step product demo

    Template: “Step one: [prepare]. Step two: [use]. Step three: [finish/check]. The important detail is [limitation or care point].” Pair each sentence with the real action. For a still-image method, see how to make a demo video from still photos.

    3. Product comparison without attacking a competitor

    Template: “Choose [variant A] when [use condition]. Choose [variant B] when [different condition]. Both include [shared fact]. Compare [dimensions/material/pack] before ordering.”

    4. Objection or FAQ answer

    Template: “Does [product] work with [condition]? It works when [verified compatibility], and it does not include/support [important limit]. Here is the detail to check before buying.”

    5. Unboxing and what-is-included video

    Template: “Inside this [exact pack/SKU], you receive [item one], [item two] and [item three]. [Visible prop] is for demonstration and is not included. Here is how the parts fit.”

    6. Launch or new-variant announcement

    Template: “New: [exact variant] joins [product family]. It changes [verified visible attribute] while keeping [verified shared feature]. Available from [truthful availability point].”

    7. Click-to-WhatsApp enquiry script

    Template: “Need [product outcome/category] for [use]? See [one proof]. Message ‘[short keyword]’ with your [quantity/size/location] and we will share the relevant option.” Connect this to GPTWala’s click-to-WhatsApp system.

    Match every claim to product proof

    Line type Evidence before approval Safer writing approach
    Specification Approved data sheet or packaging State the exact value and condition
    Compatibility Tested model/list and documented exclusions Tell buyers what to check
    Performance Defined test method and result Describe the observed result, not a universal promise
    Customer quote Real consented source and exact context Do not generate or polish into a different claim
    Comparison Like-for-like criteria Compare use cases or verified attributes
    Scarcity Actual stock or deadline Remove false countdowns and invented urgency

    Plan timing without rushing the buyer

    Duration should follow the decision, not a fashionable number. A single hook and proof may fit a short placement. Assembly, compatibility or safety may require a longer product-page video. Read the script aloud and time the actual product action. A lid cannot be understood if the cut hides the mechanism.

    • Give the opening one idea, not three claims.
    • Let important label or dimension text stay long enough to read.
    • Use cutaways to clarify, not to hide product behaviour.
    • Create separate edits for different placements instead of squeezing one timeline everywhere.

    Design for sound-off and sound-on viewing

    The main meaning should survive muted viewing where the platform or user starts without sound. Use concise on-screen text and readable captions. Do not paste the full voice-over as tiny text. Sound can add rhythm, human tone and explanation, but the product and CTA must remain identifiable visually.

    Adapt language, presenter and voice

    Use the words buyers already use in calls and WhatsApp chats. Explain technical terms once. For multilingual versions, translate meaning and units carefully rather than replacing words mechanically. Keep one approved claims sheet across languages.

    An AI presenter can be useful for consistent delivery, but disclose synthetic presentation where required and never use a fake expert or customer identity. GPTWala’s AI spokesperson workflow covers consent, trust and disclosure.

    Use AI to draft, not to invent the product story

    Give an AI tool approved facts, audience, goal, proof shots, tone and prohibited claims. Ask for alternative structures, then verify every line. Do not ask it to “make claims stronger”. Keep the product data and approval owner outside the model.

    Safe prompt frame: “Use only the facts below. If a proof or specification is missing, mark the line for removal. Write four columns: time, picture, spoken words and on-screen text.”

    Pre-production script QA

    1. One audience, one video job and one destination are named.
    2. Every factual line has approved evidence.
    3. Every important line has a feasible proof shot.
    4. The exact SKU, variant and included items are correct.
    5. On-screen text is readable in the target crop.
    6. CTA matches what happens after the click or message.
    7. Music, voice, presenter, location and stock media rights are documented.
    8. AI output has been reviewed for invented product details.

    Worked example: from buyer question to approved script

    Suppose a wholesaler repeatedly receives the question, “Will this 25 kg packaging bag work for sharp-edged metal parts?” The script should not answer yes unless the product team has an approved use condition and test. A safe video can show the material layers, seam construction and available specification, then ask the buyer for part dimensions and handling conditions.

    Draft line Problem Approved rewrite
    “The strongest bag for any metal part.” Absolute, unsupported comparison and universal use “This model uses [verified material and seam]. Share part shape, weight and handling method so the team can check fit.”
    “It never tears.” Impossible guarantee Show the approved test/condition, or remove the claim
    “Buy now.” CTA ignores qualification “Send part dimensions, quantity and delivery location for the relevant option.”

    This version may sound less dramatic, but it does a better sales job. It qualifies the enquiry, preserves the role of technical data and gives the production team specific evidence to film. Keep rejected lines in the approval record so they do not return during editing or translation.

    Frequently asked questions

    How do you write a script for a product video?

    Define one audience, outcome and proof, then write time, picture, spoken words and on-screen text in separate columns. Verify every claim before production.

    What should a product video script include?

    Include the exact SKU, buyer question, visible proof, approved claim, scene/action, audio or voice, on-screen text, timing, destination and call to action.

    How long should a product video script be?

    Long enough to complete one viewer task without rushing. A simple hook and proof can be short; setup, compatibility or detailed demos may need longer edits.

    Can I use the same script for Reels, ads and a product page?

    Use one approved factual core, but create placement-specific openings, crops, timing and calls to action. The viewer context differs.

    Can AI write product video scripts?

    Yes for options and structure, provided it receives approved facts and a prohibited-claims list. A human owner must verify every product detail and claim.

    What is the best call to action for a product video?

    The CTA should match the next real step, such as checking dimensions, viewing variants, requesting a quote or sending specific enquiry information on WhatsApp.

    Sources and further reading