How Automated HTS Classification Works: GRI Logic Explained
What changed: Clarified the September 2025 ATLAS benchmark, its test set and limits, removed unsupported accuracy comparisons, and corrected the relevant penalty and documentation claims. Removed the freshness-only title year.
Automated HTS classification tools can use text matching, model predictions and workflows that apply the GRI and legal Notes to product facts. Verify the resulting code and explanation on reviewed products; a method or architecture label does not establish greater accuracy or audit defensibility.
In this post
- Why does the classification method matter for compliance teams?
- What Is Keyword Matching and Why Do Most Tools Use It?
- How Does GRI Logic Classification Actually Work?
- How Does AI HTS Classification Differ from Simple Keyword Search?
- Why Do GRI-Logic Systems Ask Clarifying Questions?
- How Do CROSS Rulings Factor into Automated Classification?
- What Should Compliance Teams Look for in an Automated Classification System?
- Frequently Asked Questions
- Automate Classification with GRI Logic, Not Guesswork
- References
Primary source: General Rules of Interpretation, Harmonized Tariff Schedule (USITC), the six legal rules governing how every product is classified.
Why does the classification method matter for compliance teams?
Classification methodology affects accuracy and the evidence available for review. Under 19 U.S.C. 1592(c), a revenue-affecting negligent violation is capped at the lesser of domestic value or twice the lawful duties, taxes and fees lost or potentially lost; gross negligence at the lesser of domestic value or four times that amount. The 20% and 40% dutiable-value caps apply when the violation does not affect their assessment. Documentation helps explain the decision but does not by itself determine culpability.
Automated HTS classification includes keyword lookup, model-based prediction and GRI-logic workflows. Evaluate the actual output and evidence rather than inferring audit defensibility from the architecture. The U.S. Harmonized Tariff Schedule contains over 17,000 distinct 10-digit statistical reporting numbers across 99 chapters, each governed by Section Notes, Chapter Notes, and the six General Rules of Interpretation published by USITC. Apply the legal provisions to the product facts and validate the resulting code. GingerControl's HTS Classification Researcher encodes GRI 1 through 6 as deterministic logic, not probabilistic text generation, producing audit-ready classification reports that follow the same reasoning framework licensed customs brokers apply.
What Is Keyword Matching and Why Do Most Tools Use It?
Keyword matching is the simplest form of automated HTS classification. The system takes a product description, tokenizes it into words or phrases, and compares those tokens against the text of HTS headings and subheadings. The heading with the highest text-similarity score gets returned as the classification.
This approach is popular for three reasons:
- Low engineering cost. Building a text-matching classifier requires a product description database and a similarity algorithm. No legal knowledge needs to be encoded.
- Speed. A keyword match against a static database can return results in under a second.
- Simplicity. Users enter a description and get a code. No follow-up questions, no iterative process.
The problem is that the Harmonized Tariff Schedule is not organized by product names. It is organized by legal definitions governed by Section Notes, Chapter Notes, and GRI rules. A "stainless steel insulated water bottle" could fall under heading 7323 (stainless steel household articles), 9617 (vacuum flasks), or 3924 (plastic household articles) depending on its construction, material composition, and insulating mechanism. Keyword matching sees the words "stainless steel" and "water bottle" and picks the heading with the most textual overlap, without evaluating which legal rule actually governs the classification.
The ATLAS paper published September 22, 2025 reported 40.0% exact 10-digit matches and 57.5% at 6 digits for its fine-tuned Atlas model on 200 CROSS-derived test examples. These historical results concern that model and dataset; the study did not isolate the effect of structured legal reasoning or establish a current LLM accuracy ceiling.
Where Keyword Matching Breaks Down
Keyword matching fails predictably on four categories of products:
| Product Type | Why Keyword Matching Fails | What GRI Logic Requires |
|---|---|---|
| Multi-function goods (e.g., smart speaker with display) | Matches text of the most prominent function keyword | The heading terms and notes first (GRI 1): CBP decided a smart display, the Google Nest Hub, under GRI 1 in HQ H319100; GRI 3(b) essential character only if two or more headings still apply |
| Composite goods (e.g., steel container with chemical inside) | Matches either "container" or "chemical" based on word frequency | GRI 3(a) most specific description analysis, then 3(b) if equally specific |
| Unassembled goods (e.g., furniture kit) | Matches "parts" or "components" keywords | GRI 2(a) allows classification of incomplete or unassembled articles as complete |
| Goods classifiable under multiple headings | Returns the highest-scoring text match | GRI 1 through 6 applied sequentially until classification is resolved |
Bottom line: Keyword matching treats HTS classification as a search problem. GRI logic treats it as a legal reasoning problem. The Harmonized Tariff Schedule is a legal document, not a product catalog, and systems that ignore its legal architecture will always underperform on composite, multi-function, and ambiguous goods.
How Does GRI Logic Classification Actually Work?
The General Rules of Interpretation govern how every product entering the United States (and over 200 countries using the WCO Harmonized System) gets classified. GRI 1 takes precedence: classification is determined by the terms of the headings and any relative Section or Chapter Notes. Only when GRI 1 cannot resolve classification do GRI 2 through 6 apply, in sequence.
- GRI 1: Heading terms and legal notes. Identify candidate headings, check each against Section Notes and Chapter Notes. If one heading clearly applies, classification is resolved.
- GRI 2: Incomplete, unassembled, or mixed goods. Evaluate whether incomplete goods have the essential character of the complete article, and whether mixtures classify under each material's heading.
- GRI 3(a): Most specific description. When multiple headings apply, select the one providing the most specific description.
- GRI 3(b): Essential character. For composite goods where 3(a) cannot resolve, determine which component gives the good its essential character, weighed by the factors in Explanatory Note 3(b)(VIII): the nature of the material or component, its bulk, quantity, weight or value, and its role in relation to the use of the goods.
- GRI 3(c) through 6: Residual rules. If 3(a) and 3(b) fail, apply numerical order (3c), most analogous heading (GRI 4), packaging rules (GRI 5), or re-apply GRI 1-5 at subheading level (GRI 6).
CBP's own Informed Compliance Publication on tariff classification states that "GRI 1 takes precedence over the remaining rules" and that classification "shall be determined according to the terms of the headings of the tariff schedule and any relative section or chapter notes." Any automated system that skips this hierarchy is not performing classification in the legal sense.
GingerControl's HTS Classification Researcher follows this exact sequence. When a product could fall under multiple headings, the system identifies the applicable GRI rule, generates targeted clarifying questions based on the divergence points between candidate codes, and converges step by step rather than guessing from a single product description.
How Does AI HTS Classification Differ from Simple Keyword Search?
The term "AI HTS classification" covers a wide range of systems, and the differences matter. Here is how the three main approaches compare:
| Capability | Keyword Matching | Generic LLM (ChatGPT, Gemini) | GRI-Logic System (GingerControl) |
|---|---|---|---|
| Classification method | Text similarity scoring against HTS descriptions | Probabilistic text generation based on training data | Deterministic GRI 1-6 reasoning with Section/Chapter Note checks |
| Handles GRI 3(b) essential character | No | Verify the essential-character analysis for the actual product | Yes, asks the essential-character questions for the product and records which component gives it its essential character |
| CROSS ruling integration | No | Verify ruling citations and their current status | Reads similar CROSS rulings during classification as active decision inputs |
| Clarifying questions | No | Check whether missing facts trigger questions | Yes, generated from divergence points between candidate codes |
| Audit trail | HTS code only | Verify the explanation, citations and retained record | Full reasoning chain with GRI citations, Section/Chapter Notes, CROSS references |
| Published accuracy | No published figure | Historical ATLAS test (September 22, 2025; 200 examples): fine-tuned Atlas 57.5% at 6 digits, 40.0% at 10 digits | 99.86% at the 10-digit level on GingerControl's own internal test of 1,000+ products (first-party, not an independent benchmark) |
These are historical results for the models and 200-example test set in the September 22, 2025 ATLAS paper. GingerControl was not tested; its internal result uses a different dataset. The figures do not establish a current accuracy ceiling or a direct vendor ranking.
Bottom line: For compliance teams that need audit-defensible classification with full GRI reasoning, GingerControl is built to surface competing candidates, ask targeted questions at divergence points, and produce documentation grounded in the same legal framework CBP applies. Have a qualified reviewer verify each code against the actual product and applicable law before filing.
When I built GingerControl's classification engine, the core design decision was to separate deterministic legal logic (GRI sequencing, Note exclusions, format validation) from any probabilistic layer entirely. The legal rules cannot be overridden by model confidence scores. GRI-logic classification is not "better AI," it is a fundamentally different architecture: keyword matching asks "what code matches this text?" while GRI logic asks "which heading does the law require given these product facts?"
The account of how GingerControl built its classification reasoning explains why the questions follow legal classification decisions rather than keyword similarity.
Why Do GRI-Logic Systems Ask Clarifying Questions?
A licensed customs broker classifying a composite product does not look at the product name and pick a code. They ask questions: What is the primary function? Which component has the highest value? What role does each component play in its use? These questions come from GRI logic, specifically from the divergence points between competing HTS headings.
GingerControl generates clarifying questions from three sources simultaneously:
- The user's product information. What is already known about the product.
- The semantic meaning of competing HTS descriptions. Where the candidate codes diverge in their legal requirements.
- The applicable GRI rule. Which specific rule determines the classification direction.
Consider a bamboo cutting board sold with a removable stainless-steel tray. Keyword matching picks whichever heading's text most closely resembles the description, wood or steel. A GRI-logic system recognizes that GRI 3(b) may apply, asks the essential-character questions for that product, and records which component gives the product its essential character.
Each answer eliminates one or more candidate headings, converging toward the legally correct classification. This is iterative divergence-based classification, and it mirrors the exact reasoning process a licensed customs broker follows when working through a complex product.
Under 19 U.S.C. 1484, reasonable care concerns the importer’s actual conduct, including the product facts, research, verification and procedures used. A report preserving GRI analysis, legal Notes and relevant rulings can support that review, but does not by itself establish compliance or determine culpability.
How Do CROSS Rulings Factor into Automated Classification?
CBP's CROSS (Customs Rulings Online Search System) database contains hundreds of thousands of binding classification rulings. These rulings are legal precedent showing how CBP has applied GRI logic to real products.
GingerControl searches for CROSS rulings on similar products during classification and incorporating CBP's reasoning into the candidate analysis before the final determination. The rulings serve as classification basis, not post-hoc decoration.
What Should Compliance Teams Look for in an Automated Classification System?
Not every team needs the same level of classification automation. Here is a framework for evaluating which approach fits your operation:
- High volume, low complexity (e.g., single commodity type, well-established codes): Keyword matching or database lookup may be sufficient, with periodic broker review.
- Moderate volume, mixed complexity (e.g., diversified product catalog with some multi-function goods): Evaluate targeted questions for missing product facts, GRI analysis and review of the resulting code.
- High complexity, high stakes (e.g., composite goods, GRI 3(b) scenarios, active CBP audits): Retain product facts, GRI and Note analysis, relevant ruling research and expert review; no software architecture alone establishes reasonable care.
GingerControl is a trade compliance AI platform that helps importers, exporters, and customs brokers classify products, simulate tariff costs, and track policy changes. For teams dealing with the second and third scenarios, the HTS Classification Researcher produces audit-ready documentation with GRI citations, Section and Chapter Note analysis, and CROSS ruling references. It follows the same reasoning process a licensed customs broker uses; the final classification decision benefits from professional judgment.
The workflow for AI research tools for licensed customs brokers keeps research support separate from the broker’s reviewed filing decision and the importer’s responsibilities.
Frequently Asked Questions
How does automated HTS classification handle products with multiple functions?
GRI-logic systems apply the heading terms and notes first, detect when a product triggers GRI 3(b) essential character analysis, and ask targeted questions about the facts that decide it. GingerControl's HTS Classification Researcher identifies all competing candidate headings, surfaces divergence points, and generates questions that mirror a licensed customs broker's reasoning. Keyword-matching systems skip this analysis and default to the highest text-similarity score.
What accuracy rate can compliance teams expect from AI HTS classification?
The ATLAS paper published September 22, 2025 reported 40.0% exact 10-digit matches and 57.5% at 6 digits for its fine-tuned Atlas model on 200 CROSS-derived test examples. These historical results concern that model and dataset; the study did not isolate the effect of structured legal reasoning or establish a current LLM accuracy ceiling. GingerControl's GRI-logic-driven system with iterative candidate convergence scored 99.86% at the 10-digit level on GingerControl's own internal test of 1,000+ products, a first-party test, not an independent benchmark; it encodes deterministic legal rules separately from any probabilistic model and asks clarifying questions at divergence points rather than guessing from incomplete descriptions. These are historical results for the models and 200-example test set in the September 22, 2025 ATLAS paper. GingerControl was not tested; its internal result uses a different dataset. The figures do not establish a current accuracy ceiling or a direct vendor ranking.
Can automated classification produce audit-ready documentation for CBP?
A documented classification can support an audit response when its facts, sources and reasoning are accurate and the importer has actually reviewed the result. GingerControl’s Classification Researcher records GRI analysis, Section and Chapter Notes and relevant CROSS rulings for one product case. Those records support review; they do not automatically satisfy reasonable care or guarantee that CBP accepts the code.
Is keyword-based HTS classification sufficient for low-risk imports?
For single-material products with well-established codes, keyword matching can serve as preliminary screening. However, even routine imports involve nuances text matching misses, such as Chapter Note exclusions or material thresholds. GingerOS batch classification lets teams run high-volume catalogs through full GRI-logic classification, catching errors keyword matching would miss without slowing the workflow; in the GingerLite app each product is its own case.
How does GingerControl use CROSS rulings differently from other classification tools?
Most tools classify first and search for matching CROSS rulings afterward, appending them as decorative references. GingerControl reads similar CROSS rulings during the classification process itself, incorporating CBP's precedent reasoning into the candidate analysis before the final determination. This means rulings actively shape the classification decision rather than being pasted on after the fact, producing reports where every cited ruling directly supports the reasoning chain.
What is the difference between GRI-logic classification and generic LLM classification?
Generic LLMs treat classification as text prediction, generating the most probable HTS code from training data without encoded GRI logic or Section/Chapter Note validation. GingerControl's architecture separates deterministic legal reasoning from any probabilistic layer, so legal logic cannot be overridden by model confidence. This is a fundamentally different system design built for the legal structure of tariff classification.
How long does automated HTS classification take compared to manual research?
Manual classification typically takes 30 minutes to 2 hours per product, by GingerControl's estimate. GingerControl's Classification Researcher takes 3 to 5 minutes per product, with full GRI verification and the audit-ready report included. For high-volume operations, GingerOS classifies several products in parallel, with how many run at once agreed with each customer.
Automate Classification with GRI Logic, Not Guesswork
Review the product facts, the applied GRI and Notes, the relevant rulings and the recorded decision before filing. GingerControl’s Classification Researcher helps preserve that reasoning for one product case. The importer remains responsible for reasonable care and the actual entry; a software architecture or report alone cannot establish that the duty was met.
For a classification workflow that scales across a whole catalog, GingerControl builds GingerOS, the AI trade compliance platform that runs on your process and the data you have, ERP or not. Book a call about building a classification workflow that scales.
References
- U.S. International Trade Commission | General Rules of Interpretation, Harmonized Tariff Schedule
Data cited: GRI 1-6 legal text and hierarchy
Source: General Rules of Interpretation
Published: Current release (continuously updated) - World Customs Organization | General Rules for the Interpretation of the Harmonized System
Data cited: GRI framework used by 200+ countries
Source: WCO GRI Publication - U.S. Customs and Border Protection | Informed Compliance Publication: Tariff Classification
Data cited: GRI 1 precedence, classification methodology
Source: CBP Tariff Classification ICP - U.S. Code | 19 U.S.C. 1592(c): Civil penalty caps
Data cited: Revenue-affecting negligence/gross negligence: lesser of domestic value or 2x/4x lawful duties, taxes and fees lost or potentially lost; nonrevenue caps 20%/40% of dutiable value; fraud capped at domestic value
Source: 19 U.S.C. 1592 - U.S. Customs and Border Protection | Reasonable Care Informed Compliance Publication
Data cited: Reasonable care standard under 19 U.S.C. 1484
Source: CBP Reasonable Care
Published: September 2017 (current edition) - ATLAS: Benchmarking and Adapting LLMs for Global Trade via Harmonized Tariff Code Classification | arXiv
Data cited: Historical 200-example CROSS-derived test: fine-tuned Atlas 40.0% at 10 digits, 57.5% at 6 digits; not a test of legal-reasoning causation, reasonable care, or explanation auditability
Source: arXiv:2509.18400
Published: September 22, 2025
Classifying SKUs one ruling at a time?
Hand this to GingerOS.
Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.
Reviewed by Michael Weick, LCB / CCS




