inriver - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between inriver and OpenText Core Signature

inriver and OpenText Core Signature complement each other well in product-led businesses that need controlled approvals, legally binding sign-off, and consistent product content across channels. inriver manages the product data, assets, and enrichment process, while OpenText Core Signature adds secure electronic signature workflows for approvals and compliance.

1. Product specification approval before publishing

Data flow: inriver to OpenText Core Signature, then back to inriver

When product managers or marketing teams complete a new product record in inriver, the finalized specification sheet, pricing summary, or launch brief can be sent to OpenText Core Signature for formal approval by legal, compliance, or product leadership. Once signed, the approval status and signed document can be stored back in inriver as part of the product record.

• Ensures product content is approved before it is published to e-commerce or partner channels
• Creates an auditable approval trail for regulated or high-risk product categories
• Reduces delays caused by manual email-based sign-off

2. Localization approval for market-specific product content

Data flow: inriver to OpenText Core Signature

For global launches, inriver can route localized product descriptions, claims, and packaging text to OpenText Core Signature for approval by regional managers, legal reviewers, or country-specific compliance teams. This is especially useful when product messaging must meet local regulatory or language requirements before release.

• Supports controlled review of translated content
• Helps prevent unauthorized or non-compliant market claims
• Speeds up multi-country product launches with structured sign-off

3. Digital approval of product launch packs

Data flow: inriver to OpenText Core Signature

inriver can assemble a launch pack containing product data, key selling points, technical attributes, and digital asset references. That package can then be sent through OpenText Core Signature for approval by cross-functional stakeholders such as merchandising, sales, legal, and operations before the product goes live.

• Replaces fragmented approval chains across email and shared drives
• Improves launch governance and accountability
• Helps ensure all launch materials are aligned before publication

4. Supplier and brand owner content sign-off

Data flow: inriver to OpenText Core Signature, with signed output returned to inriver

Manufacturers and distributors often rely on suppliers or brand owners to approve product descriptions, compliance statements, or usage instructions. inriver can send these content packages to OpenText Core Signature for external sign-off, then store the signed approval alongside the product record for future reference.

• Provides a formal approval process for third-party content
• Improves collaboration with suppliers and brand owners
• Creates traceability for audits and disputes

5. Contract-linked product catalog approvals

Data flow: bi-directional

For businesses that manage product assortments tied to commercial agreements, inriver can provide the approved product set while OpenText Core Signature handles signature workflows for related agreements, such as reseller terms, distribution contracts, or pricing approvals. Signed contracts can then be linked back to the relevant product families in inriver.

• Connects commercial agreements to the exact products they govern
• Reduces risk of publishing products before agreements are executed
• Improves visibility for sales, legal, and product operations teams

6. Compliance approval for regulated product attributes

Data flow: inriver to OpenText Core Signature

In regulated industries such as healthcare, chemicals, food, or industrial manufacturing, certain product attributes, warnings, or certifications may require formal approval. inriver can route those specific fields or documents to OpenText Core Signature for sign-off by compliance officers before the product is released to downstream channels.

• Supports controlled approval of regulated content
• Reduces compliance risk from incomplete or unapproved product data
• Provides a documented approval history for audits

7. Signed approval archive attached to product master data

Data flow: OpenText Core Signature to inriver

After a document is signed in OpenText Core Signature, the signed PDF, certificate of completion, and signer metadata can be pushed into inriver and attached to the relevant product, variant, or content record. This gives product teams a single place to find both the approved content and the proof of approval.

• Improves recordkeeping and retrieval of approved documents
• Helps product teams verify which version was approved and by whom
• Supports internal audits and external compliance reviews

8. New product introduction governance workflow

Data flow: bi-directional

During new product introduction, inriver manages the creation and enrichment of product data while OpenText Core Signature handles formal approvals at key milestones such as concept approval, final content approval, and launch authorization. Status updates from OpenText Core Signature can trigger workflow progression in inriver so teams know when a product is ready for publication.

• Creates a structured end-to-end launch process
• Aligns product, marketing, legal, and operations teams
• Improves launch speed while maintaining control and compliance