PGA Message Sets Explained: What Every Customs Broker and Importer Needs to Know

If you file customs entries in the United States, you have almost certainly encountered PGA message sets. They are the electronic data elements that Partner Government Agencies require alongside your standard CBP entry data, and getting them wrong is one of the fastest ways to land a shipment on hold. This guide breaks down what PGA message sets are, which agencies require them, what data is involved, and how to keep your filings accurate.

What Are Partner Government Agencies (PGAs)?

Partner Government Agencies are federal agencies-other than U.S. Customs and Border Protection-that have authority to regulate specific categories of imports. While CBP is responsible for collecting duties and enforcing trade laws broadly, PGAs enforce regulations in their own domains: food safety, environmental protection, consumer product safety, agriculture, and more.

The major PGAs you will encounter in customs entry filing include:

• FDA - Food and Drug Administration (food, drugs, medical devices, cosmetics)
• USDA/APHIS - Animal and Plant Health Inspection Service (agricultural products, plants, animals)
• EPA - Environmental Protection Agency (vehicles, engines, chemicals)
• CPSC - Consumer Product Safety Commission (consumer goods)
• NHTSA - National Highway Traffic Safety Administration (motor vehicles and equipment)
• TTB - Alcohol and Tobacco Tax and Trade Bureau (alcohol, tobacco, firearms)
• FWS - Fish and Wildlife Service (wildlife and wildlife products)
• AMS - Agricultural Marketing Service (grading and quality standards)
• FSIS - Food Safety and Inspection Service (meat, poultry, egg products)

Each PGA has its own set of regulations, and when an imported product falls under one or more of these agencies, the entry must include that agency's required data elements. That is where PGA message sets come in.

What Exactly Is a PGA Message Set?

A PGA message set is a structured collection of electronic data elements that a specific Partner Government Agency requires for goods under its jurisdiction. These data elements are transmitted to the agency through the Automated Commercial Environment (ACE), the single-window system CBP uses to process imports and exports.

Before ACE, importers and brokers often submitted PGA information on paper forms or through separate systems for each agency. The move to electronic PGA message sets within ACE consolidated that process. Now, when you file an entry, your ABI software transmits both the standard CBP data and all applicable PGA message set data in a single electronic filing.

Each PGA defines its own message set structure. The data elements vary from agency to agency, but they typically include product identifiers, compliance codes, certification information, and details about the shipment that the agency needs to make an admissibility determination.

Key PGAs and Their Message Set Requirements

AgencyScopeKey Data ElementsFDAFood, drugs, devices, cosmetics, tobaccoProgram code, processing code, product code, manufacturer/shipper ID (FEI), packaging details, intended use, country of productionAPHISAgricultural products, plants, animalsPPQ form data (PPQ 505, 587, etc.), permit numbers, treatment codes, pest risk category, origin informationEPAVehicles, engines, chemicalsVehicle/engine certification codes, TSCA compliance certifications, chemical identity, importer certification statementsCPSCConsumer productsProduct certificate data, testing lab information, applicable safety standards, product identifiers (expanding requirements ahead)AMSAgricultural grading and marketingCommodity inspection data, grade certificates, organic certificationFSISMeat, poultry, egg productsEstablishment numbers, product category codes, country certificates, reinspection marksLACIPlants, wood, plant products (Lacey Act)Species scientific names, country of harvest, quantity, unit of measure for plant material

FDA: The Most Complex Message Set

FDA's message set is arguably the most data-intensive. Each product line requires a program code (identifying the FDA program, such as food, drugs, or devices), a processing code (describing how the product was processed), and a product code (a seven-character identifier for the specific product). You also need the manufacturer's FDA Establishment Identifier (FEI), the shipper, packaging type and quantity, and anticipated arrival information. Errors in any of these fields can trigger an FDA hold.

APHIS: Agriculture and Pest Prevention

APHIS message sets focus on preventing the introduction of agricultural pests and diseases. Depending on the commodity, you may need to reference PPQ forms (like PPQ 505 for plant imports), provide permit numbers, and include treatment certification codes that verify the product was fumigated, heat-treated, or otherwise processed to meet phytosanitary requirements.

EPA: Vehicles, Engines, and Chemicals

EPA's message set covers two major areas. For vehicles and engines, the data includes emission certification codes and conformity statements. For chemicals, you must provide TSCA (Toxic Substances Control Act) certification indicating whether the imported substance is on the TSCA inventory and in compliance. Each requires different data elements within the EPA message set.

