CPSC eFiling CSV Upload Errors and How to Fix Them
CPSC CSV upload errors usually come from one of three places: the file no longer matches the official bulk-upload structure, a row contains an invalid or missing value, or a conditional field is absent because another answer triggered an additional requirement. The safest fix is to identify the exact row and field, correct the original working file, validate its related fields, and export a fresh CSV.
This guide explains how to separate file-wide failures from row-level errors, diagnose common Product Registry problems, correct product updates and trade-party references, preserve dates and identifiers, review citation and laboratory fields, and repeat the upload without inventing missing compliance data.
What a CPSC CSV upload error actually means
The Product Registry parses the uploaded CSV and checks its records against backend requirements. A problem affecting the file structure can stop the upload attempt; a problem in one certificate row can cause that record to be rejected while other valid records remain available for import.
The Registry cannot process the upload structure
Start with the file itself when no rows are parsed or the upload fails before a useful row review appears. Common causes include uploading an Excel workbook instead of a CSV, missing required headers, renamed columns, an outdated structure, embedded commas, or a damaged export.
The file opens, but one or more certificate records contain errors
The import review can identify products ready for import and products containing errors. CPSC instructs users to inspect the specific row errors, correct rejected records in the template, save a new CSV, and repeat the upload.
A value is present, but another field makes more data mandatory
Product Update, manufacturer status, laboratory type, laboratory status, point-of-contact type, and point-of-contact status all control related fields. Validate the complete dependency group instead of repairing only the cell named in the first error.
The requested fact is not available in the source records
A formatter cannot safely invent a citation code, testing date, laboratory identifier, manufacturer address, or certificate type. Return the row to the responsible supplier, importer, laboratory, or compliance owner and obtain supported information before trying to make the file pass.
Check these items before changing any certificate data
Begin with facts that can invalidate an entire batch. This prevents hours of row editing when the actual problem is the template version, file format, header row, or destination Product Collection.
Confirm that the workbook matches the current official template
Compare the working file with the version currently published in CPSC’s eFiling Document Library. As of this page’s July 16, 2026 review, the listed bulk-upload template and CSV guide are both Version 3 dated December 18, 2025.
Verify that the selected upload is a CSV—not the Excel working file
CPSC provides the template as an Excel file for preparation, but the Product Registry accepts CSV uploads. Save the reviewed workbook as a fresh CSV immediately before uploading and confirm that the correct exported file was selected.
Compare every required header with the official template
The current guide states that missing required column headers cause the upload attempt to fail. Standard column names should not be changed. Extra laboratories are the controlled exception and must follow the prescribed sequential Lab 3, Lab 4, and later header pattern.
Remove all sample product data from the downloaded template
CPSC states that the example rows in the template are instructional and should be fully deleted before upload. Leaving a sample row in the batch can create avoidable errors or introduce a record that does not belong to the importer.
Confirm the correct Product Collection and user permission
CSV upload requires Collection Editor permission or above. The selected Product Collection also determines which existing products, manufacturers, laboratories, points of contact, GLNs, and Alternate IDs the uploaded rows can reference.
Common CPSC CSV upload errors caused by the file itself
These problems can affect many rows at once. Repair the controlled template structure first, then return to certificate-level values.
Restore the exact official column names
Likely cause: A header was deleted, shortened, translated, reordered through a custom export, or changed to an internal field name. Safe fix: Start from a clean current template, compare headers character by character, and move the source values under the correct official columns. Do not guess at a near match.
Export and upload a real CSV file
Likely cause: The user selected the XLSX workbook, an old CSV, a temporary file, or a different worksheet export. Safe fix: Save the final reviewed sheet as CSV, give it a unique batch name, close and reopen it for a quick check, and select that exact file in the Registry.
Remove commas from certificate data before export
Likely cause: A company name, address, description, or another value contains a comma that interferes with the comma-separated structure. Safe fix: Follow the current CPSC guide and remove commas from field values—for example, use “Example Company LLC” instead of “Example Company, LLC.”
Use semicolons where one field contains several allowed values
Likely cause: Citation codes or test-report details were separated by commas, line breaks, slashes, or spaces. Safe fix: Use a semicolon between multiple values in fields where CPSC allows them, and preserve the official code text exactly.
Restore dates, identifiers, and leading characters from the source records
Likely cause: Excel converted a date, displayed an identifier in scientific notation, removed a leading zero, or changed a long value. Safe fix: Format the affected source columns as Text, re-enter the verified value from its source, and inspect the exported CSV rather than relying only on the workbook display.
Check the current field limit without altering the underlying fact
Likely cause: A product name, identifier, address, description, report reference, or contact value exceeds the limit stated in the current CSV guide. Safe fix: Compare the exact field with the official limit and use an accurate supported value that fits. Do not truncate identifiers or legally meaningful information blindly.
Fix blank, invalid, and incorrectly formatted row values
A required header can be present while a particular row still fails because its value is blank or outside the accepted format. Work through the required field group for every rejected row rather than filling the visibly empty cell in isolation.
Check Product Update, version, ID, ID type, certificate type, and product name
Required product fields include Product Update, New Version ID, Primary Product ID, Primary Product ID Type, Certificate Type, and Product Name (Model). Use only accepted values for controlled fields: Y or N for Product Update; the listed CPSC product ID types; and GCC or CPC for Certificate Type.
Provide a valid manufacturer reference and manufacture date
Each row needs either a Manufacturer GLN or Manufacturer Alternate ID, plus Manufacture Date. The current guide specifies the manufacture month and year in MM/CCYY format. If the manufacturer is new, the corresponding new-party fields also become required.
Include at least one correctly identified laboratory entry
A valid row needs at least one lab entry. Lab Type accepts ITL, LAB, or NOL. An ITL entry requires its CPSC-ID; a LAB entry requires its GLN or Alternate ID and may require full new-party details; NOL is used with applicable testing-exclusion codes.
Match the code type, laboratory type, and test date
A valid certificate needs at least one citation or testing-exclusion code. Multiple codes use semicolons. The current guide specifies Last Test Date as MM/DD/CCYY. Do not replace an unsupported code or date merely to eliminate an error; confirm the value against the current CPSC materials and test records.
Use an accepted point-of-contact category
Point of Contact for Test Result Records accepts Importer, Manufacturer, Laboratory, Broker, or Other. Selecting Other can trigger additional identifier and contact requirements, depending on whether the party already exists in the destination Product Collection.
Fix “The product was not found” and version mismatches
CPSC documents one specific blocking message: “The product was not found.” It appears when a row is marked as a product update but the Registry cannot find the corresponding product in the selected Product Collection.
“The product was not found”
Likely cause: Product Update is Y, but no corresponding product is available in the destination Product Collection. Safe fix: Verify the collection, Primary Product ID, ID type, and Current Version ID against the existing Registry record. If the row is actually a new product, correct its update status based on the real workflow.
Populate the current version when Product Update is Y
Current Version ID is contingent on Product Update. The current CSV guide requires it when Product Update is Y. Copy it from the intended existing certificate record; do not infer it from an internal revision number unless the two are confirmed to be identical.
Check whether the certificate is still editable
CPSC describes updates without a separate certificate entry for records in Awaiting Certification, incomplete records with a saved Version ID, or complete records still within the editing grace period. For an update, Product Update is Y and both Current Version ID and New Version ID are populated according to the intended change.
Do not treat every correction as a simple overwrite
The required action depends on the existing certificate’s status, certification history, testing, and editing window. Confirm whether the change belongs in the current entry or requires a new version before preparing the row. The data-preparation tool should validate supplied IDs, not decide the legal versioning outcome.
Reset “Is New?” fields when reusing stored parties
CPSC’s current guide tells users updating an existing certificate to ensure existing trade parties are not marked as new unless they are intentionally being changed. Reuse the confirmed GLN or Alternate ID and set the related new-party indicator to N or leave it blank where the current rule permits.
Repair manufacturer, laboratory, and point-of-contact dependencies
Trade-party rows fail when the new-or-existing status conflicts with the identifiers and details supplied. The correct fix depends on whether that exact entity already exists in the destination Product Collection or Business Account context.
Use the stored GLN or Alternate ID exactly
If a manufacturer, LAB-type laboratory, or Other point of contact already exists, reference the identifier linked to that record. Check for added spaces, missing leading characters, source-system substitutions, and use of an identifier from a different collection or account context.
Pair “Is New? = Y” with an identifier and complete party data
When a new trade-party record is created through CSV, CPSC requires a GLN or Alternate ID and all applicable identifying, address, and contact fields. A name alone is not a complete new-party record. Validate the entire group before retrying the row.
Do not expect full details to replace an identifier when “Is New?” is N
The current guide states that name, address, and contact details supplied while the party is marked N or left blank are ignored; the Registry associates the record identified by GLN or Alternate ID. If the identifier is wrong, adding more descriptive fields will not repair the reference.
Match ITL, LAB, or NOL to the correct supporting fields
ITL requires the laboratory’s CPSC-ID. LAB uses the laboratory GLN or Alternate ID and the new-party rules when appropriate. NOL carries testing-exclusion codes rather than a conventional laboratory’s testing citation data. Do not move one identifier type into another field to make the row look complete.
Number every laboratory group consecutively
The template includes two laboratory groups by default. Additional labs may be added with sequential official labels such as Lab 3 Name and Lab 3 Address 1. Do not skip numbers, mix fields from different lab groups, or create a custom lab-header convention.
Validate codes against current CPSC materials and the actual evidence
A syntactically valid code is not necessarily correct for the product. Resolve code errors from the applicable rules and test records; never choose a nearby code only because the file validator accepts its format.
Replace obsolete text only after checking the official update
Download the current citation and testing-exception file from the CPSC Document Library. Compare the rejected value exactly, including punctuation and spacing, then confirm that the replacement is supported by the product’s applicable rule and evidence.
Use NOL with the relevant exclusion codes
CPSC’s current guide instructs users providing testing exclusions through CSV to include a laboratory entry of type NOL and put the applicable testing-exclusion codes in that lab group’s Citation Codes field.
Separate values with semicolons and remove accidental spaces
Inspect the raw field when several codes are present. Use the delimiter required by the guide, preserve each complete official value, and remove empty entries created by doubled semicolons or trailing separators.
Use the most recent supported date in the required format
Confirm Last Test Date from the test records and enter it in MM/DD/CCYY format. Do not convert Manufacture Date to the same format: Manufacture Date is a month-and-year field using MM/CCYY under the current guide.
Complete the dependent component description
If Lab {#} Is Component? is True or Yes, the corresponding component description becomes relevant. Confirm that the testing data truly concerns a component and describe that component accurately rather than using the field as a workaround for finished-product data.
How to correct and re-upload rejected CPSC CSV rows
Keep the correction traceable. The goal is not merely to produce a file that parses; it is to preserve accurate certificate data while resolving the structural or business-rule error identified by the Product Registry.
Save the rejected file, source workbook, and import results
Give the batch a stable name and keep its Registry review with the original source. If valid records were imported, record that fact before creating the retry file so they are not accidentally treated as new products in the next upload.
Map every error to one row, one field, and its dependency group
Use the Primary Product ID and a stable internal row ID to find the source record. Then inspect fields controlled by the same answer—for example, Product Update with version IDs, or Lab Type with lab identifiers and citation data.
Compare the row with the current official guide
Check the current header, accepted value, length, date format, and conditional rule. When the problem concerns applicability, certification type, citation selection, testing, or party identity, confirm it with the responsible compliance source rather than relying on formatting logic.
Update the working record and retain the reason for the change
Correct the workbook or source system from which the CSV is generated. If the change came from a supplier, laboratory, broker, or internal compliance owner, retain the confirmed source so the same incorrect value is not regenerated next month.
Run structural and row-level checks again
Recheck headers, required values, conditional groups, controlled values, lengths, identifiers, date formats, commas, semicolon-separated fields, laboratory numbering, and duplicate retry risk before exporting.
Create a fresh CSV and verify the raw result
Save a new CSV from the corrected workbook. Confirm the header count and several representative rows, especially dates, long IDs, leading zeros, international addresses, and fields containing multiple codes.
Read the Product Registry results before selecting valid products
The Registry shows how many records are valid and how many contain errors. Review row-specific problems. You can cancel to correct the batch, or import valid products while the Registry rejects invalid records, depending on the intended retry plan.
Confirm certification status after import
Under the current CSV Upload Guide V3, authorized users may see an option to certify eligible valid certificates during import. If that option is unchecked or unavailable because of permissions, imported records remain Awaiting Certification and require a separate authorized certification step.
What not to do when fixing CPSC CSV upload errors
A clean import does not prove that the certificate facts are correct. Avoid changes that hide a missing record, change the product’s compliance meaning, or create an untraceable mismatch between the CSV and its supporting evidence.
Never invent a citation, laboratory, date, party, or certificate type
A missing compliance fact must go back to the owner of that information. A validator can show what is absent or inconsistent, but it cannot replace a test report, determine product applicability, or create evidence.
Keep internal mappings outside the final upload structure
Use a separate mapping sheet or controlled transformation to connect source columns to CPSC fields. The final upload must retain the official headers and permitted laboratory extensions.
Preserve an audit trail from error to correction
Keep the original file and create a new corrected version. This makes it possible to show which values changed, prevent valid rows from being uploaded as duplicates, and trace the correction to its source.
Verify import and certification separately
A row can be accepted for import without being certified, depending on the selected option and the user’s permissions. Confirm the Product Registry status and complete any required attestation and certification step.
Check the Document Library before every new preparation cycle
Template fields, length limits, controlled values, citation materials, and Registry behavior can change. Archive the version used with each batch and compare it with the current official publication before reuse.
Resolve the rule behind the error—not only the error text
Use the guide that matches the failing part of the workflow: template structure, data elements, Product Registry records, importer obligations, product scope, or a special entry scenario.
CPSC eFiling Resource Center for U.S. Importers
Open the central hub for current dates, official sources, preparation guides, special scenarios, and the CSV application.
CPSC eFiling CSV Template: How to Prepare a Bulk Upload File
Prepare the current workbook, protect its headers and formats, complete dependent fields, and export a controlled CSV.
CPSC eFiling Data Elements and CSV Field Requirements
Review product, manufacturer, laboratory, testing, citation, version, identifier, and contact fields in detail.
How to Use the CPSC Product Registry
Understand Business Accounts, Product Collections, users, trade parties, certificate versions, import review, and certification.
CPSC eFiling Requirements for U.S. Importers
Review compliance dates, covered imports, certificate data, Full and Reference PGA routes, and broker coordination.
Which Products Require CPSC eFiling?
Determine why the finished product’s certificate requirement must be resolved before CSV preparation.
CPSC eFiling for Amazon and Private-Label Sellers
Organize supplier data, testing records, importer roles, identifiers, variants, and repeat product imports.
CPSC eFiling Requirements for Foreign Trade Zones
Prepare for the separate effective date and workflow for covered merchandise withdrawn from a Foreign Trade Zone.
Use current CPSC instructions for every correction
Registry behavior and field rules may change. The official Document Library, CSV Upload Guide, Product Registry Guide, and CPSC FAQ remain the primary sources for current files and instructions.
eFiling Document Library
Official location for the current bulk-upload template, CSV guide, Product Registry guide, code lists, implementation guidance, and archived versions.
User Guide for CSV Upload, Version 3.0
Official bulk-upload instructions covering file format, dates, commas, product updates, trade parties, required and contingent fields, accepted values, length limits, and import review.
eFiling Product Registry User Guide, Version 3.0
Official detailed instructions for accounts, collections, certificate records, CSV import results, product updates, certification, and the documented “product was not found” condition.
eFiling Frequently Asked Questions
Official answers covering Product Registry use, upload methods, certificate reuse, product identifiers, filing routes, and importer scenarios.
Common questions about failed Product Registry uploads
These answers summarize the current CPSC bulk-upload workflow. Use the actual Registry review and current official guide to resolve each file.
Will one invalid row block all valid products?
No. CPSC states that the Registry can identify valid products and products with errors, import valid records, and reject invalid records. Plan the retry carefully so already imported products are not accidentally submitted as new records.
Where can I see which row failed?
The Product Registry import review displays counts of records ready for import and records containing errors. The Product Registry Guide states that users can preview specific errors by hovering over the product row with errors.
Should I edit the rejected CSV directly?
Correct the original controlled template or source workbook, then export a fresh CSV. This prevents the next source export from recreating the same error and preserves a traceable relationship between supplied data and the upload file.
What does “The product was not found” mean?
CPSC documents this message when Product Update is Y but no corresponding product exists in the selected Product Collection. Verify the destination collection and existing product and version identifiers, or correct the row if it is truly a new product.
Why does a date that looks correct in Excel fail?
Excel can silently reformat date cells. CPSC recommends keeping relevant cells in Text format. Under the current guide, Manufacture Date uses MM/CCYY, while Last Test Date and production dates use MM/DD/CCYY.
Does a successful import mean every certificate is complete?
Not automatically. Authorized users may be able to certify eligible records during import. Otherwise, imported records remain Awaiting Certification and require an authorized certification action.
Can Registry Intelligence fix missing compliance evidence?
No. The application can identify absent or inconsistent user-supplied data, validate structure, and prepare output. It does not determine legal applicability, choose unsupported codes, create test evidence, certify products, submit to CPSC or CBP, or guarantee acceptance.
Find preventable CSV problems before upload
Upload one or several supported source files, confirm the field mapping, identify missing and inconsistent information, and prepare a CPSC Product Registry-formatted CSV from rows supported by the data you provide.
Confirm every correction against official instructions and source records
Registry Intelligence is not affiliated with, endorsed by, or operated by the U.S. Consumer Product Safety Commission or U.S. Customs and Border Protection. This page provides educational and data-preparation information, not legal advice, customs brokerage, product testing, certification, Product Registry access, or a government filing service. Official rules, current CPSC files, technical instructions, Product Registry results, and product-specific evidence remain controlling.