Keep the applicable context
Create a product in its category and bind it to a specific regulatory-pack version. Later pack updates are assessed through an explicit migration, so existing records retain their original context.
Compliance Engine
Know which product data still needs work
Bring requirements, source documents and review decisions into one product workspace. Every missing value or unresolved evidence requirement has a place in the preparation workflow.
From a category to a reviewable product record
For manufacturers, importers and compliance teams who need to explain where a product value came from and who checked it before publication.
Collect values with their sources
Upload product documents or request selected fields from a supplier. Document extraction creates proposals with source references; a reviewer can compare them with the underlying evidence.
Resolve gaps and conflicting sources
Review proposed values, inspect differing source values and record a reason for a conflict decision. Supplier submissions and extracted data enter the review workflow before they become accepted product data.
Check the publication gate
See completeness, evidence coverage, validation coverage and blocking issues separately. A high display score does not clear a blocking rule: publication checks the product's recorded pack requirements.
A decision trail your team can follow
Document hashes and source locations connect a value to the file from which it was taken.
Roles determine who can propose, review and publish within the organisation.
Legal regulatory status and the maturity of the Passvanta pack remain separate.
Readiness has a defined scope
Results describe the rules available in the product's assigned pack. Preparation packs are incomplete working material and cannot establish full legal compliance. Your organisation remains responsible for assessing the applicable law and the sufficiency of its evidence.
FAQ
Questions about product readiness
Is the public readiness score the same as the product assessment?
The public tool asks nine questions about your preparation. Inside a workspace, readiness is calculated from the actual product values, evidence and review states against the assigned pack. Both make their scope visible.
Can AI approve a product value?
Document analysis proposes values and links them to sources. Authorised people review the proposals; extraction does not independently publish a passport or replace the human decision.
What happens when a category pack changes?
Existing products retain their recorded pack version. The organisation can examine a later version and perform a controlled migration before evaluating the product under that new context.
Continue through the product workflow
Supplier Portal
Turn missing product fields into a focused request. Suppliers see the requested information and submit their answers; your team keeps control of the review and product record.
Supplier Portal →Digital Product Passports
A passport connects accepted product information to a stable public address. Passvanta keeps the published revision, the evidence behind it and the publication decision traceable.
Digital Product Passports →Product Passport API
Use Passvanta's versioned REST API to connect product operations with your existing systems. Organisation scopes, review requirements and publication gates remain part of the integration.
Product Passport API →Start with one product and its evidence
Create a product record, choose its category and work through the available requirements with your team.