What Proof2Ship does—and what it deliberately does not do.

Proof2Ship is software for organizing product certificate evidence, extracting candidate data, validating CPSC Product Registry structure, and preparing CPSC eFiling workflows. It is not a testing laboratory, customs broker, or law firm.

No. Proof2Ship can flag missing fields, data-format problems, internal inconsistencies, and CPSC API errors. The importer and authorized certifier remain responsible for determining applicable rules, testing, and certification.

The alpha is designed around PDFs and common document types such as supplier certificates, CPC/GCC drafts, test reports, product specifications, manufacturing records, and supporting lab documentation.

AI extracts candidate facts from your documents and returns structured values with confidence and source context. A deterministic rules engine handles required-field and formatting checks, and a human confirms the result before submission.

Not in the initial architecture. Proof2Ship connects to the CPSC Product Registry. After a certificate is stored and certified there, Certificate Identifiers can be handed to your customs broker for a Reference PGA Message Set in ACE.

The CPSC API can support certification for API users with the Certifier role, but Proof2Ship alpha intentionally defaults to submission without automatic certification. This leaves the record Awaiting Certification for an authorized user.

For the Reference PGA workflow, yes. CPSC also supports Full PGA Message Sets that do not require use of the Product Registry. Proof2Ship alpha is focused on the reusable Product Registry workflow.

The planned authentication layer supports email/password, Google (including Workspace accounts), and Microsoft through the Azure/Entra provider. Enterprise SSO can be added later.

The architecture uses tenant isolation, private object storage, server-only third-party credentials, encrypted CPSC tokens/secrets, signed file access, and audit events. A production launch should also complete an independent security review and incident-response plan.

The product can surface official code tables and suggestions, but it should not silently choose legal classifications. CPSC itself notes that its guidance lists are not all-encompassing, so uncertain classification should be reviewed with the appropriate CPSC, CBP, broker, or legal resource.