APHIS Core Message Set Questions and Answers

APHIS requests that filers provide the common name for the regulated product. For instance, grape and plum tomatoes are regulated as tomato. Animal products may have a general name when listing a product with more specific components. For example, in PG02 a product reported as bouillon can have a component reported as milk. When looking for terminology to use, please refer to import documentation such as permits and phytosanitary certificates. You may also use APHIS’s ACIR Database to look up common names for fruits and vegetables.

The PG01 globally unique product code is an optional field for the APHIS Core message set.

Certain government-to-government documents such veterinary certificates and Convention on International Trade in Endangered Species (CITES) certificates must be presented in their original paper format at the first port of arrival to the inspecting officers. While phytosanitary certificates are now accepted as electronic copies, inspectors can still request originals to verify authenticity. To obtain commodity-specific import guidance, visit the APHIS Import & Exports webpage or APHIS Contacts page to find out how to reach specific programs. Please contact U.S. Customs and Border Protection (CBP) Agriculture at the port of arrival for information on where to provide paper certificates.

The Harmonized Tariff Schedule Code master correlation table in the APHIS Core Supplemental Trade guide and on the APHIS Automated Commercial Environment (ACE) website makes recommendations based on tariff code descriptions and past filing data; however not all correlations will be appropriate for all situations. In addition, the Government Agency Program Code is a requirement in the CBP ACE CBP and Trade Automated Interface Requirements (CATAIR) PGA Message Set and must be entered by the broker. Please contact your software vendor about possibly using the correlation table to auto-populate certain fields to fit your specific business needs.

APHIS restrictions on agriculture imports and transits, including in-bond movements, apply to all shipments. Entry types Transportation and Exportation (62) and Immediate Exportation (63) are exempt for the message set. For in-bond immediate transportation (61), APHIS still requires admissibility information at the first port of arrival. Importers and brokers who are not filing electronic entries (other than in-bonds) in ACE may submit paper documents at the first U.S. port of arrival. Importers and brokers filing electronically in ACE should submit an APHIS Core message set concurrently with the in-bond. Failure to submit the message set with the in-bond will result in paper clearance of the cargo at the first U.S. port of arrival and flagging of APHIS Core message set at the in-bond port of entry, duplicating work.

For APHIS Core submission information, please see “ When to Submit an APHIS Core Message Set, by Entry Type, in ACE” on the APHIS website. Visit the APHIS Imports & Exports website for information on restrictions for agriculture imports and transits.

The system will not generate an SO70 “may proceed” message when PGA data is disclaimed, but a one USG message and release will still occur if all PGA requirements are met.

The APHIS Core Implementation Guide does not provide a table of minimally required data elements as each shipment is unique in the information required by APHIS. The APHIS Implementation Guide does indicate which data elements are mandatory, conditional, or optional when reviewing specific PG lines. Please work with your software vendor to identify which elements are required when filing APHIS Core message set.

No. The APHIS Core message set is transmitted at entry (cargo release) and does not change manifest. The APHIS Core message set must be provided at or before arrival because it contains the information required to determine product admissibility. While cargo isn’t cleared on manifest, APHIS does recommend providing accurate manifest information to help better identify cargo contents.

Beginning January 25, 2021, APHIS will activate Core Message Set flags in ACE. This will change the severity from a “warning” that a message set is needed to “reject” entry for not filing the APHIS message set. That means, importers and brokers using ACE to submit electronic customs entries that include APHIS-regulated plants, plant products, animal products, or live dog imports will have to use the APHIS Core Message Set to provide APHIS-required import data for those items. This phase does not include other live animal imports.

APHIS can only view documents properly coded for APHIS per the DIS implementation guide. The APHIS Core Supplemental Trade Guide includes an LPCO/DIS Correlation Table that provides DIS document codes for commonly used APHIS documents.

Entry type 06 for Foreign Trade Zones (FTZ) are exempt from message set filings at this time. Please review the table of entry types for which APHIS Core message set flags will be enforced on the APHIS ACE website for the most up-to-date guidance. Remember, FTZ admissions still require the submission of APHIS admissibility documentation (permit, certificate, etc.) even if no message set is required for the entry type.

Within the Appendix PGA, there is a subset of units for APHIS Core. This is the general list for most of APHIS. In addition, guidance on APHIS preferred units of measure by category type are in the APHIS Supplemental Trade Guide. One exception to this list is the cut flowers and greenery commodity category type, which is limited to box (BX), bouquet (BQT), bunch (BH), and stem (STM).

