CPSC eFiling is now in effect for most covered imported consumer products. FTZ products follow January 8, 2027.
CPSCReady
Required CPSC eFiling, simplified

Don't Let Missing CPSC Data Delay Your Shipment

Answer a short shipment check, add your product and test records, and download a broker-ready export package for your filing partner.

Get startedCheck if my shipment is affectedView sample packet
packet.console

Product packet

Toy Shape Sorter

86%
Certificate detailsReady
Product Registry IDsNeeds IDs
Export packageMapped
Built forImportersAmazon sellersShopify brandsPrivate-label teams
Scope notes
Private software for generating CPSC export packages, broker-ready files, and review-ready source notes.

Broker request playbook

Turn a vague CPSC document request into the files your broker needs.

CPSCReady helps you choose the right export path, fill the source record, and close missing fields before you send your broker, carrier, supplier, or lab another email.

Get startedStart the request checkCarrier asked for documents

Request triage

What to clarify first

Broker-ready
01

Choose the export path

Translate "send CPSC documents" into certificate details, Product Registry ID numbers, or both.

02

Fill the product record

Add the supplier, lab, product, manufacturing, rule, and records-contact details needed for that export.

03

Generate the files

Download the broker summary, certificate details, Product Registry CSV draft, ID notes, request templates, and ZIP package.

Why this matters

Required CPSC eFiling is complicated. CPSCReady makes it manageable.

Importers need to know what applies, what records support it, what the broker is asking for, and what is still missing. CPSCReady turns those moving parts into a clear export package.

Required eFiling, without the scramble.

CPSCReady turns records, broker questions, Product Registry IDs, and missing fields into downloadable files before the shipment deadline.

Required eFiling

Turn the new import filing requirement into a clear checklist

Full or reference

Map what your broker is actually asking for

3 registry IDs

Track Certifier ID, Product ID, and Version ID together

One ZIP export

Package the PDF, CSV draft, broker text files, and checklists your partner needs

Where CPSCReady fits

Add your records. Generate the broker-ready export.

Some partners ask for all certificate details. Others ask for Product Registry reference IDs. CPSCReady turns your source records into reviewable exports for either path: broker text files, registry notes, CSV drafts, request templates, and a ZIP package.

Review the export, then send it to your licensed customs broker or filing partner for entry filing and final shipment coordination.

Supplier records
Lab reports
Product facts
Rule citations

Export builder

CPSCReady

builds PDF, CSV draft, broker text files, registry ID notes, templates, and ZIP exports

Certificate details export

Use this when your broker asks for Full PGA data: product identity, rules, manufacturer, testing, lab, and records contact.

Product Registry ID export

Use this when your broker asks for Reference PGA data: Certifier ID, Product ID, Version ID, and registry notes.

Certificate details fileRegistry CSV and IDsBroker summary ZIP

Assisted filing prep

Prefer not to enter every field manually?

Choose managed prep, upload your documents, and an account manager will prepare the CPSCReady packet fields into a packet data package for your review.

See assisted optionStart with document upload

CPSCReady prepares packet records and broker-ready outputs. Importers still review accuracy and use qualified advisors or brokers for legal, compliance, customs, tariff, and filing decisions.

Managed path

Documents in. Packet out.

Human support

Upload what you have

Add supplier spreadsheets, lab reports, certificates, broker emails, product photos, labels, invoices, or ZIP files after checkout.

Account manager organizes it

Your account manager uses CPSCReady tools to prepare packet fields, flag missing data, and coordinate follow-up by email.

Review the packet

Review the prepared packet data package before sending outputs to your broker or filing partner.

Accepted intake examples

PDFsCSVsExcelWord docsImagesZIP filesBroker emails

What this replaces

Replace document chasing with one export-ready product record.

The product record answers the operational questions importers actually struggle with: which export path applies, which records support each field, what is missing, and what has to be reused on the next shipment.

BeforeWith CPSCReady
One-off certificate templatesOne guided packet that creates the broker-ready export files
Spreadsheet columns from supplier emailsSource-backed product, lab, rule, and manufacturing data in export format
Repeated partner follow-up threadsCopy-ready request emails plus a final broker summary
Untracked repeat-shipment changesProduct ID and Version ID history carried forward by product
Guessing what the broker meansA clear choice: certificate details, Product Registry IDs, or both

How it works

From scattered records to downloadable export files.

The workflow is built around the files importers need to send: what the broker is asking for, what records support it, what is missing, and which export is ready to download.

01

Pick the filing package

Answer the practical questions that decide whether you need certificate details, Product Registry IDs, or a combined export.

Export path

02

Add the product data

Bring importer, supplier, lab, manufacturer, rule, test, file, and contact details into one guided record.

Product record

03

Fix gaps before download

See missing fields, warning items, and request templates while there is still time to ask the right partner for evidence.

