Offline field-completeness check against CBP
CPSC eFiling CATAIR Implementation Guide Version 2.5 (22 Jun 2026).
Nothing leaves your browser.
Read this before you use the output
This is a pre-validation aid, not a filing service. It does not
transmit anything to CBP, ACE or CPSC. You still file through ACE yourself.
This is not legal advice and not a compliance determination.
It cannot know whether your product actually complies with any safety rule.
You remain legally responsible. Under 16 CFR 1110.15 the
certifier is responsible for the validity, accuracy and completeness of the
certificate. A pass here changes nothing about that, and no part of it transfers
to us.
A "no errors" result is not a compliance certificate. It means no
defect was found in the shape of the data you pasted. It cannot confirm your
product is safe, tested, or correctly certified.
16 CFR 1110.13(a)(1) requires the certificate data to be filed
"as provided in CPSC's PGA Message Set CATAIR Implementation Guide (including revisions
thereto)". Final rule 90 FR 1800 (8 Jan 2025), applicability
8 Jul 2026; correction 90 FR 45917 (24 Sep 2025).
JSON: an array of records, or an object with a records array.
CSV: long format with a recordType,fieldName,value header. Use a row
RECORD,PG19, to start a second record of the same type.
What this tool cannot verify
These are stated plainly rather than hidden. A tool that quietly skips checks is worse
than one that admits it.
The rules it does check
Field layouts and cross-record rules, with guide page references
This page runs entirely in your browser: no network requests, no accounts, no payment,
no analytics. Reloading loses your draft, so copy it out before you close the tab.