Case Study: Why a Jewelry Brand’s Marketplace Images Were Rejected — and the Fix

A jewelry brand selling rings, necklaces, earrings, and bracelets across their own WooCommerce store, Amazon, and eMag had 180 product listings suppressed on the two marketplace channels over a 3-month period. Suppressed listings do not appear in search results and generate zero sales. For a brand where marketplaces accounted for 44% of total revenue, the suppression affected a meaningful share of their catalog. The cause was product image handling — specifically, the systematic failure of their images to meet the technical requirements of each marketplace.

The Challenge

Marketplace image rejections are not always communicated clearly or immediately. Amazon’s listing quality alerts appear in Seller Central with a delay that can range from 24 hours to several weeks after a listing goes live. eMag’s compliance notifications arrive via a batch report that the team had not been monitoring consistently. The brand discovered the full extent of their suppressed listings only when a quarterly revenue reconciliation showed marketplace revenue running 31% below forecast for the prior 90 days. Investigating the variance led to the discovery of 180 suppressed listings.

An audit of the rejected listings identified five distinct categories of image non-compliance:

1. Non-white backgrounds. Amazon’s main image policy requires a pure white background (RGB 255,255,255). The brand had been using off-white or light gray studio backgrounds. eMag has the same requirement. Of the 180 suppressed listings, 94 failed on this criterion. The images looked white to the human eye but failed automated background detection because the actual background was #F5F5F5 or #EEEEEE rather than true white.

2. Images below minimum resolution. Amazon requires main images to be at least 1000 pixels on the longest side to enable zoom functionality. eMag requires a minimum of 800 pixels. The brand’s supplier-provided images — used for approximately 40% of the catalog — were consistently 600x600 pixels. A total of 67 listings were rejected on resolution grounds, with overlap with the background issue accounting for some products appearing in both categories.

3. Watermarks on main images. The brand had been using watermarked photographer credit images for some products during a transition period when they were working through a photography backlog. Amazon prohibits text, logos, and watermarks on main images. Watermarked images were the issue for 28 listings.

4. Lifestyle photographs as main images. Both Amazon and eMag require that the main listing image be a product-only photograph against a plain background, not a lifestyle or contextual shot. The brand’s marketing team had been uploading lifestyle images — bracelets worn on a wrist, earrings styled with an outfit — as the primary image for 19 products, which failed compliance for both channels.

5. Aspect ratio and centering violations. Images where the product occupied less than 85% of the image frame were flagged by eMag’s compliance system. For some products, the photographer had left excessive negative space in the frame — an aesthetic choice that was incompatible with eMag’s framing requirements.

The 180 suppressed listings represented the most serious cases. An additional audit of active (non-suppressed) listings found another 200 products where images technically met the minimum requirements but were at risk of future suppression as platform standards tightened — primarily borderline resolution cases and products using borderline background colors.

What They Tried First

The immediate response was to manually correct the most severe cases — the 94 background compliance failures. A freelance photo editor was contracted to re-edit backgrounds to pure white on the affected product images. This work took 11 days and cost approximately €800 in editing fees. The corrected images were re-uploaded to both marketplaces.

The manual approach revealed a process problem: the re-edited images were uploaded directly to the marketplace listing tools, not to the brand’s central image library in WooCommerce. This meant the corrected versions existed on Amazon and eMag but not in the central catalog. Future synchronization jobs that pushed product data from WooCommerce to the marketplaces would overwrite the corrected marketplace images with the non-compliant originals.

This happened to 31 of the 94 corrected products within two weeks of the manual fixes. Those 31 listings were re-suppressed when the next catalog sync job ran and pushed the uncorrected WooCommerce images back to the marketplaces.

The team also reached out to the freelance photographer who had produced the lifestyle images and the supplier representatives for the low-resolution images. The photographer provided reshoots for 12 of the 19 lifestyle image products over 3 weeks. Supplier re-photography requests were sent to the 4 suppliers whose images were consistently below resolution requirements; one supplier responded within 2 weeks, the other three did not respond within the 6-week follow-up window.

After 6 weeks of manual remediation, 67 of the 180 suppressed listings had been reinstated. The remaining 113 were still suppressed, and the process for fixing them had no clear completion timeline.

The Solution

The team implemented MicroPIM’s product image handling pipeline to address both the immediate remediation and the systemic process problem that had allowed non-compliant images to reach marketplace channels in the first place.

Step 1: Centralize All Product Images in MicroPIM

