CPSC Mandatory eFiling July 2026: The Complete Importer’s Action Guide for July 8

CPSC mandatory eFiling July 2026 takes effect on July 8, exactly 63 days from today. On that date, every importer of regulated consumer products entering the United States must electronically file product certificate data through CBP’s Automated Commercial Environment at the time of entry. Not after. Not on request. At the time of entry. The CPSC mandatory eFiling July 2026 rule transforms the Consumer Product Safety Commission from a post-entry enforcement agency into a real-time entry surveillance system. CPSC gains visibility into every regulated shipment the moment it is filed in ACE. Importers who arrive at the CPSC mandatory eFiling July 2026 deadline without their product certificates mapped to the correct data elements, their ACE filing workflows updated, and their IOR structure confirmed will face cargo holds of up to 60 days, civil penalties of up to approximately USD 120,500 per violation under current adjusted CPSC enforcement figures, and a permanently elevated importer risk score that triggers more frequent inspections on every subsequent shipment. This guide covers every fact you need about CPSC mandatory eFiling July 2026, every action step in sequence, and the one IOR question that Covington and Burling specifically flagged as the issue most businesses have not answered yet.

CPSC Mandatory eFiling July 2026: In Plain Language What Changes on July 8

Right now, if CBP wants to verify that your imported toy, child’s car seat, or power tool meets CPSC safety standards, they contact you after the goods arrive and ask for the certificate of compliance. The certificate is a paper document sitting in your files. That system ends July 8.

From July 8, the certificate data must be transmitted electronically to CBP through ACE at the moment of entry filing, before goods are released. CPSC staff and AI tools will review eFiled certificate data in real time. Shipments under flagged HTS codes without complete, accurate eFiling will receive electronic warning messages immediately upon filing. Goods under heightened scrutiny can be held for CPSC examination for up to 60 days. The importer bears all associated storage, manipulation, and delay costs throughout the hold. The era of producing certificates only when asked is over.

Which Products Are Subject to the CPSC Mandatory eFiling July 2026 Rule

The eFiling rule applies to all imported consumer products that are required by CPSC to have a certificate of compliance under existing law. Two certificate types are in scope:

• Children’s Product Certificate (CPC): Required for all children’s products subject to mandatory CPSC safety standards. This covers toys, children’s apparel, cribs, strollers, child restraints, children’s furniture, and any product designed or intended primarily for children aged 12 and under. The CPC must be based on third-party testing by a CPSC-accepted laboratory and must identify every applicable CPSC safety rule for which the product was tested
• General Certificate of Conformity (GCC): Required for general-use consumer products subject to mandatory CPSC standards that are not children’s products. This covers power tools, electrical appliances, lighters, fireworks, smoke detectors, upholstered furniture meeting flammability standards, and many other regulated categories. The GCC certifies that the product complies with all applicable consumer product safety rules and bans

The rule applies to all such products entered for consumption or warehousing from July 8, 2026. Products entered into a Foreign Trade Zone have a separate effective date of January 8, 2027. Products that are not subject to any CPSC mandatory standard do not require a CPC or GCC and therefore do not require eFiling of certificate data. However, importers of non-regulated products under flagged HTS codes are strongly encouraged to file a Disclaimer Message Set to inform CPSC that their product falls outside CPSC jurisdiction. This proactively reduces the likelihood of examination holds on non-regulated goods.

CPSC Mandatory eFiling July 2026: The 600 Flagged HTS Codes Explained

On January 27, 2026, CPSC published a list of approximately 600 HTS codes that will be automatically flagged in ACE from July 8. The official list is published on the CPSC eFiling official page. These codes represent HTS headings where at least half of the products classified under that code normally require a CPC or GCC, or where products of special CPSC enforcement interest are typically found. Starting July 8, any entry filed under a flagged code without complete eFiling data will receive an immediate electronic warning in ACE.

Two critical points about the flagged list that most importers misunderstand:

• The list is not exhaustive: Importers are responsible for CPSC eFiling on all regulated products regardless of whether their specific HTS code appears on the flagged list. A product requiring a CPC or GCC that is classified under an unflagged HTS code is still subject to the eFiling requirement. The absence of a flag does not mean the product is exempt. It means ACE will not automatically generate a warning on that entry. The compliance obligation exists regardless
• The list will change: CPSC has explicitly stated that the flagged HTS code list will be updated over time. Importers should check the CPSC eFiling page regularly rather than relying on a one-time review of the January 2026 list

