Planning Use SEO page 89

HTS code for beanie: document knit construction and fiber content

Planning Use only. Broker review required for Entry Use.

A beanie file should prove the headwear construction. The product may be a knit beanie, cuffed winter hat, fleece-lined hat, pom-pom hat, balaclava-like item, skull cap, children's hat, or a cap with Bluetooth speakers. Fiber and construction details matter.

Use this page to prepare the Planning Use record before broker review. The record should show the hat, material, lining, decoration, origin, and any missing facts.

quick answer

For "hts code for beanie", collect fiber content by weight, knit construction, lining, cuff, pom-pom, ear flaps, fleece band, decoration, size range, gender or intended wearer, origin, and supplier code.

A simple acrylic knit beanie is not the same fact pattern as a fleece-lined winter hat or a Bluetooth beanie. A balaclava, headband, or baseball cap should not be forced into the beanie record.

facts to collect for a beanie

Collect:

Product name, invoice wording, SKU, and product page.
Front, side, inside, label, cuff, lining, pom-pom, decoration, and packaging photos.
Fiber content by weight for shell, lining, cuff, pom-pom, and trim.
Knit construction, fleece lining, pile lining, or woven panels if present.
Headwear type: beanie, cuffed hat, winter hat, skull cap, balaclava, headband, children's hat, or electronic beanie.
Size range, wearer, cuff style, ear coverage, decoration, patch, embroidery, or reflective trim.
Any electronics, speakers, battery, cable, or removable module.
Country of origin and production support.
Supplier HS or HTS code and source notes.

If the beanie includes speakers or a battery, document those electronics separately. If it is lined, collect shell and lining fiber content.

missing facts

Mark the file incomplete when:

Fiber content by weight is missing.
Knit construction is unsupported.
Lining, cuff, pom-pom, or decoration facts are missing.
Beanie versus balaclava, headband, or cap status is unclear.
Electronics are present but undocumented.
Origin is assumed from shipment route.
Supplier code is unsupported.
Similar CBP CROSS rulings have not been checked.

These gaps can move the review between knit headwear, lined headwear, electronic accessory, or another headwear type.

HTS candidate notes

Build candidate rows for the actual headwear: knit beanie, lined winter hat, children's hat, balaclava, headband, electronic beanie, or other headwear. Each row should cite a product fact.

Rejected alternatives matter. If it is not a cap because it has no brim or structured crown, say that. If it includes electronics, do not ignore them just because the garment is mostly textile.

authority sources

Use USITC HTS for tariff text. Use CBP CROSS for beanie, knit hat, balaclava, lined headwear, and electronic headwear rulings.

planning path

Start with inside label and outside photos. Then write a table for fiber, knit construction, lining, headwear type, wearer, decoration, origin, and supplier code. If electronics are included, add a separate line for them.

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 beanie?

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 beanie has Bluetooth speakers?

Record the electronics and battery facts before review.

internal links

planning boundary

This beanie 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 →