Planning Use SEO page 59

HTS code for sensor module: build the evidence before lookup

Planning Use only. Broker review required for Entry Use.

"Sensor module" is one of those invoice descriptions that sounds clear until you open the photos. It might be a temperature probe on a tiny board, a camera sensor board, an ultrasonic distance module, a pressure transducer with housing, a motion detector, or a finished alarm accessory. The phrase does not tell you enough to pick an HTS path.

Use this page when the shipment record says sensor module and the team needs a planning file before broker review. The work is practical: identify the sensing function, describe the board or housing, collect the electrical facts, check whether the item is a bare component or a finished apparatus, and document the authority sources.

quick answer

For "hts code for sensor module", do not start with the supplier's suggested code as the answer. Start with what the module senses, how it outputs the signal, whether it includes processing or communication circuitry, and whether it is imported as a loose board, a housed unit, or part of a kit.

A sensor board sold for Arduino projects is a different fact pattern from an industrial pressure sensor in a threaded metal body. A camera image sensor board is different again. The planning page should make those differences visible instead of flattening them into one lookup result.

what to collect before the shipment moves

• Photos of the front, back, connector side, label, and packaging.
• Datasheet naming the sensor type and measured variable.
• Output format, such as analog voltage, digital bus, relay output, USB, Bluetooth, Wi-Fi, or proprietary connector.
• Whether the board includes a microcontroller, amplifier, transmitter, battery, lens, housing, magnet, probe, cable, or mounting bracket.
• Whether it is imported alone, in a retail kit, or as a replacement part for a named machine.
• Country of origin evidence and the place where assembly, programming, or calibration occurred.
• Supplier HS or HTS code and any explanation behind it.
• Intended use in the United States.

The intended use should be specific enough to matter. "Electronics" is too broad. "Replacement temperature sensing board for a commercial coffee machine" gives a broker and ruling researcher a much better starting point.

missing facts

• Sensing function and measured variable.
• Whether the imported article is a sensor, a module, a board assembly, or a finished measuring/control device.
• Whether software, firmware, or calibration gives the product its function before import.
• Whether it includes wireless transmission, display, alarm, relay, data logging, or control outputs.
• Whether it is dedicated to one machine or sold for general use.
• Origin facts for the sensor element, board assembly, and final test.

Missing facts matter because sensor modules often sit between several headings. The same trade name can describe a cheap hobby board, an industrial measuring instrument part, or a finished detector. Those should not share a planning file unless the evidence proves they are the same imported article.

HTS candidate notes

For Planning Use, record HTS candidate families rather than a single answer. Candidate paths may depend on whether the product is electrical apparatus, measuring or checking equipment, an instrument part, a semiconductor device, or a component of a named machine. The product facts decide which paths stay on the table.

Write down rejected paths too. If the item is not a finished measuring instrument because it has no display, housing, processor, or direct readout, say so. If it is not a bare sensor element because the board has conditioning circuitry and connectors, say that. Good classification records show the dead ends alongside the path that survived.

authority sources

• USITC HTS
• CBP CROSS
• 19 CFR 177.2

Use the tariff text first. Then use CBP CROSS for fact patterns close to the imported module. Search by sensor type, measured variable, board assembly, detector, transducer, and the industry name printed on the datasheet. If the closest ruling turns on a detail missing from your file, move that detail into Missing Facts.

planning path

Make the first page of the record boring and concrete. What is in the box? What does it sense? What signal comes out? What else is on the board? What country made the thing being imported? Once that is written, the HTS research becomes less random.

Then build a candidate table. One column should name the candidate path. One column should list the product fact that supports it. One column should name the fact that could knock it out. One column should link to the authority source. That table is the part a broker can challenge or confirm.

duty stack notes

Sensor modules can carry origin-sensitive risk because electronics supply chains often move through several countries. The sensor die, PCB assembly, firmware loading, enclosure assembly, and final testing may happen in different places. For duty planning, record what operation creates the imported article's identity and what evidence supports the origin claim.

If the article comes from China, check whether the proposed HTS path changes Section 301 exposure. If the module includes radio communication, check whether the product evidence should also support other import compliance reviews outside HTS. Keep those notes separate from classification so the record stays clean.

related planning questions

• hts code for sensor module
• sensor module hts code
• hs code for sensor module
• sensor board tariff code
• pressure sensor module import duty
• temperature sensor module customs classification
• motion sensor module hts code
• electronics module hs code

These queries usually come from the same anxiety: the invoice description is vague and the supplier code feels thin. Keep the research tied to the actual imported module.

classification record outline

A sensor module Classification Record should include product evidence, product facts, Missing Facts, HTS candidate families, rejected alternatives, authority sources, duty stack notes, and a review decision. Add a small diagram or photo index if the board has several visible parts. It saves time when the reviewer has to compare the datasheet with the imported article.

internal links

• /hts-code-lookup
• /classification-record
• /duty-surprise-scan
• /reasonable-care-file

questions importers ask

Can I use this page as the HTS code for a sensor module?

No. This page is for Planning Use. Entry Use needs broker or customs authority review.

Is every sensor module treated like electronics?

No. The classification path depends on the imported article. A bare board, a housed detector, a transducer, and a part for a named machine can raise different questions.

What is the best first document to request from the supplier?

Ask for the datasheet and clear photos. If the datasheet does not identify the sensing element, output signal, board components, and operating role, ask follow-up questions before code review.

When should this become a ruling packet?

Consider a ruling packet when the module sits between plausible HTS paths, when a close CBP CROSS ruling turns on a missing fact, or when the import volume makes the duty exposure worth formal review.

planning boundary

This Classification Record 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.