Planning Use SEO page 46

HTS code for LED bulb: facts to check before import

Planning Use only. Broker review required for Entry Use.

An LED bulb file should say more than "lamp" or "bulb."

The review needs the base type, voltage, wattage, shape, whether the bulb is smart or dimmable, whether it includes a driver, and how it is packaged. A supplier code can help, but the bulb specs should support it.

quick answer

For an LED bulb, use the lookup result for Planning Use until bulb type, base, wattage, voltage, smart function, dimming, packaging, origin, supplier code, Missing Facts, Authority Sources, and Broker review status are documented. Do not use the result as Entry Use classification.

The bulb should be reviewed by its electrical and lighting facts.

facts to collect for an LED bulb

Collect:

Product name and invoice description.
Photos of bulb, base, label, packaging, and markings.
Bulb shape and base type, such as A19, GU10, E26, E27, MR16, tube, or specialty base.
Voltage, wattage, lumens, color temperature, and dimming claims.
Whether the bulb is smart, Wi-Fi, Bluetooth, sensor-based, or remote-controlled.
Whether a driver, adapter, remote, or fixture part is included.
Pack count and retail packaging details.
Country of origin and production support.
Supplier HS or HTS code.
Product page, spec sheet, test report, or bill of materials.

Smart bulbs and ordinary bulbs should not be collapsed into one record without explanation.

missing facts

Mark the record incomplete when:

Base type is unclear.
Wattage or voltage is missing.
Smart or sensor function is not documented.
Pack count is unclear.
Supplier code is unsupported.
Origin is assumed.
Similar CBP rulings have not been checked.
Duty-stack exposure has not been reviewed.

These gaps make the duty estimate weak.

authority sources

Use official sources:

USITC gives the tariff text. CROSS can help compare LED lamps, bulbs, smart lighting, and lighting components.

what TariffCase should produce

TariffCase should produce a Planning Use record with bulb specs, base type, electrical ratings, smart-function notes, packaging, supplier code, HTS Candidate, Missing Facts, Authority Sources, and Broker review status.

That record is more useful than a generic lighting code.

smart bulb trap

Smart bulbs deserve their own facts. Wi-Fi, Bluetooth, sensors, speakers, color control, app control, or a remote should be captured in the record. If the supplier code treats smart and non-smart bulbs as the same item, mark that as a review issue. Also separate bulb packs by base type, wattage, voltage, and smart function.

Pack count matters too. A single replacement bulb, a four-pack retail box, and a kit with hub or remote should not be treated as the same evidence file. List the exact retail pack on the invoice.

internal links

questions importers ask

Does base type matter?

Yes. Base type, shape, and electrical ratings should be visible in the record.

What if the bulb is smart?

Document wireless or app-control functions before review.

Can I use one code for every LED bulb?

No. Review the exact bulb specs and official sources.

What should the file say plainly?

Record base type, voltage, wattage, lumens, color temperature, smart features, driver details, and packaging count. A smart bulb needs more review notes than a plain LED lamp.

planning boundary

This LED bulb 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 →