OpenText DAM (OTMM) - BigCommerce Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and BigCommerce

1. Publish approved product images and videos from OpenText DAM (OTMM) to BigCommerce product pages

Marketing or product teams manage master product photography, lifestyle images, and demo videos in OpenText DAM (OTMM), then push approved assets to the corresponding BigCommerce product records. This ensures every SKU in the storefront uses the latest brand-approved media without manual file handling.

• Data flow: OpenText DAM (OTMM) to BigCommerce
• Business value: Faster product launches, consistent storefront presentation, reduced risk of outdated or unapproved media
• Typical workflow: Asset approved in DAM, mapped to SKU or product ID, then synced to BigCommerce image and video fields

2. Automatically update seasonal campaign assets across BigCommerce storefronts

Campaign teams can store banners, hero images, promotional videos, and landing page visuals in OpenText DAM (OTMM) and distribute them to BigCommerce storefronts for seasonal promotions, flash sales, or brand campaigns. When a campaign asset is replaced or updated in DAM, the storefront can be refreshed automatically.

• Data flow: OpenText DAM (OTMM) to BigCommerce
• Business value: Faster campaign execution, fewer manual content updates, improved brand consistency across channels
• Typical workflow: Campaign asset tagged by region, brand, or promotion type in DAM, then published to the relevant BigCommerce store or page

3. Sync product media variants for channel-specific commerce experiences

Retailers often need different image sets for different markets, customer segments, or storefront themes. OpenText DAM (OTMM) can manage multiple renditions such as high-resolution, web-optimized, square, or localized assets, and BigCommerce can receive the correct version based on channel rules or storefront requirements.

• Data flow: Bi-directional, with master asset control in OpenText DAM (OTMM) and channel assignment in BigCommerce
• Business value: Better customer experience, optimized page performance, localized merchandising
• Typical workflow: DAM stores renditions and metadata, BigCommerce references the appropriate asset version by storefront, locale, or device profile

4. Enrich BigCommerce product listings with metadata from OpenText DAM (OTMM)

OpenText DAM (OTMM) can provide structured metadata such as image captions, usage rights, product angles, campaign tags, and expiration dates. This metadata can be synchronized to BigCommerce to support richer product content, better internal governance, and more accurate asset usage.

• Data flow: OpenText DAM (OTMM) to BigCommerce
• Business value: Improved content governance, better search and merchandising support, reduced compliance risk
• Typical workflow: Asset metadata in DAM is mapped to custom fields or product content attributes in BigCommerce

5. Return product and campaign performance insights to OpenText DAM (OTMM) for asset optimization

BigCommerce can provide sales and conversion data that helps marketing and merchandising teams understand which product images, banners, or videos are driving engagement. Those insights can be used in OpenText DAM (OTMM) to prioritize high-performing assets, retire underperforming content, and guide future creative production.

• Data flow: BigCommerce to OpenText DAM (OTMM)
• Business value: Data-driven creative decisions, improved asset reuse, stronger conversion performance
• Typical workflow: Storefront performance metrics are associated with asset IDs or campaign tags and fed back into DAM reporting or asset governance processes

6. Manage asset approvals and publishing workflows for new product launches

For new product introductions, product teams can upload images and videos into OpenText DAM (OTMM), route them through approval workflows, and only publish approved assets to BigCommerce once product data is ready. This creates a controlled launch process across merchandising, marketing, and eCommerce teams.

• Data flow: Bi-directional, with approval status in OpenText DAM (OTMM) and product readiness in BigCommerce
• Business value: Coordinated launches, fewer content errors, reduced rework between teams
• Typical workflow: Product record is created in BigCommerce, assets are approved in DAM, then media is attached when both content and commerce data are complete

7. Support omnichannel asset distribution for marketplace and regional storefronts

Enterprises selling through multiple BigCommerce storefronts or regional commerce experiences can use OpenText DAM (OTMM) as the central source for product and marketing assets. The DAM can distribute approved media to each storefront based on region, language, brand, or channel-specific requirements.

• Data flow: OpenText DAM (OTMM) to BigCommerce
• Business value: Centralized asset control, faster expansion into new markets, reduced duplication of media management
• Typical workflow: Assets are tagged by market or channel in DAM, then pushed to the correct BigCommerce storefront or catalog segment

8. Maintain rights-managed and time-sensitive media compliance across commerce channels

OpenText DAM (OTMM) can track usage rights, expiration dates, and approved distribution rules for product and campaign media. BigCommerce can consume only compliant assets, helping prevent expired, restricted, or region-limited content from appearing in the storefront.

• Data flow: OpenText DAM (OTMM) to BigCommerce
• Business value: Reduced legal and compliance risk, automated asset lifecycle control, fewer manual audits
• Typical workflow: DAM flags asset expiration or usage restrictions, and integration removes or replaces the asset in BigCommerce when rules change