inriver - OpenText Active Community - Trading Grid Integration and Automation

Common Integration Use Cases Between inriver and OpenText Active Community - Trading Grid

1. Publish approved product master data to trading partners

Flow: inriver – OpenText Active Community - Trading Grid

Use inriver as the system of record for product content and syndicate approved product data, attributes, descriptions, images, and compliance details to the Trading Grid community for suppliers, distributors, and resellers. This ensures partners receive a consistent and current product record for onboarding, ordering, and catalog updates.

Business value: Reduces manual rekeying, shortens partner onboarding cycles, and improves data consistency across the partner network.

2. Share enriched product content for partner-specific selling materials

Flow: inriver – OpenText Active Community - Trading Grid

Distribute localized product descriptions, marketing copy, technical specifications, and digital assets from inriver to partner collaboration spaces in Trading Grid so channel partners can access ready-to-use content for their own web stores, sales sheets, and campaigns.

Business value: Speeds partner go-to-market execution and reduces the need for partners to create their own product content from scratch.

3. Collect partner feedback on product data gaps and corrections

Flow: OpenText Active Community - Trading Grid – inriver

Enable trading partners to flag missing attributes, incorrect specifications, packaging changes, or compliance issues in Trading Grid, then route those requests back into inriver for review and enrichment by product, marketing, or master data teams.

Business value: Improves product data quality by capturing partner feedback close to the point of use and closing content gaps faster.

4. Coordinate new product introduction with external partners

Flow: Bi-directional

When a new product is launched in inriver, automatically create a collaboration thread or shared workspace in Trading Grid for affected partners to review launch assets, confirm readiness, and resolve open issues such as missing translations, regulatory documents, or packaging approvals. Status updates and issue resolutions can then be synchronized back to inriver.

Business value: Supports smoother product launches, reduces launch delays, and improves cross-functional coordination across internal teams and external partners.

5. Distribute compliance and regulatory documentation with product records

Flow: inriver – OpenText Active Community - Trading Grid

Attach safety data sheets, certificates, declarations of conformity, and market-specific regulatory documents managed in inriver to partner-facing community records in Trading Grid. Partners can access the correct documents for each market, product variant, or shipment requirement.

Business value: Lowers compliance risk, reduces document retrieval time, and helps partners meet market and customs requirements.

6. Manage product change notifications to the partner ecosystem

Flow: inriver – OpenText Active Community - Trading Grid

When product attributes change in inriver, such as dimensions, materials, packaging, or lifecycle status, automatically notify impacted partners through Trading Grid and provide the updated content package, effective date, and change summary.

Business value: Prevents outdated product information from being used in ordering or selling channels and improves partner responsiveness to changes.

7. Support exception handling for partner-specific catalog issues

Flow: OpenText Active Community - Trading Grid – inriver

If a partner identifies a catalog discrepancy, such as a missing variant, incorrect UOM, or market-specific pricing attribute, they can raise the issue in Trading Grid. The request is then routed to inriver for correction, approval, and republishing to all downstream channels.

Business value: Creates a controlled process for resolving catalog exceptions and reduces back-and-forth email traffic between internal teams and partners.

8. Enable collaborative localization and market readiness reviews

Flow: Bi-directional

Use inriver to manage localized product content and send draft market-ready content to Trading Grid for review by regional distributors or channel partners. Partners can comment on terminology, legal wording, and market fit, and approved changes can be fed back into inriver before publication.

Business value: Improves localization accuracy, accelerates regional launches, and ensures product content is aligned with local market expectations.