How to Audit Existing HTS Codes: Step-by-Step Process Guide

How do you audit existing HTS codes for an importer?

To audit existing HTS codes, a compliance manager exports the catalog of classified products from the ERP or broker filing system, runs each code through the current HTS schedule and current GRI logic to verify accuracy, checks the country of manufacture and Section 232/301/122 application, confirms reasonable care documentation per code, and produces a remediation plan for any code flagged as outdated, misclassified, or under-documented.

Why audit existing HTS codes in 2026?

Three regulatory shifts in early 2026 invalidated portions of every importer's HTS catalog: the February 28 Section 321 suspension added classification requirements to formerly-de minimis parcels, the April 6 Section 232 restructuring changed metals tariff methodology and added a new de minimis test, and the IEEPA-to-Section-122 transition reset country-specific tariff stacks. Catalogs that were audit-clean in 2025 are not audit-clean in 2026 without a re-audit.

TL;DR

The five-step process for auditing existing HTS codes: (1) export the catalog, (2) verify each code against the current HTS schedule, (3) re-run classification through current GRI logic for any flagged or high-risk SKUs, (4) confirm Section 232/301/122 application by country and composition, (5) produce a remediation plan with reasoning chains attached. GingerControl's Product Sandbox automates steps 2-4 across the entire catalog, returning a flagged report that compliance teams use to prioritize remediation.

Last updated: May 2026

Step 1: Export the catalog

The audit starts with a complete inventory of HTS-classified products. The export sources:

ERP product master with HTS code field
Broker filing system entry summary records
Customs entry data from ACE for the audit period
Product information management (PIM) system if separate from ERP

The export should produce a CSV with at minimum: SKU, product description, current HTS code, country of manufacture, value, and entry date for the most recent shipment of each SKU. Compliance teams that lack a centralized HTS field often discover at this step that the catalog is incomplete, which is itself an audit finding.

Step 2: Verify each code against the current HTS schedule

Codes get retired, subdivided, or reassigned in annual HTS schedule revisions and sub-revisions. The verification step checks each existing code against the current schedule:

Does the code still exist?
Has it been subdivided into more specific subheadings?
Has the duty rate changed?
Are there new Chapter 99 layers (Section 122, Section 232, Section 301) that apply?

Codes flagged as outdated need reclassification under the current schedule. This is mechanical work that scales poorly by hand but well by tool.

Step 3: Re-run classification through current GRI logic

For codes that are still valid in the current schedule, the next question is whether the original classification was correct under General Rules of Interpretation analysis. The audit re-runs each high-risk SKU through GRI logic:

GRI 1: classification by heading text and Section/Chapter Notes
GRI 2: incomplete or unfinished articles, mixtures and combinations
GRI 3: most specific heading; essential character (3b); last in numerical order (3c)
GRI 4: kindred goods if 1-3 do not resolve
GRI 5: containers and packaging
GRI 6: subheading-level classification

Composite goods, ambiguous descriptions, and SKUs with mixed-material composition are highest-risk. A re-audit typically flags 5-15% of codes for reclassification.

GingerControl's HTS Classification Researcher follows GRI logic, surfaces multiple candidate HTS codes, and asks clarifying questions before converging on a classification, producing audit-ready reports grounded in Section Notes, Chapter Notes, and relevant CROSS rulings.

Step 4: Confirm Section 232/301/122 application

The 2026 regulatory environment requires confirming three additional layers per SKU:

Section 232 metal content. The April 2026 restructuring introduced a 15% metal-content de minimis exception. Each metal-containing SKU should be evaluated against the threshold, with composition data confirming the determination.

Section 301 country exposure. China-origin product on the Section 301 list carries 25-30% on top of base MFN. The audit confirms country of origin per SKU and checks against the current Section 301 product list.

Section 122 reciprocal tariffs. The 10% Section 122 baseline (set to expire around July 23, 2026 unless extended) applies to most countries. The audit confirms the country of origin determination and the applicable Section 122 layer per SKU.

Step 5: Produce a remediation plan with reasoning chains

The audit output is a remediation plan: a list of SKUs needing action, the reason for each, and the proposed remediation. The remediation plan typically includes:

SKUs needing HTS code update (outdated or reclassified)
SKUs needing country of origin confirmation (substantial transformation analysis)
SKUs needing composition confirmation (Section 232 metal-content threshold)
SKUs needing reasoning chain documentation (no audit trail on existing code)
SKUs needing licensed customs broker review (10-digit HTSUS classification under HQ H290535)

Each remediation should produce a reasoning chain attached to the SKU's master record, ready for any future CBP Focused Assessment under 19 U.S.C. 1509.

How GingerControl's Product Sandbox automates the audit

