HS Codes for Pharmaceuticals and Medical Devices

How to manage HS and tariff codes for pharmaceuticals and medical devices, where customs classification overlaps with FDA, CBP, and product regulatory data.

Pharmaceuticals and medical devices expose a common tariff-data problem: the HS or HTS code is necessary, but it is not the whole compliance record. Customs needs a tariff classification for duty and statistics. Regulators may need product codes, intended use, registration, listing, approvals, declarations, or other data to decide whether the product is admissible. If those values live in disconnected spreadsheets, one shipment can look correct to finance and incomplete to a regulatory reviewer.

Claro helps regulated-product teams maintain one governed product record with tariff classification, regulatory attributes, source evidence, and reviewer status linked together. That makes tariff codes useful without pretending they replace FDA, CBP, or other agency requirements.

Tariff classification vs regulatory admissibility

Question	Tariff classification answers	Regulatory data answers
What is the product for customs duty?	HS root and national tariff code	Not the primary purpose
What duty rate or statistical category applies?	Tariff schedule, notes, special measures	May influence total import process but not the tariff line itself
Is the device, drug, or ingredient admissible?	Only indirectly	Agency product code, intended use, registration, listing, approval, declarations
What evidence supports the filing?	Classification notes, broker decision, ruling, product attributes	Labels, certificates, product listing, technical file, regulatory status
Who should review it?	Trade compliance or customs broker	Regulatory affairs, quality, FDA/import specialist

Pharmaceuticals: what drives classification

Pharmaceutical products can move between chemical, pharmaceutical, diagnostic, and retail-preparation areas depending on the facts. The key attributes include:

active ingredient and concentration
finished medicine versus intermediate or bulk ingredient
dosage form and whether it is put up in measured doses
retail packaging versus bulk packaging
therapeutic or diagnostic use
controlled-substance, hazardous, or cold-chain indicators
country-specific notes, exclusions, and additional duties

A product title like “amoxicillin suspension” is not enough if the catalog lacks strength, package form, finished status, and destination-market context. The right classification workflow extracts those fields first, then routes ambiguous or regulated cases for expert review.

Medical devices: tariff code plus agency data

Medical-device catalogs create another data challenge: many commercial products are kits, accessories, parts, consumables, instruments, software-enabled devices, or radiation-emitting products. A tariff code may identify the customs category, while FDA or other agency data identifies the regulated product and admissibility path.

Useful fields include:

Field	Why it matters
device type and intended use	Separates general instruments, diagnostic devices, implants, accessories, and non-medical lookalikes
FDA product code or equivalent agency code	Supports admissibility and entry review where applicable
manufacturer, registration, and listing status	Connects product identity to regulatory responsibility
sterile, implantable, single-use, radiation-emitting, or software-enabled flags	Triggers review paths and required data
kit components	A kit may require classification and regulatory analysis beyond the headline product name
tariff code by market	U.S., EU, Canada, and other markets can require different national extensions

The governed workflow

1

Resolve product identity

Confirm whether supplier rows, internal SKUs, UDI/GTIN values, and manufacturer part numbers describe the same product or different regulated items.
2

Extract classification-driving attributes

Pull ingredients, dosage form, intended use, device type, sterile status, material, and package form from source documents and supplier feeds.
3

Assign tariff codes by market

Maintain HS root plus national tariff classifications separately for each destination market.
4

Attach agency data

Link FDA product codes, registrations, declarations, certificates, or equivalent regulatory attributes to the same canonical record.
5

Route exceptions for review

Send sparse, contradictory, high-risk, or regulated records to trade compliance and regulatory affairs before they block an entry.

Claro automates much of this data preparation while preserving provenance. That does not replace brokers or regulatory experts; it gives them cleaner evidence and fewer avoidable exceptions.

Guide

HS Code vs HTS Code

Understand the global root and the U.S. tariff extension.

Guide

U.S. HTS vs EU CN/TARIC

Dual-market importers need separate market-specific classifications.

Tool

HS Code Lookup

Catch malformed tariff-code values before they enter the product record.

Claro

Regulated product data enrichment

Connect tariff codes, regulatory attributes, and source evidence in one governed catalog layer.

FAQ

Are HS codes enough for importing medical devices?

No. The tariff code supports duty and statistical classification, but medical-device imports can also require FDA product codes, registration or listing information, intended-use data, and other admissibility details.

Why are pharmaceutical HS classifications difficult?

Pharmaceutical classification can depend on active ingredient, dosage form, whether the product is put up in measured doses or retail packings, and whether it is a finished medicine, intermediate, reagent, or chemical input.

Should trade and regulatory teams share the same product data?

Yes. Customs classification and regulatory admissibility use different code systems, but they describe the same product. Keeping them in separate spreadsheets creates inconsistent filings and slow exception handling.

How does Claro help regulated-product classification?

Claro connects product identity, tariff classification, regulatory attributes, source documents, and reviewer decisions in one governed layer, so teams can validate codes and agency data before a shipment or channel feed is blocked.