CBP's Automated Commercial Environment is the front door for all commercial imports into the United States, but CBP isn't the only agency with jurisdiction over what enters. A growing list of federal agencies — collectively called Partner Government Agencies in ACE terminology — have integrated their admissibility and compliance requirements into the ACE system. When your shipment contains goods regulated by one of these agencies, the entry data requirements expand beyond the standard CBP fields, and the entry can't clear until the PGA requirements are satisfied.
For freight forwarders and customs brokers, PGA requirements are a significant source of entry complexity and delay. Missing a required PGA field or submitting incorrect agency data causes the entry to be held — sometimes with an automated "May Proceed" message from the PGA, sometimes with a request for additional documentation, and occasionally with a physical examination. Understanding which shipments trigger PGA requirements and what data each agency needs is the baseline competency for anyone processing entries across general merchandise categories.
Which Agencies Are PGAs in ACE?
ACE currently integrates with more than 40 federal agencies, but the ones that generate the most entry-level complexity for general freight forwarders are a manageable subset. The Food and Drug Administration (FDA) covers food, drugs, devices, cosmetics, and radiation-emitting electronics. The USDA's Animal and Plant Health Inspection Service (APHIS) covers plant and plant products, certain animals, and biological items. The USDA's Agricultural Marketing Service (AMS) and Food Safety and Inspection Service (FSIS) cover certain agricultural commodities and meat products respectively. The Environmental Protection Agency (EPA) covers pesticides, chemicals regulated under TSCA, and certain vehicles and engines. The Consumer Product Safety Commission (CPSC) covers consumer products subject to CPSC-administered standards. The Fish and Wildlife Service covers wildlife, wildlife products, and items made from species regulated under CITES.
Each of these agencies has distinct data requirements in ACE. They're not interchangeable, and understanding FDA requirements doesn't help you much with APHIS. The data elements are agency-specific because the regulatory purposes are different: FDA is looking for establishment registration numbers, product codes, and country of manufacturer; APHIS is looking for country of origin, species, and import permit numbers; EPA may want product identifier and compliance certification.
FDA: The Highest-Volume PGA Requirement
FDA is the PGA that most freight forwarders encounter most frequently because its jurisdiction is so broad. Almost any food product, any cosmetic, any device with electronic components, any drug or supplement, and any radiation-emitting product triggers an FDA data requirement on the entry.
The core FDA data elements in ACE are: affirmation of compliance codes (a coded set of declarations about the product's regulatory status), the FDA product code (a 7-character alphanumeric identifying the specific product category), the country of manufacture, the shipper name and address, the manufacturer/grower name and address, and the importer's FDA-registered facility number if the importer is a food facility. For most food products, the Bioterrorism Act Prior Notice requirement also applies — this is a separate filing that must be submitted before the shipment arrives, not as part of the entry itself.
The affirmation of compliance codes are the field that causes the most confusion. There are dozens of codes, covering everything from "FDA1" (FDA registered food facility) to "MID" (manufacturer ID) to specific drug application numbers (NDIN, ANDA, NDA, etc.). The correct codes for a given shipment depend on the product type, the regulatory pathway it came in under, and sometimes the shipper's specific registration status. For most general merchandise food imports, the relevant codes are a small subset, but knowing which subset requires understanding the product category.
USDA APHIS: Plants and Agricultural Products
APHIS requirements apply to any shipment containing plant material, wood packaging, soil, certain animals, or biological items. The PPQ (Plant Protection and Quarantine) side of APHIS is the most commonly encountered: almost any fresh fruit, vegetable, or plant product requires an import permit or phytosanitary certificate, and these need to be referenced in the ACE entry data.
The practical challenge with APHIS data is that the required country-of-origin specificity is often more granular than what appears on the commercial invoice. APHIS cares about country of harvest or country of origin at the agricultural product level, not country of last shipment. A pineapple from Costa Rica shipped via Miami may have a commercial invoice origin of "Costa Rica" — that's fine. A shipment that transited through multiple countries with intermingled product from different origins requires more careful documentation of which product came from where.
Wood packaging material (WPM) is an APHIS requirement that catches forwarders who aren't thinking about it: any wooden pallet, crate, or dunnage used in the shipment must meet ISPM 15 treatment standards and have the appropriate IPPC mark. The entry may need to declare compliance with ISPM 15 treatment. Missing this isn't caught by the entry system automatically — it becomes an issue if the shipment is selected for examination.
EPA: Pesticides, Chemicals, and Vehicles
EPA requirements divide into several distinct regulatory programs. For pesticides, the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA) registration or exemption information is required on entries for pesticide products — this means the EPA Registration Number for registered pesticides, or specific exemption codes for products that are exempt from registration. For chemicals subject to TSCA (Toxic Substances Control Act), the entry must include either a TSCA certification that the chemical is not subject to TSCA, or specific certifications for chemicals that are subject but compliant.
Vehicles and engines imported into the United States must comply with EPA emissions standards under the Clean Air Act. The entry must include conformity certifications or exemption documentation. This applies to vehicles not originally manufactured for the US market that don't meet US EPA standards — a common issue with parallel imports and personal imports of foreign-market vehicles.
The TSCA certification is the EPA requirement most commonly encountered by general freight forwarders handling industrial chemicals, polymers, or certain chemical-containing products. The negative TSCA certification ("the chemicals in this shipment are not subject to TSCA regulation or are exempt") is the most common case and is straightforward to complete. Positive TSCA certifications for subject chemicals require more detailed product knowledge and coordination with the importer's technical team.
CPSC: Consumer Product Safety Data
CPSC's ACE integration is more recent and still evolving. CPSC has jurisdiction over a wide range of consumer products, and products subject to mandatory safety standards administered by CPSC — children's products, fireworks, mattresses, bicycle helmets, and many others — may require specific certificates of compliance (CoC) to be filed as part of the import process.
The data requirements for CPSC in ACE are tied to the HTS classification: certain HTS headings trigger CPSC data requirements. Getting the HTS right isn't just a tariff question — it's also the mechanism by which the ACE system determines whether PGA requirements apply at all. A product classified under the wrong HTS might avoid triggering the CPSC check in the entry system while still being subject to CPSC jurisdiction. This is one of several reasons why classification accuracy matters beyond just the duty rate.
Practical Extraction Challenges for PGA Data
The data elements required for PGA compliance — FDA product codes, APHIS permit numbers, EPA registration numbers, manufacturer facility IDs — rarely appear in a standardized location on commercial trade documents. They're not typically on the bill of lading. They may be on the commercial invoice if the exporter has been thorough, but more often they need to be gathered separately from the importer's own compliance documentation or from communications with the exporter.
This creates an extraction challenge that's different from standard entry fields. For most CBP-required entry data, the source document is the commercial invoice and bill of lading. For PGA data, the source may be a separate FDA Prior Notice confirmation, an APHIS import permit, a TSCA certification letter, or a CPSC certificate of compliance. These documents have different formats, different issuing authorities, and different field structures.
When we built PGA data extraction into Tradevynt's pipeline, the core decision was to treat each PGA as a separate document type with its own extraction schema, rather than trying to apply a unified extraction model to all regulatory documents. FDA Prior Notice confirmations have a predictable structure from the FDA system itself; APHIS permits have a different structure; TSCA certifications vary by party but have common required elements. Each gets its own field mapping, its own confidence model, and its own validation against the known constraints for that agency's data format.
The validation step is particularly important for PGA data because errors here don't just cause entry delays — they can result in holds, examinations, or refusal of admission that affect the entire shipment. A malformed FDA product code or an APHIS permit number with the wrong format will bounce from the ACE system; but an FDA product code that's syntactically valid but semantically wrong for the actual product may pass the system check and only surface as an issue when a CBP or FDA reviewer looks at the entry.
The honest answer to "can you automate PGA data entry" is: for known, repeat product lines where the regulatory documentation is established and consistent, yes — reliably and with appropriate confidence validation. For new product lines or new suppliers where the PGA documentation is being obtained for the first time, automation helps gather and structure the data, but human verification of the regulatory classification and the appropriate PGA codes is still the right call before filing.