Seedance Product Video Prompts That Keep the Product Consistent

THE CONSISTENCY CONTRACT

Keep identity, evidence and state separate.

Product consistency has three different jobs. Identity keeps the submitted object recognizable. Evidence controls which features and claims may appear. State defines what may change during the shot. A single instruction such as “keep the product consistent” is too vague to perform all three.

SEVEN REVIEWABLE FIELDS

Compile the prompt from fields you can inspect independently.

Do not start with a cinematic paragraph. Complete these fields first, then translate them into provider-native language only after the shot plan is approved.

1. 01

   Product lock

   Name the exact submitted item and the reference asset that defines its shape, finish, controls and visible accessories.

2. 02

   Advertising job

   Choose one job for the shot: recognition, feature proof, use context or desire.

3. 03

   Approved action

   Describe one visible product or camera action that belongs to the approved shot plan.

4. 04

   Evidence

   Point to the product image or verified fact that permits the action, feature or state shown.

5. 05

   Camera and light

   Specify framing, movement, angle, lighting and pace without changing the product.

6. 06

   Continuity

   State what must remain stable from the reference through the final frame.

7. 07

   Claim boundary

   Exclude unsupported text, features, logos, accessories and state changes.

ORIGINAL PRODUCT VIDEO TEMPLATES

Choose the template by advertising job, not visual style.

Replace every bracketed field with verified product information. If the evidence required by a template is missing, use the simpler product reveal instead of inventing a scene.

[PRODUCT LOCK]
Keep the exact submitted [product name and category] from [primary reference]. Preserve its [shape, finish, controls and visible accessories].

[SHOT JOB]
Create a recognition-first product reveal.

[APPROVED ACTION]
Begin with [starting frame]. Move the camera [single camera action]. End on [stable closing angle].

[CAMERA + LIGHT]
Use [shot size], [lens feeling], [lighting] and [pace].

[CONTINUITY + CLAIM BOUNDARY]
The same product remains visible and unchanged. Do not add readable text, new logos, accessories, functions or unsupported product states.

[PRODUCT LOCK]
Use the exact submitted [product] defined by [primary reference].

[VERIFIED SELLING POINT]
Show only [one verified feature]. Evidence: [asset or page fact].

[APPROVED ACTION]
Move from [whole-product frame] to [supported detail]. Keep the feature readable through one controlled [push / orbit / rack focus].

[CONTINUITY]
Preserve product geometry, materials, color and control layout across the shot.

[CLAIM BOUNDARY]
Do not imply performance, certification, compatibility or functions beyond the supplied evidence. Do not generate interface copy or CTA text.

[PRODUCT LOCK]
Keep the submitted [product] identical to [primary reference].

[APPROVED USE MOMENT]
Show [one verified interaction] in [approved setting]. The product begins in [approved initial state] and ends in [approved final state].

[SUBJECT + CAMERA]
Use only [approved hand / person / no person]. Frame the action as [shot size] with [single camera move].

[CONTINUITY]
The product identity, finish, controls and approved accessories remain unchanged before and after the interaction.

[CLAIM BOUNDARY]
Do not introduce a person, accessory, environment, result or state transition that is absent from the approved plan.

Browse more structures in the product video prompt library, or review the complete Seedance ecommerce production workflow.

NEGATIVE PROMPTS ARE NOT THE FOUNDATION

A long blacklist cannot repair an undefined product contract.

Negative instructions are useful for narrow, known risks such as unwanted readable text or extra accessories. They do not replace a stable primary reference, a defined product category, an approved action or evidence for the selling point.

When the result introduces a new story, the first question is not which prohibition to add. Check whether the shot job, state transition and evidence were defined. Fix the owning field and recompile the prompt. This prevents one failed example from becoming a permanent rule for every product.

BEFORE AND AFTER GENERATION

Use the same contract to approve the prompt and judge the result.