Static vs. Dynamic PGA Data

One practical distinction that experienced entry writers understand is the difference between static and dynamic PGA data elements.

Static data remains the same every time you import a given product. Product codes, processing codes, program codes, and manufacturer identifiers do not change from shipment to shipment. Once you have established the correct codes for a product, they can be stored in a parts library or automation system and reused.

Dynamic data changes with each shipment. Packaging types and quantities, lot numbers, shipment-specific permit references, and arrival information are all examples. These fields must be populated fresh for every entry based on the actual commercial documents for that shipment.

Why this matters: The most efficient filing operations automate the static elements and focus human review on the dynamic data that changes per shipment. This approach reduces errors without removing the oversight that variable data requires.

How PGA Data Flows in the Entry Process

The journey of PGA data follows a predictable path from origin documents to agency review:

• Commercial documents arrive - Invoices, packing lists, certificates of analysis, permits, and other shipping documents contain the raw information needed to populate PGA fields.
• Entry writer extracts PGA data - The broker or entry writer identifies which PGAs apply (based on HTS codes and product descriptions), then pulls the required data elements from the documents and any stored product records.
• Data is transmitted via ABI to ACE - The  and its associated PGA message sets are filed electronically through the broker's ABI-certified software into the ACE system.
• ACE routes data to the relevant PGA - ACE distributes each agency's message set to that agency for review. FDA receives FDA data, APHIS receives APHIS data, and so on.
• PGA issues a disposition - The agency reviews the data and returns a decision: may proceed, hold, examination, or refused entry.

The first flag at every HTS line on the entry that determines whether a PGA message set is needed is the PGA flag itself. Accurate PGA screening at the start of the process ensures you include message sets for every applicable agency and avoid filing without required data.

Common Challenges with PGA Message Sets

Despite the structured nature of PGA message sets, they remain one of the most error-prone areas of customs entry filing. Here is why:

• Multiple PGAs per line item. A single product can fall under two, three, or more agencies simultaneously. A food product imported from overseas might require both FDA and APHIS message sets. A wood product could trigger both APHIS and Lacey Act declarations.
• Different data requirements per product. Even within the same shipment, each line item may need a completely different set of PGA codes. There is no one-size-fits-all template.
• Manual data entry errors. Product codes, processing codes, and FEI numbers are long, alphanumeric, and easy to mistype. A single wrong digit can trigger a hold.
• Regulatory changes. PGA requirements evolve. CPSC is expanding its electronic filing requirements. FDA updates its product code database. Brokers must track these changes across every agency.
• Incomplete commercial documents. Shippers do not always provide the information a PGA requires. Entry writers often have to chase down manufacturer IDs, treatment certificates, or species declarations that are missing from the original paperwork.

Consequences of Getting PGA Data Wrong

The stakes for incorrect PGA message sets are real and immediate:

• Holds: The PGA flags the entry for review, and the shipment cannot be released until the data is corrected or additional information is provided. This creates delays and storage costs.
• Examinations: The agency may order a physical inspection of the goods, adding days or weeks to the clearance timeline.
• Refused entry: If the product does not meet the PGA's requirements, it can be denied entry entirely and must be exported or destroyed.
• Penalties: Repeated errors or negligent filings can lead to monetary penalties from both CBP and the relevant PGA.
• Importer reputation: A pattern of PGA holds can increase an importer's risk score in ACE, leading to more frequent examinations on future shipments.

For customs brokers, PGA accuracy is not just a compliance issue-it is a client service issue. Importers expect their shipments to clear quickly, and repeated holds erode trust.

Getting PGA Message Sets Right, Every Time

The most reliable approach to PGA message sets combines three elements: accurate PGA screening at the point of classification, a well-maintained parts library that stores static PGA data for recurring products, and a systematic review process for dynamic fields on each shipment.

Automation plays a growing role here. Modern customs entry automation platforms can identify applicable PGAs from HTS codes, pre-populate known product data, and flag missing fields before filing-catching errors that would otherwise result in holds at the agency level.

See How Cervo Automates PGA Screening

Cervo AI identifies applicable PGAs, pre-fills message set data from your parts library, and flags missing fields before you file-so your entries clear faster with fewer holds.

Learn About PGA Screening