What changed in the ACE message set?
CBP added one new qualifier code, CP4, to the PG60 record and said it is valid for the parent record PG19. The agency said the code was created for CPSC eFiling, though it may also be used by other partner government agencies in the future if applicable.
| Item | Update |
|---|---|
| Bulletin date | July 7, 2026 |
| System touched | ACE CATAIR PGA Message Set |
| New code | CP4 |
| Intended use | CPSC eFiling support |
Why does this matter for importers and brokers?
Because technical message changes quickly become filing-risk changes. If your entries involve CPSC-regulated goods, the operational issue is not the code itself but whether brokers, software providers, and compliance teams update mapping logic fast enough to avoid rejects, missing data, or manual rework.
Is this only a software-team issue?
No. Importers should read this as a filing-readiness issue. Even if your customs broker handles submission, you still need to confirm that product data, component descriptions, and supporting compliance records are being passed in the format now expected by CBP and CPSC workflows.
What Shippers Should Do
- Ask your customs broker or filing software provider whether CP4 support is already live.
- Flag any CPSC-regulated SKUs that may be affected by new eFiling data requirements.
- Verify that product-component descriptions and compliance records are organized before entry filing.
- Expect more scrutiny around data quality, not less, as CPSC eFiling becomes more structured.