How to Create Amazon Listing Images From Photos

Here is how to create Amazon listing images from real product photos and verified listing facts, then expand the workflow from one SKU (stock keeping unit) to a product family and catalog batches. Keep each variant’s appearance and included items accurate. Generate and review candidates in batches; approve each image and choose the submission workflow separately before anything changes on Amazon.

A family can share the same scene without sharing the same product facts. Your smallest size, newest color and multipack may need different measurements, references and labels. The Listing Optimizer Skill reads those listing differences through the Selling Partner MCP. Amazon Agent Iris creates the requested image from the references you select, so reuse starts with the creative direction, not an assumption that one sibling’s image fits every child.

Plan the gallery around what a buyer needs to see. This is a production worksheet, not the result of a customer run.

Real photos and listing facts define the first SKU’s brief

The first SKU establishes a brief your team can inspect before expanding production. Confirm the seller, marketplace and Amazon Standard Identification Number (ASIN). The Selling Partner MCP reads the current listing attributes and catalog images; the Listing Optimizer Skill uses the existing photos as generation references. Supply additional owned photos when a missing angle or obscured feature cannot be established from the listing.

Treat the listing as evidence to verify, not permission to repeat a contradiction. If the photo shows one lid and the attributes describe another, resolve the difference before generation. A size graphic needs confirmed dimensions; a missing measurement stays missing. Product identity, packaging, quantity and included accessories belong in the brief alongside the desired scene.

For each requested slot, record:

• The product references to preserve and the facts they establish.
• The image’s job: main shot, lifestyle, detail or explanatory graphic.
• What may change, such as lighting or background, and what must remain accurate.
• The marketplace and product-type rules, plus the person who will review the result.

Use Iris as the Amazon listing image generator for the creation and editing steps. The Iris documentation explains model access, uploads and returned asset URLs. The standalone Listing Optimizer image workflow is another path: it calls your configured image provider and stages approved files in your storage. It does not host images itself. Pick the configured path before promising a generation run.

A product family can share a layout without sharing every image

A product family is the next useful scope because shared creative direction and variant-specific facts meet in the same review. Read each child listing through the Selling Partner MCP. A variation parent organizes the family; it does not establish the size, color or pack count of every child.

Reuse an approved composition, lighting brief or genuinely variant-neutral explanation where it remains true. Recheck product depictions against each child’s references. Recoloring an image is not evidence that the resulting product exists, and a graphic approved for a single unit may misrepresent a multipack.

The Iris family workflow can identify potentially reusable sibling images. Your review still decides whether each candidate accurately represents the receiving SKU. Hold a child with missing or conflicting facts instead of carrying an uncertain image across the family.

Catalog batches need an asset record and a review owner

Bulk product image generation is useful when it repeats a reviewed brief while preserving a separate record for every SKU and image. Start with the one-SKU result, test the family differences, then group catalog work by marketplace, product type and image need. This is a recommended rollout sequence, not a claim that the Skill automatically clones an approved gallery across your catalog.

Ask the Listing Optimizer Skill to scan the scope you name for image gaps. A whole-catalog scan requires that scope explicitly; generation need not start for every listing the scan finds. Prioritize unresolved main-image issues and the gallery gaps your team chooses to address. Where commercial context matters, Amazon Ads MCP supplies advertising evidence rather than a guessed return from better imagery.

Keep a batch review sheet with these fields:

Your team can retain the review sheet beside catalog history in the Amazon Agent Data layer. Agree the batch size, provider spend and review owner before generation. Expand after the first batch exposes its reference gaps and review effort; there is no universal throughput or cost promise here.

The same product references can support a separate Omni video brief

Approved product references can also seed Google Gemini Omni shots through Iris. Fresh clips are 3–10 seconds; an owned Iris video can be extended up to 40 seconds total. Review product fidelity and actual returned duration. A finished 60-second deliverable needs external assembly: Iris has no native stitching or final-export tool. Listing-image approval does not authorize billed video creation or publication; use a separate placement-specific brief and the video controls.

Every candidate needs file checks and human product review

Amazon AI product images need the same truthful product representation and applicable image rules as other listing images. Amazon Agent Atlas supplies the Product image guide, Image suppression guidance and Product page style guides. The last source matters because category rules can change what belongs in the main image.

The Listing Optimizer validator measures format, color space, size, the main image’s white border and estimated product fill. Its PASS means those checks cleared. It does not certify product fidelity or guarantee Amazon will display the image. Text, labels, logos, focus, proportions and included parts remain human review items; FAIL candidates return for correction and unresolved REVIEW items stay on hold.

Amazon recommends six additional images and one video, but that is not a reason to generate filler. Cover the buyer’s unanswered questions with accurate assets. Noncompliant images can cause suppression, so replacing a failed main image takes priority over adding another lifestyle scene. The image requirements and suppression guidance establish those boundaries.

What happens next: approve assets, then choose the submission path

Approve each image before it becomes a listing change. Confirm its SKU, marketplace and slot, then ensure the approved file remains fetchable during Amazon’s ingestion. Iris returns hosted asset URLs; the direct Skill path stages files in your configured storage. Neither a generated file nor an image-review decision is a submission receipt.

For a small test, the Listing Optimizer Skill previews the proposed patch, asks for separate confirmation and submits the same change. Amazon’s VALIDATION_PREVIEW is intended for testing a small number of listings and has lower rate limits; it is not designed as a production catalog loop. Production bulk submission needs a separately reviewed integration. Amazon offers multi-SKU media submission through JSON_LISTINGS_FEED, but that API capability does not establish that this Skill implements a bulk feed publisher.

• Rejected or held image: correct the candidate or resolve its missing product fact; do not submit it.
• Approved small-scope change: review the exact patch and confirm submission through the Selling Partner MCP.
• Catalog production rollout: agree the submission method, retry handling and per-SKU results before sending the batch.
• ACCEPTED submission: retain the submission ID and check later status and issues. Acceptance is not proof that the image is live or selected for display.

Keep the same product evidence attached as work expands. The reusable asset is the brief and review process; the approval remains specific to the product and image.

If an image change begins with a listing problem, start with the listing audit-to-patch workflow.