Ready check

04

Download the export package

Generate the PDF, CSV draft, broker summary, certificate details, registry ID notes, request templates, and checklists.

ZIP export

What you get

The export package your filing partner needs.

When required fields are complete, CPSCReady packages the practical files around your product: broker summary, certificate details, Product Registry CSV draft, registry ID notes, request templates, and checklists.

One guided packet that creates the broker-ready export files
Source-backed product, lab, rule, and manufacturing data in export format
Copy-ready request emails plus a final broker summary

Export package status

86%

Readiness

Mapped

Broker data

Tracked

Version status

Broker-ready files

  • Broker summary
  • Certificate details text file
  • Broker email language

Product Registry files

  • CSV draft
  • Certifier/Product/Version ID notes
  • Collection and review notes

Review controls

  • Missing-data checklist
  • Supplier and lab request templates
  • Product version history

ZIP export

  • CPC/GCC certificate draft
  • PDF and CSV package
  • Source notes and checklists

Before you start

Have your core certificate and filing-partner 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 or exemption applies. Used, resold, or overstock commercial imports may still need certification and import filing.

Product identity

  • Product name and product ID
  • ID type: GTIN, SKU, UPC, Model Number, Serial Number, Registered Number, or Alternate ID
  • Company responsible for the import, if known

Certificate support

  • Importer or domestic manufacturer information
  • Records contact
  • Manufacture date and place
  • Applicable CPSC rules or standards from your records, lab report, or qualified advisor

Testing and lab records

  • Test date and test location, if applicable
  • Lab name, address, and phone, if applicable
  • Test report PDF, if available

Filing partner request

  • Whether the broker needs certificate details, Product Registry IDs, or both
  • Certifier ID, Product ID, and Version ID, if Reference PGA-style data is requested
  • Shipment timing and broker or carrier contact, if known

Sample packet

Preview the broker-ready export before you start.

Review a polished sample with certificate PDF, CSV draft, broker-ready certificate details, Product Registry ID numbers, request templates, broker summary, missing checklist, version history, and ZIP contents.

View sample export

Broker email preview

Copy-ready request language for the next email.

The sample packet includes broker, carrier, supplier, and lab messages so users know exactly what to ask next.

Subject: CPSC import filing data for [Product ID] / [Shipment]

Hi [Broker Name],
We are preparing CPSC data for the attached product. Can you confirm whether you need all certificate details, Product Registry ID numbers, or both?

Trust and security

Private handling for CPSC import-data records.

Packet records and uploaded files are stored in your authenticated workspace. File metadata is used to organize export drafts and missing-data checks. Packet records and uploaded files are not sent to AI models by this app.

Authenticated record storage

Packet records and uploaded files are stored in your authenticated workspace.

File organization

File metadata is used to organize export drafts and missing-data checks.

Authorized records

Upload records you are authorized to use for export generation and broker-ready files.

Delete saved records

You can delete saved drafts and uploaded files from your account.

Private packet handling

Packet records and uploaded files are not sent to AI models by this app.

Independent software

CPSCReady is private preparation software for organizing broker-ready CPSC import records.

FAQ

Clear answers before you start.

How should I use the readiness check?

Use it to identify likely next steps, open questions, and the records to confirm with your broker or qualified advisors.

What do Full PGA and Reference PGA mean?

They are broker terms for two different requests. Full PGA usually means the broker wants all certificate details for the product. Reference PGA usually means you entered the details in CPSC Product Registry and now need to give the broker Certifier ID, Product ID, and Version ID.

How do customs filings fit into the workflow?

Prepare the packet in CPSCReady, then review and send the generated export package to your licensed customs broker or filing partner for entry filing.

How does Product Registry setup fit?

Self-service exports prepare Product Registry ID notes and CSV drafts. Assisted prep can help organize uploaded records and packet fields after managed checkout, but importer review and approval are still required.

Can I upload documents instead of entering every field myself?

Yes. The assisted prep path lets you upload source records after managed checkout so an account manager can organize packet fields, prepare broker-ready outputs, and coordinate missing-data questions by email.

Will failure to eFile automatically deny entry?

CPSC's FAQ says certificate data may still be used in enforcement and risk scoring. Keep source records and generated export details organized before shipment.

Fit check

Before you rely on a packet

CPSCReady works best when source records, product scope, and filing responsibilities are clear enough for broker review.

Confirm whether your product is CPSC-regulated.
Identify CPSC rules or standards from your records, lab report, broker, or qualified advisor.
Collect test reports, a reasonable testing basis, or documented exception/exemption support.
Use qualified legal or compliance advice when product scope depends on facts.
Confirm the customs broker or filing partner for the entry.
Review certificate accuracy before sending records to a broker.
Confirm tariff classification and clearance details with your broker or trade advisor.