Product data
Catalogue auto-enriched from PLM and commerce
Internal tools showed product rows with no product images, because the images lived in PLM and getting them out was a manual download. We built a pipeline.
- Function
- Product data
- Primary source
- PLM
- Fallback
- Live retail sources
- Throughput
- ~600 SKUs / 15 min
The problem
Every internal screen that listed products listed them as text. The images existed — they were in PLM — but pulling one meant opening PLM, finding the style, downloading the asset and putting it somewhere the tool could reach. At catalogue scale nobody did this, so nobody did it at all.
PLM coverage was also incomplete. Some styles had no usable asset attached, so even a full export would have left gaps.
What we built
A pipeline that treats PLM as the primary source and live retail listings as the fallback. It walks the catalogue, takes the PLM asset where one exists, and where one doesn't it resolves the product against public retail sources and takes the image from there.
Results are served through the internal tools directly, so a screen that used to render a row of text now renders the product.
How it landed
The pipeline processes roughly 600 SKUs in fifteen minutes, which makes a full catalogue refresh a scheduled job rather than a project. The fallback path matters more than the throughput: it is what takes coverage from "most styles" to "effectively all of them".
Anonymised by agreement. We'll walk you through the specifics — the system, the numbers, the parts that went wrong — on a call under NDA.