Reduce Importer-Client Handoff Rework Without Changing Broker Judgment
Synthetic training examples are clearly labeled. Official instructions and responsible professional decisions remain controlling.
Narration
When a broker has to chase an importer for missing product facts, the problem often starts before the entry workflow. The client may send a folder of reports, an old certificate, two product identifiers, and an email that says the shipment is urgent. The broker still has to decide what is usable and what belongs in the ACE filing. CertifyPreflight is designed to improve the handoff without changing that professional judgment.
The workflow is deliberately divided. The importer owns the product and certificate source facts. CertifyPreflight organizes candidate values, their provenance, missing items, and conflicts. An authorized user reviews and approves any allowed Product Registry action. The broker or other authorized filer separately decides how to prepare and transmit the ACE PGA Message Set. Product Registry activity and ACE filing remain distinct.
Here is a simulated example. A fictional importer sends a certificate labeled model LMP-220, a report labeled LMP-220B, and an invoice using SKU NORTH-22. The certificate lists Bright Harbor Manufacturing, but the invoice lists Bright Harbor Products. The email asks the broker to “use the CPSC number,” yet no current Certifier ID, Product ID, or Version ID is included. Nothing here proves which value is correct.
In the prepared view, those competing values remain visible instead of being silently overwritten. Each candidate points to a file, page, or quoted source. Missing current Registry identifiers are marked as missing. The unresolved questions ask the importer to confirm the exact product identity, factory record, and filing path. The broker receives a fixed case snapshot rather than an editable copy of the importer’s underlying record.
Authority stays visible throughout the workflow. A customer-authorized Product Registry action requires an explicit request. Import and certify is available only when CPSC returns the exact Certifier role and the signed-in user provides a second certification-specific authorization. Without that role, the safe path is import-only for later certification. None of those actions performs the broker’s separate ACE transmission.
The broker can review the shared snapshot, leave a timestamped note, request a change, or mark review status. Those actions are separate records. They do not rewrite the importer’s case, certify the product, authorize a CPSC submission, or decide customs treatment. The broker retains the client relationship, professional judgment, and responsibility for the separate ACE filing process.
CertifyPreflight currently offers two truthful collaboration paths. A broker may participate in one importer-paid case through a limited invitation. A brokerage may also discuss assisted Organization Access under a written scope. Firm-wide self-service administration, automatic seat management, automated billing, portfolio reporting, and custom integrations are not advertised as live capabilities.
To review the workflow, visit CertifyPreflight dot com slash partners slash brokers. Choose “Collaborate on a client’s paid case” for a specific importer matter, or “Use CertifyPreflight across your brokerage” to discuss the assisted firm path. CertifyPreflight does not replace a broker, decide customs treatment, transmit the ACE entry, provide legal advice, or guarantee acceptance or release.
Meaningful visual descriptions
1. Rework Starts Upstream
On screen: The filing decision still belongs to the broker. Scattered client facts; Unclear source ownership; Repeated follow-up.
Source card: CPSC broker resources · reviewed Oct. 8, 2026.
2. A Cleaner Workflow
On screen: Prepare → review → authorize → hand off. Importer owns the source facts; Broker retains judgment; ACE remains separate.
Source card: CPSC importer + broker resources.
3. Before
On screen: A fictional client sends a folder and an email. Two product IDs; Factory name conflicts; No current Registry IDs.
Source card: Simulated example.
4. After
On screen: One fixed, source-linked case snapshot. Provenance beside each value; Missing items are explicit; Unresolved questions stay visible.
Source card: Simulated example.
5. Authority Stays Visible
On screen: Every system action has a named owner. Importer authorizes Product Registry action; Exact Certifier role gates certification; Broker controls the ACE transmission.
Source card: CertifyPreflight capability register.
6. Broker Review
On screen: Review notes do not rewrite the client record. Comment; Request a change; Mark review status.
Source card: CertifyPreflight verified capability.
7. Two Ways To Collaborate
On screen: Choose the bounded path that fits. One importer-paid case; Assisted Organization Access; No partnership claim.
Source card: Current /partners/brokers offer.
8. Next Step
On screen: Keep professional judgment where it belongs. Collaborate on a client’s paid case; Use CertifyPreflight across your brokerage; certifypreflight.com/partners/brokers.
Source card: Independent software · no ACE filing.
Official sources
- CPSC eFiling Resources for Brokers
- CPSC eFiling Resources for Importers
- CPSC Product Registry FAQ V1.4
- CPSC Product Registry User Guide V3
Sources reviewed October 8, 2026.