Keep product documents and certificates current: expiry dates, reviews with deadlines, versions with checksums and publication blocked for products with invalid certificates.
Problems this page solves
What the team gets
Next step
We will show the product flow, public page, automated checks and API angle that best matches this use case.
Deep dive
Declarations, technical data sheets, manuals and certificates come from different suppliers, in different versions and with different expiry dates. They usually end up in network folders and mailboxes, and the knowledge of which version applies lives in one person's head. The problem only surfaces when a customer, distributor or inspector asks for the current document and the team is not sure whether the one in the folder is still valid.
In DPPC, PDF documents and certificates are not kept in a separate archive. They are linked to specific products. A certificate has a number, issuer, issue date and expiry date, and one certificate can cover many products. That makes it immediately visible which products a document applies to, and which products will lose their complete evidence when a certificate is no longer valid.
Once the expiry date passes, DPPC automatically marks the certificate as expired. A product with an expired or rejected certificate loses full readiness, and its readiness score shows the gap. Such a product cannot be approved for publication until a valid document is added. The expiry date is also visible on the public passport page, so anyone scanning the QR code can see how long the certificate is valid.
Every new document and certificate goes into review with a deadline: five days by default, and two days for a certificate that expires within 30 days. If the deadline passes and the document is still waiting for a decision, the system sends an in-app reminder. The review center gathers all documents awaiting a decision in one place and lets you approve or reject them in bulk, with a note explaining the decision.
A new version of a document does not silently overwrite the old one. DPPC stores each version with a SHA-256 checksum, so you can verify that a file has not been altered and restore an earlier version when needed. Product approvals, rejections and publications are added to the history, and organization owners and admins can see an activity log for the whole team. The duplicate center helps catch the same document uploaded more than once.
Start with the product group that has the most certificates. Import products and certificates from CSV files and add PDF documents through the import with attachments. Automatic pre-checks point out files whose names do not match, duplicates and unusual file sizes. After the review, the readiness score shows which products are missing documents or valid certificates, and those gaps are a good starting point for conversations with suppliers.
FAQ
Every certificate has an expiry date. Once it passes, the system automatically marks the certificate as expired, and the products it covers lose full readiness and cannot be approved for publication until a valid document is added.
Yes. Every version of a document and certificate is stored together with its SHA-256 checksum, and an earlier version can be restored.
Permissions depend on the role in the organization, for example compliance manager or admin. Every decision is recorded, and a rejection can include a note for the person who uploaded the document.
Product documents are added as PDF files of up to 10 MB. Each document has a type, an owner, a review status and a setting that controls whether it appears on the public passport page.
No. Only documents and certificates marked as public appear on the passport page. Downloads go through links that are valid for 30 minutes and are logged.
Next paths
Related use cases
QR Code Product Passport: A Public Product Page That Always Shows Current Data
QR code product passports: a permanent address, current data, materials, documents and certificates in four languages. How it works, what customers see and how to roll it out.
Product Data API for Digital Product Passports and External Systems
Connect ERP, PIM, supplier workflows and external tools through API keys, sync jobs, preview validation and webhooks.
Automated Checks for Product Documents and Certificates
Automated pre-checks catch missing fields, wrong dates, duplicates and mismatched PDF files before documents and certificates reach review and the product passport.