Make the evaluation comparable
Write the decision criteria before the demonstrations. Separate requirements that are essential to your use case from preferences that can be traded against effort. Use the same product, a conflicting source, a restricted value and an intended integration in each evaluation.
Our suggested evidence levels are: described publicly, shown in a demonstration, reproduced in your pilot and agreed for delivery. They are a procurement method, not a platform feature. An undocumented function remains a question for the provider; it is not evidence that the function is absent. Record assumptions and acceptance conditions beside every assessment.
Source: Passvanta — Documented product evidence and review workflowSource: Passvanta — API and integration boundaries
Passvanta: documented review and publication workflows
Passvanta documents source-linked extraction proposals, supplier field requests, human review, publication gates and revision snapshots. Its carrier workflow supports SVG, PNG, PDF and ZPL exports. An API and CSV workflow provide integration surfaces.
Evaluate those functions with their stated limits. Preparation packs do not establish full legal coverage; ready-made PIM or ERP connectors are not included. Item identifiers resolve to parent passport data. Official EU registry integration still requires interface mapping, test access and acceptance. Our suggested pilot checks whether these boundaries match your intended scope and whether your team can maintain the resulting record.
Source: Passvanta — Documented product evidence and review workflowSource: Passvanta — Supplier PortalSource: Passvanta — Passport publication and lifecycleSource: Passvanta — Data Carrier StudioSource: Passvanta — API and integration boundariesSource: Passvanta — EU Registry preparation and acceptance boundary
osapiens: connected product and supplier information
The osapiens DPP page describes a product-compliance record connected to product systems, supplier requests and evidence. It also describes audience-specific access and several carrier technologies. These are the provider's public statements, not capabilities independently tested for this guide.
Our evaluation suggestion: bring an existing source-system field and change it during the demonstration. Ask the provider to show the affected product context, evidence and publication decision. Clarify which components, integration work and operating responsibilities are included in the proposed scope. Treat any promise about an external registry as a separate acceptance question.
Circularise: collection, traceability and controlled sharing
Circularise presents modules for supplier-data collection, material traceability and permissioned sharing through digital passports. Its public positioning includes mass balance and chain-of-custody workflows. This guide records that positioning without treating a marketing description as your project acceptance result.
Our evaluation suggestion: use a material transformation with a clear input and output, then define the claim your customer should receive. Ask for the source relationships, calculation boundaries and disclosure behaviour to be demonstrated. Agree which evidence your own team must supply and which decisions still require review before sharing information downstream.
Minespider: product and battery passport workflows
Minespider presents product and battery passports, with a focus on batteries, metals and circular supply chains. Its site describes document extraction, customisable passport content and API connectivity. These are attributed provider statements; this review does not independently validate their performance or legal coverage.
Our evaluation suggestion: provide one representative document and a later correction. Ask to see the proposed data, responsible review step, public output and update process. If your project depends on downstream material relationships, include that journey in the pilot and request a clear description of the data and services included.
Test operation and exit as well as creation
Use one common acceptance sheet for every candidate, including Passvanta. Record the input, expected outcome, observed outcome and unresolved point. Test a bad import, a revoked credential, a restricted field and a revised product. A successful presentation of a clean example leaves these operating questions unanswered.
Request a usable export and ask a second team to interpret it. Clarify identifier continuity, availability obligations, support, change handling and exit arrangements in the proposed agreement. Our recommendation is to select against evidence for your scope, with explicit owners for gaps. Do not rank a product as universally superior because one feature matches one pilot.
Source: Passvanta — Passport publication and lifecycleSource: Passvanta — API and integration boundaries
Sources and supporting material
- Passvanta — Documented product evidence and review workflow
Checked:
- Passvanta — Supplier Portal
Checked:
- Passvanta — Passport publication and lifecycle
Checked:
- Passvanta — Data Carrier Studio
Checked:
- Passvanta — API and integration boundaries
Checked:
- Passvanta — EU Registry preparation and acceptance boundary
Checked:
- osapiens — HUB for Digital Product Passport
Checked:
- Circularise — Collect, trace and share
Checked:
- Minespider — Product and battery passport platform
Checked: