Planning Use SEO page 93

HTS code for men's shirt: document fabric, construction, and style

Planning Use only. Broker review required for Entry Use.

A men's shirt file needs fabric and garment construction facts. The product may be a woven dress shirt, knit polo, casual overshirt, work shirt, flannel shirt, t-shirt, hoodie-like shirt, or jacket-style shirt. The word "shirt" is too broad.

Use this page to prepare the Planning Use record before broker review. The record should show whether the shirt is knit or woven, what it is made of, and why it belongs in the proposed candidate path.

quick answer

For "hts code for men's shirt", collect fiber content by weight, knit or woven construction, garment type, collar, placket, sleeve length, cuffs, pockets, closure, lining if any, size range, origin, and supplier code.

A woven button-front shirt is not the same fact pattern as a knit polo, t-shirt, sweatshirt, or shirt jacket. Men's sizing and styling should be supported by labels and product photos.

facts to collect for a men's shirt

Collect:

Product name, invoice wording, SKU, and product page.
Front, back, collar, placket, sleeve, cuff, pocket, hem, inside label, care label, and packaging photos.
Fiber content by weight for shell, lining, collar, cuffs, and trim.
Knit or woven construction, fabric type, yarn-dyed or printed fabric, and fabric weight if available.
Garment type: dress shirt, casual shirt, polo, t-shirt, work shirt, overshirt, shirt jacket, or set component.
Men's size range, fit, collar type, sleeve length, closure, pockets, yoke, cuffs, and decoration.
Country of origin and production support.
Supplier HS or HTS code and source notes.

If the product is an overshirt or shirt jacket, capture fabric weight, lining, pockets, and outerwear-like features.

missing facts

Mark the file incomplete when:

Fiber content by weight is missing.
Knit or woven construction is unsupported.
Shirt versus polo, t-shirt, jacket, or sweatshirt status is unclear.
Collar, placket, sleeve, pocket, cuff, or closure details are missing.
Men's sizing or intended wearer is unsupported.
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 woven shirts, knit shirts, outerwear, or other apparel categories.

HTS candidate notes

Build candidate rows for the actual garment: men's woven shirt, men's knit shirt, polo, t-shirt, work shirt, shirt jacket, or set component. Each row should cite a garment fact.

Rejected alternatives should stay in the record. If the garment is not a jacket because it lacks lining and outerwear construction, say that. If it is knit, do not rely on a woven shirt path.

authority sources

Use USITC HTS for tariff text. Use CBP CROSS for men's shirt, woven shirt, polo, knit shirt, work shirt, and shirt jacket rulings.

planning path

Start with label photos and construction photos. Then write a table for fiber, construction, garment type, wearer, collar, closure, sleeve, origin, and supplier code. If product photos disagree with invoice wording, record the conflict.

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

questions importers ask

Can I use this page as the HTS code for a men's shirt?

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

Does knit versus woven matter?

Yes. Construction should be documented with photos, labels, or supplier support.

What if it is a shirt jacket?

Record lining, fabric weight, pockets, and outerwear features before review.

internal links

planning boundary

This men's shirt 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 →