How to Use AI Classification Tools Without Violating Customs Law

How Can I Use AI for HTS Classification Without Breaking the Law?

AI classification tools are permissible when they function as pre-classification research aids: standalone from entry filing, with meaningful disclaimers, and with a licensed customs broker making the final classification decision. CBP's January 2026 ruling in HQ H350722 established the framework. The key is separating research from entry preparation and keeping a licensed professional in the decision seat.

Do AI Classification Tools Require a Customs Broker License?

Not necessarily. CBP distinguishes between general-purpose research tools (no license required) and tools that provide specific classifications for specific merchandise being entered (license required). The dividing line is whether the tool's output has a "nexus to a prospective entry," meaning a reasonable possibility that the classification will end up on an entry filed with CBP.

Trade compliance teams are under more pressure than ever. The tariff environment is volatile, product lines are expanding, and classification backlogs are growing. AI-powered tools promise faster, more consistent HTS research. But after CBP issued HQ H350722 in January 2026, compliance leaders need to understand exactly where the legal lines are before adopting any AI classification tool.

The good news: the ruling does not prohibit AI classification tools. It establishes a clear framework for using them compliantly. This guide translates that framework into a practical workflow.

Last updated: March 2026

What Makes an AI Classification Tool Legal vs. Illegal?

CBP does not regulate AI classification tools as a separate category. It applies the same "customs business" test that has governed classification activities since 1999. The test comes down to three questions.

Question 1: Does the tool provide classifications beyond six digits?

Classification to the six-digit level of the Harmonized System is never customs business, regardless of context. CBP confirmed this in HQ H260075 (2017) and HQ H045695 (2010), noting that six-digit classifications are "insufficient for entry" since U.S. entries require the full ten-digit HTSUS code. If your AI tool only operates at six digits, you can stop here.

If the tool provides eight-digit or ten-digit subheadings, move to Question 2.

Question 2: Is the classification tied to merchandise that will be entered?

This is the "nexus to entry" test. CBP has consistently held that providing tariff numbers for imported merchandise constitutes customs business when the classification information will, or may, end up on an entry. In HQ 115248 (2001), CBP stated that even when there is a "possibility" that classification data will be reflected on an entry, a broker's license is required.

There are two scenarios:

The tool is used as a general research resource, available for any product regardless of whether it will be imported. This is what CBP found permissible in HQ H272798 (2017), where a classification database was available for all products "regardless of whether a particular product is ever actually imported into the United States." General research tools do not have a nexus to a specific entry.

The tool provides specific classifications for specific goods the user intends to import. This is what CBP found impermissible in HQ H290535 (2022), where a supplier provided HTS subheadings for the exact merchandise its customers were purchasing and importing. Even though the customers had their own compliance teams, the "strong possibility" that the subheadings would appear on entries made this customs business.

Question 3: Does a licensed broker independently make the final classification decision?

Even when an AI tool operates in the permissible zone (general research, not directing entries), the output must be treated as input for professional review, not as the classification itself. CBP stressed in HQ H350722 that "the actual decision regarding the classification of imported merchandise must be made by a duly licensed customs broker." A tool does not constitute a "person" under 19 C.F.R. 111.1, so it cannot make classification decisions for entry purposes.

The Compliant AI Classification Workflow

Based on the H350722 framework and its precedent chain, a compliant workflow separates research from entry preparation and keeps the broker in the decision seat. Here is how to structure it:

Step 1: Use the AI tool for research, not entry preparation.

The AI classification tool should be a separate step in your process, disconnected from your entry filing system. Do not allow AI output to auto-populate entry fields. Do not use the same platform for both AI classification research and entry filing. CBP found in H350722 that when an AI tool operates on the same platform as the broker connection for entry purposes, the tool's output can impermissibly "direct" the classification on the entry.

In practice, this means your AI classification tool and your ABI/entry software should be distinct systems. The research output is a document or report that a broker reviews; it is not data that flows automatically into an entry.

Step 2: Treat AI output as candidate research, not a classification decision.

