Marketplace Product Image Requirements: A PIM Control Playbook

In September 2026, product media is no longer a simple “upload the best photo” task for marketplace sellers. Amazon asks for a pure white main image with the product filling most of the frame, bol.com requires at least 500×500 pixels and strict image rules, Zalando publishes crop and model-guideline requirements, OTTO expects a cutout-style main image, and Kaufland now treats image alt text as part of product data. One SKU can pass on Shopify and still fail on Google Shopping, Meta Commerce, Amazon, bol.com, Zalando, OTTO or Kaufland because the wrong image slot was exported.

That is why marketplace product image requirements belong inside the PIM workflow, not in a shared drive, not in a one-off marketplace spreadsheet, and not in the memory of whoever launched the SKU last year. Multichannel sellers need a controlled media release process that sits next to attributes, descriptions, translations and feed rules. ChannelDock’s PIM feeds and PIM feature overview give teams the structure to publish product content without turning every marketplace exception into manual cleanup.

Why image compliance is now a PIM problem

The ranking pages for PIM, DAM and syndication usually explain the same broad idea: centralize product content, map fields, publish to every channel. That advice is useful, but it misses the operational failure that sellers actually feel. Image issues do not only happen because an asset is missing. They happen because the correct asset is present but attached to the wrong variant, exported as the wrong marketplace slot, blocked by a crawler rule, rejected for a promotional overlay, overwritten by a marketplace catalog contribution or cached for days after the team believes it has been fixed.

Seller forums show the pattern clearly. Shopify merchants ask why only one image reaches Meta. Amazon sellers report images that appear to update and then revert to old variation photos. Google Merchant Center flags promotional overlays, placeholders, blocked URLs and invalid image links. These are not “creative production” issues. They are control-plane issues.

The channel rules sellers should model explicitly

A practical PIM does not store “image 1, image 2, image 3” and hope the feed manager knows what to do. It stores channel intent. Amazon’s MAIN image is not the same object as a Shopify product gallery image, a Zalando front crop, a Google Shopping image_link, a Meta catalog image, a Kaufland picture.url or a bol.com labeled asset. Each destination applies different rules to background, aspect ratio, file size, minimum dimensions, product fill, text overlays, lifestyle styling and variation matching.

• Amazon: the main image needs to represent the exact product, use a pure white background for most categories, avoid text and promotional claims, and often requires 1,000+ pixels on the longest side for zoom.
• bol.com: sellers must meet image-size and content rules, and product feed implementations commonly carry image URLs together with title, description and other attributes.
• Zalando: fashion-oriented image rules make crop, model, packshot and aspect-ratio choices operationally important, not only aesthetic.
• OTTO: marketplace guides call for a main image link with specific resolution, clean cutout style, RGB JPG/PNG files and a product that fills most of the image area.
• Kaufland: product data guidelines recommend 5-10 images, white-background first photos, no promotional elements, high-resolution zoom assets and alt text as product-data fields.
• Google and Meta: crawler access, promotional overlays, placeholder images and wrong Shopify image selection can cause disapprovals or partial catalog sync.

A five-step release workflow for marketplace images

The best sellers treat product media like code: there is a source of truth, a validation step, a staged release, monitoring and rollback. The goal is not to make marketers slower. The goal is to prevent one beautiful but non-compliant image from suppressing a high-revenue SKU across multiple channels.

1. 1
   Name a single master image set per SKU

   Store one approved packshot, ordered gallery, language-neutral image, localized media variant, and fallback image against the PIM record.
2. 2
   Map channel slots, not just image URLs

   Treat Amazon MAIN, bol.com main image, Zalando front crop, OTTO main image link, Kaufland picture.url and Google image_link as separate slots with rules.
3. 3
   Validate dimensions and policy before export

   Block files that miss minimum pixels, use promotional overlays, contain text in the main image, or point to URLs crawlers cannot fetch.
4. 4
   Stage the release by SKU risk

   Publish high-revenue SKUs and variation families in smaller batches first, then compare accepted image URLs against the PIM version.
5. 5
   Keep an overwrite log

   Record the image hash, feed timestamp, marketplace response and live PDP screenshot so support can prove whether a marketplace or another seller changed the asset.

What competitors rarely cover

Competitor PIM articles from Akeneo, Plytix, Salsify, Pimcore and Inriver correctly emphasize syndication, DAM integration and centralised product content. What they rarely spell out is the live-marketplace loop after the feed leaves the PIM. A product record can be “complete” in the PIM and still fail commercially if the live PDP shows an old Amazon catalog image, if Meta chooses only the first Shopify image, if Google cannot crawl the URL, or if Kaufland rejects a main image with text embedded in the photo.

This is the gap multichannel sellers should close: PIM should not stop at export. It should own the evidence trail. Which media file was approved? Which hash was sent? Which marketplace accepted it? Which image URL is live now? Which user changed the order of the gallery? Which previous version can be restored before a peak-sale campaign? That level of traceability is what turns “we uploaded the image” into “we can prove the correct image is live.”

For marketplace sellers, the highest-value image workflow is not faster uploading. It is controlled publishing: the right image, in the right slot, at the right resolution, with proof that the marketplace accepted it.

How to prioritize SKUs when every listing needs media cleanup

Do not start by polishing the full catalog. Start with risk. Export a list of SKUs where image problems can immediately cost revenue: top sellers, paid-shopping products, items with high return rates, variation families, marketplace-exclusive bundles, seasonal products, and any SKU where the main image contains text, badges, flags, discounts, old packaging or lifestyle context. Then add products where image URLs are hosted on fragile systems, blocked by robots rules, or manually edited inside marketplaces.

ChannelDock’s integrations help sellers connect product data with operational systems, but the discipline still matters: image cleanup should be linked to launch windows, stock availability, feed validation, and marketplace acceptance. If a SKU is out of stock or paused, cleanup can wait. If a SKU has paid traffic and stable stock, a wrong main image becomes a conversion and compliance problem today.

FAQ

Conclusion

Marketplace product image requirements are becoming more specific, more automated and more closely tied to product-data compliance. A multichannel seller that keeps images in folders and feed columns will keep fighting the same rejection pattern: wrong URL, wrong crop, wrong variant, wrong background, wrong live image. A seller that models media inside PIM can approve once, map per channel, validate before export, monitor the live result and roll back quickly when a marketplace behaves unexpectedly.

The practical next step is simple: pick your 50 highest-revenue SKUs and build a media control sheet from your PIM. For each SKU, record the approved main image, gallery order, channel-specific exceptions, validation status and live marketplace proof. Once that workflow is stable, automate it through your PIM feed process and use ChannelDock to keep product content, marketplace feeds and operational execution connected.