Rebuild Your Listing Images From Your Own Photos

Rebuilding a thin listing gallery is one conversation: the Amazon Agent Iris Skill seeds new images from your own product photos, fills factual details from the listing's own catalog data, grades every image against Amazon's rules through Amazon Agent Atlas, and waits for you to approve before it publishes a single one through the Selling Partner MCP. One photo in, a full compliant set out, nothing live until you say yes.

That sequence exists because of a Slack message I get some version of every month: "Can the agent use our existing product photos as seeds to make better listing images that still pass Amazon's image rules, and let me approve before anything publishes?" The pain underneath is the long tail. Most catalogs stay underbuilt because fixing every laggard meant a photographer, a studio, a designer, and a round of manual uploads, and that was never worth it for a SKU doing twelve units a month. Good imagery used to mean picking two of fast, cheap, and safe. So I handed a thin water-bottle listing to our agent with one rule: seed from our real photos, check before you publish, and stop at my approval.

Why not just do this in ChatGPT or Claude? A generic chat hits the same three walls on any Amazon job. It has no access to your data, so it cannot read your live listing or your existing photos and works only from what you paste in. It has no way to take action, so it cannot check an image against Amazon's policy, publish it, or confirm it landed; the most it can do is hand you a file to upload by hand in Seller Central, where images can take up to 24 hours to appear and uploading does not guarantee display. And it runs on generic knowledge, not Amazon's, public training data rather than Amazon's current, in-depth image rules (white background, the zoom threshold, per-category main-image rules, suppression triggers). What you get is disconnected, generic, manual work that ships silent mistakes, and a non-compliant image can suppress the listing from search until you fix it. Each section below clears one of those walls with the Selling Partner MCP (your data, plus the tools to act and publish), Atlas (the private Amazon image rule book), and the Amazon Agent Iris Skill (the seed, check, approve, publish loop).

Seeding from your own product photos turns a photographer-studio-designer-upload chain into one conversation

The benefit first: you get studio-quality images without a studio, and the time and cost of that whole chain collapse into a single run. The Amazon Agent Iris Skill on the Selling Partner MCP reads the listing and its existing images, then generates new images seeded from the seller's own product photos, so the real product identity, logos, and printed text stay intact rather than becoming generic stock. It fills factual details, like size-guide measurements, from the listing's own catalog data, so the specs are exact and not invented. The whole loop runs in one conversation with no manual Seller Central uploads.

Here is what it looked like. The water-bottle listing started with one image and ended with four candidates in a single run: a sharpened white-background main shot, a true lifestyle scene of the bottle in use, a precise size guide whose measurements came straight from the listing's own data, and a detail shot the validator bounced for falling under the zoom threshold. That gate is the point, and the surviving set still cleared the four-image target shape, which is not arbitrary. It follows the recommended set in Amazon's image guidance: one image of the product on a white background, one in an environment, and one with product information such as dimensions. The Skill seeded all of it from photos we already owned.

When cost-per-image and effort-per-listing crater, the math flips: every listing gets brought up to standard, not just the heroes

The benefit here is catalog-wide quality that was never economically possible before. Because the loop is a reusable Skill, the same seed, check, approve, publish run scales across the catalog. The long tail of thin and single-image listings was never worth a studio shoot, so it stayed underbuilt and under-converting. When the per-listing cost collapses, the recovered conversion from that long tail becomes reachable, and the recommended set (white-background main, an environment image, a product-information image, ideally six or more images per the Product Image Requirements for Amazon Listings guidance) is now within reach for a SKU doing twelve units a month, not just the flagship.

The standard each listing is brought up to is Amazon's, not a house style. I run it as a recurring Skill across the catalog, often kicked off when the audit-to-patch workflow flags an image laggard, so a thin gallery gets re-merchandised the same week it is found instead of next quarter.

Every generated image is graded against Amazon's image rules before it can publish, and a human approves the final set