APHIS does not have a de minimis exception for admissibility of regulated goods. Filers may submit admissibility information using any applicable entry type including the new entry type 86 for de minimis goods.

Disclaim code B (“per agency guidance”) refers to a product regulated by APHIS, but the agency has determined the product does not need a message set or license, permit, certificate, or other document (LPCO) as a condition of entry. Admissibility guidance can be found on the APHIS  Imports and Exports  webpage or by contacting APHIS directly. Example: Certain animal products fall under Veterinary Guidelines that do not require LPCOs.

APHIS Core does not have a standalone system for filing message sets. Message sets for APHIS Core must be filed in ACE at or before arrival in the United States.

When APHIS Core flags a shipment as AQ2 (data is required), a message set is required regardless of whether a license, permit, certificate or other (LPCO) document is required for admissibility. When APHIS Core flags a shipment as AQ1 (data may be required), you must file a message set if an LPCO is required for admissibility. However, if no LPCO is required for admissibility, the shipment may be disclaimed. Please see the APHIS Core Supplemental trade guide for more information on disclaiming.

APHIS has successfully integrated ACE with ePermits and eFile (the agency’s permitting systems). This integration allows ACE to automatically match permit data reported in PG13/14 record lines with official permit records from ePermits and eFile. “LPCO Type” and “Number” are key data elements for a successful match. When reporting permits issued by ePermits and eFile, an SO72 match/no match message will be sent to the filer. This message is informational only and lets the filer know whether the officers received the permit via the automated process. If the filer receives a no match permit, first check that the “LPCO type” code is appropriate for the permit (a table of codes and their respective permits can be found in the Supplemental Trade Guide). If both the “LPCO type” and permit number are correct, please upload your permit into DIS with the appropriate codes for APHIS and send an e-mail with the entry and permit number to ace.itds@usda.gov so that we can determine the issue.

Several APHIS permits are not currently transmitted to CBP ACE DIS and will not match with proper input. These permits include Veterinary Services Center for Veterinary Biologics permits and Animal Care permits.

If you only have an application number, filers may submit the PPQ application number in lieu of the permit number when applicable. The application number does not have the same matching feature of permits. Please upload a copy of the application to the DIS to help expedite your shipment. Note: if you do have a permit number and submit with the corresponding LPCO type in the message set, the permit will automatically be available to the CBP Agriculture Specialist. This means you would not need to upload a copy of the permit to the DIS. Currently, Animal Care and Veterinary Services Center for Veterinary Biologics do not match in the DIS and must still be uploaded.

The PG02 product code is optional for all message sets, except for all Veterinary Services Center for Veterinary Biologics permitted products that use an APHIS 2006 permit (LPCO type code A06 and PG10 Category Code 307).

Speak to your software vendor about using this field to auto-populate other fields based on product codes. Some readily available codes include the GS1 Global Product Classification Lookup, Taxonomic Serial Number (TSN), and the UN Standard Products and Service Code (UNS)

After entering an APHIS Core message set that passes all validation, the filer will receive a “may proceed” message. This does not bypass the authority of CBP Agriculture to place a shipment on hold for review or inspection.

APHIS requires various licenses, permits, certificates and other documents (LPCO) as a condition of entry. LPCOs include permits, phytosanitary certificates, CITES certificates, certificates of origin, and health certificates, as well as required manufacturer statements. LPCO’s provide CBP Agriculture and APHIS officers with the ability to clear and/or inspect commodities. Some LPCOs provide key information about the commodities’ identity (e.g. the name, amounts, conditions, origin etc.), provide statements of sanitary/cleanliness, or conditions of admissibility (e.g. permission, authorizations, attestments, statements, etc.), and provide arrival notification (e.g. notice of arrival, declaration of importation, etc.).

APHIS regularly updates the Implementation Guide and the Supplemental Trade Guide to make corrections, adjust data element requirements, and update rules. With any new release, APHIS will notify stakeholders about the updates. Stakeholders may also visit the APHIS ACE website to see the most up to date releases.

An example of an “other” document would be a manufacturer’s statement verifying a condition for an animal product. Please refer to the requirements of individual APHIS programs to determine import requirements.

Currently, APHIS Core message set does not validate the expiration dates on permits. An expired permit would not be rejected if entered into PG13/14. However, CBP Agriculture reviews documentation on behalf of APHIS and will reject shipments that do not import requirements, including expired permits.

For a full list of LPCOs and their submission requirements please see the LPCO/DIS Correlation Table in the APHIS Core Supplemental TradeGuide.

