By Genflow
Evidence checked: August 28, 2026
An ecommerce product video storyboard should settle the argument before describing camera moves: one audience, one supportable proposition, one proof, and one destination. Then assign every beat a job, duration, source, continuity rule, and pass condition.
Copy the template below into a campaign ticket or production document. It organizes decisions but does not predict views, clicks, sales, or any other outcome.
Research scope and responsibility
Genflow is accountable for this guide. On August 28, 2026, the Genflow editorial team inspected live public Genflow video pages and an ecommerce creative template, then reviewed Google Ads guidance and commercial-storyboard references. The template’s input schema and options were research context only. Volatile interaction counters were omitted because they are not output tests or business results.
We did not buy or run a generation. The worked concept in this article is therefore a planning exercise, not a controlled before-and-after demonstration. AI assisted with research organization and drafting; Genflow’s editorial team checked the claims and retained the evidence pack and reviewer record. Correction requests can be sent through Genflow’s published website contact route with the article title, the passage at issue, and an accountable source so the team can investigate and preserve the revision trail.
Start with a one-sentence creative contract
Before making panels, complete this sentence:
For [specific audience], we will make [one supportable proposition] credible by showing [one approved proof], then ask them to [one action at one destination].
“One” is a production constraint, not a universal advertising law. It prevents a short video from carrying several unrelated jobs.
A strong contract names things the team can inspect. For example:
For shoppers comparing travel mugs, we will show that the lid locks by using an approved close-up of the actual mechanism, then ask them to view the product details.
A broader “spill-proof in every situation” claim would need different substantiation. A generated splash cannot provide it.
Match the board to its destination
Record whether the destination is a PDP, organic post, paid placement, or marketplace. It affects framing, safe areas, captions, offers, duration, delivery, and policy review.
Ask these questions before drawing panels:
- Sound-off behavior and first-frame requirements?
- Current aspect ratios, safe areas, captions, disclosures, or restrictions?
- Does the CTA match the destination?
- Will any frame become a thumbnail, PDP still, or feed-bound image?
Requirements change. Link the live specification in the job record rather than copying a platform dimension into a permanent template and assuming it remains current.
Copyable 15-second ecommerce storyboard worksheet
Copy this section into your planning document and complete every applicable field.
A. Campaign decision card
| Decision | Approved entry |
|---|---|
| Audience | |
| One proposition | |
| Evidence or proof owner | |
| One CTA | |
| Destination URL or screen | |
| Placement and current policy URL | |
| Product / SKU / variant | |
| Required aspect and safe-area plan | |
| Rights and consent owner | |
| Producer / factual reviewer / channel approver |
B. Five-beat board
| Time | Beat and job | Picture / action | On-screen copy, voice, sound | Evidence and continuity | Pass condition |
|---|---|---|---|---|---|
| 0:00–0:02 | Relevance: identify the viewer’s reason to stay | Meaning is understandable in the destination context | |||
| 0:02–0:05 | Product: identify the exact offer | SKU, pack, color, quantity, and visible geometry are correct | |||
| 0:05–0:09 | Proof: support the proposition | Visual shows no more than the cited evidence supports | |||
| 0:09–0:12 | Resolution: make the use or idea clear | Outcome does not become a new unsupported claim | |||
| 0:12–0:15 | Action: deliver CTA and destination | CTA, offer, availability, and landing destination agree |
These ranges are a working allocation, not a platform rule. If proof or a qualification will not fit, reduce the proposition or choose a longer format.
C. Shot contract for every generated or captured clip
| Field | Shot entry |
|---|---|
| Shot ID and beat | |
| Start frame: product orientation, crop, visible facts | |
| One primary action | |
| Camera movement or locked view | |
| Locked product facts | |
| Background and prop limits | |
| Required end frame for the next cut | |
| Copy, caption, voice, music, and legal line | |
| Evidence source / asset IDs | |
| Observable pass condition | |
| Selected take / rejection reason |
D. Release checklist
- Every claim has an accountable source and owner.
- No generated illustration is presented as a controlled product test.
- Product identity remains stable within and between shots.
- Product, people, voice, music, logos, and references have documented rights.
- Captions and material qualifications are readable in the intended placement.
- CTA, offer, availability, and destination were checked at release.
- Current channel policy and export specification were reviewed.
- Any extracted still passed its own image-placement and metadata gate.
- Reviewer, version, decision, date, and rejected takes are retained.
Release decision: Pass / Revise / Reject / Not verifiable
Blocking issue:
Approvers and date:
Master asset ID / export IDs:
Build a claim-to-proof ledger
Complete the ledger before choosing visual effects so a metaphor or simulation cannot become “proof.”
| Statement planned for the video | Acceptable source for this job | What the picture may communicate | Common overreach to block |
|---|---|---|---|
| Dimensions or capacity | Approved product specification | Measured graphic or accurate physical relationship | Enlarging the product for drama |
| Material or construction | PIM, supplier record, or approved technical file | Faithful macro and exact approved label | Invented texture, component, or material |
| Functional behavior | Suitable controlled real test and approved record | What the observed test actually establishes | Generated action presented as a real test |
| Ingredient, flavor, or scent note | Approved product copy and substantiation | Clearly interpretive mood or approved text | Turning a visual metaphor into a literal composition claim |
| Customer experience | Authorized, traceable testimonial with required context | The exact approved statement | Synthetic speaker presented as an actual customer |
| Price, discount, or availability | Current commerce system and terms owner | Complete approved offer and conditions | Expired, partial, or destination-mismatched offer |
If the team cannot name the source, remove the statement.
Write continuity as facts, not adjectives
Continuity often fails between shots: labels, colors, package seams, or proportions change during motion.
Create a continuity strip for the product:
| Continuity fact | Approved state | Shots that must match | Reviewer note |
|---|---|---|---|
| Silhouette and proportions | |||
| Variant, color, and finish | |||
| Logo / label plane and exact text | |||
| Components and included items | |||
| Product position and orientation | |||
| Light direction and shadow logic | |||
| Background geography and prop position | |||
| End-frame match for the following cut |
State the opening orientation, one action, and required end position. Add exact typography and offers during a controlled edit step.
Worked planning example: fragrance discovery
Suppose approved copy describes floral and aquatic notes. This hypothetical, ungenerated board leads to a notes page.
| Time | Planned frame and motion | Copy / audio | Evidence and acceptance |
|---|---|---|---|
| 0:00–0:02 | Verified bottle silhouette appears against dark negative space; camera remains still | Exact bottle name, typeset in edit | Bottle shape, cap, liquid color, and front label match approved references |
| 0:02–0:05 | A soft reflection opens beneath the bottle; a lotus form enters the distant background | “Floral and aquatic,” only if this is approved wording | Lotus and water read as atmosphere, not literal ingredients or origin |
| 0:05–0:09 | Controlled side light reveals the bottle edges; the product does not rotate beyond evidenced views | Approved note-family copy or no claim | Label text, fill level, glass geometry, and closure do not change |
| 0:09–0:12 | Motion settles and leaves negative space beside the verified front view | Music resolves; no additional promise | Final product state can cut cleanly to the action frame |
| 0:12–0:15 | Hold on approved pack shot and separately composited CTA | “Explore the notes” | CTA lands on the notes page; pack, availability, and destination are current |
This concept proves no ingredient, longevity, mood, or purchase claim. Its symbols must not create an unsupported literal impression.
During our public product inspection, a Genflow ecommerce creative template accepted a product image and offered aspect and transformation choices. That schema helped frame the handoff questions above, but the template was not run and its public preview was not treated as a controlled result.
Hand off AI generation one shot at a time
For identity-sensitive products, begin from an approved still and a narrow shot contract. The public Image-to-Video AI page describes a route from a source image to motion, while the AI Video Generator page covers broader video creation workflows. The video ads use-case page provides related production context.
Use separate clips for materially different actions or settings. Review each take’s first frame, motion, and final frame. Assemble approved shots where exact text, captions, offers, audio, and legal copy remain controllable.
Use exploratory footage for atmosphere when exact identity is unnecessary. For mechanisms, legible packaging, or proof, use controlled capture, verified compositing, or another evidence-suitable method.
Add an image destination and metadata gate
Video production creates still-image assets: source frames, thumbnails, posters, end cards, and exported frames. Do not assume an image approved inside a campaign video is also eligible for a product feed.
For editorial or campaign images, record the generated context, source rights, product review, intended placement, and any disclosure required by that destination. A stylized setting may be appropriate, but it must not introduce a false material, accessory, package size, endorsement, or product result.
For feed-bound images or main listing stills, run a stricter, separate check against the current marketplace or shopping specification. Confirm that the exact SKU, variant, color, sellable quantity, included items, and feed attributes match the picture. Check current rules for backgrounds, overlays, borders, watermarks, placeholders, quality, and AI-image handling. Google’s current guidance for generative AI content states that AI-generated Merchant Center images must contain IPTC DigitalSourceType=TrainedAlgorithmicMedia metadata. Preserve that metadata, treat AI-generated title or description data separately, and recheck the live destination policy. Campaign approval does not satisfy this gate.
For every retained image, review the filename, SKU, locale, crop, destination, alt text, caption, version, source IDs, edit or generation history, rights owner, reviewer, and approval date. Retain embedded provenance or content credentials when your workflow uses them, but do not claim that metadata alone proves an image is authentic. Its practical role here is traceability.
Review the board in five passes
Use separate passes so visual enthusiasm does not bury factual failures.
- Claim pass: Verify every written, spoken, and implied proposition against the ledger.
- Product pass: Check identity, geometry, color, pack, component count, label, and continuity across frames.
- Edit pass: Check that each shot begins and ends where the adjacent cut expects, and that the CTA has a readable hold.
- Access and rights pass: Review captions, contrast, sound-off comprehension, flashing, safe areas, licenses, consent, identity, and required notices.
- Destination pass: Recheck current policy, export, offer, URL, availability, metadata, and any extracted still.
A factual, rights, identity, or destination failure blocks release. A subjective style preference can be logged for a later revision without obscuring the blocking issue.
Plan variants that remain interpretable
The storyboard can also define what changes between versions. Keep the commercial argument and evidence stable while changing one purposeful element, such as the first frame, the order of approved proof, the CTA wording, or the crop plan. Give every export a variant ID and record its exact difference.
This predicts no winner; it prevents later comparisons from confusing simultaneous changes.
Preserve the production and review record
Retain the decision card, ledger, evidence, board, shot contracts, rights, workflow version, settings, outputs, chosen takes, rejection reasons, approvals, policy link, exports, reviewers, and asset IDs. Link later reporting to the exact released version without turning its result into a universal promise.
Frequently asked questions
Does a 15-second video require five separate scenes?
No. The template uses five decision beats: relevance, product, proof, resolution, and action. One continuous shot may perform several jobs if the meaning, evidence, and timing remain clear.
Can an AI-generated demonstration support a product claim?
Not by itself. It can illustrate a concept, but the support must come from an accountable record or a suitable controlled real test. The picture must not imply a stronger finding than that evidence establishes.
Should the whole ad be generated from one prompt?
That may reduce review control when exact products, claims, or transitions matter. Shot contracts make it easier to inspect product drift and assemble approved segments with controlled copy and audio.
What is the most important approval field?
There is no single universal field, but an unowned claim is an immediate stop. It cannot be repaired by stronger motion, a more realistic render, or a more prominent CTA.
Sources and editorial responsibility
Production terminology was checked selectively against StudioBinder’s commercial storyboard guide and Boords’ marketing video storyboard guide. Destination review should use current Google Ads video asset guidance and the rules of the actual placement. Genflow workflow context comes from the public AI Video Generator, Image-to-Video AI, and video ads pages inspected on August 28, 2026.
The decision card, five-beat worksheet, claim ledger, continuity strip, and release checklist are Genflow editorial planning frameworks. They are not product features, validated performance methods, or guarantees of output quality, time, cost, approval, conversion, or commercial success.