Automating product and listing images for e-commerce
Your catalogue already knows the price, the name and the photo. The only missing step between the feed and the finished image is a render.
·6 min read
Every e-commerce catalogue is a factory for image work. A sale touches five hundred SKUs and each one needs a price-drop visual. A marketplace demands its own card layout. A new collection launches and the social team wants a promo tile per product. Multiply layouts by SKUs by markets and you get numbers no design team survives.
The structural fix is to stop treating product images as files and start treating them as views of the feed — rendered from a template, refreshed when the data changes.
The feed is the source of truth — keep it that way
The moment a price lives inside a PSD, it is wrong waiting to happen. Somebody updates the catalogue, nobody re-exports the artwork, and the ad shows last week’s number. Rendering from the feed makes the image a projection of the data: if the catalogue says 39 €, the artwork says 39 €, because that is where the artwork got it.
Photos come from URLs, layouts stay locked
Product photos rarely live beside the design tool — they live on a CDN. A template accepts the photo as a URL field, fetches it at render time, and places it inside a fixed crop with your treatment applied. The photography changes per SKU; the composition never drifts.
One SKU, many destinations
- Listing card for the storefront — WebP, sized for the grid.
- Marketplace export — the exact pixel spec the channel demands, per channel template.
- Price-drop promo for social — same data, bolder layout, rendered in the campaign batch.
- Localised variants — a language parameter renders the same SKU for each market.
- Print shelf tag — the PDF format from the same template family.
Nightly runs beat heroic sprints
The teams that make this stick automate the cadence, not just the render: a scheduled job diffs the feed, batches the changed SKUs, and lets the cache serve everything that did not move. A sale that touches five hundred products becomes a five-minute batch run, and the design team’s involvement ended weeks ago — when they designed the template.