Threekit - OpenText Content Metadata Service - Dictionary Integration and Automation

Common Integration Use Cases Between Threekit and OpenText Content Metadata Service - Dictionary

1. Standardized product metadata for 3D configuration assets

Data flow: OpenText Content Metadata Service - Dictionary to Threekit

Use OpenText as the master source for product metadata definitions such as product family, material, finish, dimensions, region, and compliance attributes, then synchronize those controlled fields into Threekit. This ensures every configurable product in Threekit uses the same approved taxonomy and data types across teams and channels.

• Reduces inconsistent naming and duplicate attribute creation
• Improves search, filtering, and configuration accuracy in the visual commerce experience
• Supports governance for enterprise product catalogs across multiple business units

2. Metadata-driven asset classification for generated product visuals

Data flow: Threekit to OpenText Content Metadata Service - Dictionary

When Threekit generates product images, lifestyle renders, or AR-ready assets, it can pass asset metadata such as SKU, variant, colorway, campaign, and usage rights into OpenText governed metadata structures. This allows downstream content teams to classify and retrieve visual assets consistently across DAM and ECM repositories.

• Speeds up asset search and reuse by marketing and ecommerce teams
• Improves governance for versioning, rights management, and product lifecycle tracking
• Supports automated publishing workflows into DAM and content portals

3. Controlled vocabulary for configurable product options

Data flow: OpenText Content Metadata Service - Dictionary to Threekit

OpenText can define approved values for configurable options such as upholstery types, frame finishes, hardware packages, or accessory bundles, and Threekit can consume those controlled vocabularies to power the product configurator. This prevents free-text variation and ensures customers only see valid combinations.

• Reduces configuration errors and invalid product combinations
• Improves order accuracy and lowers returns for custom products
• Helps product, merchandising, and operations teams maintain a single source of truth

4. Governance of localized product metadata across regions

Data flow: Bi-directional

For global brands, OpenText can manage standardized metadata definitions while Threekit stores region-specific visual and configuration data such as language, market availability, and local compliance attributes. Updates to regional product metadata can flow back to OpenText for governance and reporting.

• Supports multi-country ecommerce rollouts with consistent metadata standards
• Enables regional teams to localize content without breaking enterprise governance
• Improves compliance and market-specific product publishing

5. Metadata synchronization for campaign-ready visual content

Data flow: Threekit to OpenText Content Metadata Service - Dictionary

Marketing teams often need product visuals tied to campaign metadata such as launch date, promotion name, channel, audience segment, and seasonal collection. Threekit can generate the visuals while OpenText governs the metadata schema used to tag and organize those assets for campaign execution.

• Accelerates campaign asset preparation and approval
• Makes it easier to find the right visuals for web, email, social, and print
• Improves consistency between product marketing and content operations

6. Metadata governance for product lifecycle changes

Data flow: OpenText Content Metadata Service - Dictionary to Threekit

When a product changes status, such as prototype, active, discontinued, or end of life, OpenText can publish the governed lifecycle metadata to Threekit. Threekit can then update which configurations, visuals, or AR experiences are exposed to customers or internal sales teams.

• Prevents outdated products from being shown in customer-facing experiences
• Supports cleaner product retirement and replacement processes
• Aligns merchandising, operations, and content governance teams

7. Enterprise reporting across product content and visual commerce

Data flow: Bi-directional

OpenText can provide the metadata framework for reporting dimensions such as product category, content owner, approval status, and publication channel, while Threekit contributes usage data for configured products, asset generation, and visual engagement. Together, they enable reporting on which product content is being used, where, and by whom.

• Improves visibility into content performance and operational bottlenecks
• Supports governance reporting for audit and compliance teams
• Helps identify high-value product assets and underused content

8. Automated onboarding of new product lines into visual commerce

Data flow: OpenText Content Metadata Service - Dictionary to Threekit

When a new product line is launched, OpenText can provide the approved metadata model for categories, attributes, and controlled terms, which Threekit uses to structure the new 3D product experience. This shortens onboarding time for new catalogs and ensures the visual commerce setup follows enterprise standards from day one.

• Reduces manual setup effort for product and content teams
• Speeds time to market for new collections and launches
• Ensures new product experiences are compliant with enterprise metadata governance