Broker packet

What to send your broker for CPSC eFiling

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

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

Check if my shipment is affected View sample packet

Ask what they need to enter

The packet changes depending on whether your broker needs all certificate details, Product Registry ID numbers, or both.

If they need all certificate details: send Product ID, CPSC rule codes, manufacture date/place, product test date, testing lab, and records contact.

If they need Product Registry ID numbers: 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 packet 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 rule 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 customs entries.

CPSCReady does not classify tariff codes.

CPSCReady prepares packet outputs for review.

Copy-ready assets

Templates you can adapt

Broker packet cover email

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

Hi [Broker Name],

Attached is our CPSC eFiling packet for [Product Name]. It includes the product and certificate details, draft CPC/GCC summary, missing-data checklist, and Product Registry ID numbers if Product Registry is used.

Please confirm:
- Whether you need all certificate details, Product Registry ID numbers, or both
- Your required spreadsheet format
- Any missing fields before entry
- The final cutoff for updates

Thanks,
[Importer Name]

Fields to confirm before shipment

Product ID and product ID type
Rule 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 Product Registry is used
Broker deadline and preferred file format

Mini FAQ

Common questions

Should the broker get both a PDF and structured data?

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

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