How FDA product codes are built
The code that routes your entry to a reviewer. Wrong, and it arrives somewhere it will not make sense.
Licensed U.S. customs brokerage. Customs broker of record; movement coordinated through vetted partners.
An FDA product code identifies an article at entry: its industry, class, subclass, how it was processed or packed, and the specific product. It determines how the entry is reviewed and against which requirements, which makes it consequential in a way its length does not suggest.
Key takeaways
- The code is built from several parts, each narrowing the description.
- It determines how and against what your entry is reviewed.
- A defensible code in the wrong position still routes the entry wrongly.
- The code and the customs classification are different things.
- Errors repeat silently across every subsequent entry.
What the code is doing
It tells FDA what is arriving in enough detail to decide how much interest to take. The industry and class place the article; the process and packaging elements say how it was made and how it travels; the product element identifies the specific thing.
Because the code drives the review, an inaccurate one does not simply mislabel the shipment. It sends the entry down a path built for something else, where the questions asked will not match the goods and the answers will not resolve.
It is not the customs classification
Importers frequently conflate the two. The HTS code determines duty treatment; the FDA product code determines regulatory review. They describe the same goods for different purposes and they do not map onto each other.
Both have to be right, and being confident about one says nothing about the other.
Where errors hide
Product codes are usually set once, at the first entry, and then reused. An error made at the outset repeats quietly on every shipment afterwards, often without consequence, until something draws attention to the file.
That is the awkward pattern: a long run of clean entries is not evidence the code is right. It is only evidence that nothing has looked closely yet.
How a product code is built
The code is what routes your entry to a reviewer. A defensible code in the wrong position sends the entry somewhere it will not make sense.
How it works
-
01
Describe the article accurately
What it is, how processed, how packed.
-
02
Place the industry and class
The broad category first.
-
03
Narrow through subclass and process
Each element adds specificity.
-
04
Check it against the customs classification
Different systems, both must be right.
-
05
Review the codes in use
Reused codes carry forward whatever was set originally.
Common mistakes
- Confusing it with the HTS code. Different systems, different purposes.
- Reusing a code without checking. Errors repeat silently.
- Choosing a code that is close enough. Close routes the entry wrongly.
- Ignoring the packaging element. It is part of the description.
- Treating clean history as validation. It may only mean nobody has looked.
Questions
Is the product code the same as the HTS code?
No. The HTS code sets duty treatment for customs. The FDA product code determines regulatory review. Both apply and both have to be right.
What happens if the code is wrong?
The entry is reviewed against the wrong expectations, which generates questions that do not fit the goods and take longer to resolve than they should.
Can I keep using the code from previous entries?
Only if it was right to begin with. Codes carry forward, so an early error propagates quietly across everything that follows.
Who is responsible for the code?
The importer of record, as with the customs classification. A broker files it; the responsibility for accuracy remains with the importer.
Related
Tell us what you're importing.
Commodity, origin, port and arrival date is enough to start.