APHIS regulates all shipments regardless of end use including express courier. For small value shipments, the filer may use the new entry type 86 for reporting information electronically.

Please be sure to use the most recent APHIS Core Implementation Guide and CBP ACE DIS implementation guide when filing ACE data for APHIS Core.

For documents that do not have a uniquely assigned number, please report the name of the document in the PG14 LPCO number line.

APHIS requires the contact and address information for two entities: the ultimate consignee (UC) and the customs brokers (CB). In a situation where a customs broker is not used, then the importer of record should be identified. When inputting a license, permit, certificate or other (LPCO) document information into the message set, APHIS requires the reporting of the LPCO authorized party (LAP). Other entities may need to be reported as described in the APHIS Core Implementation Guide.

The APHIS Core message set has been in production since 2016. APHIS encourages filers to begin filing message sets before the January 25, 2021 date. If you have questions or receive any errors when filing APHIS Core message sets, please contact us at ace.itds@usda.gov.

Please refer to the most updated APHIS Core Implementation Guide for software needs. Although we might make changes to the APHIS Core Implementation Guide that require minor software updates, APHIS message set in general is established and will not change.

APHIS Core does not have a standalone filing system. APHIS Core information must be transmitted through ACE prior to or at arrival for those filing electronic entries.

Working with software vendors you may be able to pre-fill information in your system before transmitting to ACE. Please see the list of software vendors on the CBP website.

When filing PG13/14 APHIS permits, APHIS Core message set users will receive a “NOT FOUND” message if the permit did match in the system. If this happens, please scan and upload a copy of your permit to the DIS using the proper APHIS DIS codes. “NOT FOUND” messaging will not impact a filing transmission.

No. APHIS has replaced the paper notice of arrival with the APHIS Core Message set. The notice of arrival is now a document with optional submission. For the most up-to-date information, review the document requirements in the LPCO/DIS Correlation Table in the APHIS Core Supplemental Trade Guide.

APHIS removed the requirement for common name general. Common name specific (vernacular or colloquial name) remains mandatory.

You can submit APHIS Core message sets now. For guidance on how to get started, please refer to the CBP ACE support website. For information about message set technical requirements, visit the ACE automated broker interface (ABI) and CBP and Trade automated interface requirements website. For information on submitting APHIS Core message sets, please visit the APHIS ACE website. For help with submitting an APHIS Core message set, please contact APHIS at aphis.itds@usda.gov.

Submitting documents to APHIS is conditional based on the document. APHIS requires paper submission of certain government-to-government documents such as veterinary certificates, and CITES certificates. While phytosanitary certificates are now accepted as electronic copies, inspectors can still request originals to verify authenticity. Requirements for submitting other documents through the ACE Document Image System (DIS) vary. Please refer to the LPCO/DIS Correlation Table in the APHIS Supplemental Trade Guide for the most up to date document requirements.

For questions regarding submitting an APHIS Core message set, please e-mail ace.itds@usda.gov.

Chains of Custody are forms used to transfer actions from CBP Agriculture to APHIS. Please contact your local port to determine when the form is required.

For APHIS Core message set data, the primary means of *enforcement* is to hold the shipment pending corrections. APHIS intends to give brokers every opportunity to amend declarations and submit correct information.

APHIS intends to give brokers every opportunity to make corrections for the most accurate filing. Failure to update after a review and request for correction can result in an Emergency Action Notification.

When disclaiming, no records beyond PG01 are required. Please refer to the APHIS Implementation Guide and CBP ACE CATAIR PGA Message set for guidance on the required elements when disclaiming.

Yes. The crop grower is identified as the party who grows the crops and may not be the same as the person shipping the cargo.

APHIS identifies the Ultimate Consignee as the party in the United States to whom the overseas shipper sold the imported merchandise. If at the time of entry or release the imported merchandise has not been sold, then the Ultimate Consignee at the time of entry or release is defined as the party in the United States to whom the overseas shipper consigned the imported merchandise. If the merchandise has not been sold or consigned to a United States party at the time of entry or release, then the Ultimate Consignee is defined as the proprietor of the U.S. premises to which the merchandise is to be delivered.

Yes. APHIS Core and APHIS Lacey Act Message Sets are separate message sets. If an HTS code flags for both programs, the filer must submit a message set for each program.

