ComplyMyImport guide
How to prepare broker-ready CPSC certificate data
Broker-ready data is approved, structured, versioned, and mapped to the actual shipment. A folder containing certificates and test reports may be useful background, but it is not a complete filing handoff.
Start from an approved certificate
Do not export filing data from an incomplete draft. Confirm the product identity, applicable citations, manufacturing details, testing details, laboratory information, and records contact. Preserve who approved the certificate and when.
Choose the required payload
For a Full PGA Message Set, provide the required certificate data elements in the broker's supported structure. For a Reference PGA Message Set, provide the Certifier ID, Product ID, and Version ID that match the approved Product Registry record.
Add shipment mapping
Connect the filing payload to:
- Importer and shipment reference
- Purchase order and commercial invoice
- Entry-line product description
- SKU, model, and variant
- Certificate version
- Filing-path selection
The mapping should let the broker identify the correct data without guessing from similar product descriptions.
Validate before delivery
Check required formats, controlled codes, dates, addresses, and identifiers. Confirm that no product or certificate change invalidates the selected version. Use a package identifier and timestamp, and deliver through an agreed secure channel.
Close the loop
Obtain acknowledgement, validation results, transmission status, rejects, corrections, and ACE response through the broker process. Keep the exported package immutable and create a new version for corrections.
ComplyMyImport can generate a controlled package from approved product records and log the export. Export does not mean transmitted, accepted, or cleared.
This guide is general educational information, not legal or customs advice.