The Children's Product Certificate (CPC) for your product

Children's Product Certificate — what it must contain, who issues it, and where to keep it in Aleph.

A Children's Product Certificate (CPC) certifies, based on testing by an accredited third-party lab, that a children's product complies with each children's product safety rule that applies to it (15 U.S.C. 2063(a)(2)). For a product made outside the United States, the importer issues it (16 CFR 1110.7(a)).

What the certificate must contain (16 CFR 1110.11(a), as revised effective July 8, 2026):

  1. Product identification — at least one identifier (GTIN, model number, registered number, serial number, SKU, UPC, or an alternate identifier) and enough description to match the product to the certificate
  2. Each applicable rule — every rule, ban, standard, or regulation the product is certified to, listed separately
  3. The certifier — name, street address, city, state or province, country, email, and telephone number
  4. The records custodian — the same contact details for the person (or always-staffed position) who keeps the test records
  5. Date and place of manufacture — month and year at a minimum, and the manufacturer's name, full address, email, and telephone number
  6. Date and place of testing — the most recent testing, and each third-party lab relied on, with its name, address, email, and telephone number
  7. The attestation — the certifier's statement, in the wording the rule sets out, that the products comply and the information is true and accurate

In Aleph, the Children's Product Certificate box on the product's Compliance tab holds the certificate as data. Filling it in, attesting it, printing it and downloading it for the CPSC Product Registry work the same way for a CPC and a GCC, so those steps are in one article in Aleph's Help, for signed-in customers: Your CPC or GCC in Aleph, part by part. Sending a certificate straight from Aleph to your CPSC Product Registry is coming soon.

If you issued the CPC elsewhere, upload it with the lab reports using Upload document, then record on the Required records list that you issued it and hold it on file. Either way, upload the lab reports it relies on. A report you upload can be filed under more than one of the product's modules, but filing it there doesn't mean it meets another regulation's testing requirement. A CPSIA lab report tests to CPSIA rules, not to Prop 65 or state PFAS laws.

The certifier "must furnish the required finished product certificate to each distributor or retailer of the finished product" (16 CFR 1110.13(b)) and make it available to CPSC or CBP "within 24 hours" of a request (16 CFR 1110.13(c)); a paper or electronic copy must be in English (16 CFR 1110.9(a)). Aleph's Download certificate (PDF) prints that copy; it does not replace eFiling at entry.

WARNING: A CPC has no fixed 12-month life, but it must stay backed by current testing. Periodic third-party testing is due at least once a year, or once every two or three years under the options in 16 CFR 1107.21. A material change to the product's design, manufacturing process, or component sourcing that could affect compliance requires new testing and a new CPC (16 CFR 1107.23(a)).