Frequently Asked Questions

A Digital Product Passport (DPP) is a legally mandated, structured information record that collects data on circularity, environmental sustainability, and regulatory compliance throughout a product’s entire supply chain lifecycle. It can be accessed through a physical carrier such as a QR code (GS1 Digital Link) and resolved into standardized, machine-readable semantic data (W3C JSON-LD).Not every product needs a Digital Product Passport (DPP). A DPP is a digital record containing key information about a product, such as what it is made of, where it comes from, and how it can be repaired, reused, or recycled. Under the Ecodesign for Sustainable Products Regulation (ESPR), the company or person placing the product on the EU market is responsible for creating and sharing the DPP. This is known as the economic operator. In most cases, this is the manufacturer or importer. If you manufacture, import, or sell products under your own brand, you are responsible for creating and sharing the DPP.…

Under the EU Batteries Regulation (EU) 2023/1542, all batteries placed on the EU market (EV, LMT, and industrial batteries >2 kWh) are required to have a mandatory Battery Passport as of 18 February 2027. Under the ESPR 2024/1781 priority plan, the European Commission is currently finalizing delegated acts for Textiles, Iron & Steel, and Aluminium, with implementation expected to begin in 2026/2027; the Electrical/Electronics sector will follow.

As a manufacturer, importer, or authorized B2B representative, you are legally responsible for the following:Creating Unique Identifiers: A Unique Product Identifier (UPI) at the level of detail required by the product category (one per product for batteries) and a Unique Facility Identifier (UFI) for each manufacturing facility.Hosting passport data: Structuring the data contained in the passport according to the decentralized DPP model under ESPR Article 10 / CIRPASS and hosting it on continuously accessible servers. The EU Registry will not retain the data; the data remains with you or a service provider designated by you.Sealing passports: Sealing passports with eIDAS advanced electronic seals to ensure that any tampering can be detected.Registering your organization in the EU DPP Registry: Using EU Login, submitting a declaration sealed by the Commission and counter-sealed with a qualified electronic seal from a Qualified Trust Service Provider, and then registering each UPI. Your organization identifier must be an NTR, LEI, VAT, eID, or local code; EORI numbers are not among the accepted types. DPPVisa is registry-ready but does not register or synchronize with the Commission’s registry on your behalf; since the semantic catalogue has not yet been defined, battery registrations cannot successfully be completed in this system in any case.

Yes. This is a core feature. In accordance with the draft FprEN 18239 standard, DPPVisa implements strict RBAC — Role-Based Access Control. Public sustainability data (carbon footprint, recycling sorting instructions, country of origin) remains publicly accessible. However, sensitive corporate intellectual property such as complete tiered supplier lists, specific material cost percentages, processing chemical formulations, and physical EUDR parcel/UFLPA document attachments are segregated and restricted to authorized parties (market surveillance and customs authorities, professional dismantling/recycling agents) or your own operators.

The system is designed to prevent this. To address “digital islands” and “digital death,” the common technical standards framework under EN 18221 (Data Storage, Archiving & Persistence) defines how passport records remain resolvable for an extended period after a product is placed on the market, regardless of the original economic operator’s operational status. DPPVisa aligns with these principles: DPPs are designed to remain preserved and publicly resolvable throughout a structured retention period, helping ensure that data persists beyond a single operator.

In accordance with the FprEN 18246 standard (final draft, under formal vote), all passport data is structured within Electronically Signed Data Structures (ESDC). When a tenant node publishes a passport, OpenDPP signs the JSON-LD payload using the brand’s eIDAS prime256v1 private keys stored in a secure database. This process creates a cryptographic digital signature seal. Anyone with the corresponding public key — a recycler, auditor, or market surveillance authority — can verify the signature, which indicates whether the passport payload has been altered since it was signed. This is an advanced eIDAS electronic seal: the signing key is stored by the software and encrypted at rest in your tenant vault, and you can also bring your own key and certificate to seal passports under your own identity.

A GS1 Digital Link is a standardized format that turns a physical barcode scan into a standard web URL. Instead of separate labels for QR codes, recycling details, and brand marketing, a single GS1 Digital Link QR code (e.g. https://domain/01/GTIN/21/Serial) is printed. When scanned by a consumer or inspector, the resolver gateway directs the request to a rich digital product passport HTML page or provides structured JSON-LD data for API integrations.

No — and this is an intentional choice. These add-ons provide a branded web address for your public passport pages, ideal for your website, emails, catalogs, and campaigns. The QR code on the physical product always contains our fixed resolver (e.g. https://dppvisa.com/01/GTIN), because a Digital Product Passport should remain accessible throughout its full retention period — typically 10 to 15 years — regardless of your subscription; whereas a domain name under your control may expire or change ownership. This allows your brand to maintain its presence across channels you own, while keeping scannable passport access accessible and stable. For more information on long-term persistence design, see the “What happens if DPPVisa shuts down?” section above.

DPPVisa provides pre-formatted compliance CSV spreadsheets for the main ESPR sectors (Textiles, Batteries, and Electronics). Compliance managers download the spreadsheet, fill in the raw product and material information, and upload it through the Portal. The server-side import engine parses the CSV in real time, performs strict validation checks (fiber ratios, positive capacity values, ISO country formats), and instantly generates signed passports from the rows that pass validation.

DPPVisa is a commercial, proprietary B2B compliance core dedicated to delivering high-performance compliance nodes and GS1 resolvers under a subscription-based SaaS model.

AAS is a standardized digital twin framework defined for industrial interoperability. DPPVisa provides AAS v3.0/3.1 import and export for product passport submodels — the exported environment is validated against the official IDTA AAS JSON Schema. Brands can import raw AAS JSON Environment documents or export product passports as standardized shells, mapping local fields to global eCl@ss or IEC logical registry dictionary identifiers.

UNTP standardizes verifiable credentials for tracking physical materials and custody transfers throughout the supply chain. On the inbound side, DPPVisa imports and validates signed supplier UNTP traceability events (compatible with GS1 EPCIS 2.0) as VC-formatted UNTP credentials; it resolves public keys and, when nodes are configured with eIDAS trust anchors, validates x5c certificate chains against them in the proof envelope. On the outbound side, DPPVisa exports each product passport as a compliant UNTP DigitalProductPassport credential — provided both as an enclosing vc+jwt (W3C VC-JOSE-COSE) and as an embedded W3C Data Integrity credential (ecdsa-jcs-2019), together with resolvable did:web export keys and W3C Bitstring Status List revocation. The legacy passport seal remains a vendor MerkleTreeAttestationProof, distinct from this compliant credential.