The first step was establishing MicroPIM as the single authoritative source for all product images. All existing product images — from WooCommerce, from the marketplace listings, from the photographer’s delivery folder — were consolidated into MicroPIM’s asset library, organized by product SKU.

This consolidation took approximately 2 days, including deduplication and matching images to their correct product records. For products where multiple versions existed (original, re-edited, photographer credit, supplier-provided), the library review identified which version was the correct current source.

[SCREENSHOT: MicroPIM asset library showing product images for a ring SKU — four versions in the library: original supplier photo (600px, gray background), re-edited version (600px, white background), photographer’s studio shot (2400px, white background), and lifestyle image tagged as secondary-only]

Step 2: Define Image Specifications per Channel

MicroPIM’s image channel configuration allows per-channel image specifications to be set as rules that apply during export and sync operations. The team configured specifications for three channels:

WooCommerce (own store):

• Minimum resolution: 1200x1200px
• Background: white or lifestyle (both permitted)
• Maximum file size: 2MB
• Format: JPEG, WebP

Amazon:

• Minimum resolution: 1000x1000px (2000x2000px recommended, set as target)
• Background: pure white only (RGB 255,255,255), enforced by background color validation
• No text, watermarks, or logos on main image
• Main image must be product-only (not lifestyle)
• Aspect ratio: square or 4:3 landscape only

eMag:

• Minimum resolution: 800x800px
• Background: pure white
• Product must occupy minimum 85% of frame
• No watermarks
• First image must be product-only

The configuration took approximately 3 hours and became the enforcement mechanism for all future product image handling.

Step 3: Run Compliance Validation on the Full Image Library

With channel specifications configured, the team ran MicroPIM’s image compliance validation scan across all 1,200 product SKUs and their associated images. The scan checks each image against the specifications for each configured channel and produces a compliance report grouped by product and by failure type.

The scan completed in 47 minutes and returned a compliance report showing:

• 322 products with at least one image failing Amazon main image requirements
• 287 products with at least one image failing eMag requirements
• 141 products compliant on all three channels

The 322 Amazon and 287 eMag non-compliant products were grouped by failure type, which made remediation prioritization straightforward. The largest failure group — background color — had 198 products, all correctable through automated background processing.

[SCREENSHOT: MicroPIM image compliance validation report showing a table of 322 products with Amazon main image failures, sorted by failure type — background color (198), resolution below 1000px (76), lifestyle image as main (31), watermark detected (17)]

Step 4: Automated Background Processing and Resolution Upscaling

For the 198 products with background color failures, MicroPIM’s bulk image processing applied automated background replacement to pure white. For the 76 products with resolution below the 1000px Amazon minimum (supplier-provided images that could not be re-sourced quickly), AI upscaling was applied to reach the minimum resolution threshold. The upscaled images were not at the quality level of native high-resolution photography, but they met the minimum resolution requirement for listing reinstatement while replacement photography was arranged.

Background replacement and resolution upscaling for 274 products ran as a batch job that completed in approximately 2 hours. The processed images were stored in MicroPIM as the canonical images for those products — not as marketplace-specific variants — so that all future channel syncs would use the compliant versions.

For the 31 products with lifestyle images as their main Amazon and eMag image, the secondary product-only images (which existed in the library for all 31 products, just not in the main image position) were promoted to the main image slot for those channels in MicroPIM’s per-channel image ordering configuration.

For the 17 watermarked products, the non-watermarked versions were sourced from the photographer’s original delivery files (which existed for all 17 — the watermarked versions had been uploaded by mistake during a handoff) and replaced in the library.

Step 5: Establish Channel-Gated Sync Rules

The final step was configuring MicroPIM’s sync rules to ensure that future product image handling enforced compliance before images could reach marketplace channels. Images that fail the configured channel specification are blocked from syncing to that channel and flagged for resolution. They can be overridden manually with an explicit approval step, but they cannot pass through an automated sync job in a non-compliant state.

This addressed the root cause of the re-suppression incident: the next catalog sync to Amazon and eMag would be working from the compliant images in MicroPIM, not from WooCommerce’s uncorrected library.

[SCREENSHOT: MicroPIM channel sync configuration showing the Amazon channel with image compliance enforcement enabled, a blocked sync count of 0 (all images now compliant), and the last successful sync timestamp]

The Results

Listing reinstatement: All 180 suppressed listings were reinstated within 18 days of beginning the MicroPIM implementation — 12 days for the batch processing and re-upload, 6 days for marketplace review and listing activation.

