Answer first
Core rule
Answer first: ACE is the electronic Single Window, not a universal PGA rulebook. An HTS flag is a routing signal, not always a final jurisdiction decision; the commodity's identity and intended use can determine whether agency data are required or a supported disclaimer is appropriate. After identifying the agency and program, use that agency's own supplemental guide and underlying law—never copy another agency's fields. Technical ACE acceptance does not by itself establish admissibility. For the October 2026 CBLE, use the designated 2025 Annual CFR and listed CBP references; current agency guides are a separate live-operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient.
Authority and lookup route
Locate the rule before returning to the facts. Links point to government or official publications.
Reference lookup task
For one flagged HTS line, document the product identity and intended use, identify the possible agency, and find the exact agency supplemental guide before deciding to file or disclaim.
Route: Start with the HTS flag, verify jurisdiction from agency guidance, then follow only that agency's PGA implementation guide and governing law.
Worked example
An FD1-flagged shipment contains safety goggles documented and sold solely for industrial grinding, with no medical claims or medical intended use. Should the filer invent FDA product data merely because of the flag?
- 1Treat FD1 as a may-or-may-not-be-regulated signal rather than conclusive FDA jurisdiction.
- 2Verify the industrial intended use and product facts against FDA's flag guidance.
- 3If the documented facts support non-FDA use, use the supported FDA disclaimer route rather than fabricated PGA data.
- 4Still check whether a different agency or non-PGA rule applies to the same goods.
Conclusion: No. Verify jurisdiction from the actual intended use and use a supported disclaimer if appropriate; never fabricate agency data from the flag alone.
Common traps
- Treating every HTS agency flag as a conclusive jurisdiction decision.
- Copying fields or codes from one PGA's guide into another PGA filing.
- Equating an ACE technical acceptance with final agency admissibility.
- Marking the topic verified despite the absence of a dedicated supported question pool.