Why did Amazon reject my CPC certificate?

A Children's Product Certificate is not a generic pass. Under Section 14 of the Consumer Product Safety Act, codified in 16 CFR part 1110, a CPC must contain seven specific elements — including a description of the product it covers, each children's product safety rule it is certified to, and the CPSC-accepted laboratory that tested it. A certificate that is missing or vague on any of those is deficient, even if a supplier produced it in good faith.

That is why a rejection is usually not "you need a certificate you don't have" — it is "the certificate you have doesn't do what a CPC has to do." The fixes below all come back to the required elements.

One of the required elements is an identification of the product the certificate covers. A CPC issued against a supplier's internal product name, an old model, or a whole product family may not clearly cover the specific item being sold. A marketplace that matches the certificate against a listing — the product name, model number, and brand — will flag the mismatch, and the underlying reason it can is that the CPC is supposed to identify that exact product in the first place.

Amazon's own CPC policy adds a marketplace-specific rule on top: if an ASIN appears on the certificate it has to match the listed ASIN exactly, and an ASIN on the CPC takes precedence over every other identifier — so a certificate carrying a wrong or stale ASIN is sent back even when the model number is right.

A CPC is required for a children's product: one designed or intended primarily for children 12 or younger that is subject to a children's product safety rule. Whether something meets that definition is not the seller's label alone — 16 CFR part 1200 weighs four things: a manufacturer's statement about the intended use, how the product is packaged and advertised, whether consumers commonly recognize it as for a child 12 or under, and the Commission's Age Determination Guidelines. A product not marketed to children can still fall inside the definition, which is how a seller ends up needing a CPC they did not expect.

A children's product cannot be certified on a manufacturer's own testing. A CPC must rest on results from a CPSC-accepted third-party laboratory, and the certificate has to identify that lab. A test report from a laboratory that is not on CPSC's accepted list — even a real, competent lab — does not support a valid CPC. This is one of the quieter rejection causes, because the paperwork looks complete until the lab is checked against the accepted list.

Because CPSC does not issue certificates — the importer does. Under 16 CFR 1110.7, the party that must issue the certificate for an imported product is the importer (for a domestically made product, it is the U.S. manufacturer). A document a supplier hands over with its own name in the certifier field is not, by itself, the certificate the rule requires: the legal duty to certify rests with the importer, and it does not transfer just because a factory produced a piece of paper that looks like one. The one case where a factory's certificate does count is where the factory is itself the importer — the rule turns on who imported the product, not on where the certifier is based, and Amazon's policy states plainly that the importer on a CPC can be a domestic or a foreign company. What a marketplace will not accept is itself in the certifier field: Amazon may not be listed as importer, record holder, or any other responsible party.

That is why a marketplace or a broker so often rejects a supplier-provided certificate even when one exists. A valid children's-product certificate has to be issued by the importer, identify the exact product, name each safety rule, and rest on testing from a CPSC-accepted laboratory — and factory-issued paperwork frequently misses one of those, most often by naming a party that is not the importer as the certifier or citing a lab that is not on CPSC's accepted list. Reissuing the certificate with the importer as the certifying party, on accepted-lab testing, is what turns a rejected supplier document into a compliant CPC.

Because the whole children's-product determination turns on the intended age, an inconsistency in age grading undermines the certificate. If the certified age range and the age stated on the listing or packaging disagree — a certificate that says one age band while the product is sold as another — that gap alone can be enough to reject, since it puts the certification and the product in different categories.

A CPC can be internally correct and still be rejected because it does not line up with the other documents in the shipment. A marketplace or CBP does not read the certificate in isolation — it cross-checks the product, model, brand, and age range on the CPC against the commercial invoice, the third-party test report, and the label. When the manufacturer name on the certificate does not match the invoice, or the model on the test report does not match the CPC, the submission gets flagged — and the rejection notice often does not say which document caused it, which is what makes these loops so hard to break.

This is a document-consistency problem, not a testing problem: the certificate, the test report, and the entry paperwork each have to describe the same product the same way. The free Broker-Ready Document Check compares the certificate's product identifier — its model or SKU — and its certifying party against the invoice, alongside the quantities, values, parties and dates across the whole set, and flags the mismatches — the same cross-document read a broker does before an entry is filed.