Planning Use SEO page 88

HTS code for baseball cap: document fabric, panels, and closure

Planning Use only. Broker review required for Entry Use.

A baseball cap file needs headwear facts. The review depends on fiber content, knit or woven panels, brim, crown construction, closure, embroidery, mesh panels, lining, sweatband, and origin. A cap, beanie, bucket hat, visor, and helmet liner should not share one record.

Use this page to prepare the Planning Use file before broker review. The file should show the cap as imported and avoid relying on a retail title.

quick answer

For "hts code for baseball cap", collect fiber content by weight, panel construction, woven or knit fabric, brim material, closure, mesh, sweatband, lining, decoration, size range, origin, and supplier code.

A cotton twill baseball cap is not the same fact pattern as a polyester mesh trucker cap, stretch-fit cap, visor, or beanie. The record should show the headwear construction clearly.

facts to collect for a baseball cap

Collect:

Product name, invoice wording, SKU, and product page.
Front, back, side, crown, brim, inside label, sweatband, closure, and packaging photos.
Fiber content by weight for crown, mesh, sweatband, lining, and trim.
Fabric construction: woven, knit, mesh, coated, laminated, or mixed.
Cap type: baseball cap, trucker cap, snapback, fitted cap, stretch cap, visor, children's cap, or uniform cap.
Brim material, panel count, structured or unstructured crown, eyelets, closure type, and size range.
Decoration: embroidery, patch, print, applique, heat transfer, or reflective trim.
Country of origin and production support.
Supplier HS or HTS code and source notes.

If the cap has mesh back panels, list the mesh fiber separately. If it has a plastic snap closure, document it but keep the headwear facts first.

missing facts

Mark the file incomplete when:

Fiber content by weight is missing.
Woven, knit, or mesh construction is unsupported.
Cap versus visor, beanie, or other headwear status is unclear.
Brim, closure, sweatband, or decoration facts are missing.
Origin is assumed from shipment route.
Supplier code is unsupported.
Similar CBP CROSS rulings have not been checked.
Duty stack exposure has not been reviewed.

These gaps can move the review between textile headwear categories.

HTS candidate notes

Build candidate rows for the actual headwear: woven baseball cap, knit cap, trucker cap, visor, children's cap, uniform cap, or other headwear. Each row should cite a product fact.

Rejected alternatives should stay in the file. If it is not a visor because it has a crown, say that. If it is not a beanie because it has a brim and structured panels, say that too.

authority sources

Use USITC HTS for tariff text. Use CBP CROSS for cap, visor, trucker cap, and textile headwear rulings.

planning path

Start with inside label and headwear photos. Then write a table for fiber, construction, cap type, brim, closure, decoration, origin, and supplier code. If panel materials differ, split them in the table.

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 baseball cap?

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

Does mesh matter?

Yes. Mesh panels and different fibers should be documented separately.

What if the cap is embroidered?

Record the decoration with photos and supplier support.

internal links

planning boundary

This baseball cap 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 →