FDA Product Codes Explained: How to Find Yours and Why It Matters

Every FDA-cleared medical device has a product code — a three-letter identifier that places it within FDA's device classification system. Product codes are not administrative trivia. They determine your device's legal classification, the CFR regulation that governs it, which FDA review panel evaluates it, what special controls apply, and most critically — which cleared devices are valid predicates.

Choosing the wrong product code, or failing to verify yours before filing, can invalidate your predicate selection and trigger a complete rework of your submission strategy.

What a product code represents

Each product code maps to a specific device type within FDA's classification database. That mapping defines:

• Device class — Class I, II, or III
• Regulation number — the specific 21 CFR section that governs devices of this type
• Review panel — the FDA advisory committee with jurisdiction (Cardiovascular, Orthopedic, Neurology, etc.)
• Special controls — any device-type-specific requirements beyond general controls
• Premarket submission requirement — whether 510(k), PMA, De Novo, or exemption applies

For example, product code DQO covers "cardiovascular monitors" — Class II devices regulated under 21 CFR 870.2300, reviewed by the Cardiovascular panel, subject to specific performance standards for cardiac monitoring.

How to find your product code

There are three reliable approaches:

1. FDA's Product Classification Database — search at accessdata.fda.gov/scripts/cdrh/cfdocs/cfPCD/classification.cfm by device name, regulation number, or panel. This is the authoritative source but requires knowing how FDA categorizes your device type, which isn't always intuitive.

2. Search cleared 510(k)s for similar devices — find a cleared device that most closely resembles yours in intended use and technology. Its product code is a strong candidate for yours. If multiple similar devices share the same product code, that's a reliable signal.

3. Pre-submission meeting — if your device is genuinely novel or sits at the boundary between two product codes, FDA will tell you the appropriate code in a Pre-Sub meeting. This is binding — FDA cannot later assign a different code without explanation.

When a device might have multiple possible product codes

Combination devices — those that combine drug, device, and/or biological components — can have complex product code situations. Software as a Medical Device (SaMD) frequently sits at boundaries between existing product codes. A device that monitors and also treats may qualify under a monitoring code or a therapeutic code depending on its primary mode of action.

In these cases, the intended use statement is the deciding factor. FDA assigns product codes based on what the device is primarily marketed to do. A device that primarily monitors and incidentally alerts for intervention gets the monitoring code. A device where the intervention is the primary purpose gets the therapeutic code.

Product code and predicate validity

This is the critical practical implication: your predicate must share your product code. FDA will not accept a substantial equivalence argument built on a predicate with a different product code unless you explicitly argue that the codes are closely related and the different classification doesn't affect the equivalence analysis — and even then, reviewers are skeptical.

Before you build your predicate strategy, confirm your product code. Then search for predicates exclusively within that code. Predicates from adjacent codes — even devices that look nearly identical — are legally problematic and waste submission preparation time.

Product codes change over time

FDA occasionally reclassifies device types, splitting one product code into two or consolidating multiple codes. When this happens, legacy clearances retain their original code but new submissions must use the current classification.

If you're using an older cleared device as a predicate, verify that its product code is still the current classification for that device type. A predicate cleared under a superseded code may still be valid, but you'll need to document the reclassification history and explain why the predicate remains appropriate.

Using product codes to scope your competitive landscape

Beyond predicate selection, product code analysis gives you a complete picture of the competitive regulatory landscape. Every company that has cleared a device under your product code is a market participant you should know about. Their clearance timelines tell you how long FDA review typically takes. Their technological choices tell you what FDA has already accepted. Their decision dates tell you when the market was most active.

This is intelligence that predicate research tools surface automatically — search by product code, filter by year, and you have a complete clearance history for your device category in seconds.