How to Audit Existing HTS Codes: Step-by-Step Process Guide
Chen Cui Co-Founder of GingerControl What changed: Rewrote the five-step audit and FAQs; removed invented catalog speeds, automatic origin checks and claims that Parts Library audits codes.
Audit existing HTS codes by comparing the code list with the current schedule, then checking the product facts and legal basis behind each classification. Validate origin and applicable duties separately, retain review evidence and assign corrections to an owner. A code that exists can still be wrong for the product. Use the five steps below to distinguish a mechanical code check from a substantive review, and to keep catalog work separate from the per-product research and cost comparisons in GingerLite.
For a large storefront catalog, ecommerce product catalog HTS audit separates outdated assignments from products that need new research.
Step 1: Export the catalog and evidence
Collect SKU, description, current code, origin, customs value and entry date. Link specifications, invoices and prior classification decisions rather than treating the description as complete.
Step 2: Verify the code against the current schedule
Check retired or subdivided codes and revised legal Notes in the USITC schedule [1]. Record the revision used. A valid-code lookup does not confirm the classification's legal basis.
Step 3: Re-run high-risk classifications
Apply the GRI to construction, materials, function and intended use [2]. Review competing headings and the relevant CROSS rulings. Classification Researcher asks clarifying questions and produces a reasoning report, one product per case; the customer's licensed broker reviews it before filing.
Step 4: Check origin and duty treatment
Verify manufacturing facts and any preference claim independently. Check the exact Chapter 99 coverage and exceptions instead of adding every Section 301 or Section 232 rate. Tariff Calculator compares U.S. duties across origins for the entry date entered.
Step 5: Produce and approve a remediation plan
Keep the existing and proposed code, reason, reviewer, affected entries and next action. A product-master change does not itself correct an entry. The broker should assess correction and refund procedures separately. Reasonable care remains the importer's duty [3]; retain the underlying records under 19 CFR 163.4 [4].
Where Parts Library fits
Parts Library compares landed costs for candidate codes and source countries and saves selections. Excel or CSV uploads are limited to 100 rows each. It does not automatically audit the catalog, establish origin or certify FTA eligibility.
For catalog batch classification and rechecks, use a customer-specific GingerOS workflow. Compliance Radar checks U.S. notices against your own codes and emails what is affected. Trade Advisory can review classification, origin and sourcing questions, quoted for scope.
Frequently Asked Questions
Does a valid HTS code prove correct classification?
No. The product facts and applicable legal provisions must support that code.
What should the export contain?
At minimum, product identifiers, descriptions, existing codes, origins, values, entry dates and links to supporting records.
Which items need reclassification first?
Prioritize changed or incomplete specifications, competing headings and missing legal reasoning.
Does a new duty always mean a new code?
No. A Chapter 99 or rate change may leave the product classification unchanged.
Can Parts Library audit my codes?
No. It compares candidate-code and country costs; it is not an automated classification audit.
Where does catalog rechecking belong?
In a GingerOS workflow fitted to the customer, with review and approval of the results.
Does updating ERP correct past entries?
No. Have the broker assess entry corrections separately.
Can a report guarantee reasonable care?
No. The importer must evaluate the facts, research, controls and decisions actually used.
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
