Importer evidence stays fixed
The invitation exposes a time-limited case snapshot. A broker cannot edit the importer’s source record or access unrelated workspaces.
For licensed customs brokers and compliance teams
Review the importer’s evidence trail before the separate ACE filing.
CertifyPreflight helps an importer organize CPSC certificate information, preserve its sources, expose unresolved conflicts, and invite a broker into a controlled review before the separate ACE filing.
The walkthrough is a professional-feedback conversation, not a partnership or purchasing commitment.
A clearer division of work
The importer prepares the record. The broker keeps control of the filing.
The purpose is not to replace broker judgment. It is to move source tracing, obvious gap identification, and importer follow-up earlier—before the filing desk has to rebuild the case.
Broker feedback stays separate
The invited broker can add notes, request changes, and record that a review occurred without changing the underlying evidence.
Submission authority is not implied
Accepting an invitation does not authorize Product Registry certification or an ACE transmission. Those actions retain their separate role and authorization gates.
ACE remains with the filing professional
CertifyPreflight does not transmit the broker’s PGA Message Set. The broker or authorized filer controls the separate ACE entry using the reviewed data or Registry identifiers.
How the 14-day review works
Importer prepares
Evidence is reviewed, conflicts remain visible, and a fixed snapshot is created.
Broker is invited
One named business email receives access to that snapshot for 14 days.
Identity is checked
The broker signs in with the invited address and two-step verification.
Feedback returns
Notes, change requests, and review completion are recorded separately for the importer.
Help shape the broker workflow
Would this reduce importer-document rework for your team?
We are looking for practical feedback from licensed brokers and compliance leads. The first conversation is about the handoff, common importer mistakes, and what would have to change before your team would trust the workflow.