GPTWala

Author: Sahil Sangani

  • Product Video Sizes and Aspect Ratios: A Multi-Channel Master Plan

    GPTWala Business Hub · Practical video systems

    A crop-first production system for vertical, square and horizontal product videos, with current official references and safe-area controls.

    Updated 23 August 2026 · Guide for Indian product businesses

    Product video sizing is not solved by exporting one horizontal file and letting every platform crop it. The product, label, hand action, captions and CTA must remain clear after the destination adds its own interface. A small team needs a three-orientation master plan and a habit of checking current platform specifications before delivery. Start with GPTWala’s AI product video guide for the factual production workflow.

    This guide is dated 23 August 2026. Platform rules change, so the linked official help pages are the final authority at upload time.

    Aspect ratio versus resolution versus safe area

    Term Meaning Example
    Aspect ratio Relationship between width and height 9:16 vertical, 1:1 square, 16:9 horizontal
    Resolution Pixel dimensions of the exported frame 1080 × 1920 for a vertical HD file
    Safe area Zone kept clear of platform controls, captions and crops Product and claim stay away from overlay regions
    Orientation How the frame is held Vertical, square or horizontal
    Delivery spec Platform/placement requirements Format, duration, file size, codec and ratio

    Use a three-master orientation system

    For a reusable paid and organic video library, plan three deliberate versions:

    • 9:16 vertical: short-form feeds and Stories/Reels-style placements.
    • 1:1 square: flexible feed and catalogue-style placement.
    • 16:9 horizontal: YouTube watch/in-stream, website players, presentations and wider screens.

    Google Ads’ current creative guidance recommends providing horizontal 16:9, vertical 9:16 and square 1:1 orientations for video ad coverage. See the official Google Ads creative guidance.

    Do not merely pad: a horizontal video placed inside a vertical canvas often leaves the product too small. Recompose the edit or capture a vertical-native take.

    Current platform and placement matrix

    Destination Useful orientation Current official reference Production note
    YouTube/Google video ads 16:9, 9:16 and 1:1 Google Ads video specs Official help lists 1920×1080, 1080×1920 and 1080×1080 as recommended HD pixels
    YouTube Shorts Vertical or square eligibility depends on current Shorts rules YouTube Shorts help Current help says square or vertical uploads up to three minutes can be categorised as Shorts under stated date conditions
    Facebook/Instagram Reels ads 9:16 vertical Meta Reels ads guidance Design for vertical and review the in-platform preview/placement controls
    LinkedIn video ads 16:9, 1:1, 4:5 or 9:16 within current ranges LinkedIn video ad specs Current page lists recommended/max dimensions and caption requirements
    Own product page Choose for player/layout and buyer task Your site implementation Prioritise mobile width, performance and visible controls
    WhatsApp send/catalogue support Simple mobile-first crop Current app behaviour and file limits Keep product and message legible on a small screen

    Specifications in this table are planning references, not a permanent upload guarantee. Check the exact campaign type and placement at export.

    Design safe compositions before editing

    Platforms can place profile names, captions, buttons and CTAs over different parts of a video. Google Ads publishes safe-zone guidance for its video formats. Use platform templates where available and inspect every placement preview.

    Element Safe-area rule Common failure
    Product Keep the decision-critical area away from edges and overlays CTA covers clasp, label or price
    Logo Use a clear but non-obstructive locked position Platform crop removes half the mark
    Headline Short lines with high contrast and breathing room Tiny multi-line paragraph
    Captions Reserve a consistent readable region Burned captions collide with platform captions
    CTA Place message where the platform button will not contradict or cover it Two competing calls to action

    Capture footage that can survive reframing

    • Frame important actions with extra clean space in selected takes.
    • Capture separate vertical takes for hand/product movement that crosses a wide frame.
    • Keep camera originals at sufficient quality for the planned crops.
    • Record clean product, detail and CTA plates for recomposition.
    • Avoid placing the exact SKU at the extreme edge.
    • Mark required orientations in the product video shot list.

    Create derivatives from an approved factual core

    Start with approved footage and script, then build each orientation as a real edit:

    1. Create timelines for vertical, square and horizontal.
    2. Reframe each shot manually; do not trust auto-reframe without review.
    3. Resize or reposition on-screen text for each layout.
    4. Change opening duration and CTA only where the placement requires it.
    5. Compare the product to the approved master after crop, scale and AI expansion.
    6. Export with a clear orientation/version filename.

    If generative expansion is used to fill a canvas, lock the real product area and inspect new background details. Do not let the tool invent parts or alter scale.

    Text, captions, audio and platform UI

    Use on-screen text to support meaning, not to replace the product. Keep contrast high and line length short. Captions should match spoken words and preserve product names, units and Indian-language terms correctly. Review sound-off and sound-on versions.

    LinkedIn’s current ad specifications, for example, describe SRT captions for its video ads, while other platforms may support uploaded or automatic captions differently. Keep a clean caption file and a reviewed transcript in the asset package.

    Compression and final quality QA

    QA area Check
    Dimensions/ratio Export matches the exact placement specification
    Product truth Label, colour, shape, components and action remain correct
    Crop No decision-critical part is clipped
    Text Readable on a phone and not covered by UI
    Compression No blockiness, banding or destroyed texture around the product
    Audio/captions Synced, intelligible and correctly named
    Preview Checked in the destination’s current preview and on a real mobile device

    Keep specifications current without rewriting the system

    Maintain a dated delivery matrix with official links, owner and last-verified date. Recheck before a new campaign, when a platform rejects an upload or when a placement changes. Keep the three-orientation production logic stable, but treat exact duration, file size, format and safe-zone rules as changeable.

    The story and proof still begin with an approved product video script; the format matrix should not dictate weak content.

    Website and WhatsApp delivery need their own checks

    For an own website, choose a player and file strategy that does not block reading or make the product page unnecessarily heavy. Provide a poster frame, accessible controls, captions/transcript where useful and a fallback when autoplay is disabled. Test on the actual mobile page, not only inside the editor.

    For WhatsApp, buyers may view on slower networks and forward the file outside its original context. Keep the opening product identification clear, make text readable, include a trustworthy next step and avoid compressing the only master. Test the delivered file in the app and keep the higher-quality approved export in the archive. Connect recurring vertical assets to the 30-day short-form video content system.

    Name versions so the team sends the right file

    Filename part Example Reason
    Product/campaign jar-a750-demo Identifies the factual asset
    Orientation 9x16, 1x1, 16x9 Prevents wrong-placement uploads
    Language en, hi Separates reviewed copy/captions
    Version/status v03-approved Avoids publishing an unapproved draft

    Example: jar-a750-demo-9x16-hi-v03-approved.mp4. Keep approval status in the register as well; a filename alone is not access control. Archive the corresponding script, captions, source project and platform-spec verification date with the master so a future editor can rebuild the deliverable safely.

    Frequently asked questions

    What is the best aspect ratio for product videos?

    There is no single universal ratio. Plan 9:16 vertical, 1:1 square and 16:9 horizontal masters when you need broad paid and organic coverage.

    Is 9:16 or 1:1 better for ecommerce video?

    Use 9:16 for vertical short-form placements and 1:1 where a square feed asset is useful. Choose by placement and preview, not a generic winner.

    Can I crop one horizontal product video for every platform?

    Sometimes, but important actions, labels and text often become too small or are clipped. Capture reframing-safe footage and create deliberate orientation-specific edits.

    What resolution should I use for product video ads?

    Check the current destination specification. Google Ads currently recommends HD examples of 1920×1080 horizontal, 1080×1920 vertical and 1080×1080 square.

    What is a video safe area?

    It is the part of the frame reserved for critical product and message elements so platform controls, captions, CTAs or crops do not cover them.

    How often should video specifications be checked?

    Check before each new campaign or major upload and whenever the platform changes placement behaviour. Keep a dated matrix linked to official help pages.

    Sources and further reading

  • How to Evaluate AI Video Tools for Product Marketing: A Same-Brief Test

    GPTWala Business Hub · Practical video systems

    A vendor-neutral evaluation method that tests real product work, rights, accuracy, editability and total effort before a team commits.

    Updated 23 August 2026 · Guide for Indian product businesses

    The “best AI video generator” is not a stable category. Tools change quickly, and the strongest text-to-video demo may be the wrong choice for a team that needs exact product labels, controllable edits, multilingual voice, predictable rights or repeatable catalogue production. Choose with a same-brief test, not a feature list.

    This framework extends GPTWala’s AI product video guide and avoids ranking vendors that have not been tested on your actual products.

    Avoid the best-tool trap

    Marketing claim Operational question Evidence to collect
    “One-click videos” How much correction is needed before approval? Hands-on edit time and rejected outputs
    “Brand consistent” Can the team lock logo, colours, fonts and product assets? Exported variants against brand QA
    “Commercial use” Which plan, inputs, outputs and regions are covered? Current terms and written clarification
    “Product accurate” Does the exact SKU survive motion and relighting? Frame-by-frame comparison with approved master
    “Fast” Fast to first output or fast to approved deliverable? Total elapsed and labour time

    Define the use case before opening tools

    Write the asset, input and approval need. “Make AI videos” is not a use case. Examples:

    • Animate approved still photos into a 15-second product demo without changing the item.
    • Create presenter-led FAQ versions in Hindi and English using an authorised avatar.
    • Generate non-product background clips for a campaign while compositing a locked real product layer.
    • Resize and caption approved footage into vertical, square and horizontal edits.

    Separate generation, editing, avatar/voice, translation and versioning. One tool does not have to perform every stage.

    Build a same-brief evaluation test

    Give each shortlisted tool the same source assets, script, duration, crops, brand rules and prohibited changes. Include one easy scene and one high-risk detail scene. Record settings and attempts.

    Test input Requirement Why
    Approved product master Exact label, shape, colour and components Tests preservation, not imagination
    Script and shot list Same words and scene jobs Keeps the comparison fair
    Brand kit Orange/black/white, logo and type rules Tests repeatable brand control
    Delivery matrix 9:16, 1:1 and 16:9 versions where needed Tests reframing and safe areas
    Prohibited changes No invented label, accessory, claim or testimonial Creates an objective rejection gate
    Rights scenario Real input types and intended commercial destination Tests plan/terms fit

    Score output quality and workflow quality separately

    Criterion Weight example Measure
    Product truth Gate, not average Any material SKU, label, colour, size or function error fails
    Scene and motion quality 15% Usable continuity, perspective, hands and contact
    Editability 15% Can correct timing, text, layers, captions and crop?
    Brand control 10% Repeatable logo, colour, type and template behaviour
    Audio/language 10% Pronunciation, timing, consent and replaceability
    Workflow fit 15% Review, versions, collaboration, export and archive
    Rights/privacy/security Gate Terms, retention, training use, access and deletion fit
    Total cost/time 15% Approved deliverable, not generation credit alone

    Adjust weights before seeing outputs. Otherwise a visually impressive result can make the team quietly change the criteria.

    Make product truth a non-negotiable gate

    Inspect the video frame by frame where the product moves, rotates, becomes occluded or interacts with a hand. Reject if the tool changes:

    • logo, label, spelling or regulatory text;
    • colour, pattern, material or finish;
    • shape, dimensions or proportions;
    • ports, clasps, controls, stones, stitching or included parts;
    • fit, drape, assembly or product behaviour;
    • the number of items in a pack.

    Use the product-accuracy checklist and keep a clean approved master beside the output.

    Review rights, privacy and governance before uploading real assets

    Terms and settings change. Read the current vendor documentation for the exact plan and intended use. Record, at minimum, input ownership, output usage rights, training use, retention/deletion, human/face/voice consent, sub-processors, confidentiality options, watermark/disclosure and account export/deletion.

    Do not upload confidential product launches, customer data, identifiable people or licensed assets until the responsible owner has approved the handling. The NIST AI Risk Management Framework provides a vendor-neutral way to think about governance, mapping, measurement and management.

    Not legal advice: commercial-use labels do not replace reviewing the exact terms, source-asset rights and consent obligations for your business and region.

    Measure total cost to an approved deliverable

    Track subscription/credits, failed generations, waiting time, operator time, manual retouching, caption/voice fixes, exports and review cycles. A cheaper tool can cost more if every output requires reconstruction.

    Cost line Record Decision metric
    Generation Credits/attempts per approved scene Cost per usable scene
    Labour Prompting, editing and QA minutes Hours per approved deliverable
    Rework Reasons and number of revisions First-pass approval rate
    Tool chain Extra editor, caption, voice or storage costs End-to-end cost
    Risk Blocked use cases or required manual controls Fit/non-fit by workflow

    Run a controlled pilot

    1. Choose two representative SKUs and one difficult variant.
    2. Create one approved script and product video shot list.
    3. Test no more tools than the team can evaluate consistently.
    4. Blind-review outputs against the pre-set scorecard where practical.
    5. Complete rights/privacy review before expanding inputs.
    6. Run one real delivery through review, export and archive.
    7. Decide approved use cases, prohibited use cases and fallback workflow.

    Keep a decision record, not a permanent winner

    Record date, plan, tested version, sources, prompts/settings, results, costs, risks, owner and review date. Approve tools for specific use cases, such as “caption and resize approved footage”, rather than “all product video”. Re-evaluate when pricing, models, terms or business inputs change.

    For human-presenter workflows, include the consent controls in GPTWala’s AI spokesperson video guide.

    Common AI video evaluation mistakes

    • Testing different briefs: one tool receives a polished prompt while another gets a vague sentence, so the comparison measures operator effort rather than tool fit.
    • Scoring only the first frame: product errors often appear during rotation, hand contact, occlusion or transitions.
    • Ignoring rejected attempts: only counting the final output hides cost and unpredictability.
    • Assuming a paid plan solves rights: plan names are not a substitute for current terms and source-asset permissions.
    • Choosing for one expert operator: test whether the actual team can repeat, review and hand off the workflow.
    • No exit path: keep originals, scripts, captions and editable assets so a vendor change does not erase the production system.

    Interpret the scorecard with gates

    Do not average a serious product-truth or rights failure into an otherwise attractive score. Mark those as gates. Among tools that pass, compare the weighted operational criteria and note uncertainty. If two tools are close, choose the simpler controlled pilot rather than forcing a winner from small samples.

    A tool may be approved for background ideation but blocked for product animation, or approved for captions but blocked for customer voice cloning. Use-case-specific approval reduces risk and prevents a broad purchase decision from overruling evidence.

    Document human review time as part of the control, not as an invisible cost. If the workflow requires a specialist to catch subtle label or motion errors, assign that reviewer and include the time in the pilot decision. Repeat the hardest test before final approval.

    Frequently asked questions

    How do I choose the best AI video generator for product marketing?

    Define the exact use case, test shortlisted tools with the same approved brief and assets, gate on product truth and rights, then compare editability, workflow fit and total cost.

    Should I choose an AI video tool from online rankings?

    Use rankings only for discovery. Tool capabilities, plans and terms change, and a reviewer may not test your SKU accuracy, rights or approval workflow.

    What should I test in an AI product video?

    Test labels, shape, colour, components, motion, hands/contact, editability, aspect ratios, captions, brand controls, rights, privacy and cost to approval.

    Can I use a free AI video generator commercially?

    Do not assume so. Review the exact plan’s current terms, watermarks, source-asset rights, output rights, retention and usage restrictions before commercial use.

    How many AI video tools should a small team test?

    Test only a manageable shortlist against the same brief. A deep comparison of a few realistic candidates is more useful than shallow trials of many tools.

    How often should we re-evaluate an AI video tool?

    Set a review date and reassess when the model, plan, price, terms, data handling or required business use changes.

    Sources and further reading

  • Product Demo vs Explainer Video vs Video Ad: Choose the Right Format

    GPTWala Business Hub · Practical video systems

    A decision framework for choosing whether the viewer needs attention, understanding or proof, with production and measurement rules for each format.

    Updated 23 August 2026 · Guide for Indian product businesses

    A product demo, explainer video and video ad can all contain the same product, but they are not interchangeable. A demo proves how the product behaves. An explainer builds understanding around a problem, method or system. An ad earns attention and moves the right viewer to a next step. Choosing the format by length alone leads to weak briefs and misleading measurement.

    Three formats, three primary jobs

    Format Primary viewer job Core evidence Typical next step
    Product demo Verify how a specific product works Real interface, mechanism, assembly or use Choose, enquire, buy or implement
    Explainer Understand a problem, process, category or solution Clear model, sequence, example and boundaries Learn more, compare or request guidance
    Video ad Notice relevance and act Fast product/audience signal plus credible proof Click, message, visit or watch
    Fast choice: if the viewer asks “Does it work and how?”, make a demo. If they ask “What is this and why does it matter?”, make an explainer. If they are not yet paying attention, make an ad that leads to the right proof.

    When to make a product demo

    Choose a demo when purchase or adoption depends on seeing the product perform a task. This is common for tools, appliances, closures, assembly, software interfaces and B2B components.

    Demo structure

    1. Name the exact product and starting condition.
    2. Show setup without hiding a critical step.
    3. Record the complete core action.
    4. Show the result and relevant limitation.
    5. Direct the viewer to specifications, compatibility or the next step.

    A demo is not a promise that every customer will get the same outcome. State test conditions where they matter. Use the still-photo demo method only when motion is not essential to proving the mechanism.

    When to make an explainer video

    Choose an explainer when the buyer needs a mental model before evaluating a SKU. It can clarify how a wholesale ordering process works, why a packaging material behaves differently, how a product family is organised or what steps a service includes.

    Explainer structure

    1. Define the audience and situation.
    2. Name the problem without exaggerating fear.
    3. Explain the process or principle in a few stages.
    4. Use one concrete product or customer scenario.
    5. Clarify fit, non-fit and next question.

    Animation is optional. A presenter, diagrams, product footage or screen recording can all work if the explanation remains accurate.

    Choose an ad when distribution is paid and the creative must create relevance before the viewer has asked for an explanation or demo. The ad should not carry every detail. Its job is to signal the audience/problem/product, provide enough proof to earn the next action, and match the destination.

    Ad structure

    1. Show or state who/what the message is for.
    2. Present one tension, opportunity or product difference.
    3. Give one credible proof moment.
    4. Use a CTA that matches the landing page or WhatsApp flow.

    Use the safeguards in GPTWala’s AI ad creative guide and test creative through the small-budget testing workflow.

    Demo, explainer and ad comparison

    Decision Demo Explainer Ad
    Starts with Product task Question or system Audience relevance
    Product visibility Usually central and exact May be one example within a concept Early enough to qualify attention
    Proof depth High for the shown action Enough to understand the model Compact proof linked to destination
    Editing Clarity over pace Sequence and comprehension Placement-aware pace and hook
    CTA Choose/check/order/use Learn/compare/consult Click/message/watch/visit
    Main risk Hiding steps or conditions Oversimplifying or becoming generic Overclaiming to win attention

    A practical decision tree

    1. Does the viewer already know the category? If no, start with an explainer or educational ad.
    2. Is the main objection about how the exact product works? If yes, prioritise a demo.
    3. Must you reach people who did not request the information? If yes, create an ad with a clear destination.
    4. Is the next action high-consideration? Use the ad to lead into an explainer, demo, specification page or sales conversation.
    5. Can one asset honestly do two jobs? Create deliberate edits with separate openings and CTAs rather than using one compromise everywhere.

    Use the formats as a sequence

    Many product businesses do not need to choose only one format. They need a connected path:

    Stage Asset Viewer movement Destination
    Attention Short video ad “This may be relevant to me” Focused page or WhatsApp entry
    Understanding Explainer “I understand the problem and approach” Product family/comparison
    Proof Product demo “I can see how this exact item works” SKU, quote or checkout
    Decision support FAQ/compatibility clip “My remaining condition is answered” Order or sales handoff

    This sequence connects naturally to a product landing page for WhatsApp enquiries.

    How the brief and script change

    • Demo brief: product, task, starting condition, complete action, result, limit and decision CTA.
    • Explainer brief: audience, question, model, stages, example, non-fit and learning CTA.
    • Ad brief: audience signal, hook, one proof, placement, destination and campaign CTA.

    Use the product video script templates, but retain the format’s primary job.

    Measure each format by its job

    Format Useful signals Misleading shortcut
    Demo Completion of key step, assisted conversion, fewer mechanism questions Views without decision context
    Explainer Qualified watch depth, next-page movement, better sales understanding Judging only by short-form retention
    Ad Qualified click/message plus post-click conversion and cost Cheap clicks that do not convert

    Keep product truth, complaints and expectation-related returns as guardrails. A higher click rate is not a win if the ad and destination disagree.

    Three product-business examples

    Local apparel brand

    A short ad can signal the audience and fabric/occasion, an explainer can clarify the size and fit system, and a demo can show drape, closure and movement on the exact garment. Do not let a mood-led ad replace accurate fit views.

    Packaging manufacturer

    An ad can reach procurement teams with one relevant application, an explainer can show the material/ordering decision path, and a demo can record assembly, seal or load handling under defined conditions. The quotation page should carry the current specification.

    Retail appliance seller

    An ad can introduce the use case, an explainer can compare model families and a demo can show controls, included accessories and cleaning. Compatibility, electrical and safety information must remain in the product documentation.

    These examples also show why one “brand film” is rarely enough. Reuse approved product footage, but create the opening, narrative depth and CTA for the viewer’s current task. When the sales team requests “one video for everything”, return to the buyer question and destination. A focused asset is easier to approve, place and measure.

    Repurpose without confusing the format

    A complete demo may supply a six-second proof moment for an ad. An explainer diagram may become a sales follow-up clip. Reuse is efficient when the team keeps the original context and does not turn a conditional result into a universal claim. Store source footage by product and proof type, then link every derivative to the approved script and destination.

    Frequently asked questions

    What is the difference between a product demo and an explainer video?

    A demo proves how a specific product performs a task. An explainer builds understanding of a problem, process, category or solution, sometimes using a product as one example.

    What is the difference between a product video and a video ad?

    A product video may serve education, proof or support. A video ad is built for paid distribution, fast audience qualification and a campaign-specific next action.

    When should I use a product demo video?

    Use one when the buying decision depends on seeing setup, operation, fit, assembly, compatibility or result for the exact product.

    Can an explainer video also be an ad?

    It can be edited into an ad, but the opening, pace, proof and CTA should be redesigned for the placement. Do not assume the full explainer works unchanged.

    Which format is best for WhatsApp enquiries?

    Use an ad or short relevance clip to start the conversation, then send the demo or explainer that answers the buyer’s specific question.

    How should I measure demo, explainer and ad videos?

    Measure each against its job: product understanding and decision support for demos, qualified comprehension for explainers, and post-click or post-message outcomes for ads.

    Sources and further reading

  • 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

  • Product Image File Names, Alt Text and SEO: A Scalable Ecommerce System

    GPTWala Business Hub · Practical ecommerce systems

    A catalogue-scale workflow for naming files, writing useful alt text, keeping image URLs stable and connecting visual assets to the right product pages.

    Updated 23 August 2026 · Reading guide for Indian product businesses

    Product image SEO is not a game of adding the same keyword to every filename and alt attribute. Search engines and assistive technology need accurate context. Buyers need fast, clear pages. Your operations team needs a naming system that survives catalogue growth. The best workflow solves all three and starts with the truthful masters described in GPTWala’s AI product photography guide for Indian businesses.

    Google says filenames can provide very light clues about an image, while alt text is a more important source of image metadata and supports accessibility. It also uses the surrounding page content and computer vision to understand the subject. Read the current Google Search Central image SEO guidance alongside this implementation system.

    What the filename, alt text, caption and page copy each do

    Field Primary job Example Common misuse
    Filename Stable, descriptive asset identity amber-glass-jar-750ml-front.webp best-cheap-jar-buy-online-1.webp
    Alt text Contextual text alternative for the image “Front view of the 750 ml amber glass jar with black screw lid” Repeated keyword list
    Caption Visible clarification when readers benefit “Lid and sealing ring shown separately” Duplicating nearby paragraph without value
    Page copy Full product facts, benefits, conditions and choice guidance Capacity, material, dimensions and compatibility Expecting alt text to carry the whole listing
    Image URL Crawlable, reusable location of the file /images/amber-glass-jar-750ml-front.webp Changing URL on every feed or resize run
    One source of truth: the product database should hold factual attributes. The image naming and alt-text workflow should pull from those approved fields, not invent new claims.

    Write short, descriptive product image file names

    Google recommends short but descriptive filenames and advises against generic names such as image1.jpg. A scalable product filename should help a human recognise the asset and remain stable after upload.

    A practical pattern

    [product-or-sku]-[variant]-[view-or-purpose].[extension]

    • linen-kurta-blue-front.webp
    • linen-kurta-blue-fabric-detail.webp
    • pump-px40-inlet-connection.jpg
    • spice-gift-box-6-pack-contents.jpg

    Use lowercase words separated by hyphens. Include only attributes that distinguish the asset. Keep the correct file extension for the actual format. Do not append adjectives such as “best”, “premium” or “cheap” unless they are part of the official product name.

    SKU-first versus product-name-first

    SKU-first naming is efficient for large B2B catalogues and production teams. Product-name-first naming is easier for editors and can be more descriptive. A combined form works when it stays readable, for example px40-transfer-pump-side.jpg. Choose one convention and document it.

    Write alt text for the image in its page context

    Alt text should communicate the relevant content or function of the image to a person who cannot see it. That means the same file can reasonably have different alt text in different contexts. A clean product image on a product page may need the item, variant and view. The same image inside an article about closures may need to emphasise the visible closure.

    A practical product-page formula

    [View or action] of [exact product] [important visible variant/detail]

    • “Front view of the blue linen kurta with concealed button placket”
    • “Close-up of the PX40 pump inlet connection and thread”
    • “Six-piece spice gift box with all included jars arranged beside the outer carton”

    Write what is visible, not what you hope to rank for

    If “food-safe”, “waterproof” or “handmade” is not visible in the image, it usually does not belong in the alt text. Put verified claims in the relevant product copy and structured data. Avoid repeating the business name in every alt attribute. Include GPTWala or another brand only when the brand is genuinely needed to identify the visible product or graphic.

    File-name and alt-text templates

    Image type Filename template Alt-text template
    Clean hero [product]-[variant]-front Front view of [product] in [visible variant]
    Back or side [product]-[variant]-back Back view of [product] showing [visible detail]
    Material detail [product]-[material]-detail Close-up of [product] showing [texture/material feature]
    Scale or fit [product]-[variant]-in-use [Product] [worn/held/placed] to show [relevant scale or fit]
    Pack contents [product]-pack-contents [Product or set] with [visible included items]
    Diagram [product]-dimensions-diagram Dimension diagram of [product] showing [visible measurements]

    Weak versus useful examples

    Weak Why it is weak Useful replacement
    IMG_9231.jpg No asset meaning amber-glass-jar-750ml-front.jpg
    “product image” Does not identify the content “Front view of 750 ml amber glass jar with black lid”
    “jar jar buy jar online cheap jar” Keyword stuffing and poor accessibility Describe the exact visible item and view once
    “red dress” for a blue variant Factual mismatch Use variant data and visual QA before publish
    Full product description in alt Overloads the text alternative Keep specifications and benefits in page copy

    Scale the system across an ecommerce catalogue

    1. Define approved source fields. Product name, SKU, colour, size, view, material and included parts must come from the catalogue record.
    2. Create a controlled view vocabulary. Use “front”, “back”, “side”, “detail”, “in-use”, “contents” and category-specific terms consistently.
    3. Rename before upload. Avoid changing URLs later unless the image itself changes or there is a migration plan.
    4. Generate a first draft at scale. A spreadsheet, PIM or script can combine approved fields.
    5. Review visually. Automation cannot confirm that the image actually shows the intended variant or detail.
    6. Publish with page context. Place images near relevant text and use captions only where readers need them.
    7. Audit after rendering. Check responsive size, layout stability, lazy loading, links and accessibility.

    This workflow should connect to the broader product-page SEO system and the product-page copy template, not operate as a separate keyword exercise.

    Technical image SEO checks

    Google Search Central recommends standard HTML image elements with a crawlable src, responsive image practices with a fallback source, supported formats, high visual quality and attention to page speed. It also explains that Google does not index CSS background images as product images in the same way as standard img elements.

    Check Pass condition Why it matters
    HTML Meaningful images use standard img markup with src Supports discovery and accessibility
    Responsive delivery srcset/picture has a fallback src Serves appropriate files across devices
    Dimensions Width and height or aspect ratio are reserved Reduces layout shifts
    Compression File is small enough for fast delivery without visible damage Balances speed and quality
    URL Stable, crawlable and not blocked unintentionally Lets search systems fetch and reuse the asset
    Context Image is near relevant product text Clarifies subject and page relationship
    Metadata Preferred image is represented consistently in page/social/schema setup where used Supports page previews and eligible search features

    For shopping feeds, the main and additional image URLs must also follow the destination’s product-image requirements. See GPTWala’s cross-channel product image rules.

    Variants, repeated images and duplicate assets

    Each visible variant should use the correct image and alt text. Do not show a red SKU with a blue filename/alt string because the template was copied. If a genuinely identical component image is reused across pages, keep one stable image URL where practical and write alt text for each page context.

    Avoid uploading several identical copies with small filename changes solely to target keywords. That increases media-library clutter and creates no new product evidence.

    Decorative images and linked images

    An image used only for decoration generally needs an empty alt attribute so assistive technology can skip it. Do not omit the attribute entirely. If an image is a link, its alt text should communicate the destination or action where surrounding link text does not already do so.

    Complex charts and diagrams may need concise alt text plus a nearby detailed explanation. Do not force an entire table into one alt attribute.

    Product image SEO QA checklist

    1. Filename is short, descriptive, stable and matches the actual file format.
    2. Image shows the exact product, variant and view described.
    3. Alt text is useful in context and not stuffed with keywords.
    4. Verified product facts live in page copy or product data, not invented in alt text.
    5. Meaningful images use crawlable HTML image markup.
    6. Responsive files include a fallback source and do not overflow the reading column.
    7. Dimensions are reserved and file size is optimised without visible quality loss.
    8. Image URLs are not accidentally blocked and remain stable.
    9. Decorative images use empty alt text.
    10. The final rendered page is checked on desktop and narrow/mobile view.

    Frequently asked questions

    What should I name product images for SEO?

    Use a short, descriptive filename that identifies the product or SKU, visible variant and image purpose, such as amber-glass-jar-750ml-front.webp.

    Are image filenames important for SEO?

    They can provide light clues and improve asset management, but they are only one signal. Accurate alt text, relevant page context, crawlable markup, quality and performance are more important parts of the system.

    How do I write alt text for ecommerce product images?

    Describe the visible product, relevant variant and view or action in the context of the page. Keep specifications and non-visible claims in the product copy.

    Should every product image include the keyword in alt text?

    No. Repeating a target phrase in every alt attribute harms usefulness and can become keyword stuffing. Describe each image naturally and accurately.

    Should decorative images have alt text?

    Use an empty alt attribute for purely decorative images so assistive technology can skip them. Meaningful images need a useful text alternative.

    Can I automate product image alt text?

    You can generate a first draft from approved product fields and a controlled view vocabulary, but a person should verify that the image, variant and detail actually match before publishing.

    Sources and further reading

  • Lifestyle vs White Background Product Photography: Which Image Should Do What?

    GPTWala Business Hub · Practical ecommerce systems

    A channel-by-channel decision framework for combining clear product proof with believable context instead of choosing one style for every image.

    Updated 23 August 2026 · Reading guide for Indian product businesses

    White-background and lifestyle product photography are not competing aesthetics. They solve different buyer tasks. A clean image helps a shopper identify and inspect the product. A lifestyle image helps the shopper imagine scale, use, setting or outcome. Most ecommerce businesses need both, but not in equal numbers and not in the same placement.

    The useful decision is therefore not “which style is better?” It is “what must this image help the buyer decide at this point in the journey?”

    The real difference: product proof versus product context

    Dimension White or neutral background Lifestyle or contextual scene
    Primary job Identify and inspect the item Explain use, scale, setting or desired outcome
    Visual competition Low Higher; props and people must be controlled
    Product-truth review Easier Harder because lighting and context influence perception
    Variant clarity Strong when each variant has its own image Can be ambiguous if several variants appear
    Channel fit Common for marketplace main images and catalogues Common for galleries, social, ads and editorial pages
    Production complexity Repeatable once setup is locked More styling, location, talent and rights management

    Google Merchant Center’s current guidance says the main product image should clearly show the product, while additional images can provide other views. It recommends a solid white or transparent background in most cases and also accepts staged or lifestyle images that clearly show the product. See the official product image guidance and always check the target channel before upload.

    When white-background images do the better job

    Identification and comparison

    A consistent background, camera angle and crop help buyers compare variants or SKUs without decoding a new scene each time. This is valuable for catalogues, category pages, marketplaces and WhatsApp product lists.

    Detail and product-truth review

    Neutral surroundings make it easier to inspect edges, colour, material, construction and included parts. They also make internal approval more reliable because creative styling is not masking the product.

    Reusable masters

    A carefully captured clean master can support channel crops, comparison cards, catalogues and approved composites. Keep the actual product layer intact. The phone-to-approved-image workflow shows how to preserve that master.

    White does not mean careless: a clipped white product on a white field, an artificial floating shadow or a tight crop can still damage clarity. Use edge definition and keep the whole sellable item visible where the channel requires it.

    When lifestyle images do the better job

    Scale that words cannot quickly communicate

    A bag held by a person, a lamp on a bedside table or a storage box inside a wardrobe can communicate proportion immediately. The context must be familiar and not rely on misleading perspective.

    Use and assembly

    Lifestyle images can show how a product opens, wears, connects, stores or fits into a routine. If the action is complex, a short demo video may be clearer than one photograph.

    Audience and positioning

    A scene can help a buyer recognise “this is for a small retail counter”, “this suits a modern home” or “this component belongs in an industrial setup”. However, do not let mood substitute for factual product information.

    Desire and campaign storytelling

    Ads and social content often need an idea, not only an isolated item. Use a lifestyle asset after the product, audience and claim are approved. GPTWala’s AI ad creative guide covers the campaign layer.

    Lifestyle versus white background: decision table

    Buyer question Best starting image Reason
    Which exact product/variant is this? Clean background Minimises ambiguity
    What does the back, edge or closure look like? Clean detail view Keeps inspection area clear
    How large is it in normal use? Lifestyle or scale image Adds a familiar reference
    How will it look in my space? Lifestyle Provides believable context
    What comes in the pack? Clean contents layout Separates included items from props
    How do I use or assemble it? Lifestyle sequence or demo video Shows action and orientation
    Does the material/finish match the listing? Clean detail plus controlled context Combines factual inspection and realistic appearance

    A strong gallery often moves from certainty to context:

    1. Identify: clean hero of the exact variant.
    2. Inspect: important front, back, side and construction views.
    3. Prove: material, closure, label, included items or functional details.
    4. Explain scale: on-body, in-hand, dimension graphic or familiar setting.
    5. Show use: one realistic action or placement.
    6. Resolve objections: care, fit, storage, installation or compatibility where visual evidence helps.

    Plan this sequence with the ecommerce product photography shot-list template. Do not shoot random lifestyle options and hope the editor finds a story later.

    Choose the image role by channel

    Channel/placement Default starting role Supporting role Gate
    Marketplace main image Clean product identification Context in allowed additional images Current marketplace image policy
    Own website product page Clear exact-variant hero Full proof and lifestyle sequence Mobile gallery clarity and truthful product data
    Category page Consistent clean thumbnails Occasional campaign tile Easy comparison across products
    WhatsApp catalogue Simple small-screen identification Send context/detail during conversation Readable crop and correct SKU
    Meta ad Depends on hook and placement Clean product proof on landing page Ad claim, product truth and destination match
    B2B catalogue Consistent inspection image Application or installation context Revision and specification accuracy

    Budget and production trade-offs

    A clean-background system is usually easier to repeat across many SKUs after the reference setup is approved. Lifestyle production adds concepting, locations, props, talent, styling, usage rights and more complex approvals. Use the larger budget where context removes a meaningful buyer objection or creates a reusable campaign asset.

    A practical allocation method

    Give every SKU the minimum factual image set. Then prioritise lifestyle assets for hero products, high-traffic pages, unfamiliar products, scale-sensitive items and campaigns with a defined audience. Do not create an elaborate lifestyle set for every low-priority SKU by default.

    Using AI for lifestyle product scenes

    AI can reduce the cost of exploring contexts, but it increases the need for product-truth control. Start with an approved clean master, preserve the product mask, and generate only the environment where the workflow allows.

    • Do not regenerate logos, labels, controls, fit or proportions.
    • Check contact shadows and perspective so the product belongs in the scene.
    • Avoid props that imply unsupported size, compatibility or included accessories.
    • Review colour next to the clean master because scene lighting changes perception.
    • Keep the clean listing image available even when a lifestyle scene performs well in ads.

    Use the detailed safeguards in AI background generation for product photos.

    Measure the right outcome

    Do not declare lifestyle or white-background imagery the winner using one generic engagement number. Evaluate the placement and decision:

    • Product-page gallery interaction and image order
    • Add-to-cart or enquiry rate on the same SKU and audience
    • Variant-selection errors and image-related customer questions
    • Returns or complaints linked to scale, colour or expectation mismatch
    • Ad click and post-click conversion, not click-through alone

    Run controlled tests where traffic allows, but keep marketplace compliance and factual product clarity as guardrails. An attractive image that creates the wrong expectation is not a conversion improvement.

    Frequently asked questions

    What is the difference between lifestyle and white-background product photography?

    White-background images primarily identify and expose the product for inspection. Lifestyle images primarily explain scale, use, setting or outcome.

    Which sells more: lifestyle or white-background product photos?

    There is no universal winner. Performance depends on placement, product risk, audience and the question the image answers. Many effective galleries use a clean hero plus factual details and selected lifestyle context.

    Should the first product image have a white background?

    For many marketplaces, the main image must follow strict clean-background rules. On an own website the exact rule is flexible, but clear product identification is still a strong default. Check the current destination policy.

    How many lifestyle images should a product page have?

    Use only the images that answer distinct questions about scale, use, fit or setting. Give every SKU its factual proof set first, then add context where it reduces a real objection.

    Can I use AI-generated lifestyle images on an ecommerce page?

    Yes when the product itself remains accurate and the scene does not imply false size, function, accessories or claims. Keep an approved clean product image and review every composite against it.

    How should I test lifestyle versus clean images?

    Test a specific placement and decision with the same SKU and comparable traffic. Evaluate post-click conversion and expectation-related questions or returns, not engagement alone.

    Sources and further reading

  • How to Photograph Reflective Products: Glass, Metal and Glossy Packaging

    GPTWala Business Hub · Practical ecommerce systems

    A practical reflection-control method for glass, polished metal, jewellery, bottles and glossy packs without deleting the material cues buyers need.

    Updated 23 August 2026 · Reading guide for Indian product businesses

    Reflective product photography becomes easier when you stop trying to light only the object and start designing what the object is allowed to reflect. Glass, polished metal and glossy packaging behave like curved mirrors. A small lamp can appear as a harsh hotspot; a large white surface can become a clean highlight; a black card can create the dark edge that makes a clear bottle visible.

    The goal is not to remove every reflection. A product with no highlight can look flat, plastic or incorrectly retouched. The goal is to create controlled reflections that reveal shape, finish and product truth. This is a material-specific extension of GPTWala’s AI product photography guide for Indian businesses.

    The reflection principle

    On a matte object, light is scattered in many directions. On a glossy object, the camera sees a more direct reflection of the light source and surrounding set. Moving the lamp a few centimetres may do little; changing the size, angle or reflected surface can transform the image.

    Think in surfaces: a softbox is visible in the product as a bright shape. A black flag is visible as a dark shape. Their size and position define the highlight, edge and perceived curvature.
    Surface What the camera tends to see Useful control
    Clear glass Bright background plus dark or bright edges Backlight/diffusion and side cards
    Polished metal Almost the entire room and camera area Large tent-like diffusion with deliberate dark lines
    Brushed metal Broad directional highlights that reveal grain Long source aligned to the finish
    Glossy pack Rectangular hotspots and warped room reflections Large diffused source placed outside the label’s reflection angle
    Gem or faceted surface Many small reflections with high contrast Controlled bright and dark cards plus category-specific expertise

    Prepare the product and set

    1. Clean with the correct material-safe method. Dust, fingerprints and microfibre lint become obvious under large highlights.
    2. Wear clean gloves where appropriate. Handle from hidden areas.
    3. Remove coloured clutter. Walls, clothing, cables and people can appear in polished surfaces.
    4. Use neutral set materials. White, black and grey boards make reflections intentional and repeatable.
    5. Lock the approved sample. Do not retouch away seams, texture, edges or finish variation that exists on the sellable item.

    Before production volume, add these views to an ecommerce shot list and define which reflections are acceptable for the brand and channel.

    Build a large diffused source

    For many shiny products, a larger apparent light source creates a broader, smoother highlight. You can use a softbox, diffusion fabric or a translucent sheet designed for photography. Keep hot lights and flammable material apart and follow the equipment manufacturer’s safety instructions.

    Use two distances, not one

    The light-to-diffuser distance changes how evenly the diffuser is illuminated. The diffuser-to-product distance changes how large the reflected panel appears. Adjust them separately. If the product reflects a bright centre and dark diffuser edges, spread the light more evenly or use a larger panel.

    Move the reflected surface before increasing power

    If a hotspot covers the label, moving the diffusion panel changes where the reflection falls. Increasing or decreasing brightness alone does not solve geometry.

    Shape the product with white and black cards

    White cards add clean bright reflections. Black cards remove reflected light and create definition. For transparent products, black edges often make the outline visible against a bright background. For polished metal, alternating broad white and controlled dark shapes can communicate curvature.

    Card Use Watch for
    Large white card Broad clean highlight or fill A flat product can lose edge separation
    Narrow white strip Long highlight on cylindrical metal or bottle Uneven strip edges become visible
    Large black card Shape definition and removal of unwanted room reflection It can make dark products disappear
    Narrow black strip Edge line on glass or polished metal Keep the line deliberate and symmetrical when required
    Lens flag with opening Hide camera/operator reflection while leaving lens view Do not block ventilation or touch the lens

    Three practical reflective-product setups

    Setup 1: clear glass or transparent bottle

    Place a large diffused light or evenly lit background behind the product. Add black cards just outside the frame on both sides to create edge definition. Move the cards inward until the contour is visible, then back them out enough to keep the glass natural. For a white-edge look, reverse the arrangement: use a darker background with white side cards.

    Setup 2: polished metal cylinder

    Surround the product with a broad curved or multi-panel diffusion surface, leaving only the camera opening. Add one or two dark strips to describe curvature. Rotate the product and cards until logos, seams and handles remain clear. A completely white reflection can erase the cylinder’s form; a completely black one can make it look dirty.

    Setup 3: glossy pouch, carton or cosmetic pack

    Use a large diffused source above and to one side, then tilt the product or light so the main reflection falls away from critical label text. Add a white fill card opposite if shadows become too deep. If the pack wrinkles, improve product preparation and angle instead of cloning out real construction.

    Setup Background Main control Approval focus
    Clear glass Bright or dark, depending edge style Backlight plus edge cards Contour, transparency, label and true contents
    Polished metal Neutral Reflected diffusion environment Finish, curvature, seams and colour spill
    Glossy pack Clean channel-appropriate surface Source angle and panel size Legible label, pack shape and controlled hotspot

    Adapt the technique by material

    • Jewellery: stones, prongs, plating and scale require specialised accuracy. Use GPTWala’s AI jewellery photography checklist before any generative enhancement.
    • Glass with liquid: control bubbles, fill level and colour; record whether condensation is natural, styled or simulated.
    • Chrome: build an intentional reflected environment because the product may mirror almost everything in front of it.
    • Black gloss: use long highlights to reveal the form while retaining a true black body.
    • Holographic or iridescent finishes: one view cannot show every appearance. Plan multiple honest angles or a short video.

    Camera and phone controls

    Stabilise the camera, use a lens perspective that does not distort the product, and lock exposure after the setup is approved. Check the brightest reflection for clipping and the darkest product area for retained detail. If the camera supports a histogram or highlight warning, use it as an aid, not as a replacement for visual inspection.

    With a phone, clean the lens, disable filters and scene enhancement, lock focus/exposure where possible, and use the rear camera. A tripod adapter prevents small changes in angle from moving a reflection across the label.

    Polarisation has limits

    A circular polarising filter can reduce some non-metallic reflections, depending on angle, but it does not remove every reflection and is less effective on metallic reflection. Cross-polarisation requires compatible lighting filters and careful colour/exposure control. Use it as one tool, not a universal fix.

    Edit reflections without faking the finish

    Clean obvious dust and temporary fingerprints, balance exposure and colour, and smooth distracting highlight transitions only when the material remains truthful. Keep characteristic reflections that show gloss, transparency or curvature.

    • Do not turn brushed metal into mirror chrome.
    • Do not remove a functional seam, clasp, edge or opening.
    • Do not make cloudy glass appear optically clear if the real product is not.
    • Do not replace the label with sharper but incorrect text.
    • Keep the approved real-product layer separate when using AI-generated backgrounds.

    Reflection troubleshooting table

    Problem Likely reason First adjustment
    Small harsh white hotspot Source appears too small Use larger diffusion closer to the product
    Camera or operator visible Open reflected environment Use a neutral lens flag with a safe opening
    Label is unreadable Reflection crosses critical text Change source/product angle before retouching
    Glass edges disappear No contrast at contour Add black or white edge cards outside frame
    Metal looks flat Reflection is one uniform tone Add controlled dark and light shapes
    Unexpected coloured stripe Room or clothing reflection Replace the reflected area with neutral flags
    Dust remains everywhere Preparation and inspection gap Clean before capture and review at 100%

    Frequently asked questions

    How do you photograph shiny objects without reflections?

    Do not try to eliminate every reflection. Surround the object with controlled white, black and diffused surfaces, then place the resulting highlights where they reveal shape without covering critical details.

    How can I photograph reflective products at home?

    Use a stable table, neutral background, large diffusion surface, white and black boards, a tripod or phone mount, and remove coloured clutter from the reflected environment.

    What lighting is best for glass product photography?

    A large, even backlight or diffused background with controlled side cards is a reliable starting point. Choose dark-edge or light-edge glass based on the background and desired contour.

    Can a polarising filter remove reflections from metal?

    A polariser may reduce some non-metallic glare, but it does not remove all reflections and is limited with metallic surfaces. Reflection geometry and set control remain essential.

    Should glossy products have no highlights?

    No. Controlled highlights communicate gloss, curvature and material. Removing all highlights can make the product look flat or incorrectly retouched.

    Can AI clean reflective product photos?

    AI may help with dust or background work, but it can also invent edges, labels, reflections and finish. Compare the result with an approved real-product master and reject factual changes.

    Sources and further reading

  • Product Photo Colour Accuracy: A Repeatable Capture-to-Approval Workflow

    GPTWala Business Hub · Practical ecommerce systems

    A practical system for controlling light, white balance, capture, editing and approval so the product stays recognisable across a catalogue.

    Updated 23 August 2026 · Reading guide for Indian product businesses

    Colour-accurate product photography is not achieved by making the image look pleasing on one screen. It is achieved by building a repeatable chain from the approved physical sample to the light, camera, reference frame, edit and final decision. The goal is not laboratory-perfect reproduction on every customer device. The goal is a controlled, defensible image that does not misrepresent the product.

    This article narrows one part of GPTWala’s AI product photography system. For shape, label and component checks, also use the broader product-accuracy workflow.

    What colour accuracy means in ecommerce

    Colour accuracy has three practical levels. First, images from the same shoot should be consistent. Second, the approved image should be a credible match to the physical reference under agreed viewing conditions. Third, variations shown on a product page should be distinguishable without artificial exaggeration.

    Important limit: a buyer’s display brightness, colour mode, ambient light and device profile can change what they see. Your team can control the production workflow, not every viewing device. Avoid absolute claims such as “the colour on screen will be identical”.
    Control point What you can control What you cannot fully control
    Physical reference Approved SKU, batch and finish Normal manufacturing variation outside tolerance
    Lighting Source type, position, intensity and unwanted mixed light How a buyer later views the item
    Capture Exposure, white balance, file format and reference target Every camera’s native colour response without profiling
    Editing Profile, neutral point, product corrections and export space Unmanaged displays and app-specific rendering
    Approval Named approver, viewing setup and accepted master Subjective memory of colour without the sample

    Why product colours shift

    Mixed light creates competing colour casts

    Window daylight, a warm room bulb and a different LED panel can illuminate separate parts of the product with different colour. One global white-balance adjustment cannot make all three neutral. Block or switch off uncontrolled sources before adding the chosen light.

    Automatic settings change between frames

    Auto white balance and auto exposure may react differently when the product colour or framing changes. That is useful for casual photography but weak for a repeatable catalogue. Lock the agreed exposure and white-balance method once the reference frame is approved.

    Reflective and fluorescent materials behave differently

    Glossy surfaces mirror the environment. Fluorescent dyes and optical brighteners can react strongly to the light spectrum. Treat these as special cases and record the limitation instead of forcing a single edit to match every light source.

    Editing by memory causes drift

    Human visual adaptation is powerful. After looking at a warm image for several minutes, it can begin to feel neutral. Compare against a neutral reference and the approved physical sample rather than editing from memory.

    Build a controlled colour setup

    1. Select the approved physical reference. Record SKU, variant, batch if relevant, and who confirmed it.
    2. Use one light family. Avoid mixing daylight, household lamps and unmatched LEDs.
    3. Control the environment. Bright coloured walls, clothing and props can reflect colour onto the product.
    4. Place a neutral reference in the product light. A neutral target is more reliable than ordinary white paper, which may contain optical brighteners or a colour cast.
    5. Stabilise camera and composition. A tripod or fixed phone mount keeps the comparison meaningful.

    X-Rite explains that changing ambient light changes how a camera reproduces colour, and that a spectrally neutral reference supports custom white balance. Review the manufacturer’s ColorChecker white-balance explanation for the principle. The tool is an option, not a requirement to buy a specific brand.

    Capture a reliable reference frame

    Step Action Reason
    1 Clean the product and lens Dust and haze affect local colour and contrast
    2 Fill the intended frame without clipping edges Reduces later upscaling and inconsistent crops
    3 Include the neutral or colour reference in the same light Creates an objective starting point
    4 Check highlights in every colour channel where tools allow A channel can clip before the overall image looks overexposed
    5 Capture the reference, then the clean product frame without changing light Keeps correction transferable
    6 Repeat the reference when light, camera, lens or setup changes Prevents one correction being applied to a different condition

    If your camera supports a raw format and the team can process it reliably, raw files preserve more adjustment flexibility than a heavily processed JPEG. A consistent JPEG workflow can still work for a small catalogue, but it requires correct light and white balance at capture because there is less room to recover.

    Edit without drifting away from the product

    Start with profile and neutral balance

    Apply the appropriate camera or device profile, then use the reference frame to establish a neutral starting point. Synchronise that base only across images captured under the same conditions.

    Correct the product, not the mood

    Separate factual corrections from creative grading. White balance, exposure and careful local corrections may be needed to match the reference. A warm preset, selective saturation or hue shift that changes the sellable product belongs in an advertising concept only when clearly separated from the factual listing asset.

    Check difficult colours locally

    Deep reds, saturated blues, metallic finishes and near-black materials can lose detail or shift hue. Inspect the product at 100%, compare the relevant area with the sample, and keep texture visible. Do not solve a colour mismatch by flattening the material.

    Export a stable web master

    Keep a high-quality approved master, then create delivery files in the format, size and colour space supported by the destination. Record the export preset. Do not repeatedly open, resize and resave the only master.

    A smartphone colour-accuracy workflow

    A phone can produce a controlled result when the team reduces automatic variation:

    1. Use the same phone, lens and camera app for the approved series.
    2. Disable beauty, vivid, scene-enhancement or filter modes.
    3. Lock focus and exposure where the app allows.
    4. Use one controlled light setup and block mixed ambient light.
    5. Capture a neutral reference and the product without changing the setup.
    6. Compare edited output with the sample on a reasonably calibrated display.

    For the complete small-team process, see how to create product images from a phone photo.

    Safeguards when AI changes the scene

    Background generation and compositing can alter perceived colour even when the product pixels are unchanged. A warm room, coloured surface or dramatic shadow changes visual adaptation. Keep a clean factual product image as the approval reference, and compare the generated scene side by side.

    • Mask the product carefully rather than regenerating it.
    • Do not let relighting change the product’s hue, finish or transparency.
    • Check coloured spill on reflective edges.
    • Keep a before/after comparison with the exact approved master.
    • Reject outputs that make one variant look like another.

    The AI background generation guide covers scene creation without surrendering product control.

    Approve and document colour

    Use a named approver who can access the physical sample. Review under stable light on a display that is not using a night-light or vivid mode. For high-risk colour products, compare more than one calibrated or controlled display, but record which display is the decision reference.

    Approval record What to save
    Product identity SKU, variant, batch/sample ID
    Capture condition Date, light setup, camera/phone and reference target
    Master Approved filename and version
    Decision Approver, date and any accepted limitation
    Derivatives Export preset and destinations

    Colour troubleshooting table

    Symptom Likely cause First check
    One side is warm, the other cool Mixed light sources Switch off room light or block daylight, then recapture
    Frames change colour without edits Auto white balance Lock a custom or fixed balance after the reference
    Colour matches in editor but not browser Export/profile handling Check the export colour space and browser file
    Dark colour loses texture Underexposure or crushed shadows Adjust light and exposure before saturation
    Glossy edge picks up a coloured line Reflected wall, clothing or set card Use neutral flags and control the reflected environment
    AI scene changes product colour Relighting or generative spill Return to the approved product mask and compare side by side

    Frequently asked questions

    How do I get accurate colours in product photography?

    Use one controlled light family, remove mixed ambient light, photograph a neutral reference, lock the capture settings, edit from that reference and approve the result beside the physical sample.

    Should I use auto white balance for product photography?

    Auto white balance can change between frames. It is safer to establish and lock a repeatable balance after the light and neutral reference are in place.

    Is a white sheet of paper good enough for white balance?

    Not always. Ordinary paper may not be spectrally neutral and can contain optical brighteners. A purpose-made neutral target is more reliable for repeatable work.

    Why do product colours look different on different phones?

    Displays, brightness, colour modes, ambient light and app rendering differ. Control your production workflow and avoid promising an identical appearance on every device.

    Can AI background generation change product colour?

    Yes. Relighting, colour spill and surrounding context can alter the pixels or the perceived colour. Compare every scene to an approved clean product master.

    How should colour approval be documented?

    Record the exact SKU and sample, capture setup, reference frame, approved master filename, display/viewing conditions, approver and any accepted limitation.

    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