Core workflow

Full PGA vs Reference PGA for CPSC eFiling

Choose the right broker handoff path before entry: full certificate data through your broker, or Product Registry identifiers sent to your broker.

Audience: Importers, ecommerce sellers, and operators whose broker asked for CPSC eFiling details.

Check if my shipment is affected View sample handoff packet

Full PGA

Full PGA is the broker-transmitted path where your broker may need the full product certificate data set before entry.

Prepare Product ID, Citation Codes, Manufacture Date, Manufacture Place, Product Test Date, Testing Laboratory, and Point of Contact.

Ask your broker whether they need a specific spreadsheet format or lead time before entry.

Use CPSCReady's Full PGA data pack when Product Registry identifiers are not the planned handoff path.

Reference PGA

Reference PGA is the Product Registry path. You pre-enter certificate data, then send your broker identifiers.

Prepare Certifier ID, Product ID, and Version ID for broker handoff.

Track Product Collection, Product ID type, Version ID, and version status.

Remember that Product Registry does not automatically transmit identifiers to ACE for your entry.

Product Registry availability and participation limits may change; confirm current access directly with CPSC.

How CPSCReady fits

CPSCReady sits before broker filing. It helps you collect, format, and hand off data, while keeping the filing and legal-compliance boundary clear.

Generate Full PGA and Reference PGA handoff packets from the same product data.

Create request templates for suppliers, labs, and brokers.

Flag missing fields before you pay for exports.

Copy-ready assets

Templates you can adapt

Broker workflow confirmation

Subject: Confirm CPSC eFiling workflow for [Product ID]

Hi [Broker Name],

For this shipment, should we prepare Full PGA data, Reference PGA identifiers from Product Registry, or both?

If Full PGA: please confirm your required spreadsheet columns, deadline before entry, and whether you want a draft CPC/GCC attached.

If Reference PGA: please confirm you can file using Certifier ID, Product ID, and Version ID, and whether you need any additional product collection or version-status notes.

Thanks,
[Importer Name]

Internal workflow note

Decision needed: Full PGA vs Reference PGA.

Full PGA pack must include Product ID, Citation Codes, Manufacture Date, Manufacture Place, Product Test Date, Testing Laboratory, and Point of Contact.

Reference PGA pack must include Certifier ID, Product ID, Version ID, Product Collection, Product ID type, and version status.

Mini FAQ

Common questions

Can we prepare both workflows?

Yes. Preparing both is useful when Product Registry setup is in progress or the broker has not yet committed to Full PGA or Reference PGA.

Does Product Registry send identifiers to ACE automatically?

No. The importer still needs to communicate the relevant Product Registry identifiers to the broker or filing partner.

Can we assume Product Registry access will stay available?

No. Availability and participation limits may change. Confirm current Product Registry access directly with CPSC before relying on Reference PGA identifiers.

Next step

Start the am I affected check to see which workflow you should prepare for.

Check if my shipment is affected