OpenText Core Signature - Stibo Systems Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and Stibo Systems

1. Product Data Governance Approval for New Item Creation

Data flow: Stibo Systems ? OpenText Core Signature

When product managers or data stewards create new product records in Stibo Systems, the record can be routed to OpenText Core Signature for formal approval before publication. This is useful for regulated or high-risk product categories where legal, compliance, or commercial sign-off is required before a product can be released to ERP, eCommerce, or PIM channels.

• Ensures product master data is approved before go-live
• Creates an auditable approval trail for governance teams
• Reduces errors caused by unapproved product attributes or descriptions

2. Customer Master Data Consent and Policy Acknowledgment

Data flow: Stibo Systems ? OpenText Core Signature

For customer onboarding or account maintenance, Stibo Systems can manage the trusted customer master record while OpenText Core Signature captures signed consent forms, privacy acknowledgments, or policy acceptance documents. Once signed, the signed document and status can be linked back to the customer profile in Stibo Systems.

• Supports compliance with privacy and consent requirements
• Centralizes customer master data and signed agreements
• Improves traceability between customer records and legal documents

3. Supplier or Vendor Master Onboarding with Signed Agreements

Data flow: Bi-directional

Stibo Systems can serve as the system of record for supplier master data, while OpenText Core Signature handles the execution of onboarding documents such as supplier terms, NDAs, and service agreements. Supplier data entered in Stibo can trigger signature workflows, and completed agreements can update the supplier profile with approval status and document references.

• Speeds up supplier onboarding and activation
• Improves governance over vendor records and contract evidence
• Reduces manual follow-up between procurement, legal, and master data teams

4. Controlled Release of Regulated Product Information

Data flow: Stibo Systems ? OpenText Core Signature

For products in regulated industries such as healthcare, chemicals, or food and beverage, Stibo Systems can manage the master data and route critical product changes to OpenText Core Signature for formal approval. This can include label text, ingredient declarations, safety statements, or market-specific compliance content before the data is published downstream.

• Creates a controlled approval gate for regulated content
• Helps prevent non-compliant product data from reaching channels
• Provides a clear audit trail for internal and external reviews

5. Signed Change Requests for Master Data Exceptions

Data flow: OpenText Core Signature ? Stibo Systems

When business users request exceptions to standard master data rules, such as a temporary product hierarchy change or customer data override, the request can be signed in OpenText Core Signature and then attached to the corresponding record in Stibo Systems. This ensures that exceptions are formally authorized before they are applied.

• Supports governance for non-standard data changes
• Links signed approvals directly to master data records
• Reduces risk of unauthorized overrides

6. New Market or Channel Launch Approval Workflow

Data flow: Stibo Systems ? OpenText Core Signature

When launching products or customer programs into a new market or sales channel, Stibo Systems can manage the required master data updates, while OpenText Core Signature captures approvals from legal, compliance, marketing, and regional operations. The signed approval package can then be stored against the master record as evidence of readiness.

• Coordinates cross-functional sign-off for launches
• Ensures market-specific data is approved before release
• Improves accountability across distributed teams

7. Audit-Ready Documentation for Data Governance Reviews

Data flow: Bi-directional

Stibo Systems can provide the authoritative master data record, while OpenText Core Signature stores signed governance documents such as policy acknowledgments, approval forms, and exception waivers. Together, they create a complete audit package for internal controls, regulatory reviews, or external audits.

• Combines master data history with signed evidence
• Supports audit and compliance reporting
• Reduces time spent gathering documentation from multiple teams