Skip to Content

Corvus ProductTrust · Product evidence & lifecycle

Every product.
A traceable story.

Connect what you make, the evidence behind it, and every change that follows.

A shared workspace for manufacturers, importers, suppliers and product-security teams: from a component certificate to a reviewed technical file, product passport or software release.

Product-specific scope and demonstration · Human decisions remain central

ONE PRODUCT, CONNECTED CONTEXT

ILLUSTRATIVE PRODUCTConnected power unit

Model → batch → individual item

01
Know the configurationComponents · supplier · firmware
02
Show the evidenceSource · assertion · reviewer · version
03
Control the next changeImpact · decision · successor record

An explanatory model, not a customer record or certification.

From disconnected documents to a reviewable record

Evidence that belongs to the right product.

Choose the product family, market and workflow first. ProductTrust connects the facts and responsibilities needed to review that scope.

01

Product identity & configuration

Follow a product beyond a single catalogue entry.

  • Families, models, variants, batches and serialised items
  • Operators, facilities, suppliers and component relationships
  • As-designed, as-built, as-shipped and as-maintained snapshots
02

Evidence & supplier review

Keep a source document distinct from the facts it supports.

  • Document versions, citations, asserted values and validity
  • Missing, expired, conflicting and unreviewed evidence queues
  • Scoped supplier requests, attestations, corrections and review decisions
03

Technical files & release decisions

Assemble the material behind an accountable product decision.

  • Intended use, design, BOMs, labels and instructions
  • Hazards, controls, test plans, reports and reviewed results
  • Purchase, manufacturing and delivery gates with reasoned exceptions
04

Passports & controlled publication

Publish the approved version for the intended audience.

  • Model, batch or item identity and data-carrier links
  • Separate public, supplier and authorised role views
  • Approved versions, successor links and publication receipts
05

Software & cyber resilience

Connect the software release to the physical products it affects.

  • CycloneDX/SPDX component and dependency inventories
  • Vulnerability applicability, VEX decisions and remediation
  • Support periods, incident timelines and reviewed report packages
06

Lifecycle & change impact

Understand what a new fact or component changes downstream.

  • Engineering changes and affected-product review
  • Custody, maintenance, repair and component replacement
  • Reuse, repurpose, recall and end-of-life history

A practical example

A supplier replaces a component.
What needs another look?

A replacement may affect a BOM, a test result, a delivered configuration and the facts shown in a passport. Reviewing the PDF alone does not explain that impact.

Connect the supplier submission to the exact component and product scope. Keep its source, effective dates and reviewer decision, then identify the downstream records that need re-evaluation.

  • Procurement sees what is missing or awaiting supplier correction.
  • Engineering reviews affected configurations and release evidence.
  • Product owners decide which approved records need a successor.

SUPPLIER CHANGE → REVIEWED OUTCOME

  1. 1
    Receive the new evidence

    Component scope, source document and supplier attestation.

  2. 2
    Compare and resolve

    Changed values, validity, conflicts and reviewer questions.

  3. 3
    Trace the affected products

    BOMs, batches, serialised items and software releases.

  4. 4
    Approve the next version

    A recorded decision and linked successor; earlier history remains intelligible.

Illustrative workflow. Rules and review roles are scoped for your organisation.

Passports with evidence behind them

More than a QR code.

A product passport needs a stable identity, appropriate information, controlled access and a way to handle corrections. The carrier is the entry point to that record.

ProductTrust connects the passport to versioned facts, its product configuration and the people responsible for approval. Registry registration and substantive product review are separate decisions.

Digital product passports

Model, batch and item records; public and authorised views; structured data; approval history; publication and carrier verification; successor, withdrawal and recall links.

Battery-specific workflows

Battery structure and chemistry, manufacturing traceability, performance and test evidence, dynamic state summaries, repair and circular-status changes. Select the battery category and applicable pack before assessing completeness.

Purposeful access

A consumer, repairer, supplier and reviewer need different information. Define what belongs in each view. Confidential evidence and personal data do not belong in the public passport by default.

Scope is product-specific.

Applicable rules, effective dates, licensed standards and registry/provider arrangements require qualified review. A published passport or registry receipt is not a conformity certificate or automatic regulatory approval.

FOLLOW A SOFTWARE CHANGE

Software releaseComponents & dependencies
AssessAdvisory, affected versions and applicability
RespondFix, update, communication and evidence
Affected product configurationsModel · batch · delivered item

Illustrative relationship, not an automated security verdict.

For products with digital elements

Know what shipped.
Understand what changed.

Link the software bill of materials to its release and the physical configurations using it. Compare versions, review candidate vulnerability matches and record why a component is affected, fixed or not affected.

Keep treatment, security updates, support-period decisions and incident evidence together. Reporting workflows prepare reviewable packages; live submissions require explicit authority and the relevant configured adapter.

  • Software and firmware release context
  • Component, licence and dependency relationships
  • Reviewed vulnerability applicability and remediation
  • Incident history, ownership and report receipts

Useful across the team

One evidence chain. Clear responsibilities.

Product & compliance

Review rule applicability, technical-file gaps, evidence validity and publication decisions.

Procurement & suppliers

Request specific missing facts, compare responses and track corrections without exposing unrelated supplier records.

Engineering & security

Trace configurations, changes, software components, risks and release consequences.

Service & circularity

Record repairs, replacements, custody and end-of-life events against the right product identity.

Connect to the work in Odoo.

Products, BOMs, purchases, manufacturing, stock, lots/serials and repairs provide the operational context. Import previews, mappings and reconciliation keep external ERP, PLM, PIM or telemetry exchanges reviewable.

Keep the decision explainable.

Versioned rules and source citations explain gaps. AI assistance can suggest extracted facts and draft text for review; it does not approve evidence, grant exceptions or publish on your behalf.

Scope the right first step

Bring one product. Follow its evidence.

Where should we start?

Choose one product family and one useful journey: supplier evidence collection, a technical-file review, a passport scope, or a software-release change. Bring a redacted example of the data and the decision your team needs to make.

Is ProductTrust a certification or legal-advice service?

No. It is product-evidence and lifecycle tooling. Applicable laws, standards, conformity decisions and filings remain with the responsible organisation and qualified reviewers. No page on this site certifies your product.

Can we assume every integration or rule pack is ready for our market?

No. Confirm the exact product category, jurisdiction, effective dates, provider access and integration scope in the demonstration and proposal. Test and live registry operations remain separate.

What can we take away from the system?

Discuss the required export package: business records, evidence files and manifests, approved versions, source-pack context and relevant receipts. Portability and retention requirements should be agreed for your deployment.

How is availability agreed?

Start with a scoped demonstration and deployment assessment. Confirm the modules, workflows, integrations, operating responsibilities and acceptance checks for your intended use before a commercial commitment.

Make the next product decision reviewable.

Show us the workflow, the evidence and the people who need to act.

Discuss ProductTrust ↗

Explore Industry Apps · Odoo engineering services · Corvus Cloud for Odoo