How to Use AI Classification Tools Without Violating Customs Law
Chen Cui Co-Founder of GingerControl What changed: Rewritten as a seven-step procedure built on CBP's reasonable care checklist and rulings read October 11, 2026, with the common mistakes that turn an AI tool into a legal problem.
Use AI classification tools legally by keeping three things straight: whose goods are classified, who makes the decision, and what stays on file. An importer may research its own codes with any tool; when codes beyond six digits go to others for goods that will be entered, a licensed broker must make the decision, because, as CBP wrote in HQ H350722, a tool is not a person. For a compliance team adding 40 SKUs a month, a written procedure (facts, tool research, internal review, broker review, a five-year record) helps you show reasonable care for each AI-assisted code.
In this post
- How can you use AI for HTS classification without breaking customs law?
- Do AI classification tools require a customs broker license?
- What does a compliant AI classification procedure look like?
- What does reasonable care require when you use AI?
- Which mistakes turn an AI tool into a legal problem?
- Where does GingerControl fit in this procedure?
- Putting the procedure into your team's handbook
- References
I'm Chen Cui, a GingerControl co-founder. We build classification software and work alongside licensed brokers, and this is the procedure we suggest to teams adopting any AI classification tool, ours or anyone else's. It is not legal advice: have your customs counsel or licensed broker review it once for your setup.
How can you use AI for HTS classification without breaking customs law?
You use it as research that a responsible person checks, not as a decision that flows straight onto an entry. Three rules hold that line:
- Your own goods: an importer classifying its own imports needs no broker license (19 U.S.C. 1641(b)(1)) but owes reasonable care for every code it files (19 U.S.C. 1484) [1].
- Someone else's goods: classifying others' goods beyond six digits, when the goods will be entered, is customs business that needs a broker license, and CBP applied that to an AI tool in HQ H350722 [2] [3].
- The decision: "A tool does not constitute a 'person'", so for customs business the classification decision must be made by a licensed broker [3].
Do AI classification tools require a customs broker license?
The tool does not, but the work it does might: using AI on your own goods needs no license, while a company that gives others 10-digit codes for goods they will enter is conducting customs business. The full decision tree, ruling by ruling, is in can AI tools legally classify HTS codes?, and the 2026 ruling itself is walked through in what CBP ruling HQ H350722 says about AI classification tools.
Compare tariff compliance software for trade platforms around the embedded classification and duty workflow your users need.
What does a compliant AI classification procedure look like?
A compliant procedure has seven steps, and only one of them is the AI.
- Gather the factsMaterials, function, use, how and where it is made; for composites, each component's weight, value and role
- Research with the toolKeep the code, the questions it asked and its reasoning
- Check the sourcesRead the Section and Chapter Notes and the rulings it cites
- Internal reviewA responsible, knowledgeable person signs off or sends it back
- Broker reviewThe licensed broker confirms the code before it goes on an entry
- Ruling for hard casesAsk CBP for a binding ruling when the code stays uncertain
- Keep and recheckKeep the record five years; recheck when the HTS or a tariff action changes
Each step maps to something CBP asks. The reasonable care checklist asks whether you know "what you ordered, where it was made, how it was made and what it is made of" (step 1), whether you "consulted the HTS, CBP's informed compliance publications, court cases and/or CBP's rulings on CROSS" (step 3), and whether "a responsible and knowledgeable individual within your organization reviewed the customs documentation prepared by you or your expert" (step 4) [4]. Binding rulings are free, and CBP says its National Commodity Specialist Division generally issues them within 30 calendar days (step 6) [5]. Entry records are kept "for 5 years from the date of entry" (19 CFR 163.4) (step 7) [6], and the schedule keeps moving: by our count of the USITC's release list, the 2026 HTS had 21 revisions by October 9, 2026 [7].
If you are still looking for free sources for step 3, see the best free HTS code lookup tools; for testing a tool's accuracy before step 2 becomes routine, see HTS classification providers compared on accuracy.
What does reasonable care require when you use AI?
Reasonable care requires that you can show how each code was reached and that someone responsible checked it; AI output alone does not show that. CBP said in HQ H290535 that "mere reliance" by importers on a supplier's classification advice "does not establish reasonable care" [2], and its reasonable care checklist itself "has no legal, binding or precedential effect" [4]. The checklist also asks whether "a laboratory analysis or other specialized procedure is suggested" for your goods: for chemicals, alloys and blends, a lab report may be the fact the tool needs.
Quotable insight: An AI classification tool changes how fast you research, not who is responsible. What makes its output usable is the paper trail around it: the facts you fed it, the reasoning it gave, the person who checked it and the broker who confirmed it. Build that record into the procedure on day one, because it is much harder to rebuild for 2,000 codes after CBP asks. How an API can capture that record automatically is covered in automating reasonable care.
Which mistakes turn an AI tool into a legal problem?
Most problems come from where the tool's output goes and who signs off, not from the AI itself.
| Mistake | Why it is a problem | Ruling or rule |
|---|---|---|
| An unlicensed company sends 10-digit codes to clients for goods they will enter | Classifying for others beyond six digits is customs business | HQ H290535, HQ H350722 [2] [3] |
| The tool's code flows into the entry with no licensed person deciding | A tool is not a person; a licensed person must have a role in what appears on the entry | HQ H350722 [3] |
| Relying on a disclaimer that nobody follows (when disclaimers protect you) | A disclaimer must be meaningfully implemented | HQ H272798, HQ H290535 [2] |
| Offshore staff key entry data into a broker's system | Picking out entry data and keying it in is preparing part of an entry; customs business must be conducted in the U.S. customs territory | HQ H326926; 19 CFR 111.3(a) [8] |
| Assuming a vendor's licensed employee covers the vendor | The employee's customs business activities are attributed to the company | HQ 114654 [8] |
| Keeping the code but not the facts and reasoning | Nothing shows how the code was reached | 19 U.S.C. 1484; 19 CFR 163.4 [1] [6] |
The same limits apply when classification sits inside someone else's platform: see embedded HS classification for SaaS. Whether your broker or your own team should own the work is covered in customs broker vs in-house classification.
Review online customs platform compliance requirements before assigning customs business and client-record access across platform participants.
Where does GingerControl fit in this procedure?
GingerControl's Classification Researcher covers step 2 for one product at a time: it asks about the facts that decide the heading, reads similar CROSS rulings during the decision and keeps the GRI reasoning, in 3 to 5 minutes including the report. Its Compliance Radar helps with step 7 by checking new U.S. trade notices against your HTS codes and listing what to redo by the effective date. GingerControl is not a customs broker, is not the importer of record, does not file entries and does not give legal advice. Our classifications are for general reference, educational, and planning purposes; before a code goes on an entry, the customer's licensed customs broker reviews it.
Putting the procedure into your team's handbook
Copy the seven steps into your import procedure, name the person for each, and run your next ten new products through it with the Classification Researcher and your broker. Research one product with its reasoning ready for review
References
- 19 U.S.C. 1641(b)(1) and 19 U.S.C. 1484
Data cited: customs business "(other than solely on behalf of that person)" requires a license; the importer of record files classification using reasonable care
Source: 19 U.S.C. 1641, U.S. Code and 19 U.S.C. 1484, U.S. Code - U.S. Customs and Border Protection, rulings HQ H290535 (September 29, 2022) and HQ H272798 (January 26, 2017)
Data cited: "Classifying goods for others is 'customs business'"; "mere reliance ... does not establish reasonable care"; a disclaimer must be meaningfully implemented
Source: CBP CROSS, HQ H290535 and HQ H272798 - U.S. Customs and Border Protection, ruling HQ H350722 (January 16, 2026)
Data cited: AI tool deriving subheadings beyond six digits for goods that will be entered conducts customs business; "A tool does not constitute a 'person'"; a licensed person "must have a role in specifying what information ... ultimately appears on an entry"
Source: CBP CROSS, HQ H350722 - U.S. Customs and Border Protection, Reasonable Care informed compliance publication (September 2017 revision)
Data cited: classification questions on knowing "what you ordered, where it was made, how it was made and what it is made of", consulting the HTS, publications, court cases and CROSS rulings, and laboratory analysis; general question 2 on internal review; "has no legal, binding or precedential effect"
Source: CBP Reasonable Care publication - U.S. Customs and Border Protection, eRuling requirements page and Rulings Program informed compliance publication (September 20, 2023)
Data cited: "Generally, the NCSD will issue all such rulings within 30 calendar days of the date of receipt"; up to five items of the same class or kind; "There are no charges or fees associated with the rulings program"
Source: CBP eRuling requirements and CBP Rulings Program publication - 19 CFR 163.4, record retention
Data cited: records kept "for 5 years from the date of entry"
Source: 19 CFR 163.4, eCFR - U.S. International Trade Commission, HTS release list (read October 11, 2026)
Data cited: Revision 21 of the 2026 HTS effective October 9, 2026
Source: USITC HTS release list - U.S. Customs and Border Protection, rulings HQ H326926 (December 19, 2023) and HQ 114654 (May 28, 1999); 19 CFR 111.3(a)
Data cited: identifying entry data and keying it into ABI is preparing parts of an entry; customs business must be conducted within the U.S. customs territory; a licensed employee's activities are attributed to the company
Source: CBP CROSS, HQ H326926, HQ 114654 and 19 CFR 111.3, eCFR
Questions people ask
Can my compliance team use an AI tool to research HTS codes for our own imports?
Yes. An importer classifying its own goods acts solely on its own behalf, which the broker-license rule in 19 U.S.C. 1641(b)(1) excepts. For a compliance team adding 40 SKUs a month, the duty that remains is reasonable care under 19 U.S.C. 1484: record the facts the tool relied on, review its reasoning internally, and have your licensed broker check the code before entry.
Is it enough if a licensed broker always reviews the AI tool's codes?
It depends on how the review works. In HQ H350722, CBP said a licensed person must have a role in specifying what the tool generates and what appears on the entry, because a tool is not a person. For a brokerage filing 300 entries a month, a review that can change the code, with the reasoning kept, is closer to that than a click-through approval; ask your customs counsel.
Is an AI classification tool safe to use if the vendor has a licensed broker on staff?
Not by that fact alone. In HQ 114654, CBP said a licensed broker on a company's staff is immaterial for avoiding the unlicensed-business penalty, because the employee's customs business activities are attributed to the company. For an importer choosing between two tools, look at what the vendor does with your codes, not at its staff list.
What should we keep on file when an AI tool suggests an HTS code?
Keep the product facts sent, the code and the reasoning the tool gave, the notes and rulings checked, who reviewed it and when, the broker's confirmation and the HTS revision in force. For an importer with 1,500 SKUs, 19 CFR 163.4 asks that entry records be kept for five years from the date of entry.
Can AI output alone show reasonable care to CBP?
No. CBP said in HQ H290535 that mere reliance by importers on a supplier's classification advice does not establish reasonable care, and its own reasonable care checklist says it has no legal, binding or precedential effect. For an importer filing 500 entries a year, what helps is the record around the output: the facts, the internal review and the broker's confirmation.
Can we use AI tools for tariff research beyond classification?
Yes. Pricing duty by origin, comparing sourcing countries and budgeting are your own planning decisions. For a buyer comparing 12 sourcing countries for 30 SKUs, GingerControl's Tariff Calculator lists the base rate, each Section 232 and 301 line, MPF and HMF for an entry date; mark planning codes as planning until your broker confirms them.
When should we ask CBP for a binding ruling instead of relying on an AI tool?
When the code is genuinely uncertain and the duty at stake is large. Rulings are free, CBP says its National Commodity Specialist Division generally issues them within 30 calendar days, and a ruling binds CBP for the product described. For an importer launching a new product line of five similar items, one eRulings request can cover up to five items of the same class or kind.
Where can I read the full CBP ruling on AI classification tools?
Search CBP's CROSS database at rulings.cbp.gov for ruling number H350722, dated January 16, 2026. For a compliance manager briefing a team of five, read the holding and the six-digit discussion first; GingerControl's walkthrough of the ruling quotes each part, service by service.
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
