PlaysbyMoat8
Back to the library
The workflow guideMarketing

Generate product images from a shared visual brief

Use approved product references and photography guidelines to prepare consistent images for a store or campaign.

6 implementation stepsIntermediate

How this works

Use approved product references and photography guidelines to prepare consistent images for a store or campaign. Product imagery must preserve the actual product even when the setting is generated. Shape, color, labels, included components, and scale can affect a buyer's expectations, so visual consistency is also a factual accuracy problem.

Use approved product references as the fixed anchor and vary only the permitted scene attributes. Generate a small set of candidates, compare them with the reference, and provide a designer with clear acceptance and rejection notes. Keep image production separate from listing publication.

Before you start

Accurate product references

Provide multiple useful views and known specifications.

Photography rules

Define background, lighting, angle, crop, and acceptable props.

Placement requirements

Specify dimensions, format, and whether the image is illustrative or a product listing.

Prepare the inputs

product_assets
Required

Approved images

Use the correct SKU and version.

product_constraints
Required

Fixed features

List colors, geometry, labels, and included items.

scene_brief
Required

Setting and composition

Separate permitted changes from fixed product details.

brand_style
Required

Visual rules

Use current guidance.

export_requirements
Required

Dimensions and formats

Identify crops needed for each placement.

Implementation, step by step

  1. Inspect the product anchor

    • Review reference views and list distinctive details that must survive generation.
    • If a side or component is not shown, avoid inventing it.

    Checkpoint: A product-fidelity checklist.

  2. Specify the scene

    • Define camera angle, lighting, background, and props within the brief.
    • Keep scale and physical relationships plausible without adding unsupported accessories.

    Checkpoint: A controlled generation brief.

  3. Generate candidates

    • Use available image tools with the approved references.
    • Label each candidate by scene and version for later review.

    Checkpoint: A manageable candidate set.

  4. Check product fidelity

    • Compare shape, color, text, components, and material details with the original.
    • Reject subtle changes that could mislead a buyer, even if the image looks attractive.

    Checkpoint: A fidelity-reviewed shortlist.

  5. Refine layout and crops

    • Prepare required placements with safe margins and readable product details.
    • Use controlled overlays for exact text rather than accepting distorted generated labels.

    Checkpoint: Placement-specific drafts.

  6. Prepare the asset handoff

    • Export actual files and record approved and rejected variants.
    • Provide the listing or campaign owner with the fidelity checklist and remaining limitations.

    Checkpoint: A reviewable image package.

Decisions along the way

A generated image changes a feature

Regenerate or use a real cutout rather than hide the discrepancy.

Reference coverage is insufficient

Request the missing view or choose a scene that avoids it.

A prop could imply inclusion

Remove it or clarify the visual according to the placement brief.

What you will produce

product-image-drafts

Image files

Provides consistent candidates for review.

Include: sku · scene_id · version · dimensions · status

product-image-review.csv

CSV

Documents why an image is usable.

Include: candidate_id · feature_check · issue · decision

Check the result

  • Compare the selected image with the exact SKU references.
  • Inspect labels and small components at full resolution.
  • Check scale and included-item implications.
  • Review every crop rather than assuming one composition fits all placements.

When something goes wrong

Generation repeatedly changes geometry

Use a reference-preserving composition or manual product cutout.

Brand style overwhelms product clarity

Simplify the scene and restore product visibility.

Export resolution is inadequate

Regenerate or export at the required size without claiming detail that is absent.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Create a consistent store image for a blue bottle.

Inputs

Synthetic example. Synthetic reference shows a plain cap and a 500 ml label; generated candidate adds a pump and changes the label to 750 ml.

Expected result

Synthetic expected result. Reject that candidate. The approved version preserves the cap and label while changing only the background and lighting.

Run a small pilot

Start small

A few SKUs with distinct shapes and label details.

Record the baseline

Record candidate rejection reasons and designer correction time.

Agree success criteria

Agree product-fidelity and placement-quality criteria before batch production.

Stop or revise

Stop listing use when an image changes a material product attribute.

Keep the scope clear

  • Do not invent features, included accessories, or certifications in imagery.
  • Generating an image does not authorize publishing it to the store.

Check before using

Check product shape, details, colors, and any visual claims.

Business activities

  • Create and publish content
  • Manage product catalogs and storefronts

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Product reference images · Brand palette · Photography guidelines

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