CPSC Product Registry bulk upload
Catch CSV problems before they turn into upload rework.
Use this practical pre-upload checklist to review structure, identifiers, dates, conditional fields, and the final file before your CPSC Product Registry bulk upload.
Start with the current CPSC template
Use the current Product Registry bulk-upload template and guide as the source of truth. Do not add fields just because a generic spreadsheet rule tells you to.
Protect the CSV structure
Keep one header row, avoid blank or repeated headers, and make sure each product row has the same number of columns. If quoting is broken, re-export from the source rather than hand-patching the file.
Check identifiers and versions
Review the Product ID, New Version ID, and, for an update row, the Current Version ID. A reused product/version pair is easy to miss and expensive to untangle later.
Use the exact date formats
Manufacture Date and test-date fields may use different formats. Check that values match the required format and are real calendar dates, not merely date-shaped text.
Link labs and contacts
When the template identifies a laboratory or another party, include the corresponding identifier and conditional fields. A name on its own is not always enough.
Finish with the source records
A clean file is a better starting point, not a compliance decision. Match the final export to your source records and the current CPSC materials before submitting.
Before you upload
Run a private file check, then review the source records.
FileCheck catches a defined set of common CSV defects in your browser and points you to the rows that need attention. It does not send the file to CPSC or submit data on your behalf.
CPSC guidance and templates change. The official CPSC materials remain controlling.