APHIS provided a Harmonized Tariff Code Master Correlation Table in the APHIS Core Supplemental Trade Guide. The Guide also indicates the category types, category codes, and the APHIS Operational Program that fall under each HTS code. Please be advised these are recommendations based on the tariff code description and are not absolute or all encompassing. In addition, the U.S. International Trade Commission (USITC) periodically updates the HTS codes throughout the year. APHIS takes reasonable steps to stay up to date with these changes. Even though an HTS code is not included on the list, an APHIS Message Set may still be required.

The PG01 Electronic Image Submitted data element is conditional and not always required. When submitting a yes indicator (Y), the filer is indicating there are documents available in the Document Image System (DIS). If the filer did not upload any documents to DIS, the filer would not provide any information in the field.

You can find the Implementation Guide on  the APHIS ACE website and on the CBP website.

In ACE, APHIS has flagged the Harmonized Tariff Schedule (HTS) codes that may require APHIS data (AQ1) or require APHIS data (AQ2). The filer will see these flags when filing an electronic entry through ACE.

The United States International Trade Commission (USITC) periodically updates the HTS codes throughout the year. APHIS takes reasonable steps to stay up to date with these changes. Filers are required to submit APHIS Core information for all APHIS regulated commodities regardless of ACE flagging. The APHIS Core Supplemental Trade Guide lists the HTS codes and their APHIS flags. 

Routing type (PG32) specifically refers to the shipment’s movement into the United States. If the shipment intended began routing from the Netherlands(NL) and only transited Canada (CA) to arrive at the U.S. port, then PG32 should indicate that routing began at NL and the transit country was CA. If the commodities were imported into CA for storage from NL, then sometime later shipped to the United States, PG32 should indicate routing began in CA.

APHIS uses the PG32 data record to capture information about commodity routing, including the routing type and information about the country through which the commodity passes on its journey to the United States. APHIS requires the country where routing to the United States began for all products regulated by the agency. APHIS uses a separate data record, PG06, to report country origin/source/production of the goods.

Please report transiting and transhipment countries when known, even if not stated on LPCO.

For definitions of transshipment and transit country, please refer to the ACE Appendix PGA. For shipments where the cargo never leaves a carrier, only the original location of routing reporting is required.

The PG26 record captures data pertaining to packaging of goods and their quantity. The first record describes the largest container (outermost container) and the number of containers. The second record describes the contents of the next smallest container. Records 3 through 6 are used in a similar manner (largest to smallest container) when necessary. The last quantity record used must describe the actual amount of product in the smallest container. For APHIS, the quantity reported should be the “net” quantities. The ACE Appendix PGA lists the units of measure allowed for APHIS Core message set. The APHIS Core Supplemental Trade Guide provides a matrix of recommended units of measure by APHIS category type at different packing levels.

Reporting of PG05 scientific genus and scientific species names are determined based on APHIS regulations. The reporting of “spp., or sp.,” for scientific species is acceptable if APHIS regulates the product to the genus level. For more information on APHIS regulations, please visit the APHIS Import & Export website or contact APHIS directly.

On February 03, 2020 APHIS published a Federal Register Notice (2020-01984) announcing full implementation of the APHIS Core message set. The notice alerted that “Importers or brokers using ACE must enter APHIS-required import data when they receive an APHIS-specific HTS flag in order to complete their entry in the system.” For paper filings, this means that an importer or broker who submits a paper-based entry to CBP will also submit APHIS required information in paper form, required by APHIS promptly upon arrival.to prevent duplication. For further information on when an APHIS Core message set is required please see the web page," When to Submit an APHIS Core Message Set, by Entry Type, in ACE". 

Yes. Both APHIS and FSIS regulate the importation of meat and poultry products, along with other agencies. As the PGA message sets for different PGAs are separate, separate data filings are required for each PGA.

APHIS Core PGA data for Animal Products (Category Type AP0300) does not require the submission of PG05 (Genus & Species) information. Source animal species information for animal products should be submitted through PG10 as Commodity Characteristic Qualifier Code A32 (Species Composition). This information is available on the LPCOs accompanying the shipment.

Through enforcement by CBP Agriculture, both APHIS Plant Protection and Quarantine (PPQ) and Veterinary Services (VS) restrict the importation of farm machinery. VS requires a foreign government certificate of steam cleaning for used farm equipment from countries affected with Foot-and-Mouth Disease (FMD). Unclean (soiled/dirty) farm machinery from any country is subject to PPQ soil/contamination restrictions.

APHIS Core PGA data can be disclaimed for new, clean farm equipment or for clean used farm equipment from countries free for FMD.

The import requirements for hunting trophies vary widely and may involve multiple PGAs, including APHIS. All trophies are subject to inspection by CBP Agriculture. APHIS Core PGA data should be submitted for hunting trophies requiring an LPCO. 

