Planning Use SEO page 383

CBP ruling request template for printed circuit boards

Planning Use only. Broker review required for Entry Use.

Printed circuit board requests need one early split: bare board or populated assembly. That difference changes the facts CBP needs. A bare PCB, PCBA, controller board, sensor module, power board, and device motherboard are not the same record.

quick answer

For cbp ruling request template printed circuit boards, collect board state, component population, function, parent device, layer count, materials, firmware or programming, and manufacturing steps. Keep the file in Planning Use until Broker or customs authority review.

facts to collect before drafting

Board state: bare printed circuit, populated PCBA, module, subassembly, motherboard, controller, power board, sensor board, or test board.
Function in the finished product and whether the board can perform any function on its own.
Layer count, board material, copper traces, solder mask, dimensions, connectors, mounted components, and heat sinks.
Components: ICs, resistors, capacitors, sensors, relays, LEDs, ports, switches, transformers, or wireless modules.
Firmware, programming, testing, calibration, and whether software loading occurs before import.
Parent device, compatibility list, part number, schematic, bill of materials, and product photos.
Origin steps for bare board fabrication, component placement, soldering, programming, testing, and packing.

missing facts

Ask whether the import is a bare board or a populated board. If populated, ask what the board does and which device it controls. If programming occurs after import, record that. If the board includes wireless, power conversion, sensing, or display functions, write those facts directly.

HTS candidate notes

Start with printed circuit and electronic assembly provisions in the USITC HTS, then test whether the board is a part of a specific machine or an electronic module with its own function. Section 301 exposure can depend on origin of board fabrication and assembly.

authority sources

Use CROSS rulings only when board state, components, function, and parent-device relationship match. A bare PCB ruling does not settle a populated controller board.

planning path

Draft the request with top and bottom photos, schematic or block diagram, BOM summary, function statement, and origin steps. List candidate families and the facts that separate bare circuits, parts, and functional modules.

The packet should include a short note on what happens after import. Post-import programming, casing, or installation can affect how reviewers understand the board.

If the board is imported for several devices, list those devices and the function in each one. If the same PCB is populated in different versions, record the missing or added components. Connector layout, firmware, and mounted parts often matter more than the board outline.

The request should also say whether the board is sold as a replacement part, a finished module, or an unfinished input for later assembly. A bill of materials helps, but it should be tied to the board function. A pile of component names without the parent device and post-import steps leaves too much room for a weak ruling request.

questions importers ask

Is a populated board still a printed circuit?

Not always for planning. The mounted components and function need review.

Should firmware be described?

Yes. Programming can show what the board does.

Can one request cover several board revisions?

Only if the function and components stay close. List revision differences.

internal links

planning boundary

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