Threekit - OpenText Content Metadata Service Integration and Automation

Common Integration Use Cases Between Threekit and OpenText Content Metadata Service

1. Standardized product metadata for 3D configuration experiences

Data flow: OpenText Content Metadata Service ? Threekit

Use OpenText Content Metadata Service as the system of record for product metadata such as category, material, finish, dimensions, compliance attributes, and localization fields. Threekit consumes these standardized metadata models to drive product configuration logic, filter options, and visual presentation rules. This ensures that every configurable product in Threekit follows the same enterprise metadata structure used across content and commerce systems.

Business value: Reduces inconsistent product data, speeds up onboarding of new configurable products, and improves search and navigation across the digital commerce experience.

2. Metadata-driven asset classification for 3D and AR content

Data flow: Threekit ? OpenText Content Metadata Service

Threekit generates product images, 3D views, and AR assets for multiple configurations. These assets can be pushed into OpenText Content Metadata Service with standardized metadata such as SKU, variant, region, campaign, usage rights, and product family. Content teams can then classify, search, and reuse visual assets more efficiently across web, sales, and partner channels.

Business value: Improves asset governance, reduces duplicate content creation, and makes it easier for marketing and sales teams to find the right approved visual for each product variant.

3. Automated metadata enrichment for configurable product catalogs

Data flow: Bi-directional

OpenText Content Metadata Service can provide authoritative metadata fields to Threekit, while Threekit can return configuration-specific attributes such as selected options, visual variant IDs, and asset references. This supports automated enrichment of product records when new options are added or when product content changes. For example, a furniture manufacturer can update finish, fabric, and size metadata centrally and have those updates reflected in the Threekit configurator without manual rework.

Business value: Lowers maintenance effort, shortens product launch cycles, and keeps visual configuration aligned with approved content data.

4. Compliance and regulatory metadata control for configurable products

Data flow: OpenText Content Metadata Service ? Threekit

For industries such as furniture, electronics, and automotive, certain product options may require compliance, safety, or regional availability rules. OpenText Content Metadata Service can store standardized compliance metadata such as restricted materials, certification status, market eligibility, and warranty conditions. Threekit uses this metadata to hide invalid options, prevent unsupported configurations, and display only approved combinations to customers.

Business value: Reduces configuration errors, supports regulatory compliance, and prevents customers from ordering invalid product combinations that create downstream fulfillment issues.

5. Localization and market-specific product presentation

Data flow: OpenText Content Metadata Service ? Threekit

OpenText Content Metadata Service can manage localized metadata for language, region, currency, and market-specific product naming. Threekit uses this metadata to present the correct product visuals, labels, and configuration options for each market. This is especially useful for global brands that sell the same configurable product with different regional specifications or naming conventions.

Business value: Improves international customer experience, supports regional product governance, and reduces the risk of showing incorrect options in local markets.

6. Content approval workflow for visual product launches

Data flow: Threekit ? OpenText Content Metadata Service

When Threekit generates new product visuals or configuration views, the resulting assets can be registered in OpenText Content Metadata Service with approval status, owner, campaign association, and publication dates. Content operations teams can then use metadata-driven workflows to review, approve, and release visuals for e-commerce, dealer portals, and sales enablement channels.

Business value: Creates a controlled launch process, improves governance over customer-facing content, and helps teams coordinate product releases across departments.

7. Searchable product experience library for sales and channel teams

Data flow: Threekit ? OpenText Content Metadata Service

Threekit can publish rendered product views, configuration snapshots, and AR assets into OpenText Content Metadata Service with rich metadata tags such as product line, customer segment, use case, and campaign. Sales, channel, and partner teams can then search and reuse approved visuals for proposals, presentations, and digital campaigns without requesting custom assets from design teams.

Business value: Increases reuse of approved content, reduces turnaround time for sales materials, and improves consistency across customer-facing channels.

8. Master metadata governance for scalable visual commerce operations

Data flow: Bi-directional

OpenText Content Metadata Service can act as the enterprise metadata governance layer, while Threekit serves as the visual commerce execution layer. Metadata definitions for product families, option sets, asset types, and lifecycle states are maintained centrally in OpenText and consumed by Threekit. In return, Threekit can send usage and configuration metadata back to support analytics, content optimization, and lifecycle management.

Business value: Establishes a scalable operating model for visual commerce, improves data consistency across systems, and supports better cross-functional collaboration between product, content, and digital commerce teams.