Planning Use SEO page 96

HTS code for baby onesie: document infant garment facts

Planning Use only. Broker review required for Entry Use.

A baby onesie page needs infant garment facts, not the retail name alone. The product may be a bodysuit, romper, sleep-and-play, footed sleeper, diaper shirt, set component, or costume-like baby garment. Closure, leg coverage, fiber, and size range matter.

Use this page to prepare the Planning Use file before broker review. The record should show whether the garment is infant apparel and what exactly is in the shipment.

quick answer

For "hts code for baby onesie", collect fiber content by weight, knit or woven construction, infant size range, closure type, sleeve length, leg coverage, snap crotch, footed or footless status, decoration, set contents, origin, and supplier code.

A short-sleeve cotton bodysuit is not the same file as a footed sleeper or baby romper. A gift set with hat and bib needs each item listed.

facts to collect for a baby onesie

Collect:

Product name, invoice wording, SKU, and product page.
Front, back, neckline, sleeve, crotch snaps, leg opening, feet if present, inside label, care label, and packaging photos.
Fiber content by weight for shell, rib, trim, lining, and decoration.
Knit or woven construction and fabric weight if available.
Garment type: bodysuit, onesie, romper, sleeper, footed pajama, diaper shirt, costume, or set component.
Infant size range, sleeve length, leg length, closure, snaps, zipper, footed status, mitts, hood, and decoration.
Country of origin and production support.
Supplier HS or HTS code and source notes.

If the garment includes feet, hood, or a zipper from neck to ankle, record those facts. They may change the garment description.

missing facts

Mark the file incomplete when:

Fiber content by weight is missing.
Knit or woven construction is unsupported.
Infant size range is unclear.
Bodysuit versus sleeper, romper, pajama, or costume status is unclear.
Closure, snaps, footed status, or set components are not listed.
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 infant bodysuits, sleepwear, sets, costumes, or other baby apparel.

HTS candidate notes

Build candidate rows for the actual garment: infant bodysuit, baby romper, footed sleeper, sleepwear, costume-like garment, or set component. Each row should cite a garment fact.

Rejected alternatives should stay in the file. If the product is not sleepwear because it lacks sleepwear styling and is sold as a bodysuit, say that. If it is footed, record that plainly.

authority sources

Use USITC HTS for tariff text. Use CBP CROSS for infant apparel, bodysuits, sleepers, rompers, and apparel set rulings.

planning path

Start with label photos and garment photos. Then write a table for fiber, construction, infant size, garment type, closure, leg coverage, origin, and supplier code. If a set includes several items, split the table by item.

Duty stack notes should include origin, special tariff program claims, and textile exposure tied to infant apparel and fiber content.

questions importers ask

Can I use this page as the HTS code for a baby onesie?

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

Does infant size matter?

Yes. Size range and infant status should be supported by label or product documentation.

What if it is sold as a set?

List each piece separately with fiber, construction, and garment facts.

internal links

planning boundary

This baby onesie 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 →