CertEvidence

Certificate Data Health Check

Ten questions, about two minutes. You get a transparent score, the specific gaps a records request would expose, and what fixing each one looks like. Everything runs in your browser - nothing is uploaded, nothing to install.

Before you start

CPSC eFiling became mandatory for covered imports on July 8, 2026. Your broker transmits three identifiers; the evidence behind them - lab reports, manufacture dates, citations, supplier documents - stays your responsibility. This check measures whether that evidence would hold up when someone asks for it. Official CPSC eFiling hub.

Answer for your covered-import portfolio as it is today, not as you plan it to be. Nothing you enter leaves this page.

Optional: check a real CSV against certificate fields

Paste rows exported from wherever your product data lives (spreadsheet, ERP export). The check looks for columns resembling the fields a certificate depends on - product name, SKU, manufacture date, testing lab, lab report ID, rule citations - and shows you what is present, what is missing, and which dates will not parse. Header names are matched loosely ("mfg date", "report no", "style number" all work).

Your data never leaves this page - nothing is uploaded. Parsing happens entirely in your browser; close the tab and it is gone.

Dates referenced on this page

DateWhat it isSource
Jul 8, 2026Mandatory CPSC eFiling effective for covered imports (now in effect) Federal Register correction
Jan 8, 2027eFiling applicability for imports from foreign-trade zones (FTZs) Federal Register correction

The CPSC Product Registry is free and supports individual entry, CSV upload, and API; your broker files the ACE PGA Reference message using Certifier, Product, and Version IDs (CPSC eFiling for importers, for brokers). Regulatory state drifts - verify against the official source before relying on any date here.