inriver - OpenText Core Digital Asset Management Integration and Automation

Common Integration Use Cases Between inriver and OpenText Core Digital Asset Management

inriver and OpenText Core Digital Asset Management complement each other well in enterprise product content operations. inriver serves as the system of record for product information, while OpenText Core Digital Asset Management manages approved images, videos, documents, and other rich media. Integrating the two platforms helps teams centralize product content, improve asset governance, and publish consistent, channel-ready product experiences faster.

1. Link approved digital assets to product records in inriver

Data flow: OpenText Core Digital Asset Management to inriver

Marketing and creative teams store approved product images, lifestyle photography, spec sheets, and videos in OpenText Core Digital Asset Management. The integration automatically pushes asset references, metadata, and renditions into inriver and links them to the correct product, variant, or family record. Product managers and merchandisers can then assemble complete product content without searching across separate repositories.

Business value: Reduces manual asset hunting, ensures only approved media is used, and speeds up product enrichment for launch readiness.

2. Synchronize product metadata to improve asset tagging and search

Data flow: inriver to OpenText Core Digital Asset Management

When product attributes such as SKU, brand, category, color, size, market, or launch status are updated in inriver, the integration sends that metadata to OpenText Core Digital Asset Management. Assets are automatically tagged with the latest product context, making them easier to find, govern, and reuse across campaigns and channels.

Business value: Improves asset discoverability, reduces duplicate uploads, and keeps media metadata aligned with current product data.

3. Automate enrichment of new product launches with approved media

Data flow: Bi-directional

As new products are created in inriver, the system can trigger a search in OpenText Core Digital Asset Management for matching approved assets based on product code, model number, or category. If assets are found, they are attached to the product record. If not, a task can be created for the creative team to produce or approve the required media. Once assets are added to OpenText Core Digital Asset Management, they are automatically linked back to the product record.

Business value: Shortens time to market and creates a controlled workflow between product teams and creative teams.

4. Support global localization of product content and media

Data flow: Bi-directional

For global organizations, inriver manages localized product descriptions, market-specific attributes, and translated copy, while OpenText Core Digital Asset Management stores region-specific assets such as localized packaging images, compliance documents, and translated brochures. The integration ensures each market receives the correct combination of product data and approved media based on language, region, or channel rules.

Business value: Reduces localization errors, supports regional compliance, and improves consistency across international channels.

5. Publish complete product content to e-commerce and partner channels

Data flow: inriver to OpenText Core Digital Asset Management, then to downstream channels

inriver assembles the structured product information, while OpenText Core Digital Asset Management provides the associated images, videos, and documents. Together, they feed e-commerce platforms, distributor portals, and marketplace listings with complete product packages. Channel teams can publish richer product pages with fewer missing assets and fewer manual handoffs.

Business value: Improves conversion rates, reduces product page gaps, and lowers operational effort in channel publishing.

6. Enforce asset approval before product publication

Data flow: OpenText Core Digital Asset Management to inriver

Only assets that have passed legal, brand, or compliance approval in OpenText Core Digital Asset Management are made available in inriver for product publication. If an asset is still under review or expired, it is blocked from being attached to publishable product records. This creates a controlled release process for regulated industries such as manufacturing, healthcare, and consumer goods.

Business value: Prevents unapproved content from reaching customers and reduces compliance risk.

7. Maintain a single source of truth for product storytelling and rich media

Data flow: Bi-directional

Product marketing teams use inriver to manage product narratives, feature claims, and structured attributes, while OpenText Core Digital Asset Management manages the supporting media that brings those stories to life. The integration keeps product copy and assets aligned so that updates to claims, packaging, or visuals are reflected across both systems. This is especially useful when product positioning changes or packaging is refreshed.

Business value: Improves content consistency, reduces rework, and ensures product storytelling stays aligned with approved media.

8. Streamline asset lifecycle management for product retirements and replacements

Data flow: inriver to OpenText Core Digital Asset Management

When a product is discontinued or replaced in inriver, the integration can flag related assets in OpenText Core Digital Asset Management for review, archival, or reuse. Teams can identify which images, manuals, or videos are tied to obsolete products and decide whether they should be retired or reassigned to successor products.

Business value: Improves content governance, reduces clutter in asset libraries, and supports cleaner product transitions.