Planning Use SEO page 97

HTS code for knitted hat: document fiber, construction, and headwear type

Planning Use only. Broker review required for Entry Use.

A knitted hat file overlaps with beanies, winter hats, balaclavas, headbands, ear warmers, and caps. The record needs fiber content, knit construction, lining, shape, decoration, wearer, and origin before a candidate path is trusted.

Use this page to prepare the Planning Use record before broker review. The file should say what headwear is imported and what facts support the description.

quick answer

For "hts code for knitted hat", collect fiber content by weight, knit construction, headwear type, lining, cuff, pom-pom, ear flaps, ties, brim if any, size range, wearer, decoration, origin, and supplier code.

A cuffed acrylic beanie is not the same fact pattern as a lined winter hat, balaclava, headband, or cap with brim. The record should not treat every knitted headwear item as one product.

facts to collect for a knitted hat

Collect:

Product name, invoice wording, SKU, and product page.
Front, side, crown, inside, label, lining, cuff, brim if present, decoration, and packaging photos.
Fiber content by weight for shell, lining, pom-pom, trim, and embroidery.
Knit construction, stitch type, gauge if available, and fleece or pile lining.
Headwear type: knitted hat, beanie, winter hat, balaclava, headband, cap, children's hat, or set component.
Size range, wearer, cuff, ear flaps, ties, brim, pom-pom, patch, embroidery, or reflective trim.
Country of origin and production support.
Supplier HS or HTS code and source notes.

If the hat includes a brim, record whether it remains a knitted hat or behaves more like a cap. If it is a balaclava, show face and neck coverage.

missing facts

Mark the file incomplete when:

Fiber content by weight is missing.
Knit construction is unsupported.
Headwear type is unclear.
Lining, cuff, brim, pom-pom, or decoration facts are missing.
Size range, wearer, or children's status is unclear.
Origin is assumed from shipment route.
Supplier code is unsupported.
Close CBP CROSS rulings have not been checked.

These gaps can move the review between knit headwear, cap, balaclava, headband, or apparel accessory.

HTS candidate notes

Build candidate rows for the actual headwear: knitted hat, lined winter hat, beanie, balaclava, headband, cap, children's hat, or set component. Each row should cite a product fact.

Rejected alternatives should stay in the record. If it is not a baseball cap because it lacks structured panels and brim, say that. If it covers the face and neck, do not hide the balaclava question.

authority sources

Use USITC HTS for tariff text. Use CBP CROSS for knitted hats, beanies, balaclavas, caps, and textile headwear rulings.

planning path

Start with photos and labels. Then write a table for fiber, knit construction, lining, headwear type, wearer, decoration, origin, and supplier code. If the listing calls it a hat but photos show a headband, mark that conflict.

Duty stack notes should include origin, special tariff program claims, and textile exposure tied to fiber and headwear type.

questions importers ask

Can I use this page as the HTS code for a knitted hat?

No. Use it for Planning Use. Entry Use needs broker or customs authority review.

Does lining matter?

Yes. Shell and lining fibers should be documented separately.

What if the hat has a brim?

Record the brim and review whether the article is better described as a cap.

internal links

planning boundary

This knitted hat HTS page is a planning artifact. It is not an Entry Use classification, not a binding ruling, and not a legal opinion. The importer remains responsible for reasonable care and must obtain broker or customs authority review before filing.

Turn this search into a file

Run a free Duty Surprise Scan, then build a Planning Use Classification Record when the Missing Facts matter.

Start scan today →