OpenText DAM (OTMM) - Salesforce Commerce Cloud (SFCC) Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and Salesforce Commerce Cloud (SFCC)

1. Product image and video syndication from OpenText DAM to SFCC product detail pages

OpenText DAM serves as the system of record for approved product photography, lifestyle images, and product videos, while SFCC consumes those assets to enrich product detail pages, category pages, and search results. This integration ensures that merchandising teams always publish the latest approved media without manually downloading and re-uploading files. Business value includes faster product launches, consistent brand presentation across channels, and reduced risk of outdated or unapproved assets appearing in the storefront.

• Direction: OpenText DAM to SFCC
• Typical data: asset renditions, thumbnails, alt text, captions, usage rights, product SKU or style code mappings
• Workflow benefit: marketing approves assets once in DAM, commerce teams automatically receive them in SFCC

2. Automated localization of commerce assets for regional storefronts

Global retailers often need different images, banners, and videos for different markets due to language, cultural preferences, or regional promotions. OpenText DAM can manage localized asset variants and distribute the correct version to SFCC based on site, locale, or country. SFCC then displays the appropriate content for each storefront without requiring separate manual asset management by regional teams. This improves localization speed, supports regional merchandising strategies, and reduces the chance of publishing the wrong creative in a market.

• Direction: OpenText DAM to SFCC
• Typical data: localized image sets, translated banners, region-specific campaign videos, locale metadata
• Workflow benefit: centralized creative governance with localized storefront execution

3. Campaign asset publishing from OpenText DAM to SFCC promotional landing pages

Marketing teams frequently create seasonal campaigns, product launches, and promotional events that require coordinated banners, hero images, and short-form videos. OpenText DAM can store the approved campaign package and push the relevant assets to SFCC landing pages, homepage slots, and promotional modules. This allows commerce teams to launch campaigns faster and ensures that all digital touchpoints use the same approved creative. The result is better campaign consistency, fewer manual errors, and improved time to market.

• Direction: OpenText DAM to SFCC
• Typical data: campaign hero images, promotional banners, teaser videos, campaign expiration dates, usage rules
• Workflow benefit: marketing controls creative approval while commerce controls placement and scheduling

4. Asset metadata synchronization for product and content governance

OpenText DAM can send key metadata to SFCC so commerce teams can filter and use only approved assets tied to specific products, categories, or campaigns. Metadata such as product ID, season, brand, rights expiration, and channel restrictions helps SFCC determine which assets are eligible for display. This reduces compliance risk and improves operational efficiency by making asset selection rules explicit and machine-readable. It is especially valuable for organizations managing large catalogs or strict usage rights.

• Direction: OpenText DAM to SFCC
• Typical data: asset metadata, rights management fields, product associations, expiration dates, channel eligibility
• Workflow benefit: automated governance and reduced manual asset validation

5. Commerce-driven asset requests from SFCC back to OpenText DAM

When merchants identify missing or underperforming product content in SFCC, they can trigger an asset request back to OpenText DAM for new photography, alternate angles, or updated lifestyle imagery. This creates a closed-loop workflow between commerce and creative teams, helping prioritize content production based on actual storefront needs. It is particularly useful for high-volume retailers where product assortment changes frequently and content gaps can directly affect conversion rates.

• Direction: SFCC to OpenText DAM
• Typical data: product SKU, missing asset type, priority, storefront context, campaign deadline
• Workflow benefit: faster resolution of content gaps and better alignment between merchandising and creative operations

6. Rights-managed asset expiration and removal from storefronts

OpenText DAM often contains usage rights and expiration dates for licensed photography, celebrity imagery, or third-party video content. By integrating these rules with SFCC, assets can be automatically removed or replaced when rights expire, preventing legal and compliance issues on live storefronts. This is critical for brands that use licensed content across multiple markets and channels. The integration reduces manual monitoring and helps maintain continuous compliance.

• Direction: OpenText DAM to SFCC
• Typical data: rights expiration date, license scope, approved usage channels, replacement asset references
• Workflow benefit: automated compliance enforcement and reduced legal exposure

7. Omnichannel content reuse for store, web, social, and marketplace experiences

OpenText DAM can distribute a single approved asset set to SFCC and other commerce touchpoints, ensuring that product imagery and campaign content remain consistent across web, mobile, social commerce, and store-assisted selling. SFCC uses these assets to support unified shopping experiences while maintaining channel-specific renditions and performance-optimized formats. This integration helps organizations maximize content reuse, reduce duplicate asset production, and maintain a consistent brand story across channels.

• Direction: OpenText DAM to SFCC
• Typical data: master assets, channel-specific renditions, format variants, crop rules, performance-optimized files
• Workflow benefit: one asset source for multiple commerce channels

8. Product launch workflow linking PIM, OpenText DAM, and SFCC

For new product introductions, OpenText DAM can be part of a broader launch workflow where product data is prepared in PIM, assets are approved in DAM, and SFCC publishes the complete product experience. Once the product record is ready, SFCC receives the product details and the associated images and videos from OpenText DAM to create a launch-ready storefront experience. This coordinated flow shortens launch cycles, improves content completeness, and helps ensure that products go live with the right merchandising assets from day one.

• Direction: OpenText DAM to SFCC, with orchestration from PIM or workflow tools
• Typical data: product identifiers, approved images, videos, launch dates, merchandising content
• Workflow benefit: synchronized product and asset readiness for faster launches