The best AI tools surface multiple candidate HTS codes with supporting analysis: which General Rules of Interpretation apply, what the relevant Section and Chapter Notes say, and what precedent exists in CBP's CROSS ruling database. This is research. The broker evaluates the candidates, applies professional judgment (including knowledge of the specific merchandise, its commercial use, and applicable trade program requirements), and selects the final classification.

GingerControl's HTS Classifier follows GRI logic and asks clarifying questions before surfacing candidate classifications, producing audit-ready reports grounded in Section Notes, Chapter Notes, and relevant CROSS rulings. The approach is divergence-based: the tool identifies where candidate codes diverge and asks targeted questions at those points, progressively converging toward the correct classification. But the broker reviews the research and makes the call.

Step 3: Implement meaningful disclaimers (and actually follow them).

CBP distinguishes between disclaimers that are "meaningfully implemented" and those that are decorative. In HQ H272798, the permissible database included a disclaimer stating that classifications were "for general, educational and planning purposes only" and that the licensed broker was responsible for the final classification. CBP found this acceptable because the disclaimer was actually followed: brokers independently evaluated the classifications.

In HQ H290535, a disclaimer stating that subheadings were "advisory only" did not protect the supplier because it was providing "specific subheadings on specific goods" that customers would import. The disclaimer existed, but the underlying activity was still customs business.

What makes a disclaimer meaningful:

The licensed broker actually reviews and independently evaluates the AI output
The AI tool's suggested classifications do not automatically become the entry classification
There is a documented step where the broker confirms or modifies the classification
The tool does not penalize or discourage brokers from departing from its suggestions

Step 4: Maintain a complete audit trail.

Reasonable care under 19 U.S.C. 1484(a)(1) requires importers to demonstrate the process they used to classify merchandise. An AI-assisted workflow should document every step.

The audit trail should show: what product information was provided to the AI tool; what candidate codes the tool surfaced and why; which GRI rules, Section/Chapter Notes, and CROSS rulings were considered; the broker's independent review and reasoning; and the final classification selected with the supporting rationale.

This documentation serves two purposes. First, it demonstrates reasonable care if CBP conducts a focused assessment or issues a CF-28 request for information. Second, it shows that the AI tool was used as a research aid, not as the classification decision-maker, reinforcing the tool's permissible status under the H350722 framework.

GingerControl produces audit-ready reports that capture this entire chain: the initial product description, the questions asked at divergence points, the candidate codes evaluated, the CROSS rulings consulted, and the reasoning that supports each candidate. The broker's independent review and final decision complete the trail.

Step 5: Evaluate your AI tool vendor's compliance posture.

Not every AI classification tool is built to comply with the H350722 framework. Before adopting a tool, ask:

Does the tool operate as a standalone research application, or is it bundled with entry filing services on the same platform?
Does the tool present its output as "research" or "candidates," or does it claim to "classify" products?
Does the tool require or facilitate broker review, or does it position itself as a replacement for broker judgment?
Is the tool provider a licensed customs broker, or does it operate as an unlicensed entity?
Does the tool auto-populate entry fields, or does it generate a separate research report?

A tool that integrates classification output directly into entry preparation, minimizes broker involvement, or positions itself as a substitute for professional classification judgment raises serious compliance concerns under the H350722 framework.

What About "Reasonable Care" When Using AI?

The reasonable care standard does not automatically attach to AI tool usage. In HQ H290535, CBP explicitly addressed whether an importer could rely on an unlicensed supplier's classification advice to satisfy reasonable care. The answer was no. The supplier was "not an appropriate expert to provide classification information," and "mere reliance" on the supplier's advice did not establish reasonable care.

To satisfy reasonable care while using AI classification tools:

