CPSC eFiling Product Registry Data Dictionary: Fields, Formats, Allowed Values & Examples
A field-level reference for the CPSC Product Registry CSV workflow, with official requirement status, formats, allowed values, conditional rules, and source locations.
- Author:
- VelaCert Editorial Team
- Published:
- Updated:
Last verified against CPSC: September 2026. Examples labeled “Example” are VelaCert illustrations of the documented format, not CPSC-issued product data or a compliance determination. Always download the current template and guidance before preparing a production upload.
Quick answer
The CPSC Product Registry data dictionary below maps commonly queried CSV fields to their official requirement status, format, allowed values, conditions, and source location. It uses CPSC's current Version 3 CSV guide and template as the primary field authority, with the Product Registry Guide V3, API Specifications V4, FAQ V1.4, and citation guidance for supporting context.
Source scope and version note
The status labels and CSV formats on this page come primarily from User Guide for CSV Upload V3 and the Bulk Upload Template V3, both listed by CPSC with a December 18, 2025 date. Interface behavior is cross-checked against Product Registry User Guide V3 dated September 22, 2025. API field shapes are cross-checked against API Specifications V4, listed January 22, 2026.
CSV column labels and API JSON keys are different representations. This page preserves the CSV field names and does not imply that a CSV format rule automatically applies to an API payload.
CPSC eFiling Field Reference Table
This table is a fast lookup. The field sections below provide the condition, common mistake, official source version, and precise guide location.
| Field | Requirement status | Format | Allowed values | Example | Official source |
|---|---|---|---|---|---|
| Product Update | Required in every CSV upload row | One uppercase character | Y or N | N | CPSC User Guide for CSV Upload |
| Current Version ID | Contingent | Alphanumeric; maximum 19 characters | The existing Version ID in the Product Registry | V3 | CPSC User Guide for CSV Upload |
| New Version ID | Required in every CSV upload row | Alphanumeric; maximum 19 characters | A Version ID unique for that Product ID | V4 | CPSC User Guide for CSV Upload |
| Primary Product ID | Required in every CSV upload row | Alphanumeric; maximum 19 characters | An identifier matching the selected Primary Product ID Type | SKU-4821 | CPSC User Guide for CSV Upload |
| Primary Product ID Type | Required in every CSV upload row | Enumerated text value | GTIN, UPC, SKU, Model Number, Serial Number, Registered Number, or Alternate Identifier | SKU | CPSC User Guide for CSV Upload |
| Certificate Type | Required in every CSV upload row | Enumerated text value | GCC or CPC | GCC | CPSC User Guide for CSV Upload |
| Product Name (Model) | Required in every CSV upload row | Alphanumeric text; maximum 250 characters | Product-specific name or model text | Wooden activity cube | CPSC User Guide for CSV Upload |
| Manufacturer GLN or Manufacturer Alternate ID | Required alternative pair | Alphanumeric; maximum 50 characters | A valid GLN or an account/collection-specific Alternate ID | factory-shenzhen-02 | CPSC User Guide for CSV Upload |
| Manufacturer Is New? and manufacturer information | Contingent | Y/N indicator plus field-specific text limits | Y or N for Manufacturer Is New?; blank defaults to N | Y with manufacturer name, address, country, city, phone, and email | CPSC User Guide for CSV Upload |
| Manufacture Date | Required in every CSV upload row | MM/CCYY | Two-digit month and four-digit year | 08/2026 | CPSC User Guide for CSV Upload |
| Additional product and production fields | Optional | Field-specific: additional IDs up to 50 characters; description up to 250; production dates MM/DD/CCYY; lot number up to 20 | Additional ID types, brand, description, color, style, production dates, lot number, and Seller or Manufacturer for Lot Number Assigned By | Production Start Date: 08/01/2026 | CPSC User Guide for CSV Upload |
| Lab Type | Required; at least one laboratory entry | Enumerated text value | ITL, LAB, or NOL | ITL | CPSC User Guide for CSV Upload |
| Lab CPSC-ID | Contingent | Alphanumeric | The laboratory’s CPSC ID from the CPSC-accepted laboratory records | 1234 | CPSC User Guide for CSV Upload |
| LAB identifier and new laboratory information | Contingent | Y/N indicator; identifier maximum 50 characters; field-specific text limits | Existing GLN/Alternate ID, or Y with complete new-laboratory details | Lab Is New?: N; Lab Alternate ID: internal-lab-7 | CPSC User Guide for CSV Upload |
| Lab Citation Codes | Required code coverage | Current CPSC code values; separate multiple CSV values with semicolons | Codes from CPSC’s current Citation and Testing Exception Codes workbook | 1215;1216 | CPSC CSV Guide and Citation, Testing Exclusion, and Disclaim Guidance |
| Testing exclusion entry | Conditional on claiming a testing exclusion | NOL laboratory entry plus current testing-exclusion codes | Testing-exclusion codes from CPSC’s current workbook | Lab Type: NOL; Citation Codes: [confirmed exclusion code] | CPSC CSV Guide and Citation, Testing Exclusion, and Disclaim Guidance |
| Last Test Date | Required in every CSV upload row | MM/DD/CCYY | A valid calendar date using a four-digit year | 08/21/2026 | CPSC User Guide for CSV Upload |
| Test Report ID, Test URL, and Test Report Access Key | Optional | Up to 400 characters per field; use semicolons to separate details for multiple reports | Report identifier, URL, and access-key text | TR-2026-184 | CPSC User Guide for CSV Upload |
| Lab Is Component? and Component Description | Optional; description depends on the indicator | Boolean-style indicator; description maximum 250 characters | True, False, Yes, or No | Yes; painted wooden block component | CPSC User Guide for CSV Upload |
| Point of Contact for Test Result Records | Required in every CSV upload row | Enumerated text value | Importer, Manufacturer, Laboratory, Broker, or Other | Importer | CPSC User Guide for CSV Upload |
| POC Is New?, POC GLN / Alternate ID, and POC information | Contingent | Y/N indicator; identifier maximum 50 characters; field-specific text limits | Existing GLN/Alternate ID, or Y with complete new-POC details | POC Is New?: N; POC Alternate ID: records-team-us | CPSC User Guide for CSV Upload |
On small screens, swipe horizontally. Examples are illustrative; bracketed text must be replaced with reviewed, product-specific data.
Field definitions and source locations
Product Update
Indicates whether the CSV row supplies a new certificate record or updates data already in the Product Registry.
- Requirement status
- Required in every CSV upload row
- When required
- Always for the CSV workflow.
- Accepted format
- One uppercase character
- Allowed values
- Y or N
- Example
- N
- Common mistake
- Using Y without supplying the Current Version ID of the record being updated.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7; Updating Data on an Existing Certificate Entry, page 5
Last verified: September 2026
Current Version ID
Identifies the existing certificate version that a Product Update row is changing.
- Requirement status
- Contingent
- When required
- Required when Product Update is Y.
- Accepted format
- Alphanumeric; maximum 19 characters
- Allowed values
- The existing Version ID in the Product Registry
- Example
- V3
- Common mistake
- Supplying a stale Version ID or leaving it blank when Product Update is Y.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Contingent Fields, page 8
Last verified: September 2026
New Version ID
Names the version being created for a new or updated product certificate.
- Requirement status
- Required in every CSV upload row
- When required
- Always for the CSV workflow, including new and update rows.
- Accepted format
- Alphanumeric; maximum 19 characters
- Allowed values
- A Version ID unique for that Product ID
- Example
- V4
- Common mistake
- Reusing a Version ID already associated with the same Product ID.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7; Product Registry Guide section 5.1, pages 36 and 41
Last verified: September 2026
Primary Product ID
The unique identifier used as the Product ID Certificate Identifier for the product certificate.
- Requirement status
- Required in every CSV upload row
- When required
- Always for the CSV workflow; it is also one of the three identifiers used in Reference PGA.
- Accepted format
- Alphanumeric; maximum 19 characters
- Allowed values
- An identifier matching the selected Primary Product ID Type
- Example
- SKU-4821
- Common mistake
- Entering a value that does not correspond to the selected identifier type or the certified product.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7; Product Registry Guide section 5.1, pages 36–37
Last verified: September 2026
Primary Product ID Type
Defines which identification system the Primary Product ID value uses.
- Requirement status
- Required in every CSV upload row
- When required
- Always with Primary Product ID.
- Accepted format
- Enumerated text value
- Allowed values
- GTIN, UPC, SKU, Model Number, Serial Number, Registered Number, or Alternate Identifier
- Example
- SKU
- Common mistake
- Putting the primary value into its matching optional identifier column as well; CPSC says not to duplicate the primary ID type.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7; Optional Fields, page 10
Last verified: September 2026
Certificate Type
Identifies the kind of certificate being entered for the product.
- Requirement status
- Required in every CSV upload row
- When required
- Always for a valid Product Registry CSV certificate row.
- Accepted format
- Enumerated text value
- Allowed values
- GCC or CPC
- Example
- GCC
- Common mistake
- Selecting the certificate type without confirming which certificate the product legally requires.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7
Last verified: September 2026
Product Name (Model)
The name of the finished product represented by the certificate.
- Requirement status
- Required in every CSV upload row
- When required
- Always for the CSV workflow.
- Accepted format
- Alphanumeric text; maximum 250 characters
- Allowed values
- Product-specific name or model text
- Example
- Wooden activity cube
- Common mistake
- Using only a generic shipment description that does not identify the certified product.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7
Last verified: September 2026
Manufacturer GLN or Manufacturer Alternate ID
References the manufacturer trade-party record associated with the certificate.
- Requirement status
- Required alternative pair
- When required
- One of the two identifiers must be provided for every CSV product entry, including when a new manufacturer is created.
- Accepted format
- Alphanumeric; maximum 50 characters
- Allowed values
- A valid GLN or an account/collection-specific Alternate ID
- Example
- factory-shenzhen-02
- Common mistake
- Supplying neither identifier, or referencing an ID that does not exist in the destination trade-party list.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7; Trade Party Management, pages 6–7
Last verified: September 2026
Manufacturer Is New? and manufacturer information
Controls whether the Registry creates a manufacturer trade party or links an existing one.
- Requirement status
- Contingent
- When required
- Use Y when adding the manufacturer for the first time. With Y, provide the required manufacturer name, address, and contact details; otherwise reference an existing GLN or Alternate ID.
- Accepted format
- Y/N indicator plus field-specific text limits
- Allowed values
- Y or N for Manufacturer Is New?; blank defaults to N
- Example
- Y with manufacturer name, address, country, city, phone, and email
- Common mistake
- Providing new trade-party details while leaving the indicator blank or N; CPSC says those details will be ignored.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Contingent Fields, page 8
Last verified: September 2026
Manufacture Date
The month and year in which the finished product was manufactured.
- Requirement status
- Required in every CSV upload row
- When required
- Always for the CSV workflow.
- Accepted format
- MM/CCYY
- Allowed values
- Two-digit month and four-digit year
- Example
- 08/2026
- Common mistake
- Using a full date such as 08/21/2026; that is the Last Test Date format, not the Manufacture Date format.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7
Last verified: September 2026
Additional product and production fields
Adds identifiers and descriptive or production details beyond the mandatory product record.
- Requirement status
- Optional
- When required
- Not required by the CSV guide; provide when the data is accurate and useful for identification.
- Accepted format
- Field-specific: additional IDs up to 50 characters; description up to 250; production dates MM/DD/CCYY; lot number up to 20
- Allowed values
- Additional ID types, brand, description, color, style, production dates, lot number, and Seller or Manufacturer for Lot Number Assigned By
- Example
- Production Start Date: 08/01/2026
- Common mistake
- Duplicating the Primary Product ID type in the additional identifier columns.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Optional Fields, page 10
Last verified: September 2026
Lab Type
Identifies whether the laboratory entry is CPSC-accepted, another laboratory, or a no-laboratory testing-exclusion entry.
- Requirement status
- Required; at least one laboratory entry
- When required
- A valid CSV product certificate requires at least one numbered lab entry.
- Accepted format
- Enumerated text value
- Allowed values
- ITL, LAB, or NOL
- Example
- ITL
- Common mistake
- Using NOL for ordinary lab testing; NOL is used to provide testing-exclusion codes.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7; Providing Testing Exclusions, pages 6–7
Last verified: September 2026
Lab CPSC-ID
Identifies a CPSC-accepted testing laboratory used in an ITL entry.
- Requirement status
- Contingent
- When required
- Required when the corresponding Lab Type is ITL.
- Accepted format
- Alphanumeric
- Allowed values
- The laboratory’s CPSC ID from the CPSC-accepted laboratory records
- Example
- 1234
- Common mistake
- Using a company’s internal lab code instead of the applicable CPSC ID.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Contingent Fields, page 8
Last verified: September 2026
LAB identifier and new laboratory information
References or creates a non-ITL laboratory trade-party record.
- Requirement status
- Contingent
- When required
- For LAB, provide an Alternate ID or GLN. Use Lab Is New? = Y and the required name, address, and contact details when creating it for the first time.
- Accepted format
- Y/N indicator; identifier maximum 50 characters; field-specific text limits
- Allowed values
- Existing GLN/Alternate ID, or Y with complete new-laboratory details
- Example
- Lab Is New?: N; Lab Alternate ID: internal-lab-7
- Common mistake
- Sending new lab details with Lab Is New? blank or N, which causes those details to be ignored.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Contingent Fields, pages 8–9
Last verified: September 2026
Lab Citation Codes
Connects a laboratory entry to the CPSC rules, bans, standards, or regulations represented by the certificate data.
- Requirement status
- Required code coverage
- When required
- A valid certificate requires at least one citation or testing-exclusion code; each applicable citation must be provided.
- Accepted format
- Current CPSC code values; separate multiple CSV values with semicolons
- Allowed values
- Codes from CPSC’s current Citation and Testing Exception Codes workbook
- Example
- 1215;1216
- Common mistake
- Copying test-method text instead of the exact current CPSC code, or using commas between multiple CSV values.
Version/date: Guidance dated February 27, 2026; CSV Guide Version 3
Location: Citation guidance, page 1; CSV Required Fields, page 7
Last verified: September 2026
Testing exclusion entry
Records a testing exclusion being relied upon while a certificate is required for another applicable requirement.
- Requirement status
- Conditional on claiming a testing exclusion
- When required
- When an applicable testing exclusion is claimed, provide its official code. In CSV, use a Lab Type of NOL and put the exclusion codes in that lab’s Citation Codes column.
- Accepted format
- NOL laboratory entry plus current testing-exclusion codes
- Allowed values
- Testing-exclusion codes from CPSC’s current workbook
- Example
- Lab Type: NOL; Citation Codes: [confirmed exclusion code]
- Common mistake
- Treating NOL as a laboratory or mixing an unverified exemption claim with ordinary Citation Codes.
Version/date: Guidance dated February 27, 2026; CSV Guide Version 3
Location: Testing Exclusions, page 2; CSV Providing Testing Exclusions, pages 6–7
Last verified: September 2026
Last Test Date
The most recent date on which the product was tested for the certificate data.
- Requirement status
- Required in every CSV upload row
- When required
- Always for the CSV workflow.
- Accepted format
- MM/DD/CCYY
- Allowed values
- A valid calendar date using a four-digit year
- Example
- 08/21/2026
- Common mistake
- Using YYYY-MM-DD or substituting the report issue date without confirming it is the relevant test date.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7; Product Registry Guide section 5.1, page 40
Last verified: September 2026
Test Report ID, Test URL, and Test Report Access Key
Provides optional references that can help locate supporting test-report records.
- Requirement status
- Optional
- When required
- Not required by the CSV guide; supply only when the references are accurate and maintainable.
- Accepted format
- Up to 400 characters per field; use semicolons to separate details for multiple reports
- Allowed values
- Report identifier, URL, and access-key text
- Example
- TR-2026-184
- Common mistake
- Assuming an optional URL or report ID replaces required citation, lab, date, or retained supporting records.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Optional Fields, page 10
Last verified: September 2026
Lab Is Component? and Component Description
Marks that the laboratory’s testing data concerns a component rather than the finished product and describes that component.
- Requirement status
- Optional; description depends on the indicator
- When required
- The description becomes available when Lab Is Component? is True or Yes.
- Accepted format
- Boolean-style indicator; description maximum 250 characters
- Allowed values
- True, False, Yes, or No
- Example
- Yes; painted wooden block component
- Common mistake
- Marking component testing without identifying the component covered by the results.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Optional Fields, page 10
Last verified: September 2026
Point of Contact for Test Result Records
Identifies the party that maintains the product’s test-result records.
- Requirement status
- Required in every CSV upload row
- When required
- Always for the CSV workflow.
- Accepted format
- Enumerated text value
- Allowed values
- Importer, Manufacturer, Laboratory, Broker, or Other
- Example
- Importer
- Common mistake
- Naming the filer without confirming who can actually produce the test-result records.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Required Fields, page 7
Last verified: September 2026
POC Is New?, POC GLN / Alternate ID, and POC information
References or creates the trade-party record when the records contact is Other.
- Requirement status
- Contingent
- When required
- When POC type is Other, reference an existing POC by GLN or Alternate ID, or use POC Is New? = Y and provide the required name, address, and contact information.
- Accepted format
- Y/N indicator; identifier maximum 50 characters; field-specific text limits
- Allowed values
- Existing GLN/Alternate ID, or Y with complete new-POC details
- Example
- POC Is New?: N; POC Alternate ID: records-team-us
- Common mistake
- Providing POC details while POC Is New? is blank or N; CPSC says those details will be ignored in favor of the referenced trade party.
Version/date: Version 3; Document Library date: December 18, 2025
Location: Contingent Fields, page 9
Last verified: September 2026
Related VelaCert references
Keep field-level evidence connected
VelaCert helps teams organize product, manufacturer, laboratory, testing, certificate, and Product Registry data before downstream filing. It does not determine product scope, applicable requirements, testing obligations, or legal compliance.
See how VelaCert organizes CPSC compliance recordsOfficial CPSC source set
- User Guide for CSV Upload V3— U.S. Consumer Product Safety Commission
- CSV Template for Bulk Upload V3— U.S. Consumer Product Safety Commission
- eFiling Product Registry User Guide V3— U.S. Consumer Product Safety Commission
- eFiling API Specifications V4— U.S. Consumer Product Safety Commission
- Product Registry Frequently Asked Questions V1.4— U.S. Consumer Product Safety Commission
- eFiling Citation, Testing Exclusion, and Disclaim Guidance— U.S. Consumer Product Safety Commission
- eFiling Document Library— U.S. Consumer Product Safety Commission
Frequently asked questions
What format is Manufacture Date in the CPSC Product Registry CSV?
Manufacture Date uses MM/CCYY in the CPSC CSV Upload Guide V3. For example, August 2026 is 08/2026. Do not use a full day-level date in this field.
What format is Last Test Date in CPSC eFiling?
Last Test Date uses MM/DD/CCYY in the CPSC CSV Upload Guide V3, with a four-digit year—for example, 08/21/2026. CPSC describes it as the most recent date of testing for the product.
What does Product Update Y or N mean?
Y means the row updates certificate data already in the Product Registry; N means it does not. When Product Update is Y, Current Version ID is required so the Registry can identify the existing version being changed.
What is the difference between Product ID and Version ID?
Product ID identifies the product, while Version ID distinguishes a certificate version for that Product ID. Together with Certifier ID, they form the three Certificate Identifiers used to reference a specific Product Registry certificate in a Reference PGA filing.
What do ITL, LAB, and NOL mean in the CPSC CSV template?
They are the allowed Lab Type values. ITL is used for a CPSC-accepted testing laboratory, LAB for another laboratory, and NOL for a testing-exclusion entry where no laboratory testing supports that exclusion record.
When is a CPSC Lab ID required?
The CSV Upload Guide V3 marks Lab CPSC-ID as required when the corresponding Lab Type is ITL. Use the applicable identifier for the CPSC-accepted laboratory, not an internal vendor code.
What manufacturer information is required in the CPSC Product Registry CSV?
Every row must reference the manufacturer using a GLN or Alternate ID. If Manufacturer Is New? is Y, the required manufacturer name, address, and contact details must also be supplied so the new trade-party record can be created.
What Point of Contact information is required?
Every CSV row identifies the records contact as Importer, Manufacturer, Laboratory, Broker, or Other. If Other is selected, reference an existing POC by GLN or Alternate ID, or create one with POC Is New? = Y and the required name, address, and contact details.