DPP-Flash: product data, review and digital product passports
Provider reference · reported pilot
DPP-Flash targets small and medium-sized businesses. WDR profiled the Bergheim founding team around Nico Bergstreiser on 7 November 2026 and reported an unnamed pilot customer. The television report aired on 6 November in Lokalzeit aus Köln. This establishes a public project profile and a reported test, not broad production deployment.
Described workflow
In a company statement dated 15 November 2026, DPP-Flash describes AI processing existing product data and documents into a Digital Product Passport. According to the provider, missing information can be obtained from ERP and PIM systems, including SAP systems, or through AI-assisted supplier requests (Supplier Outreach), then incorporated into the passport. The product website describes human review and confirmation of extracted data. Automating creation and maintenance as far as possible is a stated company goal. Specific interfaces, the degree of automation and backend workflows have not been tested here; the new statement does not establish a particular supplier portal.
Public demo: passport interface, not workflow validation
The VoltStride 720 demo, read on 15 November 2026, shows an example battery passport with product identity, composition, repair information, carbon-footprint data and technical fields. Several evidence, study and certification links point only to “#” and provide no retrievable supporting documents there. The interface does not establish data extraction, ERP/SAP connections, actual supplier communication or automatic updates. Its displayed date, March 2025, is demo content, not evidence of a product launch or customer deployment at that time.
Customer references, infrastructure and security
According to the company statement of 15 November, specific customer references and project details cannot currently be published because of confidentiality agreements. This explains non-disclosure from the provider’s perspective, but does not replace independent deployment or outcome evidence. The same statement places the server infrastructure in Germany and says ISO 27001 certification has not yet been obtained. Neither verified GDPR compliance nor an ongoing or completed certification process is inferred.
Editorial relevance to the Atlas
The approach connects previously separate product documents, supplier responses and human review to the next data version. The research axis is input → extraction → correction or completion → confirmed passport. QR retrieval alone does not satisfy the Atlas definition. Publicly traceable evidence is still needed to show how feedback changes the next system action or passport version in the pilot. The project is therefore an ecosystem reference, not an additional established practice case or core dossier.
Regulation: distinguish the battery passport from ESPR
Article 77 of EU Batteries Regulation 2023/1542 requires a battery passport from 18 February 2027 for LMT batteries, industrial batteries above 2 kWh and electric-vehicle batteries placed on the market or put into service. This is not a universal passport requirement for all goods or all batteries. The ESPR framework and product-specific requirements must be distinguished. Public passport information and restricted-access information are also different.
Evidence limits and next research questions
WDR provides external reporting on the project, not a compliance audit. Claims about legal assurance, ESPR conformity, five-minute completion, 15-year hosting or general penalty levels are not adopted as independently verified. The website also displays illustrative future headlines with .example addresses; these are not news sources. The pilot’s actual feature scope, data provenance and versioning, access roles, error handling and measured outcomes remain open. To qualify as an evidenced interactivation case, the project would particularly need an anonymised, traceable sequence from a missing field through a supplier request, response and review or approval to a new passport version. Documented interfaces and measured pilot results remain absent. RegTech denotes the regulatory application area, not verified legal conformity.
Comparison axes: documents, supplier responses and data correction
Aleph Alpha Pharia provides a comparison for document-dependent extraction paths; extracted information is not yet a professionally or regulatorily validated result. SAP Business Network / Ariba illustrates how a supplier response changes a process, while Open Food Facts illustrates collaborative data correction. These references establish neither a SAP integration nor a partnership with DPP-Flash. Voluntary product identities and reuse processes in the existing reading path remain distinct from statutory passport requirements.
Dates and source roles
Atlas entry: 14 November 2026; supplementary source and demo review: 15 November 2026. WDR article: 7 November, 09:53; broadcast: 6 November, 19:30. WDR lists conversations with the founders among its sources; the pilot therefore remains a reported test, not an independently documented technical evaluation. The editorial team holds Nico Bergstreiser’s company statement of 15 November by email. The product website and demo are provider sources. Additional publications checked at Leitquelle and Trendkraft are labelled press releases and provide no further independent functional validation. No exact incorporation, product-launch or pilot-start date is inferred; 2026 denotes the documentation year.
Direct sources
- WDR / Lena Wensch: article 7 November; broadcast 6 November 2026 · independent reporting incorporating founder statements ↗
- DPP-Flash: product website · undated provider source; checked 14 November 2026 ↗
- EU Batteries Regulation 2023/1542, Article 77 · consolidated version 13 August 2026 ↗
- European Commission: ESPR framework · 19 July 2024 ↗
- DPP-Flash: VoltStride 720 · provider demo; interface read 15 November 2026, backend not tested ↗
- Leitquelle: 7 September 2026 · DPP-Flash press release, not independent functional validation ↗
- Trendkraft: 13 November 2026 · press release, not additional independent deployment evidence ↗
Mechanism and limits
Provider statement of 15 November describes ERP/PIM/SAP data access and AI-assisted supplier requests; extensive automation is a goal, not independently validated deployment.
Public battery-passport demo inspected; backend, integrations, permissions and automatic updates not tested. Server location in Germany and absence of ISO 27001 certification are company statements.
Dates and evidence scope
- Recorded event / reference date
- 2026 (Dokumentationsjahr; kein bestätigter Produktstart)
- Atlas first publication
- 2026-11-14
- Source review in this audit
- 2026-11-15
The editorial update date is not a claim that every source or current product feature was rechecked. Unknown dates remain open. Source publication dates are listed with the evidence above.
Structured evidence and geography register · Unclassified source roles and unassigned origin/market fields are explicitly marked.