The Product Sandbox accepts the catalog export from Step 1, performs Steps 2-4 across the entire catalog, and returns a flagged report ready for Step 5 remediation. The output includes:

Status per SKU: match, outdated, reclassify, clarify, audit
Reasoning chain per SKU: GRI rules applied, Section/Chapter Notes referenced, CROSS rulings considered
Section 232/301/122 application per SKU with composition and country checks
Clarifying questions structured for resolution by the merchandiser

This converts a manual catalog audit (weeks for a 10,000-SKU catalog) into a systematic process (hours for the same catalog).

Comparison: manual audit vs Product Sandbox audit

Audit step	Manual process	GingerControl Product Sandbox
Catalog export	Same	Same
HTS schedule verification	Manual lookup per SKU	Automated against current schedule
GRI re-classification	Manual analysis per SKU	Automated through Classification Researcher
Section 232/301/122 application	Manual per SKU	Automated per SKU with country and composition
Remediation plan	Compiled manually	Generated as flagged report
Reasoning chain documentation	Written per SKU if at all	Generated per SKU automatically
Time per 10,000-SKU catalog	4-8 weeks	Hours
Time per 100,000-SKU catalog	Not feasible	1-2 days

Bottom line: Manual catalog audit does not scale past a few thousand SKUs. The Product Sandbox makes catalog re-audit feasible at the scale most importers actually operate at, and produces audit-ready documentation that survives a CBP Focused Assessment.

FAQ

How do compliance teams audit existing HTS codes at scale? Compliance teams use a bulk audit tool that accepts a CSV of existing classifications and re-runs each through current GRI logic, current HTS schedule, and current tariff rates. GingerControl's Product Sandbox returns a flagged report by status (match, outdated, reclassify, clarify, audit) and produces audit-ready reasoning per SKU.

What are the five steps of an HTS code audit? (1) Export the catalog from ERP, broker, or PIM. (2) Verify each code against the current HTS schedule. (3) Re-run classification through current GRI logic for high-risk SKUs. (4) Confirm Section 232/301/122 application by country and composition. (5) Produce a remediation plan with reasoning chains attached per SKU.

Why audit existing HTS codes in 2026? Three 2026 regulatory shifts invalidated portions of every importer's HTS catalog: the Section 321 suspension, the Section 232 restructuring, and the IEEPA-to-Section-122 transition. A catalog that was audit-clean in 2025 needs re-audit in 2026.

How does GingerControl handle the Section 232 metal-content de minimis check? The Product Sandbox evaluates each metal-containing SKU against the 15% metal-content threshold. SKUs with composition data confirming under-15% metal content are flagged as exempt. SKUs without composition data are flagged for clarifying questions.

What documentation does the audit produce? Per remediated SKU: GRI rules applied, Section and Chapter Notes referenced, CROSS rulings considered, staged HTS determination at 4-digit, 6-digit, 8-digit, and 10-digit levels, country of origin determination, and full tariff stack calculation. This is the documentation a CBP Focused Assessment examines.

How long does a catalog audit take? Catalogs up to 10,000 SKUs typically complete in hours through the Product Sandbox. Larger catalogs (50,000-100,000 SKUs) complete in 1-2 days, with checkpoints for clarifying questions on SKUs with insufficient description.

Does the audit replace licensed customs broker review? No. The audit produces audit-ready research that supports the broker's classification decisions. Final classification at the 10-digit HTSUS level is customs business under CBP Ruling HQ H290535 and benefits from licensed customs broker professional judgment.

If your team is preparing for a CBP audit or post-2026 catalog re-audit

If your compliance team is preparing for a CBP Focused Assessment or remediating the catalog after the 2026 regulatory changes, GingerControl's Product Sandbox is built for that workflow.

Try GingerControl's Product Sandbox

Talk to our team about catalog re-audit projects or audit preparation.

References

[REF 1] CBP Section 321 Programs and February 2026 suspension Data cited: Global de minimis suspension, classification on every parcel Source: CBP Section 321 Programs Published: February 2026

[REF 2] Perkins Coie analysis of April 2026 Section 232 restructuring Data cited: 50% metals rate on full customs value, 15% metal-content de minimis exception Source: Restructured Section 232 Tariffs Published: April 2026

[REF 3] CBP Focused Assessment Program Data cited: 19 U.S.C. 1509 audit authority for reasonable care examination Source: CBP Focused Assessment

[REF 4] U.S. International Trade Commission, HTS schedule Data cited: Annual schedule revisions affecting catalog currency Source: hts.usitc.gov

[REF 5] CBP Ruling HQ H290535 Data cited: 10-digit HTSUS classification as customs business under 19 U.S.C. 1641(b)(1) Source: CBP Ruling HQ H290535 Published: September 29, 2022