Annual HTS Classification Review Checklist for Compliance Teams
Chen Cui Co-Founder of GingerControl What changed: Rebuilt the seven-step review around documented decisions; catalog rechecks belong to GingerOS, and unsupported turnaround and legal guarantees are removed.
An annual HTS classification review checks whether each code still exists, whether the product facts support it, and whether origin, duties and supporting records remain correct. Prioritize changed or ambiguous goods, record the decision and assign remediation. A valid code is not proof of a correct classification, and a duty change does not necessarily require a new code. Catalog rechecks belong to GingerOS; in GingerLite, Classification Researcher handles one product per case and Parts Library compares candidate-code and source-country costs.
The seven-step annual review checklist
1. Align with the current HTS schedule
Record the schedule and entry date used. Compare the current USITC revision with the one behind the existing record [1].
2. Reconcile the catalog against that schedule
Export SKU, description, code, origin, value and the supporting decision. Separate retired codes from valid codes needing a factual review. Keep a named owner for each discrepancy.
3. Re-classify high-risk SKUs
Review changed composition, function and construction using the GRI and legal Notes [2]. Classification Researcher asks for missing facts and records its reasoning, one product per case. The customer's licensed broker reviews the result before filing.
4. Confirm origin separately
A supplier address does not establish origin. Distinguish nonpreferential origin from FTA qualification and collect the manufacturing evidence needed for each claim.
5. Verify applicable duty layers
Check the exact code, origin and entry date. Section 232, China Section 301 and other Chapter 99 duties have their own scope and exceptions; do not add every rate automatically. Use Tariff Calculator for U.S. duties by entry date.
Use HTS classification confidence scoring and review queues to define which uncertain outputs reach a human before an approved code is stored.
6. Keep the reasoning and review record
Save product facts, GRI and Note analysis, relevant rulings, reviewer and decision date. Reasonable care is the importer's obligation [3]; a report does not guarantee compliance. Records generally must be retained five years under 19 CFR 163.4 [4].
7. Remediate and approve changes
Log the old and proposed code, affected entries, owner and deadline. Have the broker assess entry corrections separately from changes to the product master.
For a review spanning several country teams, use the trade compliance RACI matrix to assign who prepares, approves and receives each decision.
Which GingerControl product supports which step?
| Work | Product role |
|---|---|
| Research one product | Classification Researcher in GingerLite |
| Compare candidate-code and source-country landed costs | Parts Library, up to 100 rows per upload |
| Receive U.S. policy alerts against your codes | Compliance Radar, by email |
| Recheck a catalog and connect approved decisions to your process | GingerOS, fitted to the customer |
Parts Library does not perform steps 2-6 automatically, establish origin, or certify an FTA claim. Review duration depends on product facts and the work required; no catalog turnaround is promised.
When should you review outside the annual cycle?
Review affected goods when product facts, suppliers, manufacturing operations or tariff provisions change. An annual calendar is a control, not a reason to postpone a known discrepancy. For catalog workflows, discuss a GingerOS project; for classification or sourcing questions, Trade Advisory is quoted for the requested scope.
Frequently Asked Questions
Is an annual review a legal safe harbor?
No. A calendar and report support controls; reasonable care depends on the actual facts and work performed.
Must every valid code be changed?
No. Verify its use for the product. A rate change can require costing updates without reclassification.
Which products should be prioritized?
Changed specifications, ambiguous goods, unsupported origin claims and missing decision records deserve review first.
Does Parts Library recheck the entire catalog?
No. It compares candidate-code and source-country costs. Catalog batch rechecks belong to GingerOS.
Can Researcher review several products at once?
In GingerLite, each product is its own case. Batch classification is a GingerOS workflow.
How much can I upload to Parts Library?
Up to 100 rows per Excel or CSV upload; that upload is not an automatic catalog audit.
What does Radar do?
It checks new U.S. notices against your own HTS codes and emails the affected items and next steps.
How long should supporting records be kept?
Generally five years under 19 CFR 163.4, subject to the provision and its exceptions.
References
- USITC, Harmonized Tariff Schedule
Source: USITC, Harmonized Tariff Schedule
Checked: 2026-10-12 - USITC, General Rules of Interpretation
Source: USITC, General Rules of Interpretation
Checked: 2026-10-12 - 19 U.S.C. 1484
Source: 19 U.S.C. 1484
Checked: 2026-10-12 - 19 CFR 163.4
Source: 19 CFR 163.4
Checked: 2026-10-12
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
