Brandfolder - OpenText Product Traceability Integration and Automation

Common Integration Use Cases Between Brandfolder and OpenText Product Traceability

Brandfolder and OpenText Product Traceability complement each other well in organizations that need both controlled brand asset distribution and end-to-end product documentation governance. Brandfolder manages approved creative, packaging, and marketing assets, while OpenText Product Traceability supports product-related records, compliance evidence, and traceability across the product lifecycle. Integrating the two helps teams keep product-facing content accurate, current, and aligned with regulated or version-controlled product information.

1. Approved product imagery and packaging assets linked to traceability records

Direction: Brandfolder - OpenText Product Traceability

When new product images, labels, packaging artwork, or instruction sheets are approved in Brandfolder, the integration can automatically attach the final asset links or asset metadata to the corresponding product traceability record in OpenText. This gives quality, regulatory, and operations teams a single reference point for the exact approved visual materials associated with a product version or batch.

• Reduces manual file handling and version confusion
• Supports audit readiness by tying approved assets to product records
• Ensures downstream teams use the correct packaging and labeling content

2. Traceability status updates trigger asset version control in Brandfolder

Direction: OpenText Product Traceability - Brandfolder

When a product record changes status in OpenText, such as a formulation update, packaging revision, or compliance hold, Brandfolder can be notified to flag related assets for review, archive outdated files, or create a new version set for the updated product line. This keeps marketing and product teams from using obsolete assets after a product change.

• Prevents use of outdated packaging or product claims
• Creates a controlled review process for impacted assets
• Improves alignment between product changes and brand content updates

3. Compliance and regulatory evidence packages assembled from Brandfolder assets

Direction: Bi-directional

OpenText Product Traceability can request approved supporting assets from Brandfolder, such as labels, certificates, product photos, or instruction inserts, and store references in the traceability record. In return, Brandfolder can receive metadata about which assets are required for a specific product, market, or regulatory scenario. This supports faster preparation of compliance evidence packages for audits, recalls, or market submissions.

• Speeds up audit and submission preparation
• Improves consistency of documentation across markets
• Helps teams prove which approved assets were used for each product release

4. Product launch content synchronized with traceability milestones

Direction: OpenText Product Traceability - Brandfolder

As products move through traceability milestones such as design freeze, pilot release, or production approval, OpenText can trigger Brandfolder workflows to release launch-ready assets to marketing, sales, and channel teams. This ensures campaign materials, sell sheets, and product visuals are only distributed when the product is officially ready.

• Aligns launch timing with operational readiness
• Prevents premature distribution of product content
• Improves coordination between product, operations, and marketing teams

5. Centralized product asset metadata for faster search and retrieval

Direction: Brandfolder - OpenText Product Traceability

Brandfolder can push asset metadata such as product SKU, revision number, region, language, and approval status into OpenText Product Traceability. This allows traceability users to search and filter product records by associated assets, making it easier to locate the correct documentation for a specific product configuration or market variant.

• Improves discoverability of product-related content
• Supports multi-region and multi-language product management
• Reduces time spent searching across disconnected systems

6. Recall and corrective action support with controlled asset distribution

Direction: OpenText Product Traceability - Brandfolder

If a product issue, recall, or corrective action is logged in OpenText, the system can notify Brandfolder to identify and restrict affected assets, such as product sheets, packaging files, or customer-facing instructions. Brandfolder can then ensure only the corrected assets remain available for internal and external use, helping teams respond quickly and consistently.

• Supports faster recall response and containment
• Reduces the risk of distributing incorrect product information
• Helps maintain a clear record of approved versus retired content

7. New product introduction workflows with controlled asset handoff

Direction: Bi-directional

During new product introduction, OpenText Product Traceability can manage the product record lifecycle while Brandfolder stores the approved creative and packaging assets. The integration can pass product identifiers, launch dates, and market details from OpenText to Brandfolder, while Brandfolder returns approved asset links and version details back to the traceability record. This creates a controlled handoff between product operations and brand execution.

• Improves launch governance across teams
• Ensures product records and asset libraries stay synchronized
• Reduces delays caused by manual coordination and file sharing