CPSC Mandatory eFiling July 2026: The Required Data Elements Every Importer Must File

Every ACE entry filing for a CPSC-regulated product from July 8 must include a set of required product safety data elements. CPSC guidance identifies at minimum the following primary fields, with additional elements required depending on product type, filing method, and applicable testing exclusions. Missing or incorrect data in any required field produces an incomplete eFiling that triggers CPSC examination:

1. Product ID: The unique identifier for the specific product being imported, linking the entry to the correct certificate in either the Full PGA submission or the CPSC Product Registry
2. Citation codes: The specific CPSC safety rule citations that apply to the product, indexed at the SKU level. These must be accurate for each product. Listing a citation code that does not apply, or omitting one that does, is a compliance error that CPSC examinations will identify
3. Manufacture date: The date the product was manufactured
4. Manufacture place: The country and facility where the product was manufactured
5. Product test date: The date on which third-party testing was completed for CPC products, or the date of self-testing for GCC products where third-party testing is not required
6. Testing laboratory: The name and CPSC acceptance status of the laboratory that conducted the testing. For CPC products, this must be a CPSC-accepted third-party laboratory
7. Point of contact: Contact information for the responsible party who can respond to CPSC requests for supporting documentation

Under CPSC mandatory eFiling July 2026, from July 8 CPSC also requires identification of any testing exclusions relied upon, as part of the revised 16 CFR Part 1110 requirements. If your product certificate relies on a testing exclusion, that exclusion must be identified in the eFiling.

CPSC Mandatory eFiling July 2026: Full PGA vs Reference PGA Message Set

CPSC gives importers two technical filing methods. CPSC has no preference between them. The right choice depends on your import volume and operational structure:

Method 1: Full PGA Message Set

All required data elements are submitted directly through ACE for each shipment at the time of entry filing. No CPSC Product Registry account is required. The Full PGA approach works well for importers with lower SKU volumes, one-time or infrequent shipments, or importers whose customs brokers already have ACE PGA filing capability fully configured. The limitation is that the same data must be submitted fresh for every entry, even for repeat shipments of identical products.

Method 2: Reference PGA Message Set via CPSC Product Registry

Certificate data is uploaded to the CPSC Product Registry, a stand-alone CPSC system that does not push data to ACE automatically. Once uploaded, the Registry generates three Certificate Identifiers. You provide these to your broker, who includes them in the ACE entry filing. Efficient for high-volume importers with recurring shipments of the same products. Critical point: uploading to the Registry without communicating the three identifiers to your broker for each shipment produces an incomplete ACE filing.

CPSC Mandatory eFiling July 2026: What Happens If You Are Not Ready

The consequences of arriving at July 8 unprepared are not hypothetical. CPSC and Livingston International have both explicitly confirmed the enforcement posture:

• Cargo holds of up to 60 days: CPSC examinations can hold goods at the US port of entry for up to 60 days. The importer is responsible for all storage, handling, and manipulation costs during the hold. On a 40-foot container of electronics or toys, 60 days of port storage at major US ports runs USD 10,000 to 30,000 in direct costs before penalties are applied
• Civil penalties up to approximately USD 120,500 per violation: Failure to comply with CPSC certification requirements, including eFiling obligations, constitutes a violation of the Consumer Product Safety Act. Civil penalties are adjusted periodically for inflation. Knowingly submitting false certificate data adds criminal penalty exposure
• Permanently elevated importer risk score: Non-compliance raises your CBP importer risk score. A higher risk score means more frequent CPSC examinations and holds on every subsequent shipment. The compliance failures of July 2026 follow your import programme for years
• Product seizure and recall exposure: Goods found during examination to lack a valid certificate of compliance, or whose certificate does not match the actual product, face seizure. If the product safety violation is substantive rather than procedural, CPSC-directed recall exposure follows

The IOR Question Covington and Burling Flagged That Most Businesses Have Not Answered

CPSC compliance guidance consistently highlights a structural gap that businesses using third-party IOR arrangements frequently miss: when a customs broker or specialist IOR provider is the named importing entity on your entries, the question of which party is responsible for ensuring CPSC certificates are accurate, current, and correctly filed must be answered in writing before the first regulated shipment after July 8. CPSC’s own guidance on importer responsibilities makes clear that the legal compliance obligation sits with the named importer. Who fulfils the operational steps to meet that obligation must be contractually defined.

