Threekit - OpenText InfoArchive Integration and Automation

Common Integration Use Cases Between Threekit and OpenText InfoArchive

1. Archive Product Configuration Records for Audit and Warranty Support

Data flow: Threekit to OpenText InfoArchive

When customers configure a complex product in Threekit, the final configuration, selected options, pricing snapshot, and associated visual render can be archived in OpenText InfoArchive as a permanent transaction record. This is valuable for manufacturers and retailers that need to prove exactly what was sold, especially for custom furniture, industrial equipment, automotive accessories, or electronics bundles.

Business value: Supports warranty claims, dispute resolution, and regulatory audit requirements while reducing reliance on live commerce systems for historical lookup.

• Store final configuration ID, SKU mapping, pricing, timestamp, and customer order reference
• Retain a visual proof of the configured product at point of sale
• Enable customer service and legal teams to retrieve archived records without accessing production systems

2. Preserve Legacy Product Visualization Assets During Platform Decommissioning

Data flow: Threekit to OpenText InfoArchive

Organizations retiring older product visualization or CPQ systems can migrate historical 3D assets, configuration rules, rendered images, and related metadata into OpenText InfoArchive for long-term retention. Threekit can remain the active visualization platform for current products while InfoArchive holds legacy content for compliance, reference, and customer support.

Business value: Reduces the cost and risk of maintaining obsolete systems while preserving access to historical product data and visuals.

• Archive legacy 3D models, render outputs, and configuration rule sets
• Maintain searchable access for support, engineering, and compliance teams
• Support phased decommissioning without losing historical product evidence

3. Retain Customer-Approved Visual Proof for Custom Orders

Data flow: Threekit to OpenText InfoArchive

For made-to-order or highly configurable products, Threekit can generate a final approved visual representation that is archived alongside the order record in OpenText InfoArchive. This creates a durable record of what the customer approved before production begins.

Business value: Lowers the risk of production errors, change-order disputes, and return claims caused by mismatched expectations.

• Archive the approved render, configuration summary, and customer acceptance timestamp
• Link archived records to ERP or order management identifiers
• Provide production, quality, and customer service teams with a single source of truth

4. Archive Regulatory and Compliance Evidence for Configurable Products

Data flow: Threekit to OpenText InfoArchive

In regulated industries, certain product configurations may require evidence that approved materials, dimensions, safety features, or labeling options were selected. Threekit can pass the final configuration data and visual proof to OpenText InfoArchive to support compliance retention policies.

Business value: Helps organizations demonstrate adherence to product, labeling, and safety requirements over long retention periods.

• Capture configuration attributes tied to regulated options
• Archive supporting images and customer-facing disclosures
• Enable compliance teams to retrieve records during audits or investigations

5. Store Historical Product Image Variants for Reference and Legal Defense

Data flow: Threekit to OpenText InfoArchive

Threekit can generate unlimited product images from 3D models, including seasonal, regional, or option-specific variants. Rather than keeping all variants in active content systems, organizations can archive older or discontinued image sets in OpenText InfoArchive for long-term reference.

Business value: Reduces storage and content management overhead while preserving evidence of how products were represented at a given time.

• Archive discontinued product visuals and marketing-approved renders
• Retain metadata such as product version, campaign, and publication date
• Support legal, brand, and merchandising teams with historical lookups

6. Support Customer Service Access to Historical Configurations After Product Retirement

Data flow: OpenText InfoArchive to Threekit, or InfoArchive as the retrieval layer for Threekit records

When a product is no longer sold in Threekit, customer service teams may still need to view the exact configuration a customer purchased years earlier. Archived records in OpenText InfoArchive can be surfaced through service portals or linked back to Threekit-style visual references for easy review.

Business value: Improves service response times and reduces errors when handling replacement parts, warranty claims, or upgrade requests.

• Retrieve archived configuration details by order number or customer account
• Display historical product visuals to service agents
• Reduce dependency on legacy commerce or visualization environments

7. Governance and Retention for Digital Asset Lifecycle Management

Data flow: Threekit to OpenText InfoArchive

Threekit can generate large volumes of visual assets, including renders, thumbnails, and AR-related files. OpenText InfoArchive can be used to retain only the records that must be preserved for policy, legal, or operational reasons, while disposition rules remove expired content according to retention schedules.

Business value: Improves content governance, lowers storage costs, and ensures retention policies are applied consistently across business units.

• Archive only approved or business-critical visual assets
• Apply retention and disposition rules by product line or region
• Provide legal and records management teams with controlled access to archived content