Marketplace images are a compliance problem before they are a design one
A single beautiful product photo is a photography outcome. A hundred listings across Shopify, Amazon, and a handful of marketplaces is an operations outcome - and operations means each channel's specific rules about size, background, and file weight, not just what looks good. Get the rules wrong and a listing can be suppressed, rejected, or simply outperformed by a competitor whose images load faster and zoom cleaner.
What Shopify actually expects
Shopify is comparatively flexible on background style, but themes still perform best with consistent aspect ratios across a product's image set and files light enough that a product page does not lag on mobile. Inconsistent crops between a product's first and second image create a jarring flicker as shoppers click through the gallery - a small detail that quietly hurts conversion.
Amazon's stricter rulebook
Amazon enforces harder requirements: primary images generally need a pure white background, a minimum pixel dimension for zoom to function, and no promotional text or watermarks overlaid on the main image. Secondary images have more freedom for lifestyle context, but the primary slot is where most new sellers get listings flagged.
Backgrounds: white, lifestyle, or both
Most channels want a clean white or neutral background for the primary image and allow lifestyle or in-context shots for supporting images. Rather than reshooting for every background style, isolate the subject once and place it against whichever backdrop the channel expects.
- Remove Background for a clean cutout of the product
- Place the cutout on pure white for marketplace primaries
- Reuse the same cutout in lifestyle or campaign templates for secondary images and ads
Resolution for zoom, without shipping bloated files
Marketplaces that offer pinch-to-zoom need a real minimum resolution to make that feature useful - but a giant, uncompressed source file also slows the page down before a shopper ever zooms. Resize to the channel's minimum plus a reasonable margin, then compress so the file stays fast without losing the detail zoom depends on.
One preset per channel, not one export for everywhere
The recurring mistake is producing a single "web export" and hoping it satisfies every channel at once. It rarely does - Amazon's requirements are stricter than Shopify's, and a size that passes one platform's automated checks can be rejected by another's. Building a named preset per channel - dimensions, background rule, compression level - turns a judgment call into a repeatable step your whole team can follow.
Keeping a growing catalog in sync
New SKUs arrive faster than any manual process can keep up with once a catalog passes a few hundred products. Bulk Image Processing applies cutout, resize, and compression rules across a batch instead of one product at a time, and the broader Picnie for Ecommerce workflow ties those steps together for teams shipping listings on a schedule rather than in one-off bursts.
Get the per-channel rules right once, encode them as presets, and marketplace image prep stops being a bottleneck between a finished product and a live listing.
Secondary images carry more of the conversion story than sellers assume
The primary image gets the compliance attention, but secondary images - lifestyle shots, size charts, close-up detail crops, in-use photography - are usually where a shopper's actual buying decision happens. A rushed primary and a thoughtful secondary set will outperform the reverse almost every time. Budget real attention to at least one lifestyle or context shot per listing, isolated and re-templated from the same base product cutout rather than reshot from scratch for each variant.
Handling color and size variants without reshooting each one
Catalogs with multiple color or size variants of the same base product do not need a full reshoot per variant. Once a clean cutout exists for one version, recoloring or swapping in a variant-specific detail shot inside the same template produces a consistent set far faster than treating each variant as an independent photography job. This is where a repeatable pipeline - cutout once, template many times - pays off most as SKU counts climb into the hundreds.
Checking listings after a marketplace policy update
Marketplace image rules do not stay fixed forever - minimum resolutions rise, background requirements tighten, and new fields like size charts or 360-degree views get introduced as optional and then eventually expected. Revisit your presets whenever a marketplace announces a policy change rather than waiting for a listing to get flagged, since a preset update applied once catches every future upload automatically, while a reactive fix only patches the one listing someone happened to notice.
Picnie at Picnie. Writes about image automation, developer experience, and shipping product faster.