Current Limitation: When a user uploads a replacement image with the same file name or identifier, Optimizely creates a new, separate asset rather than replacing the existing one. While version control exists for individual assets, there is no bulk version-replacement workflow.
Use Case: In industries like retail, manufacturing, and consumer goods, suppliers regularly update product packaging while keeping the same SKU and naming convention. When these updated images need to be loaded into the DAM, the platform creates duplicate assets instead of recognizing them as replacements. Users are then forced to manually identify and delete the old versions — a process that is not feasible when hundreds or thousands of product images change at once. A bulk replacement capability that matches incoming files to existing assets based on a configurable key (e.g., file name, SKU, or custom field) would eliminate this problem entirely.
Requested Enhancement: Introduce a bulk image replacement feature that matches incoming files to existing assets based on a configurable key and replaces the asset in place — preserving metadata, integration history, and folder placement while updating the image file and triggering any associated workflows.
Expected Impact: Eliminates duplicate asset proliferation, preserves metadata and integration continuity, dramatically reduces manual cleanup effort, and enables scalable support for supplier-driven image refreshes across large catalogues.