HTS code in 2026: why the revision date belongs beside the code

Where to look up an HTS code and check its revision

Start with the product description or candidate code. Read the relevant legal text and notes; a keyword match alone is insufficient. If classification remains unresolved, give the product facts and candidate provisions to the responsible customs professional.

• Open official USITC HTS lookup
• Check the USITC revision archive
• Search CBP rulings in CROSS
• Read USITC classification guidance

What is the current 2026 HTS revision?

Checked October 8, 2026: the USITC archive lists Revision 20 dated September 28 above Revision 19. Its modification source is the September 23 Commerce notice on specialty pharmaceuticals and technical corrections. The archive date, notice publication date and applicable entry date are different checks; the listing alone does not determine duty treatment.

That does not mean every revision changes every product. It means the decision record must say which release was consulted and when. “We used the 2026 HTS” is incomplete when the same year contains many legal and statistical versions.

How large is the schedule?

The USITC's 2026 item-count sheet reports 1,228 four-digit headings, 5,612 six-digit subheadings, 11,414 eight-digit subheadings, and 19,738 ten-digit statistical reporting numbers. The scale is one reason a product nickname or supplier code cannot safely stand in for classification facts.

USITC maintains and publishes the HTS. CBP is responsible for interpreting it, issuing binding rulings, and administering customs laws. A search result can help a reviewer find candidate language; it is not itself a binding classification decision.

Why the same digits can still produce a wrong cost

Duty depends on more than copying an HTS number. The relevant date, product description and composition, intended use, origin, value, special-program eligibility, Chapter 99 provisions, exclusions, and trade remedies can all matter. A code may remain textually identical while an additional-duty provision changes around it.

Keep ordinary duty, merchandise processing fee, Section 232 or 301 treatment, antidumping or countervailing duty questions, and other charges as separate sourced layers. This makes a broker correction explainable and prevents finance from treating one composite percentage as timeless.

• Do not classify from a photo, SKU nickname, or old invoice alone.
• Do not silently overwrite the product facts or rationale behind a reused code.
• Do not treat a supplier's code as the importer's final U.S. determination.
• Do not use Tyllus, a search engine, or an AI answer as a binding ruling.

A version-controlled HTS review

Begin with a complete product fact pack. Compare it to the current HTS and relevant notes, identify unresolved questions, route the review to the licensed broker, counsel, or CBP as appropriate, and record the approved conclusion with its revision. Then link the conclusion to the affected SKU and shipment population.

When USITC publishes a revision, do not automatically reclassify the catalog. Screen the change record for relevant provisions, identify impacted products, reopen only the affected decisions, and preserve the superseded rationale for audit history.

Where Tyllus fits—and where it stops

Tyllus can keep product and shipment evidence, customs questions, document versions, partner responses, approved operational context, and cost records connected. It helps teams find the source and understand which shipments used which reviewed assumption.

Tyllus does not assign HTS codes, interpret chapter notes, determine origin or valuation, decide trade-remedy scope, issue rulings, or file entries. Use USITC for the current schedule and CBP or qualified customs professionals for authoritative treatment.