Plan: Pro, Enterprise | Platform: AfterShip Shipping API

Overview

US Consumer Product Safety Commission (CPSC) eFiling requires you to submit Certificate of Compliance (CoC) data electronically when you import regulated consumer products into the United States. Learn how to add CPSC eFiling data to your US-bound labels using AfterShip Shipping.

This guide walks you through identifying regulated products, choosing a filing path, gathering your data, adding it through the API or product metafields, and testing your shipments. Once set up, your FedEx and UPS shipments carry the data US customs needs, which helps you avoid holds and delays.

Before you begin

Requirements

An AfterShip Shipping account that creates labels for US-bound shipments
FedEx or UPS as the carrier for your US-bound shipments
A list of the products you ship to the United States, with their Harmonized Tariff Schedule (HTS) codes

Limitations

AfterShip Shipping supports the Reference and Disclaimer filing paths only. The Full Partner Government Agency (PGA) Message Set isn't supported.
AfterShip Shipping passes your data to the carrier but doesn't verify whether your certificate data is correct
Portal and Returns labels include CPSC data only after AfterShip enables metafield fetch for your products

Setup steps

Step 1: Identify your CPSC-regulated products

Your shipments need CPSC data only when they contain products that CPSC regulates under 16 CFR Part 1110.

Check that the shipment's destination is the United States.
Confirm the shipment contains finished consumer products, not component parts.
Check each product with the CPSC Regulatory Robot.
List the products that need a certificate and the products that are exempt.

Tip: Common regulated categories include children's products, household goods, consumer electronics, recreation gear, and flammable textiles.

Step 2: Choose your filing path

Your filing path decides which data you collect and send for each product.

Filing path	When to use	Data you need	`fill_mode` value
Reference	Your product is registered in the CPSC Product Registry	Certifier ID, Product ID, Version ID	`reference`
Disclaimer	Your product's HTS code triggers CPSC review, but the product doesn't need a certificate	Disclaim code, intended use code	`disclaimer`

Use Reference filing for products that need a Certificate of Compliance.
Use Disclaimer filing for products that are exempt from certification.

Step 3: Gather your filing data

Collect the values your filing path requires before you add them to AfterShip.

For Reference filing, register each product in the CPSC Product Registry.
Record the Certifier ID, Product ID, and Version ID for each registered product.
For Disclaimer filing, choose disclaim code A (not subject to any CPSC rule) or B (subject to a CPSC rule but exempt from certification).
Find the intended use code in CBP CATAIR Appendix R (Customs and Trade Automated Interface Requirements).

Note: If your intended use code is 980.000, also prepare a written description of the intended use.

Step 4: Add CPSC data to your API requests

If you create labels with the AfterShip Shipping API, add a regulatory_data array to each regulated item.

Locate each regulated item at shipment.parcels[].items[].regulatory_data[] in your label request.
Set regulation_code to CPSC.
Set fill_mode and the fields for your filing path, using the tables below.

Reference filing fields

Field	Type	Required	Description
`regulation_code`	string	Yes	Fixed value: `CPSC`
`fill_mode`	string	Yes	Fixed value: `reference`
`certifier_id`	string	Yes	Your Certifier ID in the CPSC Product Registry
`product_id`	string	Yes	The product's ID in the CPSC Product Registry
`version_id`	string	Yes	The certificate version ID for this product

"items": [   {     "description": "Toy Car",     "regulatory_data": [       {         "regulation_code": "CPSC",         "fill_mode": "reference",         "certifier_id": "CERT-00123",         "product_id": "PROD-98765",         "version_id": "V2"       }     ]   } ]

Disclaimer filing fields

Field	Type	Required	Description
`regulation_code`	string	Yes	Fixed value: `CPSC`
`fill_mode`	string	Yes	Fixed value: `disclaimer`
`disclaim_code`	`A` or `B`	Yes	`A`: not subject to any CPSC rule. `B`: subject to a CPSC rule but exempt from certification.
`intended_use_code`	string	Yes	Intended use code from CBP CATAIR Appendix R
`intended_use_description`	string	No	Required only when `intended_use_code` is `980.000`

