Broker handoff

What to send your broker for CPSC eFiling

A practical checklist for turning product, lab, citation, and Product Registry records into a broker-ready CPSC eFiling handoff.

Audience: Importers whose customs broker asked for CPSC certificate data or Product Registry identifiers.

Check if my shipment is affected View sample handoff packet

Ask which message set they want

The handoff changes depending on whether your broker will file Full PGA data or Reference PGA identifiers.

Full PGA: send Product ID, Citation Codes, Manufacture Date, Manufacture Place, Product Test Date, Testing Laboratory, and Point of Contact.

Reference PGA: send Certifier ID, Product ID, and Version ID from Product Registry.

Ask whether the broker requires a spreadsheet, PDF certificate draft, or both.

Send source-backed data

Broker handoff data should trace back to supplier, manufacturer, lab, certificate, or Product Registry records.

Include lab report number, test date, lab legal name, lab address, and phone.

Associate each citation with the supporting report or exception/exemption note.

Flag missing data instead of guessing.

Keep the boundary clear

Your broker may file entry data, but you remain responsible for certificate accuracy and applicable product requirements.

CPSCReady does not file ACE entries.

CPSCReady does not classify HTS codes.

CPSCReady prepares handoff outputs for review.

Copy-ready assets

Templates you can adapt

Broker handoff cover email

Subject: CPSC eFiling handoff data for [Product ID] / [Shipment]

Hi [Broker Name],

Attached is our CPSC eFiling handoff packet for [Product Name]. It includes the Full PGA data pack, draft CPC/GCC summary, missing-data checklist, and Reference PGA identifiers if Product Registry is used.

Please confirm:
- Whether you will file Full PGA, Reference PGA, or both
- Your required spreadsheet format
- Any missing fields before entry
- The final cutoff for certificate-data updates

Thanks,
[Importer Name]

Fields to confirm before shipment

Product ID and product ID type
Citation codes and supporting report or exception note
Manufacture date and place
Product test date
Testing laboratory legal name, address, and phone
Point of contact for records
Certifier ID, Product ID, and Version ID if Reference PGA is used
Broker deadline and preferred file format

Mini FAQ

Common questions

Should the broker get both a PDF and structured data?

Ask. Some workflows need a PDF for review and structured fields for filing. CPSCReady prepares both styles so the broker can confirm the format.

Should missing data be hidden?

No. Flag unknown fields instead of guessing, then resolve them with suppliers, labs, brokers, or qualified advisors.

Next step

Prepare a broker-ready data pack before your broker deadline.

Check if my shipment is affected