Revenue recovery: In the 30 days following reinstatement of all 180 listings, marketplace revenue increased 38% compared to the suppression-affected prior 30-day period. Over the following quarter, marketplace revenue returned to expected levels and outperformed the prior year quarter by 12%.

Ongoing compliance rate: In the 9 months following the image pipeline standardization, zero additional listings were suppressed on either Amazon or eMag due to image non-compliance. The pre-launch compliance scan had caught and flagged issues for 3 new product batches before those products reached the marketplace channels.

Time savings on new product image preparation: Before MicroPIM, preparing images for a batch of 30 new products for marketplace channels took approximately 8 hours — manual background checking, resolution verification, and individual upload to each channel. After MicroPIM, the same 30-product batch preparation takes approximately 1.5 hours, including the automated compliance scan and any corrections required.

Supplier image quality: The compliance scan data was shared with suppliers whose images consistently failed resolution requirements. Two suppliers updated their standard photography specifications based on this feedback. Supplier-provided images from those two suppliers have met resolution requirements for all products delivered in the months since.

Key Takeaways

• Marketplace image suppression is often a delayed and indirect notification. Monitoring listing quality health proactively, rather than waiting for revenue variances to surface problems, is the only way to catch suppressions before they have a significant business impact.
• The most common image compliance failure — near-white backgrounds that fail automated detection — is not visible to the human eye. Systematic validation against exact RGB specifications is necessary; visual inspection is not sufficient.
• Centralizing product images in a single managed library is a prerequisite for consistent channel compliance. Images corrected in a marketplace tool but not in the central source will be overwritten by the next sync.
• Per-channel image specifications enforced at the sync layer prevent non-compliant images from reaching channels. Compliance enforcement at the output stage is more reliable than compliance enforcement as a manual review step.
• Supplier-provided images frequently fail marketplace requirements, particularly for resolution. Building compliance validation into the supplier onboarding workflow identifies these issues before the products enter the active catalog.

If your marketplace channels have suppressed listings, or if your product image handling relies on manual checking before each upload, the compliance gaps in your current workflow are costing you sales. MicroPIM’s image compliance validation and per-channel specification enforcement can be configured for your channels in a single session. Set up your account at app.micropim.net/register.

Related Reading

• CDN for Product Images
• Case Study: Skincare Brand 20,000 Product Images
• Multi-Channel Ecommerce Strategy

Frequently Asked Questions

How does MicroPIM’s background color validation work — can it detect near-white backgrounds that look white to the eye?

Yes. The validation checks the actual RGB values of background pixels in the image against the specification (pure white = RGB 255,255,255 for Amazon’s requirement). An image with a #F5F5F5 or #EEEEEE background will fail this check even though it appears white visually. The validator samples background pixels from the four corners and edges of the image where background is most likely to be present. It returns the detected background color values alongside the pass/fail result, so you can see exactly what background color the image has before deciding whether to apply automated background replacement.

Does automated background replacement produce images good enough for marketplace listing use?

For most jewelry product photography — where the product is photographed against a clean studio background — automated background replacement to pure white produces results that are visually indistinguishable from re-photographed products. The quality is high enough for compliant marketplace listings. The cases where quality is visibly compromised are complex shots with reflections, transparent materials like glass, or products where the original background color is similar to the product color (for example, a white gold ring against a near-white background). For jewelry specifically, the gold, silver, and gemstone tones typically contrast well with white backgrounds, making automated replacement reliable. Visual review of the processed images before publishing is recommended for any product category with complex transparency or reflection characteristics.

What is the process for managing the primary vs. secondary image distinction across channels when the same product needs different main images for different channels?

MicroPIM supports per-channel image ordering — you can configure which image is in the main (first) position for each channel independently. A product can have a lifestyle image as its main image on the WooCommerce store (where lifestyle shots are permitted and perform better for the brand’s audience) and a pure white background product-only image as the main image for Amazon and eMag. Both are stored in MicroPIM’s asset library; the channel configuration determines which appears first on each channel. The ordering configuration is set once per product and applies to all subsequent sync jobs.

How does the compliance validation handle products where no compliant image exists yet — new products being onboarded before photography is complete?

Products with no compliant main image for a channel are blocked from publishing to that channel by the sync enforcement rules. They appear in MicroPIM’s publishing queue with a status indicating they are pending image compliance, and they cannot pass to the channel until a compliant image is assigned. This is preferable to allowing listings to go live with placeholder or non-compliant images, which typically results in immediate suppression. For pre-launch catalog builds, the compliance validation serves as a pre-flight check that shows which products are image-ready for each channel and which still need photography or processing before they can go live.