Ask the right operational question
Do not start by asking whether a PDF is enough. Start by asking which CPSC PGA workflow they support.
No-broker mode
If a carrier, freight forwarder, or broker asks for CPSC documents, the first job is to confirm who will transmit CPSC PGA data in ACE.
Audience: Importers whose carrier, freight forwarder, broker, or shipping partner requested CPSC data.
Do not start by asking whether a PDF is enough. Start by asking which CPSC PGA workflow they support.
CPSCReady does not file ACE entries. If your shipping partner cannot transmit required CPSC data, you may need a licensed customs broker or another trade partner.
A broker-ready packet should include the data needed for Full PGA and the identifiers needed for Reference PGA, plus source notes and missing-data flags.
Copy-ready assets
Subject: Clarify CPSC document request for [Shipment/Tracking] Hi [Name], You asked for CPSC documents or data for [Product ID]. Can you confirm exactly what is needed before entry? 1. Are you asking for Full PGA certificate data? 2. Are you asking for Product Registry Reference PGA identifiers: Certifier ID, Product ID, and Version ID? 3. Can your team transmit CPSC PGA data in ACE, or do we need a customs broker? 4. Do you require a spreadsheet, a draft CPC/GCC PDF, or both? 5. What is the deadline for final data before entry? Thanks, [Importer Name]
We are the importer preparing CPSC eFiling data. Before the shipment moves, we need to confirm who can transmit CPSC PGA data in ACE. Do you support Full PGA, Reference PGA, both, or neither? If neither, do you require us to appoint a licensed customs broker? Once a broker is assigned, what product ID, citation, testing, lab, records-contact, shipment, and Product Registry fields should we provide?
Mini FAQ
Maybe not. A PDF may support the record, but the filing partner may need structured Full PGA data or Product Registry identifiers.
Confirm whether a licensed customs broker or another filing partner is needed. CPSCReady does not act as that filing party.
Run the no-broker readiness path and generate a broker request checklist.