Prepare broker-ready CPSC eFiling data before your shipment arrives
Answer the "am I affected?" questions, collect product and test data from suppliers and labs, generate Full PGA or Reference PGA handoff packets, and track Product ID / Version ID records for future shipments.
Built for importers, Amazon sellers, Shopify brands, and private-label companies preparing regulated consumer products for CPSC eFiling.
Broker or carrier asked for CPSC documents? Start here.
Product packet
Children's Toy Shape Sorter
Packet completeness
86%
CPC/GCC draft
Certificate PDF preview
Full PGA data pack
Seven data elements mapped
Reference PGA pack
Certifier/Product/Version IDs
Request templates
Supplier, lab, broker emails
Shipment moving soon?
If someone asked for CPSC data, handle the next 30 minutes in order.
Check if the shipment is affected
Start with import status, commercial use, product type, carrier request, broker status, and test basis.
Confirm who files CPSC PGA data
Ask the broker, forwarder, or carrier whether they support Full PGA, Reference PGA, both, or neither.
Collect supplier and lab fields
Turn generic certificates and lab PDFs into source-backed fields with missing items clearly marked.
Generate a broker-ready handoff pack
Prepare the Full PGA pack, Reference PGA identifiers, broker email, supplier/lab requests, and checklist.
Why this matters
CPSC eFiling is becoming a broker handoff problem.
Am I affected?
Triage imported vs. domestic, commercial vs. personal, new vs. used, category, HTS confidence, broker status, and timing.
Broker handoff
Prepare Full PGA data packs or Reference PGA identifier packs before your broker asks for CPSC details.
Product Registry prep
Organize Certifier ID, Product ID, Version ID, Product Collection, and CSV draft workflows.
Version tracking
Track Product ID / Version ID status, retesting, material changes, factory changes, and broker handoff dates.
Where CPSCReady fits
Full PGA, CPSCReady, Reference PGA.
Full PGA Message Set
You give your broker the required certificate data for each imported product.
CPSCReady
Prepare Full PGA data packs, Reference PGA identifier packs, request templates, CSV drafts, and missing-data checklists.
Reference PGA Message Set
You enter certificate data into Product Registry and give your broker Certifier ID, Product ID, and Version ID.
CPSCReady does not file ACE entries and does not communicate with CBP systems. If your shipping partner cannot transmit the required CPSC data, confirm a licensed customs broker or trade partner who can.
What this replaces
Less spreadsheet chaos before the broker deadline.
CPSCReady is built around the operational handoff importers actually struggle with: source-backed fields, partner requests, Full PGA/Reference PGA ambiguity, and reusable version records.
How it works
A guided four-step handoff flow.
Start am I affected check
Answer non-sensitive questions to see which CPSC eFiling workflow may be the next step.
Create secure workspace
Create an authenticated workspace before entering importer, lab, supplier, or certificate records.
Build handoff data
Map product, certifier, manufacturer, testing, lab, citation, broker, file-reference, and version fields.
Review, pay, export
Review the readiness score, missing fields, packet preview, and output list before checkout unlocks production exports.
What you get
A handoff system, not just a PDF.
CPSCReady formats your data, flags missing fields, prepares request templates, and keeps the compliance boundary clear before export.
Full PGA data pack
Seven certificate data elements, broker email template, and certificate-data summary for broker Full PGA workflows.
Reference PGA identifier pack
Certifier ID, Product ID, Version ID, Product Collection notes, and Product Registry handoff sheet.
CPC/GCC certificate draft
Certificate draft generated from the product, certifier, manufacture, testing, and citation data you provide.
Product Registry CSV draft
Structured export draft for Product Registry preparation, labeled for review against the current CPSC template.
Named request templates
Supplier/factory data request, lab citation/test-report request, broker handoff email, and carrier clarification email.
Missing-data checklist
Clear resolved, missing, and warning items before you pay for final exports.
Handoff ZIP
PDF, CSV draft, Full PGA pack, Reference PGA pack, request templates, broker summary, and checklist bundled together.
Product ID / Version tracking
Save version status, reason, prior Version ID, effective date, upload date, and broker handoff date.
Before you start
Have your core certificate and handoff data ready.
GCC packets can support N/A lab details when a third-party lab is not the basis for the certificate. CPC packets generally require third-party CPSC-accepted lab data unless a valid exception/exemption applies. Used, resold, or overstock commercial imports may still need certification and eFiling.
Sample packet
Preview the packet before you start.
Review a polished sample with Certificate PDF, CSV draft, Full PGA pack, Reference PGA pack, request templates, broker summary, missing checklist, version history, and ZIP contents.
Broker email preview
Copy-ready handoff language, not just a PDF.
The sample packet includes broker, carrier, supplier, and lab messages so users know exactly what to ask next.
Subject: CPSC eFiling data for [Product ID] / [Shipment]
Hi [Broker Name],
We are preparing CPSC eFiling data for the attached product. Can you confirm whether you want Full PGA data, Reference PGA identifiers from Product Registry, or both?
Pricing
Start with broker-ready handoff data.
Create a secure workspace, enter authorized records, review missing fields, and start checkout when the handoff packet is ready.
Broker-Ready eFiling Data Pack
- am I affected readiness result
- Full PGA data pack
- Reference PGA identifier pack
- CPC/GCC draft
- Product Registry CSV draft
- supplier/lab/broker request templates
- missing-data checklist
5-SKU Importer Handoff Pack
- up to 5 SKU handoff packets
- reusable certifier/importer profile
- reusable lab/manufacturer profiles
- Product ID / Version ID tracker
- combined broker handoff summary
- multi-SKU CSV draft
Managed Product Registry Setup Beta
- separate written approval required
- Product Registry data-entry assistance only
- customer reviews and certifies data
- does not include ACE filing
- not a customs broker service
- limited availability
Fit check
CPSCReady may not be the right next step if...
Trust and security
Private workspace for certificate-data prep.
Packet records and file-reference metadata are stored in your authenticated workspace. The current version records lab-report file names or links for organization, not the underlying lab-report file contents.
Authenticated workspace
Packet records and file-reference metadata are stored in your authenticated workspace.
Metadata only today
The current wizard records lab-report file names or links, not the underlying lab-report file contents.
Authorized records only
Do not provide file names, links, or records unless you are authorized to use them.
Delete workspace records
You can delete saved drafts and file references from your workspace.
No AI training
Packet records and file-reference metadata are not sent to AI models by this app.
No government affiliation
CPSCReady is private software and is not affiliated with CPSC, CBP, Amazon, Alibaba, DHL, FedEx, UPS, or any government agency.
FAQ
Plain boundaries before anyone pays.
Does the readiness check decide whether I am covered?
No. It flags likely workflow fit and missing questions. You remain responsible for determining applicable requirements.
What is the difference between Full PGA and Reference PGA?
Full PGA means your broker transmits full certificate data in ACE. Reference PGA means you enter data in Product Registry and give your broker Certifier ID, Product ID, and Version ID.
Does CPSCReady file ACE entries?
No. CPSCReady does not file ACE entries and does not communicate with CBP systems. Use your customs broker for entry filing.
Does CPSCReady submit Product Registry data?
Self-service exports do not submit data to CPSC or Product Registry. Managed Product Registry setup beta is separate and may involve data-entry assistance only after written importer authorization, review, and approval.
Will failure to eFile automatically deny entry?
CPSC's FAQ says it does not currently intend to ask CBP to deny entry solely because certificate data was not eFiled, but CPSC can still enforce certificate requirements, request seizure of non-compliant products, and use certificate data in risk scoring.