When CPSC eFiling becomes mandatory on July 8, 2026, importers will submit certificate data electronically at the time of import. But what data, exactly? This is a plain-English rundown of the data elements eFiling actually requires and where the all-important citation codes come from.
Key takeaways
- An eFiling ties a physical good to its proof of compliance using a small set of data elements.
- The core identifiers are a Certifier ID, a Product ID, and a Version ID.
- Citation codes name the specific mandatory standards your product meets — they come from your lab’s results summary.
- Tracking data — batch number, manufacture date, and place of manufacture — is required and is run-specific.
Free download: Get the CPSC eFiling Watchlist Guide — the ~600 HTS codes CPSC flags as likely regulated, the certificate data elements, and how to disclaim. Download the list →
The data elements CPSC eFiling requires
At its core, an eFiling connects what you ship to the report and certificate that prove it complies. That connection is made with a handful of data elements:
- Certifier ID — identifies the party issuing the certificate (you, the importer or certifier).
- Product ID — a unique identifier for the product. Accepted types include a UPC/GTIN, SKU, or model number.
- Version ID — distinguishes versions of the same product so the right record is matched.
- Product description — enough detail to match the physical good to its certificate.
- Citation code(s) — the specific mandatory standards the product is certified against.
- Tracking information — a batch or run number, the date of manufacture, and the place of manufacture.
- Linked test report — the accredited-lab report (where testing is required) that backs the certificate.
New to the registry? Begin with the CPSC self-registration page to create your account. For a full screen-by-screen walkthrough of where each of these is entered, see our 7-step CPSC Product Registry eFiling walkthrough.
Where citation codes come from
Citation codes are the part importers most often ask about. A certificate has to reference the specific mandatory standards and rules that apply to the product — and you do not invent these. When a product is tested, the laboratory provides a results summary that contains the necessary citation codes, and often a blank certificate for you to complete using those results. Common examples include 16 CFR 1303 (lead in paint), 16 CFR 1501 (small parts), and ASTM F963 (toy safety). The CPSC Regulatory Robot will also surface the citations that apply when you classify a product.
Tracking data is run-specific
Every CPSC-regulated product carries tracking information, and it is tied to the production run rather than the certificate. Each run gets its own batch number and lists the actual date it was made, along with the place of manufacture. If you reorder the same product without a material change, the certificate and its date of manufacture stay the same — only the batch number and production date on the tracking label change.
CPC vs. GCC vs. Disclaim, in one minute
The data elements you file depend on which path your product takes. Children’s products need a Children’s Product Certificate (CPC) backed by accredited testing. Non-children’s products subject to a CPSC rule need a General Conformity Certificate (GCC). And products with no applicable CPSC rule require a Disclaim filing — because under eFiling, having nothing to submit is not the same as submitting nothing. If you are unsure which applies, start with whether your product is subject to CPSC, then confirm the July 8, 2026 mandate timeline.
Download the CPSC eFiling Watchlist Guide (free)
Frequently asked questions
What are the core data elements in a CPSC eFiling?
A CPSC eFiling typically includes a Certifier ID, a Product ID (such as a UPC, SKU, or model number), a Version ID, a product description, the applicable citation codes, tracking information (batch number, manufacture date, place of manufacture), and a linked test report where testing is required.
What is a Product ID in the CPSC Product Registry?
A Product ID is a unique identifier for the product. Accepted types include a UPC/GTIN, SKU, or model number. Each sellable color or variation should carry its own identifier under the certificate.
Where do CPSC citation codes come from?
Citation codes name the specific mandatory standards your product meets. They come from the testing laboratory’s results summary, and the CPSC Regulatory Robot also surfaces the citations that apply when you classify a product. Examples include 16 CFR 1303, 16 CFR 1501, and ASTM F963.
Is tracking information tied to the certificate or the production run?
It is tied to the production run. Each run has its own batch number and actual manufacture date on the tracking label, even when the certificate and its date of manufacture stay the same.
