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 21 of 419 messages. Clear filters
- PGA UpdateCSMS #69988954
CBP moves three APHIS PGA message set documents to the production section
CBP moved three PGA message set documents from the draft section to the production section of CBP.gov. The documents are Appendix PGA, the APHIS (CORE) Implementation Guide v6.4 and the APHIS Supplemental Guide Appendix APH-A v4.2. The message does not list the changes and refers to CSMS messages 69379587 and 69402038 for details.
Show Allied's positionHide Allied's position
These are technical specifications for filing software. If you import goods that need APHIS data, ask us to review how the changes affect your entries.
- PGA UpdateCSMS #69536147
CBP and Commerce held a webinar on fighting unfair trade practices
CBP announced a webinar with the Department of Commerce on Combating Unfair Trade, held September 21, 2026 at 2:00 PM EST. The session covered new antidumping and countervailing duty orders and how to report suspected violations or file Enforce and Protect Act allegations. Registration was free but required in advance.
Show Allied's positionHide Allied's position
This was an informational webinar and the registration deadline has passed. It does not change how we file entries for clients. Clients who want guidance on AD/CVD orders or possible violations affecting their goods should ask us to review their entries.
- PGA UpdateCSMS #69402038
CBP updated draft ACE CATAIR appendix for USDA APHIS PG10 codes
CBP announced an updated ACE CATAIR Appendix PGA in the Draft Chapters section of CBP.gov. The update added AGAR and EXAR to the PG10 Commodity Characteristic Qualifiers list for USDA APHIS. It also updated the name and definition for code 406 in the PG10 Category Codes section.
Show Allied's positionHide Allied's position
This update concerns the technical ABI data specifications that brokers use to file entries with USDA APHIS data. It does not require any action from importers or shippers. Clients with questions about how this affects specific APHIS filings should ask us to review their entries.
- PGA UpdateCSMS #69382435
CPSC eFiling Requirements Took Effect, but CBP Still Accepted Incomplete Data
CBP announced that CPSC fully implemented its eFiling PGA message set requirements on July 8, 2026, making eFiling of CPSC certificate of compliance data mandatory. CBP said ACE would still accept entries with missing or incomplete CPSC data, without rejecting them, as long as the overall CATAIR PGA format was followed. CPSC could still review or reject the CPSC data through a separate message and pursue enforcement action when required eFiling data was missing.
Show Allied's positionHide Allied's position
This applied to entries for CPSC-regulated products that we filed for clients. It meant CBP would not reject an entry solely for missing CPSC data, but CPSC could still reject that data later or take enforcement action. We advised clients importing CPSC-regulated goods to provide complete certificate of compliance information at the time of filing. Later CSMS messages may have changed these requirements, so clients should ask us about their specific entries.
CBP added an enforcement flag for Entry Type 13 to its draft PGA flag table
CBP updated the draft Partner Government Agency (PGA) Flag Enforcement Table and posted it in the CATAIR Draft Chapters section. The update added an enforcement flag for Entry Type 13 (ET13). CBP said the table is available online and gave an email contact for questions.
Show Allied's positionHide Allied's position
This is a technical draft update to CBP's PGA data table for automated filing systems, not a rule change for importers. It concerns how brokers and their ABI systems handle Entry Type 13 filings. Clients do not need to act, and later CSMS messages may update or finalize this draft table.
- PGA UpdateCSMS #69379587
APHIS updated plant inspection filing rules for tissue culture and lab status codes
CBP announced that USDA's APHIS revised the Core Message Implementation Guide for imports going to Plant Inspection Stations. The changes renamed Category Code 406 to Tissue Culture and added new required data fields, and added a new laboratory testing status code "I" for automated routing to inspection stations. APHIS said the changes went live in the ACE certification environment on July 27, 2026 and in production on August 27, 2026.
Show Allied's positionHide Allied's position
This notice affected filers who submit APHIS Core Message Set data for plants for planting and tissue culture shipments routed to Plant Inspection Stations. Since the production deployment date of August 27, 2026 has passed, we apply these data requirements to the entries we file that involve tissue culture or Plant Inspection Station routing. Clients importing these commodities should confirm with us that their shipment data meets the updated field requirements. Clients who do not ship regulated plant commodities do not need to act.
- PGA UpdateCSMS #69368723
CBP finalized CPSC filing guide and PGA enforcement table on CBP.gov
CBP announced that it moved the CPSC Implementation Guide and the PGA Flag Enforcement Table from the draft chapters section to the official PGA Message Set Documents section on CBP.gov. This made the documents part of the standard CATAIR reference material for entries with CPSC data. The message did not state an effective date for any filing requirement.
Show Allied's positionHide Allied's position
This was a documentation update, not a new filing requirement. It affects the technical reference we and our software use for entries with CPSC-regulated goods, but it did not change what data clients must give us. Clients do not need to act, and later CSMS messages may have further updated these documents, so ask us if you have a specific entry question.
- PGA UpdateCSMS #69177694
CPSC clarified it will not require PGA data on flagged HTS codes
CBP passed along a CPSC notice that as of July 8, 2026, CPSC implemented its PGA Message Set for eFiling. CPSC clarified that, unlike some other partner government agencies, it will not require ABI software to block entries missing PGA data for HTS codes flagged CP1 or CP2. Filers may submit no CPSC message even when a flag is present, though CPSC encourages advisory messages to remind filers that data may be needed.
Show Allied's positionHide Allied's position
This message concerns how ABI software and filers handle CPSC flagged HTS codes, not a new duty or entry requirement. Based on the message, CPSC's position was a permanent policy choice rather than a temporary rule, so it likely still applies, but clients should ask us to review their specific entries if CPSC data questions come up. Clients do not need to take any action on this notice.
CBP added a new CPSC data code to the ACE PGA message set
CBP announced an update to the ACE CATAIR PGA Message Set. The update added a new qualifier code, CP4, for component part descriptions under the PG19 record, created for Consumer Product Safety Commission eFiling. CBP noted other partner government agencies may use this code in the future.
Show Allied's positionHide Allied's position
This update concerns the technical data fields brokers use to file Partner Government Agency data in ACE, mainly for CPSC filings. It does not change any duty, classification or entry requirement for importers. Clients do not need to act, and we apply the correct data fields when we file entries that require CPSC information.
- PGA UpdateCSMS #69019366
CBP updated CPSC message filing guide to version 2.5 in June 2026
CBP announced that an updated version 2.5 of the Consumer Product Safety Commission (CPSC) Message Implementation Guide was available on the CATAIR website. The update included updated scenarios under Disclaim A. It applied to filers who transmit CPSC data through ABI.
Show Allied's positionHide Allied's position
This update concerns the technical ABI message format that brokers use to file CPSC data, not the substance of any CPSC requirement. It is a broker and filer system matter, so clients do not need to act. If a later CSMS message has updated the guide further, ask us and we can confirm which version we apply to filings.
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.
- PGA UpdateCSMS #68770001
CBP Updated Its PGA Error Code Dictionary in May 2026
CBP announced an updated PGA Error Code Dictionary on May 28, 2026. The update added new error codes (PHI, PHJ, PHK), revised descriptions for PHF and PHG, and added DEA and FDA program code errors for existing codes. CBP published the full list in a Table of Changes on its website.
Show Allied's positionHide Allied's position
This update concerns the technical error codes brokers and filers see when transmitting partner government agency data through ABI. It does not change any duty, classification or entry filing requirement for importers. Clients do not need to act. We refer to the current dictionary when resolving PGA transmission errors on entries we file, and note that CBP issues these updates quarterly so a newer version may now exist.
- PGA UpdateCSMS #68634647
CBP Updated CPSC Electronic Filing Guide for ABI Messaging
CBP announced an updated Consumer Product Safety Commission (CPSC) Message Implementation Guide, posted to the CATAIR website. The update clarified that only one OI record is allowed per HTS code, and added language on the Intended Use Code restriction for type B disclaims. The guide is a technical reference for filers submitting CPSC data through ABI.
Show Allied's positionHide Allied's position
This message concerns the technical ABI filing format that brokers use to submit CPSC data, not a change in import requirements. Clients do not need to act. Later CSMS messages may have updated these filing specifications further, so if a specific entry raises a CPSC data question, ask us to review it.
- PGA UpdateCSMS #68510400
CBP Reinserted Footnote 4 in PGA Flag Enforcement Table (May 2026)
CBP announced that the April 27, 2026 version of the PGA Flag Enforcement table reinserted footnote #4. The updated document is posted in the Draft Chapters section of the CATAIR page. This was a technical documentation update related to an earlier message, CSMS # 68468385.
Show Allied's positionHide Allied's position
This message concerns technical PGA flag documentation used for ABI filings and does not require client action. We reference the current PGA Flag Enforcement table when preparing entries with partner government agency data. Clients do not need to do anything in response to this update.
CBP updates ACE CATAIR PGA message set with new data codes
CBP announced an update to the ACE CATAIR PGA Message Set on May 1, 2026. The update added two new qualifier codes, LAT and LON, to the PG60 record valid for the parent PG19 record. It also added a new inspection or lab testing status code, N, to the PG30 record.
Show Allied's positionHide Allied's position
This is a technical update to the data set used for filing partner government agency information in ACE. It concerns the systems and data formats brokers use, not actions importers or shippers need to take. Later CSMS messages may have changed related PGA requirements, and clients with questions about how this affects their specific entries should ask Allied to review them.
- PGA UpdateCSMS #68468385
CBP added CPSC enforcement flagging to its PGA flag table
CBP announced it updated the Partner Government Agency (PGA) Flag Enforcement Table on CBP.gov. The update added flagging enforcement for the Consumer Product Safety Commission (CPSC). CBP directed questions about CPSC flagging to the CPSC eFiling Support team.
Show Allied's positionHide Allied's position
This update concerns the technical PGA flagging data that brokers use in filing systems, not a new rule for importers. We monitor CATAIR table updates like this one as part of how we file entries with PGA data. Clients do not need to act on this notice.
- PGA UpdateCSMS #68290359
CBP published CPSC Message Implementation Guide for ACE filing, production set for July 8
CBP announced on April 8, 2026 that the Consumer Product Safety Commission (CPSC) Message Implementation Guide was available on CBP.gov. The guide appeared in the Draft Chapters: Future Capabilities section of the ACE ABI CATAIR. CBP scheduled the CPSC Message Set for certification on April 15 and production on July 8. CBP directed questions to the CPSC eFiling Support team.
Show Allied's positionHide Allied's position
This message was a technical notice for software developers and filers who transmit data through ABI. It did not require importers to act. Later CSMS messages may have changed how CPSC data is filed, so clients who import consumer products should ask Allied to review their entries.
- PGA UpdateCSMS #68096516
CBP detailed reporting for a March 2026 Jones Act waiver, which has since expired
CBP announced that DHS issued a 60-day Jones Act waiver on March 17, 2026, at the request of the Department of War, letting foreign-flag vessels carry listed commodities between U.S. ports. The waiver ran until May 17, 2026. CBP asked carriers using the waiver to email vessel, cargo, and port details, and required a paper CBP Form 1302 with specific wording so the cargo could clear as domestic. Foreign vessels still had to file vessel entrance and clearance under 19 CFR Part 4, and vessel owners had to report voyage details to the Maritime Administrator.
Show Allied's positionHide Allied's position
This message concerned vessel carriers operating under a Jones Act waiver that expired on May 17, 2026. It did not affect the import entries Allied files for clients, since it dealt with vessel entrance and clearance, not cargo entry filing. Clients do not need to act on this message. If a client has questions about a shipment that moved under this waiver, they should ask Allied to review the entry.
CBP updated PGA Appendix document for FDA, DEA and NHTSA/NMFS codes
CBP announced updates to the Appendix Partner Government Agency document on its CATAIR webpage. The changes covered FDA Affirmation of Compliance codes for tobacco, a new DEA agency program code for encapsulating machines, and corrections to NHTSA and NMFS program codes. CBP said filers should review the Appendix PGA table of changes for details.
Show Allied's positionHide Allied's position
This is a technical update to PGA data element codes used in ACE filings for FDA, DEA, NHTSA and NMFS shipments. We apply the updated codes when we file entries that require these PGA disclosures. Clients importing tobacco products, encapsulating machines, or NHTSA or NMFS regulated goods should ask us to confirm the correct codes are used on their entries.
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