Productsup - OpenText Core Case Integration and Automation

Common Integration Use Cases Between Productsup and OpenText Core Case

• Product content issue resolution case management
  When Productsup detects feed validation errors, missing attributes, broken image links, or channel-specific compliance issues, it can create a case in OpenText Core Case with the affected SKU, channel, error details, and priority. Product content, merchandising, and operations teams can then collaborate in a single case record to investigate, correct the source data, and track resolution through to republishing. Data flow: Productsup to OpenText Core Case.
• Marketplace rejection and appeal handling
  If a marketplace rejects product listings due to policy violations, incomplete content, or taxonomy mismatches, Productsup can pass the rejection reason and impacted product set into OpenText Core Case. Case handlers can coordinate with catalog, legal, and channel teams to review the issue, gather supporting evidence, and manage the appeal or remediation process. Once resolved, the updated content can be republished from Productsup. Data flow: Productsup to OpenText Core Case, then OpenText Core Case to Productsup for closure confirmation.
• Product data governance and approval workflow
  For regulated or high-value product categories, Productsup can send proposed content changes, enrichment requests, or exception cases into OpenText Core Case for formal review and approval. OpenText Core Case provides a controlled workspace for compliance, legal, and brand teams to approve or reject changes before they are syndicated to external channels. This reduces the risk of publishing inaccurate or non-compliant product information. Data flow: Productsup to OpenText Core Case, with approval status returned to Productsup.
• Customer complaint investigation tied to product listings
  Customer service teams using OpenText Core Case can open a case when complaints relate to inaccurate product descriptions, missing specifications, or misleading imagery seen on a storefront or marketplace. Productsup can supply the current channel-specific content, feed history, and publication timestamps to help investigators determine whether the issue originated in the source data, transformation rules, or channel mapping. This shortens root-cause analysis and improves customer response times. Data flow: OpenText Core Case to Productsup, with supporting product content returned to the case.
• Compliance exception tracking for channel-specific requirements
  Some channels require localized disclosures, certifications, or restricted-claims handling. Productsup can flag products that fail channel rules and create a compliance case in OpenText Core Case for review by regulatory or quality teams. The case can store evidence, decisions, and remediation actions, while Productsup is updated with approved exceptions or required content changes. This creates an auditable process for managing channel compliance. Data flow: Productsup to OpenText Core Case, bi-directional for status and remediation updates.
• Supplier content dispute resolution
  When supplier-provided product data conflicts with internal catalog standards or channel requirements, Productsup can identify the discrepancy and open a case in OpenText Core Case. Procurement, category management, and supplier operations teams can use the case to request clarification, collect corrected attributes, and document the final approved version. This helps reduce back-and-forth emails and ensures a clear audit trail for content decisions. Data flow: Productsup to OpenText Core Case, with final approved content returned to Productsup.
• Channel launch readiness and exception management
  Before launching products to a new marketplace or advertising platform, Productsup can identify missing assets, incomplete attributes, or taxonomy gaps and create readiness cases in OpenText Core Case. Cross-functional teams can use the case to track outstanding tasks such as image creation, copy approval, localization, and legal review. Once all blockers are resolved, Productsup can receive the launch-ready status and proceed with syndication. Data flow: Productsup to OpenText Core Case, then OpenText Core Case to Productsup for launch approval.