Productsup - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between Productsup and OpenText Core Signature

1. Signed product content approval before channel syndication

Productsup can prepare channel-specific product feeds, while OpenText Core Signature captures formal approval from merchandising, legal, or brand teams before publication. This is useful when product claims, pricing, or regulated content must be approved before being pushed to marketplaces or advertising platforms.

• Flow: Productsup to OpenText Core Signature
• Business value: Reduces compliance risk and prevents unapproved content from going live
• Example: A retailer finalizes a seasonal campaign feed in Productsup, sends it for digital sign-off, and only publishes after approval is completed

2. Supplier onboarding and content authorization

When onboarding new suppliers or brands, Productsup can collect and normalize product data, then route supplier agreements or content authorization forms through OpenText Core Signature. This ensures suppliers formally approve data usage, channel distribution terms, and content responsibilities before their catalog is activated.

• Flow: Productsup to OpenText Core Signature
• Business value: Speeds supplier activation while maintaining contractual control
• Example: A marketplace operator uses Productsup to ingest supplier product data and OpenText Core Signature to obtain signed content distribution agreements

3. Regulated product launch approval workflow

For industries such as cosmetics, pharmaceuticals, food, or electronics, product launches often require formal approval of claims, labels, and disclosures. Productsup can assemble the final product content package for each channel, and OpenText Core Signature can manage the required sign-off from regulatory, quality, and legal stakeholders before syndication.

• Flow: Productsup to OpenText Core Signature
• Business value: Supports auditability and reduces the chance of non-compliant product listings
• Example: A cosmetics brand routes ingredient and claim approvals through OpenText Core Signature before publishing marketplace listings from Productsup

4. Contracted marketplace listing authorization

Some brands require signed authorization before third-party marketplaces or distributors can publish their product content. Productsup can generate the listing package, and OpenText Core Signature can capture approval from the brand owner or channel manager to authorize distribution to specific sales channels.

• Flow: Productsup to OpenText Core Signature
• Business value: Improves governance over where and how product content is distributed
• Example: A manufacturer approves a reseller?s marketplace listing rights through a signed workflow before Productsup syndicates the feed

5. Signed exception handling for feed corrections

Productsup?s validation and error correction capabilities can identify missing or non-compliant product attributes. If a business exception is needed, OpenText Core Signature can be used to obtain formal approval for publishing with known deviations, such as temporary missing assets, alternate descriptions, or region-specific disclosures.

• Flow: Productsup to OpenText Core Signature
• Business value: Keeps launches moving while preserving accountability for exceptions
• Example: A product team requests signed approval to publish a feed with temporary image substitutions until final assets are delivered

6. Signed internal approval for promotional content and pricing changes

Productsup can manage promotional product data for campaigns across multiple channels, while OpenText Core Signature can formalize approval for discount structures, bundle offers, or time-sensitive pricing changes. This is especially useful when finance, merchandising, and marketing must all approve the final offer before it goes live.

• Flow: Productsup to OpenText Core Signature
• Business value: Reduces pricing errors and improves control over promotional execution
• Example: A retail promotion is configured in Productsup and routed through OpenText Core Signature for finance approval before marketplace activation

7. Signed audit trail for content governance and compliance

OpenText Core Signature can provide a legally binding record of who approved which product content version, while Productsup maintains the operational feed history and channel distribution record. Together, they create a stronger governance model for audits, disputes, and regulatory reviews.

• Flow: Bi-directional
• Business value: Improves traceability across content creation, approval, and publication
• Example: An enterprise can prove that a specific product description was approved before it was syndicated to a marketplace and later updated after a signed revision request

8. Customer or partner onboarding for product data distribution agreements

For organizations that distribute product content to dealers, affiliates, or channel partners, Productsup can manage the content package and OpenText Core Signature can handle signed onboarding agreements, usage terms, and brand guidelines acknowledgements. This creates a controlled process for granting access to product content feeds.

• Flow: Productsup to OpenText Core Signature
• Business value: Accelerates partner onboarding while protecting brand and content rights
• Example: A brand shares approved product feeds with a new distributor only after the distributor signs content usage and channel compliance terms