This is the compliance gap that exists at the intersection of CPSC eFiling and IOR structure. Here is what it means in practice:

The what an Importer of Record is matters here because the IOR is the legal entity named on the CBP customs entry. That entity bears the CPSC compliance obligation. If you use a specialist IOR provider or a customs broker acting as IOR, that entity is named on your entries. CPSC’s records of who bears the compliance obligation point to the IOR. The question of who is responsible for ensuring the CPC or GCC is accurate, current, and correctly filed, and who can respond to a CPSC request for supporting documentation, must be answered in your agreement with your IOR before July 8.

Three scenarios and the compliance risk in each:

• You are the IOR with your own ACE account: You bear full responsibility. Your customs broker files the eFiling data you provide. The required data elements must come from you. Your CPSC Product Registry account must be set up. Your three Certificate Identifiers must be communicated to your broker before every shipment
• Your customs broker files as your authorised agent but you are the named IOR: You remain the legal compliance party. Your broker’s ACE filing capability for CPSC PGA Message Sets must be confirmed operational before July 8. Your broker cannot file complete eFiling data without the required data elements from you. Confirm this workflow is tested before the deadline, not on the day
• A specialist IOR provider is the named IOR on your entries: Confirm explicitly with your IOR provider that they hold CPSC eFiling capability, that they are registered in the CPSC Product Registry, and that your agreement specifies which party, you or the IOR, is responsible for providing the required data elements and maintaining the underlying product certificates. An IOR provider that assumes you will provide certificate data without confirming this in writing creates a gap that only surfaces when CPSC holds a shipment

CPSC Mandatory eFiling July 2026: Five Steps to Complete Before July 8

1. Map every active HTS code against CPSC regulated product categories. Pull your complete list of 10-digit HTS codes imported in the last 12 months. For each code, determine whether the product requires a CPC, a GCC, or neither. Products classified under flagged codes that do not require certification should be identified for Disclaimer Message Set filing. Products requiring certification that are not under flagged codes are still subject to eFiling. Complete this mapping before any other step. Without it you cannot scope the rest of your compliance effort. Use the CPSC Regulatory Robot Tool at cpsc.gov/eFiling to check each HTS code
2. Audit your existing certificates of compliance. For every product requiring a CPC or GCC, confirm the certificate is current, reflects the actual product configuration being shipped, lists every applicable CPSC safety rule citation, and was based on testing by a CPSC-accepted laboratory for CPC products. A certificate that does not match what is currently manufactured is a compliance failure waiting to surface. If you have changed any component supplier, moved production, or modified a product design in the past 12 to 24 months, assess whether that change was material enough to require a new third-party test. Our Global Trade Compliance team conducts CPSC certificate audits across active import portfolios ahead of the July 8 deadline
3. Register in the CPSC Product Registry and choose your filing method. If using the Reference PGA method, register your business account at the CPSC Product Registry now. Upload your product certificate data. Obtain your three Certificate Identifiers for each product. Establish the workflow for communicating those identifiers to your customs broker before each shipment. If using the Full PGA method, confirm your customs broker has the ACE PGA Message Set capability configured and tested. CPSC strongly encourages participation in the voluntary eFiling stage before July 8 to identify and fix workflow errors in a penalty-free environment
4. Test in CBP’s ACE Certification Environment before going live. Untested changes to ACE filing workflows are the most common source of first-day errors on any new filing requirement. CBP’s ACE Certification Environment allows testing of PGA Message Set submissions before they go live in the production system. Build in at least two to three weeks of testing before July 8. For air freight importers specifically, confirm that your air freight broker has the same CPSC data pipeline in place as your ocean broker. Air entries are filed within hours of arrival, not days in advance. The window to correct errors is smaller
5. Confirm your IOR structure and CPSC responsibility allocation in writing. If you use a specialist IOR provider, confirm in your service agreement which party is responsible for CPSC certificate accuracy, currency, and the provision of the required data elements to the ACE filer. If your customs broker acts as IOR, confirm the same. This written allocation is your protection if CPSC examines a shipment and asks who is responsible for the certificate. Our IOR services include CPSC eFiling capability confirmation as part of the standard import compliance framework for all regulated consumer product entries into the United States