This is the part that makes the speed safe: nothing publishes that breaks Amazon's rules or that you did not approve. The Skill checks each generated image against Amazon's image policy before anything publishes, a policy validator that returns a per-image verdict, grounded by Atlas against the Product Image Requirements for Amazon Listings, Suppressed Listings Management, and the per-category style guides such as the Fashion Category Style Guide (the listing_categories_style_guide set). That verdict set is the audit report the Skill produces:

{
  "asin": "B0EXAMPLE34",
  "sku": "BOTTLE-32OZ",
  "seeded_from": "existing main product photo + 1 detail photo",
  "starting_images": 1,
  "proposed_images": [
    {
      "slot": "main",
      "kind": "white-background product shot",
      "verdict": "pass",
      "checks": ["pure white background (255,255,255)", "product ~85% of frame", "no text/logos", ">1,000 px longest side"],
      "grounded_in": "Product Image Requirements for Amazon Listings"
    },
    {
      "slot": "secondary-1",
      "kind": "lifestyle / environment scene",
      "verdict": "pass",
      "checks": ["represents real product", "no added accessories not included"],
      "grounded_in": "Product Image Requirements for Amazon Listings"
    },
    {
      "slot": "secondary-2",
      "kind": "size guide (measurements from catalog data)",
      "verdict": "needs changes",
      "fix": "specs pulled from listing's own catalog data; confirm dimensions before approve",
      "grounded_in": "Product Image Requirements for Amazon Listings (product-information image)"
    },
    {
      "slot": "secondary-3",
      "kind": "detail / texture shot",
      "verdict": "reject",
      "fix": "longest side under 1,000 px; regenerate at higher resolution for zoom",
      "grounded_in": "Product Image Requirements for Amazon Listings (1,000 pixels)"
    }
  ],
  "suppression_risk_if_published_uncorrected": true,
  "awaiting": "human approval before publish"
}

Read the verdicts left to right. Pass means compliant and ready. Needs changes is a human judgment call, like confirming the size-guide dimensions the Skill pulled from the catalog. Reject plus fix is a hard rule failure with the exact remedy attached. The rules behind those verdicts are Amazon's, retrieved through Atlas, not paraphrased from training data. The main image must have a pure white background (RGB 255,255,255), the product must fill about 85 percent of the frame, and there can be no text, logos, or watermarks. Images over 1,000 pixels on the longest side enable the zoom Amazon prioritizes, with all images between 500 and 10,000 pixels. The image must accurately represent the product's real scale, quantity, and color. And the reason the check runs before publish rather than after: a non-compliant image will suppress the listing from search until compliant images are provided, the rule grounded in Suppressed Listings Management. Which rule applies to the main image depends on the category, so the validator grades a Fashion item against the Fashion Category Style Guide and a different product type against its own guide. The agent never makes the judgment call of whether an image truly represents the product; a human signs off, and only then does the Skill publish through the MCP and verify ingestion.

What happens next

Once the verdicts are clean and the human approves the set, the Skill publishes the approved images through the Selling Partner MCP and then confirms ingestion. It verifies the images actually went live rather than assuming success, the opposite of the manual path where images can take up to 24 hours and may never display. Anything that cannot clear forks off: an image marked reject goes back through the seed-and-check loop at higher resolution, and an underlying suppression that no image can fix is the audit-to-patch concern. I run the whole thing as a recurring Skill across the catalog so newly thin or newly suppressed listings get re-merchandised, with the same approval gate in front of every run. Run this way, the loop is one lane of the Amazon Agent Data layer: the same Amazon Agent Flow fabric that wires the Selling Partner MCP, the Amazon Ads MCP, and Atlas into automation your team approves rather than babysits. This is the image side of the audit-to-patch workflow, which forks an image-suppression finding straight into this loop.

The pattern is the same one that makes any of this safe: seed from your own truth, check before publish, approve before live. That is not model cleverness. It is the product surface doing its job.

Next in the series: bringing a suppressed FBA (Fulfillment by Amazon) listing back into search when the problem is not the image but the inventory state behind it.