Consonance - OpenText Product Traceability Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Product Traceability

1. Title and component traceability from manuscript to finished product

Data flow: Consonance - OpenText Product Traceability

When a manuscript moves from acquisition into production in Consonance, the title record, edition details, ISBNs, format variants, and key milestones can be sent to OpenText Product Traceability to establish a traceable product record. This gives publishers a controlled link between editorial workflow and downstream product tracking, helping teams monitor each book version through print, digital, and audio release stages.

Business value: Reduces manual rekeying, improves product visibility, and creates a reliable audit trail across publishing and traceability teams.

2. Packaging and component status synchronization for print and digital releases

Data flow: Bi-directional

Consonance can send publication schedules, format readiness, and asset completion status to OpenText Product Traceability, while OpenText can return component or production status updates for items tied to a title. This is useful when a publisher needs to confirm that cover files, interior files, proofs, and final production components are aligned before release.

Business value: Helps prevent release delays caused by missing or incomplete components and gives production managers a single view of readiness.

3. Rights and edition control for market-specific product variants

Data flow: Consonance - OpenText Product Traceability

Consonance manages rights and edition metadata, including territory restrictions, language variants, and format-specific publishing rights. That information can be pushed into OpenText Product Traceability so product teams can track which editions are approved for specific markets and ensure only authorized variants move into production and distribution.

Business value: Lowers compliance risk, supports territory-specific publishing decisions, and reduces the chance of unauthorized product release.

4. Recall and issue management linked to title metadata

Data flow: OpenText Product Traceability - Consonance

If a product issue is identified in OpenText Product Traceability, such as a defective print run, incorrect file version, or packaging error, the issue record can be sent back to Consonance and linked to the affected title, edition, and production stage. Editorial and production teams can then assess whether a corrected file, revised metadata, or reprint workflow is required.

Business value: Speeds response to product defects, improves cross-functional coordination, and supports faster corrective action.

5. Batch and version traceability for multi-format publishing

Data flow: Bi-directional

For publishers releasing the same title in multiple formats, Consonance can provide the master title record and version history, while OpenText Product Traceability can maintain traceability for each production batch or release instance. This is especially valuable when print, ebook, and audio versions are produced on different timelines and need to be linked back to the same source title.

Business value: Improves version control, simplifies root-cause analysis, and gives operations teams a clear relationship between source content and released products.

6. Supplier and production partner accountability for outsourced manufacturing

Data flow: Consonance - OpenText Product Traceability

When publishers outsource printing, packaging, or other production steps, Consonance can pass title specifications, delivery dates, and approved production files to OpenText Product Traceability. The traceability platform can then track supplier execution against those requirements and capture production evidence tied to the title record.

Business value: Strengthens supplier oversight, improves accountability, and helps publishers manage third-party production more consistently.

7. Release readiness reporting across editorial, production, and traceability teams

Data flow: Bi-directional

Consonance can provide milestone completion data such as manuscript approval, design signoff, and final proof approval, while OpenText Product Traceability can contribute status on traceable production steps and issue resolution. Combined, these updates create a release readiness dashboard that shows whether a title is truly ready for market launch.

Business value: Gives leadership a more accurate view of launch risk, reduces missed deadlines, and improves coordination across departments.

8. Audit and compliance reporting for regulated or high-value publications

Data flow: Bi-directional

For publishers managing sensitive, regulated, or high-value content, Consonance can provide editorial approval history, rights status, and publication metadata, while OpenText Product Traceability can provide evidence of product handling, production lineage, and issue history. Together, they support stronger audit reporting and internal compliance reviews.

Business value: Improves governance, supports audit readiness, and creates a defensible record of how each product moved from manuscript to market.