CPSC eFiling CSV Template: How to Prepare a Bulk Upload File
The CPSC eFiling CSV template is used to prepare multiple product certificate records for bulk upload to the CPSC Product Registry. A successful file must preserve the official column structure, use accepted values and date formats, satisfy conditional field rules, and contain certificate data supported by the importer’s records.
This guide explains where to obtain the current template, how the Excel working file becomes a CSV upload file, which field groups must be completed, how new and updated products differ, what formatting changes can break the file, and what happens when the Product Registry reviews the upload.
What the CPSC bulk-upload template does
The official template provides the column structure used to convert product certificate data into records that the Product Registry can review and import. It is a data-entry and upload mechanism for the Reference PGA workflow—not a substitute for product testing, certification, or the later CBP entry filing.
Create or update multiple certificate records in one job
Each completed data row supplies the information for a product certificate entry. The same file can contain new product records and properly identified updates, provided every row follows the current template and business rules.
Enter data in the preformatted workbook, then save it as CSV
CPSC distributes an Excel template with preformatted fields. Users enter and review the certificate data in that working file, then manually save the completed sheet in CSV format for upload to the applicable Product Collection.
Uploading the CSV does not transmit a customs entry
The Product Registry is a stand-alone certificate repository. After a valid record is imported and certified, the importer must still provide its Certifier ID, Product ID, and Version ID to the broker for the Reference PGA Message Set in CBP ACE.
Download all current CPSC files from the same source
Do not reuse a template saved months earlier without checking the official Document Library. The template, upload guide, accepted values, citation codes, testing-exclusion codes, and Product Registry rules can be revised independently.
Use the current .CSV Template for Bulk Upload
As of this page’s July 16, 2026 review, CPSC lists Version 3 dated December 18, 2025. Download the current Excel file directly from the official Document Library before starting a new batch.
Read the business rules before filling the workbook
The current User Guide for CSV Upload explains field definitions, accepted values, required and conditional relationships, formatting, and the Product Registry upload process. The template alone does not explain every dependency.
Use the current official codes supported by the certificate
Download the current citation and testing-exclusion materials separately. Do not select a code merely because its description appears similar to the product; the code must reflect the actual applicable requirement and supporting records.
Confirm collection, trade-party, and certification rules
CSV rows are uploaded into a specific Product Collection and can reference existing manufacturers, laboratories, and points of contact. Understand those account records before deciding whether each trade party is new or already stored.
Collect the evidence before mapping columns
A correctly formatted CSV can still contain unsupported or inaccurate certificate data. Assemble the product, manufacturing, testing, laboratory, citation, and records-contact information first; then map it into the official field structure.
Identify each finished product and certificate version
Prepare the Primary Product ID, ID type, product name or model, certificate type, update status, and version information. Keep variants separate when their certificate facts are not identical.
Confirm the production location and reusable identifier
Determine whether the manufacturer already exists in the Business Account. Use the corresponding GLN or Alternate ID, or prepare the complete identifying and contact information required to create a new trade-party record.
Connect each laboratory to the rules it tested
Gather laboratory type and identifiers, the most recent test date, applicable citation or testing-exclusion codes, and any optional test-report references supported by the records.
Identify the party maintaining test-result records
Determine whether the point of contact is the importer, manufacturer, laboratory, broker, or another party. If “Other” is used, additional identifier or new-party details may become mandatory.
Preserve the template structure while entering data
CPSC’s current guide treats the workbook as a controlled upload structure. Spreadsheet software can silently change dates, identifiers, delimiters, and header text, so review the exported CSV rather than assuming the visible Excel sheet will be preserved exactly.
Do not rename, reorder casually, or rewrite standard field names
CPSC states that column field names may not be changed except when adding laboratories according to the designated sequential naming convention. A clearer internal label belongs in a separate working copy, not in the final upload header.
Keep the preformatted data types intact
Date fields are formatted as text to stop Excel from rewriting their values. Avoid converting dates, long identifiers, postal codes, or numbers into automatic spreadsheet formats that remove characters or change the expected representation.
Remove commas from values entered in the workbook
The current Product Registry guide instructs users to remove commas from product data—for example, changing a company name such as “Example Company, LLC” to “Example Company LLC”—before saving the CSV.
Separate multiple entries in one field with semicolons
When a field accepts more than one value, CPSC instructs users to use a semicolon. This commonly matters when a laboratory is associated with multiple citation or testing-exclusion codes.
Extend lab columns only with the official numbering pattern
The template includes fields for the first laboratories. When more are needed, add the complete lab field group in the prescribed position and continue the sequential labels—Lab 3, Lab 4, and so on—without inventing new header names.
Manually save the completed working file as CSV
The Product Registry upload expects the CSV file, not the Excel workbook. After saving, reopen or inspect the final CSV to verify headers, row counts, delimiters, dates, identifiers, and the absence of unintended blank rows.
Complete each part of the product certificate row
The template groups related information for the product, manufacturer, laboratories and citations, and point of contact. Required fields apply to every relevant row; contingent fields become mandatory only when their triggering condition is true.
Define the record, identifier, version, and certificate type
Key fields include Product Update, New Version ID, Primary Product ID, Primary Product ID Type, Certificate Type, and Product Name or Model. When Product Update is “Y,” the Current Version ID is also required.
Accepted certificate types: GCC or CPC.
Reference an existing manufacturer or create a new one
Each entry uses a Manufacturer GLN or Manufacturer Alternate ID and the manufacturing date. If “Manufacturer Is New?” is “Y,” the row must include the required name, address, country, phone, email, and other identifying fields for the new trade party.
Manufacture Date format: MM/CCYY under the current guide.
Complete both connected lot fields or leave both blank
Lot Number is optional. If it is provided, Lot Number Assigned By becomes required. CPSC’s business rules state that supplying either of these fields makes the other mandatory.
Identify at least one lab type and the applicable details
The current guide accepts ITL, LAB, or NOL lab types. Depending on the type and whether the laboratory is new, the row may require a CPSC ID, GLN or Alternate ID, full trade-party details, Last Test Date, and citation codes.
Last Test Date format: MM/DD/CCYY when required.
Connect each laboratory to the requirements it tested
A valid certificate requires at least one citation or testing-exclusion code. Use only current official values supported by the certificate records, and separate multiple codes for the same lab with semicolons.
Identify the party maintaining test-result records
Accepted categories include Importer, Manufacturer, Laboratory, Broker, or Other. If “Other” is selected, the GLN or Alternate ID—or the complete information for a new contact—must be supplied according to the POC Is New value.
Do not treat every blank cell the same way
The CPSC template contains three types of fields. A readiness check must evaluate the conditions on each row, because a field that is optional for one product can become mandatory for another based on an update flag, trade-party status, lab type, or point-of-contact choice.
Values needed for the product certificate entry
Examples include Product Update, New Version ID, Primary Product ID, Product ID Type, Certificate Type, Product Name, manufacturer identifier, Manufacture Date, at least one lab entry, citation information, and a records contact.
Requirements activated by the row’s own answers
Current Version ID is required when Product Update is “Y.” New manufacturer, laboratory, or POC flags trigger full trade-party details. Certain lab types trigger test dates and particular identifiers. Lot fields form a required pair when either is used.
Include useful data only when it is accurate and properly formatted
Optional fields can provide additional product, testing, or record references, but they still must follow the accepted format. An optional field should remain blank when the user does not possess reliable supporting information.
Set Product Update correctly for every row
The Product Update field tells the Registry whether a row creates a new certificate entry or updates a product already stored in the target Product Collection. An incorrect value can cause the upload to search for a record that does not exist or create an unintended new entry.
Create a new certificate record with a new Version ID
Confirm that the Primary Product ID does not conflict with the intended record structure in the Product Collection. Complete the required certificate and trade-party data for the new product.
Identify the current stored version and the desired new version
When Product Update is “Y,” Current Version ID becomes required. The Primary Product ID and current version must match an existing certificate in the target Product Collection, and the New Version ID must identify the updated record.
An update cannot be applied to a missing product
CPSC’s current guide explains that “The product was not found” can appear when Product Update is marked “Y” but no corresponding product exists in the Product Collection. Correct the original data and repeat the upload.
How to prepare the CPSC eFiling CSV template
Use a controlled sequence so source evidence, mapping decisions, spreadsheet formatting, row validation, and Product Registry results can be traced. Keep the original official template unchanged and work from a dated copy for each batch.
Download the template, guide, and code lists
Record the version and date of each official file used for the batch. Do not combine columns from different template versions.
Create a dated copy without changing the original structure
Use the working copy for data entry and retain the untouched official file for comparison, troubleshooting, and audit evidence.
Map each source field to the exact CPSC column
Document uncertain mappings and require confirmation. A similar label does not prove that two fields have the same regulatory meaning.
Complete required and triggered contingent fields
Evaluate each row independently for new-party flags, update status, lab type, multiple citations, lot information, and POC conditions.
Check headers, formats, accepted values, and relationships
Find blank required fields, invalid Y/N values, unsupported ID types, incorrect date formats, duplicate identifiers, broken lab numbering, and inconsistent version data.
Save manually as CSV and inspect the final file
Verify that the exported row count and headers match the working copy and that dates, identifiers, semicolons, blank cells, and added lab columns remain intact.
Select the correct Product Collection and import the CSV
Use the Import action in the target collection, add the CSV file, and allow the Registry to review the records against its backend requirements.
Import valid products and correct rejected rows
The Registry can import valid records while rejecting rows with errors. Correct rejected rows in the source template, upload them again, and ensure authorized users complete the required attestation and certification.
What happens after the CSV is uploaded
The Product Registry reviews the file and separates certificate records that are ready for import from records containing errors. The review does not certify the data or guarantee that the underlying certificate is legally sufficient.
Import the records that pass the Registry review
CPSC’s guide states that users can choose “Import valid products” to bring valid new certificates and updates into the collection. Imported records then appear with an Awaiting Certification status until the certification step is completed.
Return to the source template instead of editing blindly
Review the error for each rejected record, correct the corresponding source row, save a new CSV, and repeat the upload. Preserve the rejected file and error list when they are needed for internal troubleshooting.
Imported data must still be reviewed and certified
A successful upload prepares Registry records; it does not itself certify compliance. An authorized user must attest to or certify the completed data according to the account permissions and current Product Registry workflow.
Problems to catch before Product Registry upload
Most avoidable failures come from using an outdated template, altering controlled headers, allowing Excel to rewrite values, or overlooking a conditional rule that only applies to certain rows.
Starting with an archived template
Always compare the saved workbook with the current template and upload guide in the official CPSC Document Library.
Renaming columns for internal convenience
Keep CPSC’s standard column names unchanged. Maintain internal labels in a mapping document or separate working workbook.
Leaving triggered fields blank
An update, new trade party, lab type, lot value, or “Other” point of contact can make additional cells mandatory for that row.
Using commas or the wrong separator inside values
Remove commas as instructed by CPSC and use semicolons when a supported field contains multiple values.
Allowing Excel to alter dates or identifiers
Preserve text-formatted date fields and inspect the exported CSV for truncated zeros, converted dates, scientific notation, or changed characters.
Inventing a value to make the row look complete
Do not guess citation codes, laboratory IDs, test dates, addresses, certificate types, or legal applicability. Stop the row and obtain reliable supporting information.
Continue with the guide for your next task
Use this page for template preparation, then move to the detailed guide for Product Registry setup, field definitions, upload errors, importer requirements, product applicability, seller workflows, or Foreign Trade Zones.
CPSC eFiling Resource Center for U.S. Importers
Open the central hub for dates, official sources, the application, and every Registry Intelligence eFiling guide.
How to Use the CPSC Product Registry
Understand Business Accounts, Product Collections, users, privacy, certificate records, certification, and broker handoff.
CPSC eFiling CSV Upload Errors and How to Fix Them
Diagnose formatting, identifier, relationship, update, trade-party, and row-level upload failures.
CPSC eFiling Data Elements and CSV Field Requirements
Review detailed product, manufacturer, laboratory, testing, citation, version, and contact fields.
CPSC eFiling Requirements for U.S. Importers
Review who must comply, effective dates, Full and Reference PGA routes, certificate data, and broker coordination.
Which Products Require CPSC eFiling?
Understand why the finished product’s certification requirement determines whether eFiling applies.
CPSC eFiling for Amazon and Private-Label Sellers
Connect supplier data, testing records, private-label products, importer roles, and repeat imports.
CPSC eFiling Requirements for Foreign Trade Zones
Prepare for the separate effective date and entry workflow for covered merchandise withdrawn from an FTZ.
Verify the template and rules before every new batch
The official CPSC Document Library is the controlling location for current and archived eFiling files. Always use its current template, CSV guide, Product Registry guide, code lists, and implementation materials rather than relying on a saved third-party copy.
eFiling Document Library
Official location for the current Bulk Upload Template, CSV Upload Guide, Product Registry guide, API specification, code lists, and other eFiling materials.
eFiling Product Registry User Guide, Version 3.0
Official detailed instructions for CSV organization, upload review, required and contingent business rules, certification, and product versions.
CPSC Product Registry
Official registration, sign-in, current status, and system information for importers using the Reference PGA route.
eFiling Frequently Asked Questions
Official answers covering Product Registry use, bulk upload, Product IDs, certificate reuse, filing routes, and special importer scenarios.
Common questions before preparing a bulk-upload file
These answers summarize the current CPSC workflow. Use the latest official template and guide for field-level requirements and the actual product records for certificate decisions.
Which CPSC CSV template should I use?
Use the current version shown in CPSC’s eFiling Document Library. As of July 16, 2026, CPSC lists Bulk Upload Template Version 3 dated December 18, 2025.
Can I upload the Excel workbook directly?
No. CPSC’s current instructions state that users enter data in the preformatted Excel template and manually save the completed file in CSV format for Product Registry upload.
Can I rename CPSC columns to match my internal spreadsheet?
No. Keep the official column field names. The current guide permits structural additions only for extra laboratories using the prescribed sequential naming convention.
How should multiple citation codes be separated?
Use semicolons when an accepted field contains more than one value. The current guide specifically applies this rule to multiple citation or testing-exclusion codes.
Will one bad row block every valid product?
CPSC’s guide states that the Registry can import valid products while rejecting records containing errors. Rejected rows must be corrected in the source template and uploaded again.
Does a successful CSV upload certify the products?
No. Valid imported records appear with an Awaiting Certification status. An authorized user must complete the current Product Registry attestation and certification process.
Can Registry Intelligence choose missing codes or certificate facts?
No. The application checks, maps, and formats user-supplied information. It does not determine legal applicability, select unsupported citation codes, create laboratory evidence, certify products, submit to CPSC or CBP, or guarantee acceptance.
Check source data before generating the CSV
Upload one or several supported source files, confirm the column mapping, identify missing or inconsistent information, and prepare a CPSC Product Registry-formatted CSV from the rows that are ready.
Use the official template and current CPSC instructions
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, and product-specific facts remain controlling.