01 / 04
Upload the evidence
Drop in supplier certificates, test reports, lab records, product specs, or manufacturing documents.
Built for CPSC eFiling workflows
Turn compliance proof into clean filing data.
Proof2Ship turns supplier and laboratory documents into structured, reviewable CPSC certificate data—then helps importers move that data into the Product Registry without living in spreadsheets.
✓ CPC + GCC workflows✓ Human review before submission✓ Product Registry API architecture
0.0AI found proof
✓ 1 field needs review
Wooden Activity CubeCPC
ProofReviewRegistryBroker
Fields found11
Evidence3
Issues1
Certificate review
Needs reviewSKU WAC-2291 · Version 3
ManufacturerFound
Testing laboratoryFound
Product test dateFound
Manufacture dateMissing
SUPPLIER DOCS→AI EXTRACTION→RULE VALIDATION→HUMAN REVIEW→CPSC PRODUCT REGISTRY
The core idea
AI extracts. Proof2Ship validates. You confirm.
Proof2Ship is designed around a simple boundary: machine extraction can accelerate document work, but certificate data should still be checked by deterministic rules and confirmed by a person before submission.
Learn how the CPSC workflow works →One guided flow
From document pile to structured certificate data.
The screen changes as you scroll—because Proof2Ship should feel like a guided workflow, not enterprise customs software.
Proof2Ship / ReviewStep 1 of 4
Upload the evidence
Drop in supplier certificates, test reports, lab records, product specs, or manufacturing documents.
Supplier test report.pdfReceived
CPC draft.pdfReceived
Product spec.pdfReceived
02 / 04
Extract candidate fields
AI finds likely manufacturer, laboratory, dates, report IDs, product identifiers, and supporting evidence—with source context.
03 / 04
Validate deterministically
Proof2Ship applies CPSC schema, formatting, conditional-field, and completeness checks separately from AI extraction.
04 / 04
Review and submit
A user confirms the evidence, then Proof2Ship builds the Product Registry payload and submits it without auto-certifying by default.
0.0
Built for the messy middle
Less chasing fields. More visible proof.
The product is not trying to replace your broker, lab, or certifier. It is trying to make the handoffs between them much easier to manage.
Proof stays attached
Every extracted value keeps its source context so reviewers can see what document supported it before anything is submitted.
Rules, not guesses
CPSC schema, conditional-field, and completeness checks run deterministically. AI is used for extraction—not the final filing decision.
Product Registry ready
Build CPSC Product Registry payloads, submit imports, poll status, and translate returned errors into a reviewable workflow.
Reusable product records
Keep products, manufacturers, labs, citations, test information, and certificate versions organized for repeat imports.
Broker handoff
Prepare the Certificate Identifiers needed for the Reference PGA path after a certificate is certified in the Product Registry.
Audit-friendly history
Track AI suggestions, user edits, submission payloads, CPSC responses, and certificate status changes in one place.
Built-in boundary
No magic “compliant” button.
Proof2Ship can show whether the data passes the software checks we implement and whether CPSC accepts a Product Registry import. It should not pretend that software alone determines legal compliance.
Avoid
“AI says your product is compliant.”
Legal applicability, testing sufficiency, citation selection, and certification responsibility remain with the appropriate business and authorized professionals.
Use instead
“Your certificate data is structurally ready for review.”
Missing required fields, format issues, evidence provenance, CPSC errors, and outstanding human confirmations stay visible.
0.0
Create an accountProof2Ship Alpha
Start with one product. Prove the workflow.
Upload a sample PDF, review extracted fields, run deterministic checks, and prepare a Product Registry payload. That is the first golden path.