OpenText Core Signature - DeSL Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and DeSL

OpenText Core Signature and DeSL complement each other well in fashion and retail organizations that need controlled approvals, legally binding signatures, and accurate product development workflows. DeSL manages the product lifecycle, collaboration, and supply chain processes, while OpenText Core Signature adds secure electronic signature capabilities for approvals that must be auditable and compliant.

1. Digital approval of product line and collection sign-offs

Data flow: DeSL to OpenText Core Signature

When a product line, seasonal collection, or style package is ready for final approval, DeSL can send the approval document to OpenText Core Signature for legally binding signatures from design, merchandising, sourcing, and leadership teams. Once signed, the executed approval is returned to DeSL and stored with the product record.

• Eliminates paper-based sign-off for collection gates
• Creates a clear audit trail for product decisions
• Speeds up time-sensitive seasonal approvals

2. Supplier agreement and compliance document execution

Data flow: DeSL to OpenText Core Signature

DeSL can generate supplier-facing documents such as quality agreements, compliance acknowledgements, and development commitments. These documents are routed through OpenText Core Signature for supplier signatures, then the completed files are attached back to the supplier or style record in DeSL.

• Improves supplier onboarding and accountability
• Reduces delays in sourcing and production readiness
• Ensures signed compliance documents are centrally retained

3. Change request approval for product specifications

Data flow: DeSL to OpenText Core Signature to DeSL

When a product specification changes, such as fabric substitution, fit adjustment, or packaging update, DeSL can trigger an approval workflow through OpenText Core Signature. Required stakeholders approve the change electronically, and the signed approval is returned to DeSL before the updated specification is released downstream.

• Controls unauthorized product changes
• Prevents version confusion across teams
• Supports traceability for quality and compliance reviews

4. Legal approval of licensing and brand authorization documents

Data flow: DeSL to OpenText Core Signature

For fashion businesses that manage licensed brands, DeSL can route brand authorization forms, licensing agreements, and usage approvals to OpenText Core Signature. Once signed, the approved documents are linked to the relevant product, brand, or season record in DeSL.

• Supports controlled use of licensed assets and brand materials
• Reduces legal bottlenecks in product development
• Provides a searchable record of approved rights and permissions

5. Executive approval of sourcing and cost exceptions

Data flow: DeSL to OpenText Core Signature

When sourcing teams need approval for cost overruns, alternate materials, or supplier exceptions, DeSL can generate an exception summary and send it to OpenText Core Signature for executive sign-off. The signed decision is then stored in DeSL to support sourcing execution and future audits.

• Accelerates exception handling without email-based approvals
• Improves governance over margin-impacting decisions
• Creates a documented approval history for finance and operations

6. Signed handoff of product development deliverables to downstream teams

Data flow: Bi-directional

At key milestones, DeSL can package finalized deliverables such as tech packs, BOM approvals, and sample confirmations for signature in OpenText Core Signature. After execution, the signed package is returned to DeSL and made available to ERP, sourcing, or manufacturing teams as the approved source of truth.

• Ensures downstream teams work from approved documentation
• Reduces rework caused by incomplete or unsigned deliverables
• Improves coordination between product development and supply chain

7. HR and contractor onboarding for product development teams

Data flow: OpenText Core Signature to DeSL

For organizations using external designers, pattern makers, or product development contractors, OpenText Core Signature can manage onboarding documents such as NDAs, work agreements, and policy acknowledgements. Once signed, DeSL can reference the approved user or vendor record to enable collaboration in product development workflows.

• Speeds onboarding of internal and external contributors
• Ensures required legal documents are completed before access is granted
• Supports controlled collaboration across distributed teams

8. Audit-ready retention of signed product governance records

Data flow: Bi-directional

DeSL can send governance documents to OpenText Core Signature for execution, then retain the signed versions in the product record for long-term traceability. This is especially valuable for regulated product categories, private label programs, and quality-sensitive workflows where proof of approval is required.

• Strengthens audit readiness and compliance reporting
• Keeps signed records tied to the correct product version
• Reduces risk of missing or misplaced approvals

Together, OpenText Core Signature and DeSL help fashion and retail organizations move faster while maintaining control over approvals, compliance, and product governance.