- Record the current HTS revision with every reviewed candidate.
- Prioritize repeated, high-value, high-duty, or measure-sensitive SKUs.
- Subscribe to or monitor official USITC and relevant agency announcements.
- Compare the new edition or revision change record with saved products and provisions.
- Re-run classification when product or supply-chain facts change even if the code text appears unchanged.
- Recheck Chapter 99 and trade-remedy layers independently.
- Document the effect on duty estimates, invoices, marketplace fields, and open orders.
- Export corrected catalog fields only after the review is approved.
How Often Do US HTS Codes Change? Revision and Recheck Workflow
Understand annual HTS editions, in-year revisions, change records, Chapter 99 updates, product-change triggers, and a practical recheck schedule for ecommerce catalogs.
Preparation checklist
The HTS has an annual basic edition, but online revisions can appear throughout the year.
A code number can remain while descriptions, notes, duty treatment, Chapter 99 measures, units, or related provisions change.
Product governance needs both time triggers and event triggers; a calendar reminder alone will miss supplier and specification changes.
Fields to prepare before the document draft
| Field or decision | What to prepare |
|---|---|
| SKU and product version | Stable identifier, model, material, function, construction, components, and revision. |
| HTS record | Full candidate, description, legal-note path, unit, duty columns, and related Chapter 99 provisions. |
| Source version | HTS edition or revision number, publication date, lookup date, source URL, and reviewer. |
| Origin and supplier | Manufacturing origin, producer, exporter, and evidence version. |
| Business exposure | Import frequency, annual value, duty impact, regulated status, and whether the SKU drives DDP or landed-cost pricing. |
| Time trigger | Pre-entry check, scheduled catalog review, annual basic-edition review, and a shorter cadence for volatile measures. |
| Event trigger | Material, design, function, component, kit, supplier, factory, origin, HTS revision, action, exclusion, or ruling change. |
| Disposition | No change, update needed, escalate, effective date, affected orders, and exports regenerated. |
How to prepare the draft
How this looks in a seller workflow
A seller has 600 US-bound SKUs but only 40 account for most import value. Several China-origin products also carry a Chapter 99 review.
The team keeps a quarterly baseline for the full catalog, checks official revisions when published, and immediately reopens a case after specification, supplier, origin, or tariff-action changes. High-value SKUs receive priority rather than treating all 600 rows as equal.
- Store revision per SKU.
- Prioritize exposure.
- Watch official changes.
- Compare change records.
- Reopen on product/supply changes.
- Regenerate exports after approval.
Review the record before it enters a shipment or filing workflow
- Every working code has a source revision and date.
- High-exposure SKUs are identified.
- Annual and in-year revisions are monitored.
- Product and supplier changes are event triggers.
- Chapter 99 and AD/CVD are separate checks.
- Review outcomes identify affected orders and exports.
- Old records remain traceable.
- Only approved changes reach platform exports.
What external guidance supports this workflow?
- USITC HTS announcementsOfficial list of basic editions and in-year revisions.
- USITC HTS archiveRevision files, dates, formats, and modification sources.
- USITC HTS searchCurrent electronic HTS and change record.
- USITC tariff announcementsOfficial tariff and HTS publication notices.
Use the same catalog data in the next review step
- Save a Review ScenarioPaid workspace: retain product, origin, destination, and follow-up notes for the next verified source check.
- Create a Classification CasePaid workspace: keep product facts, candidates, risk findings, source evidence, and exports together.
- Run a Catalog ReviewPaid workspace: process repeated SKUs or platform CSV rows with server-side credits and review history.
- Export Reviewed RecordsPaid workspace: export reviewed fields for TariffCatalog, Shopify, WooCommerce, or Amazon workflows.
- Compare PlansCompare one-time and monthly credits for repeated customs-data work.
- Official SourcesOpen the government tariff, trade-remedy, origin, or recordkeeping source before filing.
- MethodologyReview the source, candidate, estimate-only, and correction boundaries used by TariffCatalog.
- CorrectionsReport an outdated source, unclear statement, or workflow problem for review.
What to avoid
- Checking only once per year.
- Saving a code without its HTS revision.
- Monitoring the number but not notes or Chapter 99.
- Ignoring product or supplier changes.
- Re-reviewing every SKU with no exposure priority.
- Updating marketplace exports before approval.
- Overwriting old evidence instead of preserving history.
Editorial review note
Written by the TariffCatalog Editorial Team for ecommerce document preparation workflows. The page is designed as a preparation checklist, not a filing outcome.
Maintained by Ryan Cole, with review focused on ecommerce catalog, document, and source-check workflow clarity.
Document requirements may be required differently by carrier, destination, shipment value, and product facts. Use the methodology, sources, and corrections pages to understand how the page is maintained.
References to verify
Use official sources, carrier guidance, postal operator rules, and destination requirements to verify before filing or shipping.
Use this official source when checking final classification, duty treatment, or customs requirements.
CBPUse this official source when checking final classification, duty treatment, or customs requirements.
EU TARICUse this official source when checking final classification, duty treatment, or customs requirements.
UK Trade TariffUse this official source when checking final classification, duty treatment, or customs requirements.
Common questions
Does the HTS change only once a year?
No. USITC can issue multiple online revisions during the year.
Can the rate change without the base code changing?
Yes. Notes, measures, or associated provisions can change.
Should every SKU use the same review cadence?
No. Prioritize by value, frequency, duty exposure, and complexity.
What product changes trigger review?
Material, function, construction, components, set presentation, supplier, factory, and origin changes.
Why save the HTS revision?
It shows which official text supported the decision at that time.
Should Chapter 99 be monitored separately?
Yes, because special measures can change independently.
Can a saved supplier code be reused forever?
No. Treat it as a dated starting record and recheck on time and event triggers.
Disclaimer
TariffCatalog provides informational tools and preparation workflows only. Verify final classification, rates, document requirements, and filing treatment with official sources or licensed professionals.
