Julian Sotek

Founders Associate, sqanit

As Founder's Associate at sqanit and contributor to DPP.cloud, he supports research, content strategy, and market analysis around Digital Product Passports, connected products, digital identities, and product lifecycle management. His articles translate complex EU regulations, compliance requirements, and emerging technologies into practical guidance, helping manufacturers prepare for the future of sustainable and connected products.

Recent Posts by this Author

Tappr Alternatives 2026: 10 DPP Platforms Compared for Manufacturers Who Need More Than Compliance
Platform Comparisons
August 26, 2026

Tappr Alternatives 2026: 10 DPP Platforms Compared for Manufacturers Who Need More Than Compliance

Tappr wins on entry price. Alternatives win when you need unit-level passports, a service layer on the QR code, or a 2-week PIM-based rollout. Ten platforms compared with honest fit recommendations, including when to just stay with Tappr.

Learn more
Digital Product Passport with Salsify: The DPP as One More Syndication Channel

Digital Product Passport with Salsify: The DPP as One More Syndication Channel

Brands on Salsify already syndicate content to demanding channels. The EU Digital Product Passport is one more, with a schema set by law. Learn how the integration works, why retail-hardened data is an advantage, and which category timelines actually apply.

Learn more
Digital Product Passport from SAP Data: Add-on Project or API Connector

Digital Product Passport from SAP Data: Add-on Project or API Connector

Material master, classification, DMS: the DPP data is already in SAP. The question is whether you run a year-long add-on project or connect a passport platform over OData in weeks. Both paths compared, with the honest caveats.

Learn more
Digital Product Passport Beyond Compliance: What Forrester's 2026 Report Means for ESPR
Business Case & ROI
July 27, 2026

Digital Product Passport Beyond Compliance: What Forrester's 2026 Report Means for ESPR

A new Forrester report argues most digital product passports fail for the same reason: they show every data field to everyone instead of designing for who is actually scanning. Here is what that means if you are building an ESPR-compliant DPP right now, and what a role-based passport looks like in practice.

Learn more