CPSC eFiling · Product Registry

How to use the CPSC eFiling CSV template without avoidable upload problems.

The template is the starting point for bulk certificate-data entry. Use this guide to keep the CSV itself clean, consistent, and ready for your final review.

01

Download the current official template

CPSC publishes the current bulk-upload template and CSV Upload Guide in the eFiling Document Library. Start there for every upload project because the template and guidance can change.

02

Keep the header row intact

The template’s column names are part of the import contract. Do not casually rename, duplicate, blank out, or reorder columns. Export as CSV only when the working copy is ready.

03

Treat IDs as relationships, not decoration

Product IDs and Version IDs distinguish a certificate record and its updates. For an update row, verify that the Current Version ID belongs to the existing record you intend to change.

04

Check the field-specific date formats

A production or manufacture field may use month/year while a testing field uses month/day/year. A spreadsheet can display a date-shaped value that is still not the required CSV value.

05

Validate the file before the upload step

FileCheck is a browser-based preflight for common CSV issues: headers, row widths, key fields, controlled values, dates, lengths, and selected dependencies. It helps with the file work; your source-record review remains essential.

Ready to inspect a file?

Run a private file check before your upload.

Your CSV is processed in your browser. FileCheck identifies common file issues but never sends the file to CPSC or submits data on your behalf.