Automated pre-checks catch missing fields, wrong dates, duplicates and mismatched PDF files before documents and certificates reach review and the product passport.
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
Every time you add a document or certificate, import data from a CSV file or send it through the API, DPPC runs a set of rules that check data quality. The result is a list of specific warnings and suggestions, such as a missing certificate number, an expiry date earlier than the issue date or a file whose name does not match the product. Errors show up right away instead of during review or after the product passport is published.
For a certificate, the system checks whether the issuer and number are filled in, whether the expiry date comes after the issue date, whether the certificate is already expired when saved or expires soon, and whether its status matches its dates. It also detects a certificate with the same name saved earlier under a different number or issuer. It warns when the PDF file name does not match the certificate name or number, or when the file is suspiciously small and may be incomplete.
For product documents, DPPC flags a document with the same title and type added a second time, very short titles and files whose names contain neither the SKU nor the product name. If the PDF has a readable text layer, the system also checks whether the document mentions the product and its own title, and whether it contains a different SKU, GTIN, batch number or serial number than the product record. It is a simple way to catch a document attached to the wrong product.
The same rules apply to CSV imports. For products, the system flags a missing brand, model or country of origin, a description that is too generic, an unusual GTIN format and empty industry fields. For materials, it detects shares that add up to more than 100 percent, suspiciously low values, mass without a unit, a missing supplier and a country of origin that differs from the supplier country. For suppliers, it points out missing contact details or country and a VAT ID already assigned to another supplier.
The checks never reject anything on their own. A document or certificate with warnings goes to review with the status "needs review", and the person in charge sees what each warning is about. If the readable PDF text contains a certificate number or issuer and that field in the record is empty, the system can suggest it. Every result also includes a confidence score. Through the API, the same checks are available in a preview mode that returns warnings without saving any data.
We are upfront about this, because trust in the process depends on it. The checks are predictable, transparent rules, not an artificial intelligence model. They do not recognize text in scans, and they only read content from PDF files that have a plain text layer. They also do not judge whether a document is correct in substance. Their job is to catch gaps, inconsistencies and mistakes before a person looks at the document, and the approval decision is always made by the person reviewing it.
FAQ
No. They are a set of transparent rules that check data, dates, duplicates, file names and readable PDF text. Every warning has a clear cause, and the same document always produces the same result.
For scans, the system checks the data entered in the record, the file name, the file size and duplicates, but it does not read content from the page image because there is no text recognition (OCR).
No. The document is saved and marked as needing review. Publishing the passport is only blocked by the readiness score, for example when a certificate is rejected or expired.
Yes. The API has a preview mode for products, suppliers, certificates and documents that returns warnings and suggestions without saving any data.
It is a simple indicator of how many signals from the document match the record and how many warnings were found. It helps decide what to review first, but it does not replace the decision of the person in charge.
Next paths
Related use cases
Product Documentation Software with Document and Certificate Control
Keep product documents and certificates current: expiry dates, reviews with deadlines, versions with checksums and publication blocked for products with invalid certificates.
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.