Article text is currently available in English. The full catalog and all search and filter tools remain available in this language edition.

PGA

A participating government agency other than CBP with import-related jurisdiction, often using ACE to receive regulatory data.

Product factsComposition, intended use and claims
Agency scopeProduct-specific legal coverage
EvidenceApplicable certificates and permits
Entry dataRequired agency and ACE fields

What it means

Requirements depend on the product's legal definition, composition, use, claims and applicable agency program, not only its HTS flags.

Why it matters

Map permits, registrations, labels, certificates and electronic fields before shipment.

How it differs

Customs release is not a substitute for every agency's admissibility or compliance requirements.

Screening partner-agency requirements

  1. 01
    Describe the regulated features

    Record intended users, materials, function, labeling and marketing claims.

  2. 02
    Identify possible agencies

    Screen FDA, CPSC, EPA, FCC and other agencies according to the goods.

  3. 03
    Confirm scope and exceptions

    Read the relevant agency requirements, exemptions and applicable dates.

  4. 04
    Prepare the filing record

    Collect required documents, responsible-party details and entry data before shipment.

Applied example

An electronic consumer product

Customs classification does not by itself answer product-safety or radio-frequency compliance questions.

  1. Identify intended users and any wireless functions.
  2. Review the relevant agency coverage and exceptions.
  3. Link applicable compliance evidence to the product model and shipment.

Common failure points

  • Assuming every product needs the same set of agency approvals.
  • Treating an HTS flag as a complete legal scope determination.
  • Confusing customs release with full product compliance.
  • Obtaining certificates without matching the actual model or use.