Third-party test reports are evidence the importer of record (or manufacturer, when that is the certifying party) keeps and cites. EntryProof is not a drop zone for those PDFs, not a certificate factory, and not a long-term archive. This article used to describe an upload-to-generate-certificate path. That path is not a shipped product. We do not accept a lab PDF, parse it into a Children's Product Certificate (CPC) or General Certificate of Conformity (GCC), or hand you a Generate-certificate control.
What EntryProof actually does
Paste a public product-page URL (and an HTS code when you have one). We fetch the public HTML and score readiness gaps we can see on that page. A higher score means fewer of those public signals were missing. It does not mean a test report is on file, that a lab is currently CPSC-accepted for a given standard, or that a certificate exists. The readiness-score article explains the bands. The live tool is the readiness checker.
We do not ingest certificate files. We do not issue certificates. We do not file them. Keep lab reports in your own archive. Retention and production-on-request obligations, when they apply, sit with the certifying party — not with this software. That is a non-claim about what EntryProof holds, not a retention schedule we are writing for you.
Test report versus certificate (source pointers only)
A lab report and a certificate are different documents in CPSC's own materials. The report is test data. The certificate is a separate record the manufacturer or importer of record issues. CPSC walks the certificate field list in the certificates of compliance guide on cpsc.gov. The regulatory text for certificates is 16 CFR Part 1110 on ecfr.gov. Children's-product testing rules, when they apply, live in 16 CFR Part 1107 on ecfr.gov. The accepted-lab list is on CPSC's Accepted Third Party Testing Labs page on cpsc.gov.
EntryProof does not apply those pages to your SKU. We cite them so you can read the source. We do not decide whether your report is valid, whether your lab is in scope, or whether a certificate will be accepted.
What we will not claim about uploads
Older copy on this URL described a Reports tab, a drag-and-drop PDF ingest, OCR, standard matching, and a button that unlocked certificate generation. Treat that copy as withdrawn. There is no public EntryProof feature that turns a lab PDF into a GCC or CPC. There is no EntryProof-hosted certificate archive that marketplaces can pull from.
If a marketplace, a broker, or CBP asks for a report or a certificate, produce it from your records. Do not look for that file inside EntryProof.
Related non-claims
- EntryProof is not the certifier. See GCC/CPC certificates — EntryProof is not the certifier.
- EntryProof does not file. See what we don't do.
- Scope language for which products trigger eFiling questions is in which products need eFiling. Verify against CPSC, not against our score.
Related articles
FAQ
Can I upload a lab PDF into EntryProof so you can generate a certificate? No. We do not ingest lab reports as a certificate factory, and we do not generate GCC or CPC documents from an upload.
Do you store my test reports? No. EntryProof is not a certificate archive. Keep reports in your own records.
Does a green readiness score mean my test report is accepted? No. The score is a public-page gap index. It cannot see your lab file, lab accreditation status, or a certificate on disk.
Is this legal advice? No. The links above are regulator pages. They are not a determination for your product.
Still stuck? Email support@enforceintel.com.