"items": [   {     "description": "Gift Item (non-commercial)",     "regulatory_data": [       {         "regulation_code": "CPSC",         "fill_mode": "disclaimer",         "disclaim_code": "A",         "intended_use_code": "996.000"       }     ]   } ]

For the full API reference, see the AfterShip Shipping API documentation.

Step 5: Add CPSC data to product metafields

If you create labels in the AfterShip Shipping portal or AfterShip Returns portal, store CPSC data in your e-commerce platform's product metafields.

Go to Products in your e-commerce platform and open a regulated product.
Add the metafields your filing path requires, using the exact keys below.
Contact AfterShip Support to enable metafield fetch for your products.

Metafield key	Filing path	Value
`cpsc_fill_mode`	Reference, Disclaimer	`reference` or `disclaimer`
`cpsc_certifier_id`	Reference	Your Certifier ID
`cpsc_product_id`		Product ID
`cpsc_version_id`		Certificate version ID
`cpsc_disclaim_code`	Disclaimer	`A` or `B`
`cpsc_intended_use_code`		Intended use code
`cpsc_intended_use_description`		Required only when the intended use code is `980.000`

CPSC metafields on a product in Shopify > Products

Note: You only need the metafields for your filing path. You can leave the other keys empty.

Step 6: Test your US shipments

Confirm AfterShip Shipping accepts your CPSC data before you ship regulated products at volume.

Create a test label for a US-bound shipment that contains a regulated product.
Confirm the label request succeeds with your CPSC values.
Repeat the test for each filing path you use.

To stop sending CPSC data for a product, remove its regulatory_data entry from your API requests or delete its CPSC metafields.

What your users will experience

After completing these steps:

AfterShip Shipping sends your CPSC data to FedEx or UPS with each regulated US shipment
Your carrier files the data with US Customs and Border Protection (CBP) through the Automated Commercial Environment (ACE)
You avoid customs holds caused by missing CPSC data
Shoppers receive regulated products without delays caused by missing filing data

Troubleshooting

Problem	Cause	Solution
My shipment is held at US customs	The shipment is missing required CPSC data	Contact your carrier about the held shipment, then add CPSC data for that product
Portal labels don't include my CPSC data	Metafield fetch isn't enabled for your products	Contact AfterShip Support to enable metafield fetch
Portal labels still don't include CPSC data after fetch is enabled	Metafield keys don't match the required names	Rename your metafields to match the keys in Step 5 exactly
My Disclaimer filing is missing information	The intended use code is `980.000` without a description	Add `intended_use_description` to the item

FAQs

1. Who is responsible for the accuracy of my CPSC data?

You are. As the importer of record, you're responsible for your certificate data, your certification or disclaimer decisions, and your Certificate of Compliance records. AfterShip Shipping is responsible for passing the data you provide to your carrier.

2. Do I need CPSC data for component parts?

No. CPSC eFiling applies to finished consumer products only.

3. Do I need to set every CPSC metafield?

No. Set only the metafields your filing path requires.

4. Which carriers support CPSC eFiling in AfterShip Shipping?

FedEx and UPS. Your carrier files the data with CBP.

Does AfterShip Shipping support the Full PGA Message Set?

No. AfterShip Shipping supports the Reference and Disclaimer filing paths only.

5. What happens if I don't provide CPSC data?

CBP can delay or hold your shipment until you provide compliant data. You can also face CPSC examinations, document requests, storage fees, and penalties for repeat or willful non-compliance.

6. When did CPSC eFiling become mandatory?

CPSC eFiling is mandatory for US entries filed on or after July 8, 2026.

Key takeaways

AfterShip Shipping sends your CPSC eFiling data to FedEx or UPS for US-bound shipments
Use Reference filing for registered products and Disclaimer filing for products exempt from certification
API users add regulatory_data; portal users add product metafields and ask Support to enable fetch
Shoppers receive regulated products without holds caused by missing CPSC data
Portal labels skip CPSC data until AfterShip enables metafield fetch for your products

Add CPSC eFiling Data to US Shipments