Planning Use SEO page 416

HTS code for printed circuit board assembly: facts to check before import

Planning Use only. Broker review required for Entry Use.

A printed circuit board assembly is more than a board with parts on it. The HTS planning path depends on what the assembly does, whether it is programmed, whether it has a housing, and whether it is a part of a named device.

quick answer

For hts code for printed circuit board assembly, collect the PCBA function, mounted components, parent device, programming state, connectors, housing, and post-import work before choosing HTS Candidates. A supplier code for "PCB assembly" is too shallow on its own.

facts to collect before drafting

Board type: controller PCBA, sensor board, power board, display board, appliance board, communications board, or replacement module.
Mounted components: ICs, resistors, capacitors, relays, connectors, LEDs, antennas, switches, sensors, battery holders, heat sinks, or fuses.
Function after import, parent device, input and output signals, voltage, firmware, software loading, and testing state.
Whether imported bare, populated, programmed, housed, wired, with cables, with display, or in a retail service kit.
Photos of both sides, component labels, connectors, part number, revision, packaging, and any installed view.
BOM summary, schematic or block diagram, datasheet, product page, invoice, and parent device manual.
Origin steps for bare board fabrication, component placement, soldering, programming, testing, housing, and packing.

missing facts

Ask what the PCBA controls or senses. If the file only says "printed circuit board assembly," the record lacks function. Missing parent-device fit, programming state, and post-import assembly steps can move the HTS candidate path.

HTS candidate notes

Start with USITC HTS provisions for electrical parts, printed circuits, and functional modules. A populated, programmed control board may need different candidate notes from a bare board or unfinished assembly. Section 301 exposure depends on origin and subheading.

authority sources

Use CROSS to compare board state and function, not the term PCBA alone. A ruling for a finished appliance controller may not support an unprogrammed board.

planning path

Create a PCBA table with function, components, parent device, programming, connectors, housing, origin steps, and missing facts. Then compare candidate rulings against each row.

If the board is imported for several devices, list each device and the function in that product. If firmware is loaded after import, record what the board can do at the border and what changes later.

Keep rejected rulings where the board state differs. That helps a Broker see why a bare PCB, PCBA, and finished module were not treated as one article.

For assemblies with cables, housings, displays, or sensors attached, list each part and whether it gives the PCBA a working function. If a test jig, programming cable, or retail service kit ships with it, keep those items separate.

Save board revision labels and connector closeups.

Keep anti-static package labels too.

Keep samples.

questions importers ask

Is PCBA the same as a bare PCB?

No. A PCBA has mounted components, and the function may matter.

Should firmware be included?

Yes. Record whether firmware is loaded before or after import.

What should the supplier provide?

Ask for a BOM summary, function statement, photos, origin steps, and parent-device evidence.

internal links

planning boundary

This printed circuit board assembly 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 →