Project visuals
Interface screenshots, reconstructed deliverable extracts and workflow illustrations are labelled. All visuals use fictional content and metadata, with client branding removed. Select an image to view it full size.
The engagement
A specialist retail chain's product visuals and documents (datasheets, manuals, service procedures) sat on one side in the DAM and on the other in PIM exports, with no automatic link between them. Assets carried none of the product repository metadata, and nothing guaranteed the DAM would stay aligned: not for new media, not for updated media, not for delisted products.
We built a standalone connector that reconciles both repositories, enriches Frontify metadata from the PIM and logs every decision. The technical stance was restraint: few files, only two external dependencies, no infrastructure to maintain. A dry-run mode replays a full cycle without writing anything, and each run produces a log the business teams can open in a spreadsheet.
The connector shipped with its technical specification and traceability setup. Teams now have reproducible enrichment instead of manual rework, and readable monitoring without needing server log access.
Takeaway
A takeaway for your project
We made asset enrichment repeatable and its decisions accessible to business teams through a spreadsheet-readable log.
Technologies
- Frontify
- PIM
- Python
- API REST
This engagement is one of the integrations documented on our dedicated page. We present delivered work, feasibility studies and scoping engagements, with the checks to make before development.
What to settle before committing to an integrationYour next step
Do your assets keep pace with the product catalogue?
Describe your PIM, DAM and the metadata that needs to stay aligned. We help scope matching, updates and the handling of delisted products.
Discuss your project