Disclaimers in Trade Compliance: When They Protect You (and When They Don't)

Do Disclaimers Protect AI Classification Tools from Customs Business Liability?

Sometimes. CBP distinguishes between disclaimers that are "meaningfully implemented" and those that are purely decorative. A meaningful disclaimer, combined with a tool that operates as a general research resource with independent broker review, can keep classification activities outside the scope of customs business. A disclaimer appended to specific classifications for specific imported goods does not provide protection, regardless of its wording.

When Has CBP Accepted a Disclaimer for Classification Services?

In HQ H272798 (2017), CBP accepted a disclaimer on a tariff classification database that was available for all products regardless of importation status, stated classifications were "for general, educational and planning purposes only," and left final classification to a licensed broker. CBP rejected a similar disclaimer in HQ H290535 (2022) because the classifications were for specific goods being imported.

One of the most common questions in trade compliance technology is: "Can I just add a disclaimer?" The assumption is that appending language like "these classifications are for informational purposes only" transforms customs business into permissible research. CBP's ruling history tells a more nuanced story. Over three key rulings, CBP has built a framework that treats disclaimers as one factor in a multi-factor analysis, not as a magic shield.

Last updated: March 2026

GingerControl is a trade compliance AI platform that helps importers, exporters, and customs brokers classify products, simulate tariff costs, and track policy changes.

The Disclaimer That Worked: HQ H272798

In HQ H272798 (January 26, 2017), an unlicensed Canadian company was engaged by a multinational chemical company to prepare a tariff classification database covering the client's products. The database would be used for pricing and cost analysis and as a resource for the client's customs brokers.

The database included this disclaimer:

"The information contained in this report is for general, educational and planning purposes only. The specific tariff classification to be applied to a specific entry of merchandise is to be determined by the licensed Customhouse broker or other agent engaged to file the entry. In the event the broker or agent handling the entry expresses an opinion different from that set out in this study, the opinion of the broker or agent should be followed, subject to post-entry verification."

CBP acknowledged this was a "fine line" but concluded the database was permissible because of several factors working together:

The database was available for all products. The client could access it for any product in its portfolio "regardless of whether a particular product is ever actually imported into the United States." There was no nexus to a specific importation requiring entry.

The company did not provide anything directly to CBP or to a customs broker. The analysis went to the client, who could then share it with brokers at its discretion.

The broker made the final call. The disclaimer was not just text on a page. It reflected the actual workflow: the broker would independently evaluate the classification, could disagree with the database, and the disclaimer instructed the client to follow the broker's opinion in that case.

The database was a "resource," not a directive. CBP emphasized the distinction between a tool used "as a resource" and one that would "direct the U.S. customs broker in the preparation of the entry."

The Disclaimer That Failed: HQ H290535

In HQ H290535 (September 29, 2022), Hampton Products, an unlicensed supplier of consumer goods, provided eight-digit and ten-digit HTS subheadings to its retail customers for the merchandise those customers purchased and imported. Hampton included this disclaimer:

"These are the HTSUS subheadings that Hampton uses for imports, in no way should this information be used as confirmation or endorsement that you (customer) should use these same subheadings for your import and export declarations. Importer of record accepts all responsibilities for ultimate submission to US Customs. Please consult with your Broker."

CBP held this disclaimer did not protect Hampton for three reasons:

The classifications were for specific goods. Hampton was providing "specific subheadings on specific goods that its clients have ordered and for which they will be filing entry documentation with CBP." This was not a general database.

There was a strong possibility the codes would be used on entries. Because customers requested the subheadings before importing merchandise they had ordered from Hampton, CBP found a "strong possibility that the customers will use subheadings provided on the entry filed with CBP."

Hampton effectively directed brokers. By providing specific subheadings for specific imported goods, Hampton was "in effect direct[ing] customs brokers on how to prepare the requisite entry documents," regardless of the disclaimer.

CBP also found that Hampton was not a qualified expert for reasonable care purposes. Customers could not establish reasonable care simply by relying on Hampton's classifications.

The AI Synthesis: HQ H350722

In HQ H350722 (January 16, 2026), CBP applied both precedents to an AI classification tool. The tool generated "tiered" HTS subheading suggestions based on product information input by importers. It included a disclaimer stating the tool was a "beta phased system" and that classifications were "merely an estimation" intended as a "guideline."

CBP's analysis created two outcomes for the same tool:

When the tool operates separately from the entry portal (analogous to H272798): the tool is akin to the "narrowly permissible database" in H272798, provided the disclaimer is meaningfully implemented and the tool does not direct either party on the classification for entry.

When the tool provides classifications to importers who have engaged a broker through the same platform (analogous to H290535): the tool is "providing specific subheadings on specific goods for which an entry will be filed with CBP," making the disclaimer ineffective.

The synthesis is clear: a disclaimer is necessary but not sufficient. The underlying activity must also fall on the permissible side of the line.

What Makes a Disclaimer "Meaningful"?

Based on the ruling history, a meaningful disclaimer has these characteristics:

Element	What CBP Expects	What Fails
Wording	States classifications are for research/planning/education, not entry	Generic "informational purposes" language without specificity
Broker authority	Explicitly states broker makes final classification decision	Suggests customer should "verify" but implies the codes are probably correct
Actual implementation	Broker independently evaluates the classification, can and does override	Broker rubber-stamps the output without review
Workflow structure	Classification output is input for broker review, not auto-populated on entries	Output flows directly into entry preparation
Scope of tool	Available for general research across products	Provides codes for specific goods being imported

The most important factor is the last one. No amount of disclaimer language can convert specific-goods-for-specific-importers classification into permissible activity. The disclaimer works only when the underlying tool is structured as a general research resource.

How This Applies to AI Classification Tools

Every AI classification tool provider and user should evaluate their situation against this framework:

Scenario 1: Standalone AI research tool with disclaimer. An importer or broker uses an AI tool to research HTS codes for various products. The tool is not connected to an entry filing system. The tool produces candidate codes with supporting analysis. The broker reviews the candidates independently and selects the final classification. The tool's disclaimer states it is for research purposes and that a licensed broker must make the final classification decision. This aligns with the H272798 model: permissible.

Scenario 2: AI tool integrated with entry platform, disclaimer included. An importer uses an AI tool on the same platform where they connect with a broker for entry filing. The tool generates HTS codes for the specific merchandise the importer intends to enter. The disclaimer says the codes are "suggestions only." This aligns with the H290535/H350722 model: impermissible despite the disclaimer. The tool provides specific codes for specific goods being entered through the same system.

Scenario 3: Supplier providing AI-generated codes to customers. A manufacturer uses an AI tool internally, then shares the AI-generated HTS codes with its customers (who are the importers of record). The supplier includes a disclaimer that customers should verify with their brokers. This aligns directly with H290535: impermissible. The supplier is providing specific codes for specific goods the customer will import.

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 Classifier operates as a standalone pre-classification research tool. Its output is a research report for broker review, not a classification determination.

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.

Frequently Asked Questions

Can a supplier legally provide HTS codes to its customers with a disclaimer?

Not for specific goods the customer will import, according to HQ H290535. Even with a disclaimer, providing specific HTS subheadings at the eight-digit or ten-digit level for merchandise a customer has ordered for importation constitutes customs business. The supplier would need a customs broker license. Providing general tariff information for planning purposes (not tied to specific orders) may be permissible under the H272798 framework, but this is a narrow exception.

Does "meaningfully implemented" mean the broker must change the classification?

No. The broker does not need to reach a different classification from the AI tool. "Meaningfully implemented" means the broker independently evaluates the classification using professional judgment. If the broker agrees with the AI tool's suggestion after independent review, that is fine. The issue is whether the broker has the opportunity and authority to reach a different conclusion, and whether the review is documented.

Can I use the H272798 disclaimer language verbatim?

The specific words matter less than the substance. CBP did not bless a particular formula. It evaluated whether the disclaimer reflected the actual relationship between the tool, the client, and the broker. Using H272798's language on a tool that functions like H290535's scenario would not provide protection. The disclaimer must accurately describe a workflow where the broker independently makes classification decisions.

What if my company is both the importer and the tool user?

The customs business restriction under 19 U.S.C. 1641(b)(1) applies to persons conducting customs business "on behalf of another." If you are using an AI tool to research classifications for your own company's imports (not for third parties), you are not conducting customs business. Additionally, 19 C.F.R. 111.1 explicitly excludes "corporate compliance activities" from the definition of customs business. Internal use of AI tools for your own compliance is not regulated by this framework.

How does GingerControl handle the disclaimer requirement?

GingerControl is positioned as a pre-classification research tool from the ground up. The product does not claim to "classify" merchandise. It surfaces candidate HTS codes with supporting GRI analysis, Section/Chapter Note references, and CROSS ruling citations. The broker reviews the research and makes the final classification decision. This structural positioning, not just disclaimer language, is what aligns GingerControl with the permissible track in the H350722 framework.

What happens if a disclaimer is found to be insufficient?

The tool provider may be found to have conducted customs business without a license, triggering penalties of up to $10,000 per transaction under 19 U.S.C. 1641(b)(6). Brokers who relied on the tool's output may also face scrutiny under the responsible supervision and control requirement (19 C.F.R. 111.28). And importers who relied on the tool's classifications may not be able to establish reasonable care if the classifications prove incorrect.

Building a compliant classification workflow means more than adding a disclaimer. GingerControl's Classifier is structured as a pre-classification research tool that surfaces candidates with GRI analysis, CROSS ruling citations, and audit-ready documentation for broker review. Try the Classifier

References

[REF 1] HQ H272798 (Jan. 26, 2017): Permissible classification database with meaningful disclaimer Source: CROSS

[REF 2] HQ H290535 (Sept. 29, 2022): Impermissible supplier classifications despite disclaimer Source: CROSS

[REF 3] HQ H350722 (Jan. 16, 2026): AI classification tool two-track framework Source: CROSS

[REF 4] HQ 114654 (May 28, 1999): General advice vs. specific classification Source: CROSS

[REF 5] HQ 115248 (Aug. 28, 2001): "Possibility" test Source: CROSS

[REF 6] HQ H068278 (Sept. 28, 2009): Software determining classification is customs business Source: CROSS

[REF 7] 19 U.S.C. 1641: Customs brokers statute Source: LII

[REF 8] 19 C.F.R. Part 111: Customs broker regulations Source: eCFR