Use the AI output as one input among several (including broker expertise, CBP rulings, and the importer's own product knowledge)
Have a qualified professional, specifically a licensed customs broker, customs consultant, or trade attorney, review the classification
Document the review process, not just the outcome
Periodically verify AI-assisted classifications against binding rulings or CBP decisions
Update classifications when the HTS schedule changes, tariff programs shift, or product specifications evolve

GingerControl helps companies build in-house AI-augmented compliance capabilities, combining process consulting with custom AI system development to ensure classification workflows meet both the H350722 framework and the reasonable care standard.

Common Mistakes to Avoid

Mistake 1: Assuming a disclaimer solves everything. A disclaimer is necessary but not sufficient. The underlying activity must also be permissible. If the tool provides specific classifications for specific imported goods, no disclaimer can transform that into non-customs-business.

Mistake 2: Letting AI output flow directly to entries. Any workflow where the AI tool's classification populates entry documents without independent broker review risks crossing the line. The broker must have a meaningful role in evaluating and selecting the classification.

Mistake 3: Using the same platform for research and entry filing. CBP specifically flagged this in H350722. When the AI classification tool and the broker entry connection exist on the same platform, the tool's output can be seen as "directing" the entry. Keep research and filing in separate systems.

Mistake 4: Treating six-digit and ten-digit classifications the same way. Six-digit classifications are never customs business. The compliance analysis only applies when the tool generates subheadings beyond six digits. Understanding this threshold prevents over-compliance (avoiding useful tools unnecessarily) and under-compliance (assuming all AI classification is permissible).

Mistake 5: Forgetting the territorial requirement. Since the 2022 broker modernization rules, all customs business must be conducted within U.S. customs territory (19 C.F.R. 111.3(a)). If your AI tool provider operates from outside the United States, and the tool's activity constitutes customs business, there is an additional territorial compliance issue.

Frequently Asked Questions

Can my compliance team use an AI tool to research HTS codes internally?

Yes. Internal classification research for your own company's products is not "customs business" because you are acting on your own behalf, not on behalf of another. The customs business restriction under 19 U.S.C. 1641(b)(1) only applies to persons conducting customs business "on behalf of another." Additionally, corporate compliance activities are explicitly excluded from the definition of customs business under 19 C.F.R. 111.1. The H350722 framework applies when an unlicensed third party provides classification services to others.

What if the AI tool only suggests HTS codes and the broker always reviews them?

This is the core of the permissible model, but the broker's review must be substantive, not pro forma. If the broker simply rubber-stamps the AI output without independent evaluation, the tool is effectively making the classification decision. CBP's framework requires that the broker "independently evaluate" the classification. Document the broker's review, including any modifications made and the reasoning behind the final selection.

Is it safe to use an AI classification tool if the vendor holds a customs broker license?

A vendor with a broker license can provide classification services as customs business, which means the vendor is operating within the regulatory framework. However, the vendor must still exercise responsible supervision and control over its customs business under 19 C.F.R. 111.28, and a licensed individual must be involved in specifying the tool's classification logic. The broker license does not exempt the vendor from exercising professional judgment.

How does GingerControl's Classifier differ from tools that CBP found impermissible?

GingerControl operates as a pre-classification research tool that surfaces candidate codes for broker review, not as a classification engine that outputs final answers. The Classifier uses divergence-based classification: it identifies multiple candidate HTS codes, then asks GRI-logic-driven questions at the points where those candidates diverge, progressively converging toward the correct classification. CROSS rulings are consulted during the research process to inform the analysis, not added as decorative citations after the fact. The broker reviews the full research output and makes the final call.

What penalties apply if my AI tool is found to be conducting customs business?

Under 19 U.S.C. 1641(b)(6), penalties can reach $10,000 per transaction. Total aggregate penalties can reach $30,000 per CBP's penalty guidelines. Licensed brokers who allow unlicensed tools to conduct customs business on their behalf can face separate penalties, suspension, or revocation under 19 C.F.R. 111.37. Intent to violate the law is not required; the penalty applies to the intentional transaction of the business itself.

Can I use AI tools for tariff research beyond classification?

Yes. AI tools for tariff cost simulation, duty rate comparison, trade policy monitoring, and compliance documentation do not involve classification for entry purposes and do not constitute customs business. GingerControl's Tariff Calculator covers the full U.S. tariff stack (base duty, Section 232, Section 301, Chapter 99, and Section 122) across 200+ countries, and the Tariff Briefing delivers daily policy updates. These tools provide analysis and information; they do not prepare or direct entry filings.

Where can I read the full CBP ruling on AI classification tools?

The full text of HQ H350722 is available on CBP's CROSS ruling database. The ruling also cites 14 prior headquarters rulings that form the precedent chain. Key precedents include HQ H272798 (permissible classification database), HQ H290535 (impermissible supplier classifications), HQ H068278 (OCR data extraction), and HQ H260075 (six-digit threshold).

GingerControl is a pre-classification research tool. It follows the same reasoning process a licensed customs broker uses, including GRI analysis, Section/Chapter Note review, and CROSS ruling research, but the final classification decision benefits from professional judgment. GingerControl produces audit-ready documentation that supports the classification decision; it does not provide legal advice or replace licensed customs expertise.

The H350722 framework rewards tools built the right way. GingerControl's Classifier surfaces candidate codes, asks GRI-driven questions at divergence points, and produces audit-ready reports for broker review. Try the Classifier

Need help structuring your AI-assisted classification workflow? GingerControl offers trade compliance consulting and AI agentic system build services. Talk to our team

References

[REF 1] U.S. Customs and Border Protection, HQ H350722 Data cited: Framework for AI classification tools, two-track permissibility test, automated tool requirements Source: HQ H350722, CROSS Published: January 16, 2026

[REF 2] U.S. Customs and Border Protection, HQ H272798 Data cited: Permissible classification database with meaningful disclaimer Source: HQ H272798, CROSS Published: January 26, 2017

[REF 3] U.S. Customs and Border Protection, HQ H290535 Data cited: Impermissible supplier classifications despite disclaimer; reasonable care analysis Source: HQ H290535, CROSS Published: September 29, 2022

[REF 4] U.S. Customs and Border Protection, HQ H260075 Data cited: Six-digit classification is not customs business; ten-digit threshold Source: HQ H260075, CROSS Published: April 3, 2017

[REF 5] U.S. Customs and Border Protection, HQ H045695 Data cited: ISF filing by unlicensed agents; six-digit HTS insufficient for entry Source: HQ H045695, CROSS Published: October 15, 2010

[REF 6] U.S. Customs and Border Protection, HQ 115248 Data cited: "Possibility" test for classification information reaching entries Source: HQ 115248, CROSS Published: August 28, 2001

[REF 7] U.S. Customs and Border Protection, HQ 114654 Data cited: General advice permissible; specific classification for entry merchandise is customs business Source: HQ 114654, CROSS Published: May 28, 1999

[REF 8] U.S. Customs and Border Protection, HQ H068278 Data cited: OCR/software extracting entry data constitutes customs business Source: HQ H068278, CROSS Published: September 28, 2009

[REF 9] 19 U.S.C. 1641, Customs Brokers Data cited: Definition of customs business, licensing requirement, penalty provisions Source: 19 U.S.C. 1641, LII

[REF 10] 19 C.F.R. Part 111, Customs Brokers Data cited: Definitions (111.1), territorial requirement (111.3(a)), responsible supervision (111.28), broker relations (111.36, 111.37) Source: 19 C.F.R. Part 111, eCFR

[REF 11] 19 U.S.C. 1484, Entry of Merchandise Data cited: Reasonable care requirement for making entry Source: 19 U.S.C. 1484, LII

[REF 12] Appendix C to 19 C.F.R. Part 171 Data cited: Penalty amounts for conducting customs business without a license ($10,000 per transaction, $30,000 aggregate) Source: Appendix C, eCFR

[REF 13] Modernization of the Customs Broker Regulations, 87 Fed. Reg. 63267 Data cited: Customs territory requirement, direct POA execution requirement Source: 87 Fed. Reg. 63267 Published: October 18, 2022