Planning Use SEO page 413

CBP CROSS rulings for printed circuit boards

Planning Use only. Broker review required for Entry Use.

Printed circuit board rulings can turn on whether the board is bare, populated, programmed, housed, or fitted for a named device. A bare PCB, PCBA, controller module, appliance board, sensor board, and replacement board are not the same record.

quick answer

For cbp cross ruling printed circuit boards, compare CROSS rulings by bare or populated state, mounted components, function, parent device, programming, housing, connectors, and imported condition. A ruling for a finished electronic module may not support a bare board.

facts to collect before drafting

Board type: bare PCB, populated PCBA, controller board, sensor board, power board, display board, appliance board, or replacement module.
Mounted components: chips, resistors, capacitors, connectors, relays, LEDs, antennas, switches, sensors, battery holders, or heat sinks.
Function after import, parent device, firmware or programming state, input and output signals, and whether housing is included.
Dimensions, layer count, substrate, copper pattern, connectors, labels, part number, and board revision.
Whether imported alone, with cables, in a kit, inside a housing, as a spare part, or for further assembly.
Photos of both sides, BOM summary, schematic or block diagram, datasheet, product page, and packaging.
Origin steps for board fabrication, component placement, soldering, programming, testing, housing, and packing.

missing facts

Ask whether the board has components and what it does. If the file only says "PCB," CROSS results will mix bare boards, assemblies, and finished modules. Missing parent-device, programming, and post-import work facts are material gaps.

HTS candidate notes

Start with USITC HTS provisions for printed circuits, electrical parts, and functional electronic modules. Then compare CROSS rulings by board state and function. Section 301 exposure follows origin and subheading work.

authority sources

Use CROSS to compare the import state and function. A bare board ruling should not support a programmed controller unless the facts explain why.

planning path

Create a table with ruling product, board state, components, function, parent device, programming, housing, and imported condition. Put your SKU beside each ruling.

For populated boards, list the components that create function. For bare boards, include layer count and fabrication state. For replacement boards, show the device they fit and whether the board can do anything useful alone.

Rejected rulings help when a board name is close but the board state or function differs.

For boards with cables or displays attached, list those parts and explain whether they are required for the board's function. For service parts, include the repair manual or product family. Save close photos of connectors, labels, and populated areas.

If the board ships with test firmware or no firmware, say that directly. If the supplier describes the board as universal, ask which products actually use it and whether any later programming changes the function.

Save anti-static packaging labels and board revision photos.

Keep samples.

questions importers ask

Is a PCB the same as a PCBA?

No. A populated board and a bare printed circuit need separate facts.

Should firmware be listed?

Yes. Record whether programming occurs before or after import.

What if the board fits several products?

List each parent product and the function in each one.

internal links

planning boundary

This printed circuit boards CROSS 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 →