CPSC Mandatory eFiling July 2026: Air Freight Importers Have a Smaller Window

Ocean freight entries are typically filed days before vessel arrival, giving time to identify and correct eFiling errors before goods reach the port. Air freight entries are filed within hours of arrival. For high-velocity air replenishment of consumer goods, electronics, and seasonal products, the time between ACE filing and arrival at the airport is measured in hours, not days. There is no correction window once the shipment is in the air.

Air freight importers must ensure their air freight customs broker has the identical CPSC eFiling data pipeline in place as their ocean broker. Many importers assume that because their ocean broker is ready, their air broker is too. Confirm this explicitly with every broker in your import programme before July 8.

How Carra Globe Supports Importers Through CPSC Mandatory eFiling July 2026

Carra Globe provides Importer of Record and Global Trade Compliance services for importers of regulated consumer products entering the United States. Our US import compliance team manages CPSC eFiling capability for regulated product entries through ACE, confirms CPSC Product Registry registration and Certificate Identifier workflow for clients using the Reference PGA method, and audits existing certificates of compliance against the July 8 data element requirements before the mandatory date. For businesses importing from China, Vietnam, India, Bangladesh, and other major consumer goods manufacturing markets, our Delivered Duty Paid service integrates CPSC eFiling preparation into the full landed cost and compliance package for regulated product entries. Our Freight Forwarding service coordinates both ocean and air freight entries with CPSC PGA Message Set data pipelines confirmed operational on every shipment.

Frequently Asked Questions: CPSC Mandatory eFiling July 2026

What happens on July 8 if my entry lacks CPSC mandatory eFiling July 2026 data?

If your product is under a flagged HTS code, ACE immediately generates an electronic warning. CPSC can then select the shipment for examination, which holds it at port for up to 60 days at your cost. Civil penalties reach approximately USD 120,500 per violation under current CPSC civil penalty adjustments. Non-compliance also permanently raises your importer risk score, meaning more frequent holds on future shipments. The voluntary stage is still available to test your process before July 8 without penalties.

Do I need to eFile if my product’s HTS code is not on the 600-code flagged list?

Yes, if your product requires a CPC or GCC under existing CPSC law. The flagged list determines where ACE generates automatic warnings. It does not determine who must comply. Compliance obligations flow from whether your product is subject to a mandatory CPSC safety standard, not from whether your HTS code is flagged. Products not requiring a certificate can file a Disclaimer Message Set to proactively reduce examination risk.

What is the difference between Full and Reference PGA under CPSC mandatory eFiling July 2026?

A Full PGA submits all required data elements directly through ACE on each entry filing. A Reference PGA references certificate data previously stored in the CPSC Product Registry using three Certificate Identifiers. The Reference method is more efficient for repeat shipments of the same products. The Full method suits lower-volume or one-time importers. CPSC has no preference between them. The CPSC Product Registry does not communicate with ACE automatically so you must provide the three identifiers to your broker for every shipment regardless.

Does a material change require new testing under CPSC mandatory eFiling July 2026?

Yes. CPSC requires a new third-party test for CPC products when there is a material change in design, materials, components, or production process, including changes to component suppliers even if the finished product looks identical. A certificate that no longer reflects your current production creates both eFiling accuracy problems and substantive compliance exposure if CPSC examines the goods and finds the certificate does not match what was manufactured.

When does CPSC mandatory eFiling July 2026 apply to Foreign Trade Zone entries?

January 8, 2027. Products entered into a US Foreign Trade Zone and subsequently entered for consumption or warehousing are subject to CPSC mandatory eFiling from that date. The July 8, 2026 mandatory date applies to direct consumption and warehousing entries only. Importers using FTZs for consumer goods have additional time but should begin preparation now to avoid a compressed timeline in late 2026.

How do I identify which safety rules apply for CPSC mandatory eFiling July 2026 citation codes?

Use CPSC’s Regulatory Robot Tool at cpsc.gov/eFiling. Enter your product description and HTS code to identify which mandatory standards apply. Every applicable standard must be listed in the citation codes field of your eFiling. Listing an inapplicable citation or omitting a required one is a compliance error. CPSC published additional guidance on citations, testing exclusions, and disclaim scenarios on February 27, 2026, available in the eFiling Document Library on cpsc.gov.