Trade News
What changed at U.S. Customs?
Every message from the CBP Cargo Systems Messaging Service (CSMS), with a plain-English summary and Allied CHB's position. We add new messages every hour.
Get the CBP messages of the week by email
One email each week with the new CSMS messages, a plain-English summary and our position. Unsubscribe at any time.
- Source
- CBP CSMS
- Updated
- Every hour
Showing 4 of 427 messages. Clear filters
FDA added an EU code option for prior notice filings in PG13
CBP announced on June 8, 2026 that FDA added a new Government Geographic Code Qualifier, EU (European Union), for the LPCO Issuer data element in PG13. FDA said the code applies to Stand-Alone Prior Notice submissions and Food Commodity Combined Entry submissions. FDA said the next version of its ACE Supplemental Guide would reflect the change.
Show Allied's positionHide Allied's position
This was a technical update to an FDA data field used in prior notice and food entry filings. Later CSMS messages may have changed FDA's PG13 requirements since June 2026, so clients with FDA-regulated food shipments should ask us to review how their current entries are coded. Clients do not need to take action on this specific message now.
FDA Supplemental Guide version 2.6 went live in ACE production on March 10, 2026
CBP announced that changes for the FDA ACE Supplemental Guide version 2.6 were deployed to the CBP production environment on March 10, 2026. CBP moved the guide to the Implementation Guide Ready for Coding section of the CATAIR PGA documents on CBP.gov. FDA said it would also update its Affirmation of Compliance Codes, the Affirmation of Compliance Quick Reference and the Industry Quick Reference Guide.
Show Allied's positionHide Allied's position
This message covered the technical format of FDA data that filers send through ABI with entries. It concerned filers and software providers, so importers did not need to act. Later CSMS messages may have changed the FDA requirements. Clients who import FDA-regulated goods should ask us to review their entries if they have questions.
CBP updated FDA data validation rule and pushed deployment to March 10, 2026
CBP announced a clarification to the draft FDA Supplemental Guide version 2.6, requiring that entries with FDA Process Indicator Code A also use Government Agency Processing Code CSU, or the entry is rejected. CBP rescheduled the production deployment of this validation to March 10, 2026 and asked filers to test in the certification environment. The message affects entries that include FDA-regulated merchandise.
Show Allied's positionHide Allied's position
This message set a technical ABI validation rule for FDA-regulated entries that took effect in production on March 10, 2026. We applied this coding requirement to FDA entries we file from that date. Later CSMS messages may have changed FDA ACE requirements since then, so clients with FDA-regulated goods should ask us to confirm the current coding used on their entries.
FDA Removed Invalid 'FTZ' Compliance Code From ACE Filings
CBP announced that FDA removed the Affirmation of Compliance code "FTZ" from ACE Appendix PGA, effective with the February 21, 2026 ACE deployment. FDA said it uses entry type and PG30 record data, not an AofC code, to identify FTZ withdrawals. CBP stated that any entry transmitting the "FTZ" code after that deployment would have its FDA data rejected.
Show Allied's positionHide Allied's position
This change took effect on February 21, 2026 and still applies today. We do not transmit the AofC code "FTZ" on FDA-regulated entries we file and rely on entry type and PG30 data instead, as FDA requires. Clients do not need to do anything unless they specifically instruct us to use an AofC code; if so, they should confirm with us that it is not "FTZ".
The summaries and positions are general information, not legal advice. Always check the official CBP message, which each page links to.
Does a change affect your entries?
Call (908) 291-8001 or email info@alliedchb.com