DAM ⇄ inRiver PIM synchronization middleware
A DAM change broke the chain feeding the PIM. Containerized middleware, zero regression at cutover, across two decoupled instances.
The engagement
An international industrial supplier's DAM was migrating from a legacy platform to Bynder. That cutover broke the chain automatically feeding assets and metadata into the inRiver PIM, across two entirely decoupled instances. The success criterion was set upfront: zero regression at cutover: same collection scope, same asset-to-entity links, same rendering, no metadata loss.
We designed and delivered containerized middleware: collection, filtering, fan-out to both instances, a composite-key mapping store, delta polling and safeguards against synchronization loops. Mapping administration runs through a web interface, backed by a spreadsheet ⇄ JSON tooling chain so business teams stay in control without touching code.
It ships with a read-only diagnostic CLI and a documented cutover scenario. The client retains ownership of its mapping and has a single control point between DAM and PIM.