Some hunting trophies require a foreign government certificate, while others require the submission of a copy of the importer’s hunting license/permit or other documentation.

No. Cell cultures are cells grown in a laboratory. Canine and equine sperm are typically collected from the live animal, but not grown in a lab.

Examples of food commodities for each AP0300 category code 301 through 304 are listed in the Appendix PGA. In general, only one PG10 AP0300 Category Code is needed. If a single message set is for food commodities that fall into multiple categories, then PG10 can be repeated.

The APHIS Supplemental Trade Guide provides examples when disclaim B code can be used. Bovine rawhide pet chews are exempt from AVS LPCO requirements if they meet certain import requirements. The guidance for this is posted on the APHIS website.

There is no defined format for the manufacturer’s statement. The document is generated by the manufacturer and varies in format.

No. You will not be required to submit APHIS animal product data for non-dairy products that contain no animal-origin material.

The ingredients used to make biofuel can be plant or animal origin and may be subject to APQ and/or AVS import requirements. LPCOs may or may not be required. The intended use code would be 150 “For Commercial Processing as a Non Food Product”.

For farm machinery, we recommend that the cargo description as well as other shipping data or documentation reflect the condition of the equipment as “new.” CBP Agriculture may still inspect the machinery to verify the condition and ensure no soil or other contaminants are present.

We will address this exception as an update to our Supplemental Trade Guide, which is due to be released in December 2020.

APHIS recently simplified and reduced the number of category codes for fruits and vegetables (AP0600) from 35 to 3. The new category codes and their definitions are in the ACE Appendix PGA. At this time APHIS does not intend to create a table that shows category codes and which products they apply to for fruits and vegetables.

The PPQ form 203 is accepted as a copy submitted to the Document Image System (DIS); however, CBP Agriculture may request original documentation to support the information provided in the DIS or the message set.

The A03 APHIS Processing Code is used to designate a shipment as pre-cleared. This designation will help the inspecting officer determine the actions necessary to process the shipment. APHIS expects faster release of shipments when using APHIS Core message sets compared to paper documents.

The PG06 Processing Information is a conditional field that should be reported for treatments required for entry. Processing dates should be reported if available. If a treatment occurs in-route and does not complete processing by arrival, the end date can be left blank. Reporting of processing information will help inspectors determine actions necessary to process the shipment.

Entity numbers for crop growers (DFI) are not required but requested if available. This information is sometimes found on government to government certificates (e.g. phytosanitary certificates).

Entity name (grower name), address, city, and country are required.

For the most up to date APHIS characteristic qualifier codes and their definitions please see the ACE Appendix PGA.

Yes. Different flowers and plants in a bouquet require a message set. For more information on how to report flowers, please see the cut flowers section of the APHIS Core Implementation Guide.

Please refer to the APHIS Import & Export website for guidance on admissibility requirements, including whether or not a permit or phytosanitary certificate is required for entry. You can also reach APHIS through our contacts page to determine the document requirements for your commodity. If your commodity is flagged AQ1 (data may be required) and does not require a permit, certificate, or other document (LPCO) for admissibility then a disclaim of B (per agency guidance) would be appropriate. However, you may choose to file a message set with the minimal data elements to help the inspector make admissibility determinations. The disclaiming of a shipment does not preclude CBP Agriculture from exercising their authority to request documentation or hold for inspection.

In order to align more fully with the  Agriculture Commodity Import Requirements (ACIR) search tool for plant and agriculture-related products, APHIS has retired the codes FRC (Fresh Chilled) and FRF (Fresh Frozen), replacing them with FRS (Fresh) and QFR (Quick Frozen). Additionally, ACIR now uses the article type "fruits and vegetables" (which aligns with AP0600) for many products previously filed under the Miscellaneous category (AP0700). APHIS believes that, in the long run, this alignment will help brokers, filers, and importers better identify import requirements and streamline ACE submissions.

At this time, APHIS Core PGA data is not required for APHIS Veterinary Services (AVS)-regulated live animals (mainly livestock, horses, birds). APHIS Core PGA data is required for live dog imports regulated by APHIS Animal Care (AAC).

AVS-regulated live animals are examined and released directly by AVS. Certain AVS-regulated live animal shipments may require information to be submitted into a VS system (Veterinary Services Process Streamlining-VSPS) for import clearance. Note: live dog imports are still regulated by APHIS, but by APHIS Animal Care, a separate program from Veterinary Services.