CPSC certificate evidence & change control
CPSC eFiling became mandatory for covered imports on July 8, 2026. The filing step is the easy part — your broker transmits three identifiers. The hard part is upstream: supplier sheets, lab reports, factory changes, and citations scattered across inboxes. We turn that into customer-approved, versioned certificate data with a broker-ready packet and a five-year evidence trail.
Card required to start · $0 for 14 days · cancel anytime in the billing portal.
How it works
Also open — Minnesota PFAS reporting
Minnesota’s Amara’s Law reporting duty covers products manufactured after July 1, 2023. Initial reports are due September 15, 2026; an extension buys until December 14, but the request and fee must be postmarked by August 16. The filing fee is $800 — the cost is in the supplier data behind it.
Certificate data lives in factory spec sheets, two generations of lab reports, component certs, and email threads that disagree with each other.
A fabric supplier changes. A retest happens. Which shipment ships under which certificate version? Most teams can’t answer without an archaeology project.
When CPSC or a buyer asks for the evidence behind a certificate, “let me search my email” is not a records program.
The 2-minute Certificate Data Health Check
Ten questions, a transparent score, and the specific gaps a records request would expose. Nothing to install, nothing uploaded — it runs entirely in your browser. Optionally paste a CSV export to see field-level completeness, including manufacture-date checks.
Take the 2-minute health checkHave a real spec sheet handy?
Drop the CSV on the file analyzer and see exactly which certificate data points it carries and which are missing — the same deterministic mapping rules the platform runs, executed entirely in your browser. The file never leaves your computer.
Analyze a real fileSupplier sheets, lab reports, component testing, emails. Every certificate field gets a source document and an exact provenance reference.
Contradictions (two manufacture dates), missing citations, stale reports — flagged in a queue a human resolves with a recorded rationale. The software never decides applicability.
Internal review and your data approval are separate recorded events. Completed versions are sealed and tamper-evident; changes create new versions.
A broker packet with your Certifier ID, Product ID, and Version ID; a workpaper for the Product Registry; and a zip-ready evidence bundle for the five-year records window.
Certification and filing stay with you and your broker — which rules apply stays your call. CertEvidence does the part underneath: our export adapter is frozen against the official CPSC bulk-upload template (hash-pinned; exports fail closed if that template ever changes), so the workpaper matches the Registry’s own columns and every value in it traces to a source document your team approved. You certify with confidence; we make the data you certify defensible.
Every number below mirrors the live console’s synthetic demo workspace — coverage, exceptions, and sealed versions trace to queries your team could run.
Client area
My dashboard Guided setup Search Notifications 10 Export my data Verify integrity Trust CenterCPSC Certificate Evidence & Change Control · workspace opened 2026-07-24
EVIDENCE PIPELINE · 6 sources → 16 assertions → 2 sealed versions → 2 deliverablesEvidence coverage
100%
9 of 9 required certificate fields, approved with a source
Aged open questions
0
open >30 days · 0 blocking. Unknowns with a next touch are managed.
Changed since sealed
0
approved values that differ from your last sealed snapshot
Needs your attention
Where things stand
| Evidence · documents with hashes | 6 |
| Approved fields | 12 |
| Open exceptions · blocking | 0 |
| Reviewed versions · hash-sealed | 2 |
Render of the console in the new theme, using the live workspace’s synthetic demo numbers. The in-app theme update ships next; trial workspaces may briefly show the previous look. The data model, numbers, and behavior shown are the real product’s.
Explore the sample data and the in-browser tools free, without a card or signup. To work with your own data, start the 14-day free trial: a card starts it, $0 is charged for 14 days, and you can cancel anytime in the billing portal before it ends. Price follows portfolio size, and you will have your number before you are ever charged.
Starter
$750
per month · up to 100 certificate familiesSelf-serve card checkout in the app — $0 for the 14-day trial, cancel anytime. No walkthrough needed to start.
Start free →Growth
$1,750
per month · 101–400 familiesMulti-factory, multi-lab portfolios. Quoted and invoiced after a walkthrough.
Book a walkthrough →Scale
$3,000
per month · 401–1,000 familiesMulti-entity groups and private-label programs. Quoted and invoiced.
Book a walkthrough →Annual prepay: two months free on any tier. Above 1,000 families, we quote it — we will not pretend a number we have not scoped.
Every tier includes
Prefer it done with you? The Certificate Data Rescue reconstructs up to 25 certificate families with field-level provenance, worked to a clean exception queue alongside your team, from the exports you already have. Credited in full against your first twelve months on any tier. Most teams start here — it is a smaller decision than a subscription and it produces the evidence base the desk then maintains.
Fourteen-day free trial on every workspace. A card starts the trial; $0 is charged for 14 days, and if you cancel in the billing portal before it ends you are not charged at all. Your full data export never stops working, including after a trial ends.
Where does each field come from?
Every field links to a source document, page/cell reference, approver, and timestamp.
Can a completed certificate version be edited?
No. Completed versions are sealed (tamper-evident, hash-verified); corrections create linked versions with reasons.
Do you make compliance determinations?
No. Applicability, testing sufficiency, and certification are yours and your qualified reviewer’s; we record those decisions.
What do you retain?
The full evidence bundle and version history for the five-year records window, exportable on demand.
Is my data used to train AI models?
No customer data enters any consumer AI tool. Any model-assisted processing runs under commercial no-training terms — or not at all, at your election.
Your security reviewer will want more than a table. The Security & Trust page lists every control by name with its actual status — shipped, armed at deploy, or not built — plus subprocessors, DPA availability, retention, and an honest statement of where we are on SOC 2. Nothing on it claims more than the code does.
Read Security & TrustTell us what the certificate evidence looks like today — states of chaos welcome.
Every message gets a reply from [email protected]
No newsletter, no sequence.
Prefer email? [email protected] reaches the same person. Please keep confidential details out of a first message.