Centric - OpenText Core Digital Asset Management Integration and Automation

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

Centric and OpenText Core Digital Asset Management complement each other well in product development and content operations. Centric manages product lifecycle data, specifications, and collaboration across design and merchandising teams, while OpenText Core Digital Asset Management centralizes approved digital assets such as images, videos, packaging artwork, and brand content. Integrating the two platforms helps teams keep product records and creative assets aligned from concept through launch and ongoing commercialization.

1. Link approved product imagery from OpenText Core Digital Asset Management to Centric product records

Data flow: OpenText Core Digital Asset Management to Centric

When marketing, studio, or photography teams approve final product images in OpenText Core Digital Asset Management, those assets can be automatically linked to the corresponding product style, SKU, or collection in Centric. This gives product development, merchandising, and eCommerce teams immediate access to approved visuals directly within the product lifecycle workflow.

Business value: Reduces manual file searching, prevents use of outdated images, and shortens the time needed to prepare product lines for launch.

2. Push product launch assets from Centric to OpenText Core Digital Asset Management for centralized brand distribution

Data flow: Centric to OpenText Core Digital Asset Management

As products move toward launch in Centric, key product data such as style numbers, season, colorways, and launch status can trigger the creation or update of asset folders in OpenText Core Digital Asset Management. Packaging files, campaign visuals, and sell-in materials can then be stored and organized against the product hierarchy for downstream use by sales, retail, and regional teams.

Business value: Creates a single, governed repository for launch content and ensures teams use the latest approved materials across channels.

3. Synchronize asset metadata with product attributes for better search and governance

Data flow: Bi-directional

Product attributes from Centric, such as brand, category, season, gender, and market, can be synchronized with asset metadata in OpenText Core Digital Asset Management. In return, asset identifiers, usage rights, and approval status can be written back to Centric. This keeps both systems aligned and improves searchability, compliance, and traceability.

Business value: Improves asset discovery, supports rights management, and reduces the risk of using non-compliant content.

4. Route approved packaging and label artwork from OpenText Core Digital Asset Management into Centric for product development review

Data flow: OpenText Core Digital Asset Management to Centric

Packaging artwork, care labels, hangtags, and regulatory visuals approved in OpenText Core Digital Asset Management can be attached to the relevant product development records in Centric. Design, compliance, and sourcing teams can review the artwork in context with product specifications and BOMs before final release.

Business value: Reduces packaging errors, supports faster compliance review, and improves coordination between creative and product teams.

5. Trigger asset requests in OpenText Core Digital Asset Management from Centric milestone events

Data flow: Centric to OpenText Core Digital Asset Management

When a product reaches a defined milestone in Centric, such as sample approval or line freeze, an integration can automatically create an asset request in OpenText Core Digital Asset Management for photography, retouching, or campaign production. The request can include product details, deadlines, and required formats.

Business value: Aligns creative production with product development timelines and reduces launch delays caused by late asset requests.

6. Publish final approved assets from OpenText Core Digital Asset Management to support omnichannel product content

Data flow: OpenText Core Digital Asset Management to Centric

Once assets are approved in OpenText Core Digital Asset Management, the integration can update Centric with links or references to the final files for use by merchandising, eCommerce, and wholesale teams. This ensures product teams can quickly access the correct content for line sheets, digital catalogs, and sales presentations.

Business value: Speeds content readiness for market launch and reduces duplicate asset handling across departments.

7. Maintain version control and approval status across product and asset workflows

Data flow: Bi-directional

When a new version of a product image, packaging file, or campaign asset is approved in OpenText Core Digital Asset Management, Centric can be updated with the latest version number and approval status. Likewise, if a product specification changes in Centric, the integration can flag related assets in OpenText Core Digital Asset Management for review or rework.

Business value: Prevents teams from working with outdated materials and supports controlled change management across the product lifecycle.

8. Support seasonal collection launches with synchronized product and asset readiness

Data flow: Bi-directional

For seasonal launches, Centric can provide the master product calendar, assortment structure, and launch dates, while OpenText Core Digital Asset Management can provide the corresponding approved imagery and marketing assets. The integration can be used to monitor readiness by collection, flag missing assets, and ensure all required content is available before launch gates are passed.

Business value: Improves launch coordination, reduces missed deadlines, and gives leadership better visibility into product and content readiness.