Product photography has always been the expensive, slow part of product data – one shoot per variant, one agency loop per marketplace format. In 2026, it has become a pipeline: a master image goes in, channel-ready variants come out. What works reliably, where humans still need to review, and which obligations the AI Act adds – a practical assessment.
The image pipeline in stages
| Stage | What runs automatically | Reliability |
|---|---|---|
| Cutouts / background removal | Remove backgrounds, reconstruct shadows | high – the standard case for automation |
| Marketplace compliance | Formats, background colors, margins per channel (Amazon, Google, social) | high – rules can be checked deterministically |
| Variant generation | Color variants, detail crops, campaign crops | medium – spot-check review |
| Scene generation | Place the product in generated environments | review required – product fidelity is the hard limit |
| Editing via text prompt | Describe adjustments directly in the PIM instead of a graphics roundtrip | new – deploy with an approval workflow |
The hard limit: product fidelity
Anything that alters the product itself is no longer image editing but deception: generated details the product does not have, retouched-away properties, changed proportions. The pipeline therefore needs a clear rule boundary – surroundings, format, and staging can be automated; the depiction of the product itself is untouchable. That is a governance decision, not a technical one, and it should be documented before the first run goes live.
AI Act: labeling becomes a mandatory part of the pipeline
The EU AI Act introduces transparency obligations for AI-generated content – and product images are not exempt: substantially generated or manipulated depictions must be recognizable as such. For the image pipeline, this means concretely: every image variant carries provenance metadata (master photo, automated editing, generated portions), and delivery decides on a rule basis where labeling is required. Whoever anchors this in the pipeline instead of debating it image by image has turned the obligation into a capability – auditability included.
Image metadata is product data
The underestimated part: an image without metadata is invisible to search, feeds, and agents. Generating alt texts from attributes, capturing channel assignments and image types (cutout, application, detail) in structured form, documenting provenance – all of this belongs in the PIM or DAM, linked to the product. The image set then becomes a data asset that AI search and the Merchant Center feed can use as well.
Image pipelines are one building block of our enrichment tracks – context and pricing on our PIM services page.
