CPSC Product Registry vs full PGA message set: two ways to eFile certificate data

For 2026 eFiling, importers can file certificate data in full at entry or reference a record in CPSC's Product Registry. How each works and what to prepare.

The problem

Under the revised 16 CFR part 1110, importers of CPSC-regulated products must electronically file certificate data with CBP at entry (most imports from July 8, 2026; Foreign Trade Zone entries from January 8, 2027). Filers can submit the full certificate data in the CPSC PGA Message Set, or create the certificate in CPSC's Product Registry and reference it at entry.

The Registry suits sellers who import the same product repeatedly: the certificate is entered once and referenced on each entry. Your customs broker files the entry, so they need your certificate data or Registry reference in advance.

How to fix it

List every SKU you import that needs a CPC or GCC.
Ask your broker which method they support (full message set or Product Registry reference).
If using the Registry, create a certificate record for each distinct product and share the reference with the broker.
Update the record when anything material changes (design, materials, factory, test).
Check CPSC's eFiling FAQ for current technical guidance.

Check your documents before you resubmit

Upload your CPC or GCC and the test report. The free pre-check compares identifiers, cited rules, lab, dates and certifier across the documents and returns a red/amber/green list of what to fix.

Run the free pre-check

Checklist before resubmitting

SKU list with certificate per product
Broker method confirmed
Registry records created (if used)
Process for updates

Sources

This is general information and a document consistency check only. It is not certification, testing, or legal advice, and it cannot guarantee acceptance by Amazon, CPSC or CBP.