This article keeps the same help URL it has always used. The capability it once described is not available. EntryProof does not issue a General Certificate of Conformity (GCC) or a Children's Product Certificate (CPC). EntryProof does not sign those documents as certifier. EntryProof does not file certificate data with CPSC or CBP. If you opened this page looking for a dashboard Download button, a versioned certificate list, or a share link for a marketplace ticket, those flows are not a shipped product.
What EntryProof does instead
EntryProof is a CPSC eFiling readiness checker. You paste a public product-page URL (and an HTS code when you have one). We fetch the public HTML and score gaps we can see on that page — age-grading language, testing-lab names, manufacturer info, certificate or CFR / ASTM citations, and Prop 65 warnings — plus the applicable v0.7 CPSIA rules for that HTS. The output is a gap index, not a certificate, not a filing, and not clearance. The readiness-score article walks the bands. The free checker is the live tool.
We do not stand in for the importer of record. We do not stand in for a CPSC-accepted laboratory. We do not stand in for counsel. The what we don't do page is the refuse list; this article is the certificate-specific version of the same non-claim.
Who certifies — a non-claim, not advice
CPSC publishes who may certify in 16 CFR Part 1110 on ecfr.gov. The certifier role sits with the manufacturer or the importer of record for the product, not with a software vendor. EntryProof is neither. We will not claim to be the certifier, we will not embed a vendor signature as if we were, and we will not ship a third-party-signed certificate as a product feature.
That is a non-claim about EntryProof. It is not a determination of who must certify your SKU, which certificate type applies, or whether a given document will be accepted. Those questions belong with your importer-of-record process, your broker, and — when the question is legal — counsel. The regulator's field list for certificates of compliance is on the CPSC certificates of compliance guide on cpsc.gov. Children's-product testing obligations, when they apply, are described in 16 CFR Part 1107 on ecfr.gov. We cite those pages so you can read the source. We do not apply them to your shipment.
We do not file
eFiling of certificate data, when required, is a CPSC Product Registry / ACE job. EntryProof does not log into the Registry, does not transmit a PGA message set, and does not certify a filing as complete. Your Registry account is yours. If a marketplace or a broker asks you for a certificate, that request is aimed at the importer of record, not at this help page.
Certificate engine is not shipping as a third-party certifier
There is an internal, gated certificate-engine scaffold in the codebase. It is off. It is not a public download product. It is not being turned on as a way for EntryProof to act as certifier. A gated flag is not a capability you can use, and it is not a promise that a signed PDF will appear later with our name on it.
Older copy on this URL described a download flow, automatic CPC-versus-GCC picking, and a vendor-signed PDF. That copy was wrong. This page replaces it. We are not reconstructing those steps as a how-to, because they are not a product you can run.
What to do instead of looking for a download
- Run the readiness checker on the public listing page you actually sell.
- Read which products need eFiling for scope language, then verify against CPSC's own materials.
- Keep lab reports and any certificate you issue in your archive. EntryProof is not a certificate factory and not a certificate archive. See test reports — what EntryProof does not store.
- File, if you file, in the CPSC Product Registry (or through your broker). We do not file for you.
Related articles
FAQ
Can I download a GCC or CPC from EntryProof? No. That capability is not available. EntryProof does not issue those certificates and does not act as certifier.
Does EntryProof sign certificates? No. We do not sign GCC or CPC documents as certifier. The certifier role described in 16 CFR Part 1110 on ecfr.gov is not a software-vendor role we will claim.
Will you file my certificate data with CPSC? No. We do not file. The Product Registry account and the filing decision stay with the importer of record or their broker.
Is this legal advice? No. Nothing on this page tells you whether your product needs a certificate, which type, or whether a document will be accepted. Read the CPSC sources linked above and use counsel when the question is legal.
Still stuck? Email support@enforceintel.com.