Step 1: Confirm it is an image suppression, not something else
A product can vanish from search for a dozen reasons, and only some of them are images. Pricing errors, a missing required attribute, a restricted-category flag, an inventory sync that zeroed stock, or an account-level health issue can all look identical from the outside: the product page exists, but nobody finds it. Fixing the images on a listing that was actually suppressed for a missing brand field wastes an afternoon and changes nothing.
Every major channel separates "this item is hidden" from "this is why", and the reason is what you are after. Here is where each one usually reports it. Menu labels move between dashboard versions, so treat these as the place to start looking rather than an exact path.
| Channel | Where the flag usually shows | How a fix is rechecked |
|---|---|---|
| Amazon | Inventory view, filtered to Search suppressed; the listing quality / fix-your-products view gives the reason | Automated recheck after a new MAIN image is uploaded |
| Walmart Marketplace | The Unpublished Items dashboard in Seller Center, or an item report | Automated, once the item is updated and re-ingested |
| Google Merchant Center | Products › Diagnostics, item-level issues on image_link | Recrawl of the image URL; a new URL is picked up fastest |
| eBay | Seller Hub or a policy email about the item | Revise the listing; contact support if the block stays |
| Etsy | A notice in your shop or a policy email | Often manual: respond to the notice once fixed |
If the reason names an attribute, a price, or a restricted product, stop here: this is not an image recovery. If it names the image, or a check the image fails (background, size, overlay, missing main image), carry on.
Step 2: Read the reason code before touching a single file
The reason text is more specific than most sellers give it credit for, and it tells you three things you need before you edit anything:
- Which image failed. On Amazon and Walmart the main image carries the strictest rules and causes most suppressions. A secondary image breaking a rule usually gets that image dropped or flagged rather than the whole listing hidden. Know which slot you are fixing.
- Which check it failed. "Image too small", "promotional overlay", "non-white background" and "missing main image" each have a completely different fix. Re-uploading a bigger version of an image that was flagged for a watermark changes nothing.
- Whether it is one listing or a pattern. Filter the suppressed view by reason. If forty products share the same flag, you have a template or workflow problem, and fixing listings one at a time is the slow way to solve it.
The instinct when a listing is flagged is to strip its images and start again. Do not. On some channels a listing with no main image is suppressed for that reason alone, and on Shopify-fed catalogs a deleted original cannot be restored. Our Shopify rollback guide covers what happens when the source file is gone. Fix forward instead: correct the image, then replace.
Write the reason down, with the product ID and the image slot, before you change anything. If the first fix does not clear the flag, that note is what you will need for a support case.
Step 3: Fix the one cause, at the source
Recovery work goes wrong in two ways. Sellers fix too little, by cropping the thumbnail in the marketplace's own editor and leaving the master file wrong, or too much, by booking a full reshoot for a background that was 247 grey instead of 255 white. The right fix is narrow and lands on the master file that feeds every channel.
The common image reason codes map to fixes like this:
| Reason the channel gives | What is actually wrong | Narrow fix |
|---|---|---|
| Background not white | Off-white, a grey gradient, or a shadow that reads as background | Replace the background with exact 255,255,255; keep a soft contact shadow |
| Image too small / low quality | Below the minimum, or upscaled from a thumbnail | Export from the original capture, not from a downloaded copy |
| Promotional overlay / text | Badge, price, watermark or logo added on top | Re-export the image without the overlay layer |
| Product fills too little | Too much empty margin around the product | Reframe so the product fills the frame; no reshoot needed |
| Image does not match product | Wrong colour variant, a bundle shown, or props in frame | Needs the correct photo; editing will not fix it |
The first four are pixel problems on a photo that is otherwise right. They can be fixed in minutes without a new shoot. In Retouchable, the Studio replaces the background with an exact plate colour and frames the product in the same pass, working from the original photo rather than the marketplace's compressed copy. The last row is different. If the image shows the wrong thing, no editing makes it compliant, and the honest fix is the right photo.
Step 4: Resubmit so the channel actually rechecks
A corrected file only helps once the channel sees it. This step catches more sellers than the fix itself, because each platform decides differently when to look again.
Amazon. Upload the corrected image into the MAIN slot from the listing's edit page, or through a flat file or feed if that is how the catalog is managed. Change only the field the reason named. Editing five attributes at once to "refresh" a listing makes it harder to tell what cleared the flag, and can trigger new checks on fields that were fine. Seller forum threads are full of re-uploads that did not clear a suppression. If the status has not changed after a reasonable wait, reopen the reason. A second, different cause is often hiding behind the first.
Walmart. Fix the item from the Unpublished Items dashboard or by updating the item through your feed so it is re-ingested. Walmart's own guidance warns against enlarging a small image to pass the minimum: upscaled images look worse, and Walmart can reject them on quality.
Google Merchant Center. Point image_link at a new URL for the corrected image. Google caches by URL, and re-uploading a fixed file to the same address can leave the old pixels in place until the next crawl. Google's documentation is explicit that resubmitting the original image gets the product disapproved again. For promotional overlays, Merchant Center also offers an opt-in automatic image improvement that tries to remove the overlay. It does not always succeed, and the result needs checking in Diagnostics.
On every channel, giving the corrected image a new filename or URL removes any doubt about whether a cache is still serving the old file. It also leaves a clean audit trail of which version was live when.
Step 5: Confirm recovery in search, not just in the status column
A status that flips from suppressed to active means the flag has cleared. It does not prove shoppers can find the product again. Check that recovery has actually happened:
- Search for it as a shopper would. Use a logged-out or private browser window and search the main keyword plus brand. Seeing the product page is not enough. It needs to appear in results.
- Check the thumbnail in results. Make sure the corrected image is the one showing in search and on the product page, not a cached copy of the old one.
- Watch sessions and impressions for a few days. Traffic coming back at the old level confirms recovery. A listing that is "active" but still near zero impressions usually has a second issue, or lost ranking while it was hidden and needs time or ad support to rebuild.
- Close the loop on ads. Sponsored ads for a suppressed product often stop serving or waste spend. Check that campaigns pointing at the product are delivering again.
In most incidents the fix itself is the shortest part. Most of the lost time is the gap before anyone notices, which is why Step 7 matters more than any single fix.
Step 6: Clean up every channel that copied the bad image
A non-compliant image rarely lives in one place. If it came from your master catalog, whether Shopify, a PIM or a shared drive, it has probably been synced to every channel that reads from it. A suppression on Amazon is often the first warning of the same file failing quietly elsewhere: a Google Shopping disapproval nobody has opened, a Walmart item stuck unpublished, a Meta catalog serving the watermarked version in ads.
Work outward from the source:
- Fix the master first. If the corrected image only goes to the marketplace that complained, the next catalog sync can push the bad file straight back and re-suppress the listing.
- List every channel the product syncs to. Check each one's diagnostics for the same product ID, even where nothing has been flagged yet.
- Force a resync where the channel allows it, rather than waiting for the scheduled one.
- Watch the next scheduled sync. Confirm it carries the corrected image and does not quietly restore the old one.
For Shopify-based catalogs, the corrected image should become the product's featured image (position 1), because that is what most feeds and sales channels read as the main image. Retouchable's Shopify integration pushes a finished image back to a product with its filename, alt text and position, so the fix lands on the source that the channels copy from. For the full playbook on undoing a bad image update across synced channels, see rolling back a bad product image update on Shopify. For how the requirements differ channel by channel, see e-commerce image requirements across marketplaces.
Step 7: Make the next suppression smaller
Image suppressions will happen again: rules tighten, a new team member exports from the wrong preset, a supplier sends images with a logo in the corner. The goal is not zero incidents but small ones, caught in hours rather than days and fixed once rather than forty times.
Reactive
- Suppression noticed when sales drop
- Each listing fixed by hand in each channel
- Fix applied to the marketplace copy only
- Same file re-synced and re-suppressed
- No record of what was fixed or why
Gated
- Suppressed and at-risk views checked on a schedule
- Pattern fixed once at the template or source
- Fix applied to the master file, then synced
- New filenames make every version traceable
- Reason, fix and date logged per incident
Three habits do most of the work:
- A pre-upload gate. Every main image is checked before it leaves your hands: exact white background, minimum size, no overlays, product filling the frame. The checklist in why marketplaces reject product images takes under a minute per image by hand, and can be automated.
- A weekly look at the warning views. Amazon's inventory filters include an at-risk view alongside the suppressed one, and Google's Diagnostics shows warnings before they become disapprovals. Ten minutes a week there is cheaper than a lost weekend of sales.
- One master file per product image. When every channel copies from one corrected source, the next fix is made once. When each channel keeps its own hand-edited copy, every fix is made five times and one is always missed.
An incident log, just a spreadsheet of product, channel, reason, fix and date, turns a series of emergencies into a pattern you can act on. After a quarter it usually shows that most suppressions trace back to two or three sources: one supplier, one export preset, one template with a badge baked in.