FDA Product Codes: How to Look Up Device Classification, Regulation Numbers, and Exemption Status

Why Product Codes Matter More Than You Think

Every medical device marketed in the United States maps to a three-letter product code assigned by the FDA. That code is the single most information-dense identifier in the entire regulatory system. From those three letters, you can determine your device's classification (Class I, II, or III), the specific regulation that governs it, whether you need a premarket submission at all, which FDA review division will handle your file, what special controls apply, whether a third-party reviewer can review your 510(k), and what predicate devices exist in your category.

Get the product code right and your regulatory strategy snaps into focus. Get it wrong and you risk submitting to the wrong review division, selecting invalid predicates, or — in the worst case — marketing a device without the required FDA authorization.

The FDA maintains over 6,500 product codes across 16 medical specialty panels, covering everything from tongue depressors to artificial hearts. This guide shows you how to find the right one, how to read every field in the database, and how to use product codes for strategic regulatory and competitive intelligence.

What Is an FDA Product Code?

An FDA product code is a three-letter alphanumeric identifier assigned to a generic category of medical device. It is not unique to a specific commercial product — it describes a type of device. Every pulse oximeter on the US market, regardless of manufacturer, falls under product code QKQ. Every automated external defibrillator maps to LLZ. Every continuous glucose monitor maps to NFT.

The product code is assigned and maintained by CDRH (Center for Devices and Radiological Health) and, for a subset of devices, by CBER (Center for Biologics Evaluation and Research). Each product code links to a web of regulatory information:

Information Linked to a Product Code	What It Tells You
Device class (I, II, or III)	Risk tier and level of regulatory control
Regulation number (21 CFR section)	The specific classification regulation that defines the device type
Review panel	The medical specialty panel (1 of 16) that oversees the device
Submission type	Required premarket pathway — 510(k), PMA, De Novo, or exempt
510(k) exemption status	Whether a premarket notification is required
GMP exemption status	Whether certain quality system requirements are waived
Special controls	Additional Class II requirements beyond general controls
Third-party review eligibility	Whether an accredited third party can review the 510(k)
Implant and life-sustaining flags	Whether the device is an implant or life-sustaining/supporting
Summary Malfunction Reporting eligibility	Whether the device qualifies for the SMR program
TPLC report	Link to the Total Product Life Cycle report aggregating all submissions, recalls, and adverse events for this device type

Why this matters: When you register your establishment and list your devices with the FDA (21 CFR Part 807), you are required to provide the product code for each device. When you submit a 510(k), De Novo, or PMA, the product code determines which review division receives your file. Product codes are foundational — they are not optional metadata.

Product Code Format and Structure

The Three-Letter CDRH Code

CDRH product codes consist of exactly three alphanumeric characters — for example, QKQ (pulse oximeter), DXN (bone screw), FRN (clinical electronic thermometer), or NFT (continuous glucose monitor). There is no inherent meaning encoded in the three letters. Unlike regulation numbers, where the first three digits identify the medical specialty panel, product code letters do not follow a systematic pattern. QKQ does not tell you "cardiovascular" — you need to look it up.

This means product codes must be memorized or referenced. There is no shortcut to decoding them from their letters alone.

Product Code vs. ORA Import Product Code

An important distinction: the three-letter product code used by CDRH for device classification is different from the seven-character product code used by the FDA's Office of Regulatory Affairs (ORA) for import admissibility review. The ORA product code follows the format XXX--XX and encodes industry, class, subclass, process indicator, and product group. For example, CDRH product code FRN translates to ORA product code 80F--RN in the Product Code Builder.

If you are working on import operations, use the ORA Product Code Builder at fda.gov/industry/import-program-tools/product-codes-and-product-code-builder. For all regulatory classification, premarket submission, and device listing purposes, use the three-letter CDRH product code from the Product Classification Database.

How New Product Codes Are Created

New product codes are created through two primary mechanisms:

1. De Novo classification requests — When the FDA authorizes a De Novo request, it creates a new classification regulation, assigns a new product code, and establishes special controls (for Class II). The De Novo device becomes the first device classified under that new code, and subsequent devices of the same type can use it as a predicate for 510(k).

2. FDA administrative action — The FDA can create new product codes when it determines that an existing product code is too broad and needs to be split, or when a reclassification order creates a new regulatory category.

Between 2010 and 2024, the FDA created an average of approximately 64 new product codes per year across all filing types. De Novo filings accounted for 46.3% of all novel product codes created between 2020 and 2024, surpassing traditional 510(k) filings (37.1%) as the leading source of new codes.

Reference Table: Common Product Codes by Device Category

The following table provides frequently referenced product codes across major device categories. Use these as starting points when searching for your device type:

Product Code	Device Name	Class	Regulation Number	Panel	Submission Type
QKQ	Pulse oximeter	II	870.2700	Cardiovascular	510(k)
DXN	Orthopedic bone screw	II	888.3040	Orthopedic	510(k)
FRN	Clinical electronic thermometer	II	880.2910	General Hospital	510(k)
LLZ	Automated external defibrillator	III	870.5310	Cardiovascular	PMA
NFT	Continuous glucose monitor	II	862.1355	Clinical Chemistry	510(k)
JJX	Pregnancy test kit (home use)	II	866.5940	Immunology	510(k)
QAS	Radiological CAD software	II	892.2080	Radiology	510(k)
MNH	Spinal pedicle screw system	II	888.3080	Orthopedic	510(k)
DQY	Dental implant	II	872.3640	Dental	510(k)
OZO	EEG electrode	II	882.1400	Neurological	510(k)
FLL	Infusion pump	II	880.5725	General Hospital	510(k)
FMF	Examination glove	I	880.6250	General Hospital	510(k) Exempt
ORC	Surgical mesh (hernia)	II	878.3300	General/Plastic Surgery	510(k)
GAL	Suture, absorbable	II	878.4493	General/Plastic Surgery	510(k)
FGB	Endoscope, flexible	II	876.1500	Gastroenterology/Urology	510(k)
DQD	Catheter, intravascular	II	870.1210	Cardiovascular	510(k)
QDD	OTC hearing aid (self-fitting)	II	874.3325	ENT	510(k)
CDQ	Blood glucose test system	II	862.1345	Clinical Chemistry	510(k)
DSG	Powered surgical instrument	I	878.4800	General/Plastic Surgery	510(k) Exempt
EAS	Elastic bandage	I	880.5075	General Hospital	510(k) Exempt

This table is illustrative, not exhaustive. Always verify the current classification in the Product Classification Database, as product codes can be reclassified.

Product Codes, Regulation Numbers, and Device Classes: The Relationship

Understanding how these three concepts relate is essential for navigating the FDA system. They are linked but distinct.

The Hierarchy

Medical Specialty Panel (16 panels)
  └── 21 CFR Part (e.g., Part 870 — Cardiovascular)
        └── Regulation Number (e.g., 870.2700 — Oximeter)
              └── Product Code(s) (e.g., QKQ, DPZ, OLK, MUD)
                    └── Device Class (I, II, or III)

A single regulation number can map to multiple product codes, each describing a different variant of the device type with potentially different intended uses, device classes, or exemption statuses.

Worked Example: Regulation Number 870.2700

Regulation 21 CFR 870.2700 covers "Oximeter." But there are multiple product codes under this single regulation:

Product Code	Device Name	Class	Submission Type
DPZ	Oximeter	II	510(k)
QKQ	Pulse oximeter	II	510(k)
OLK	Pulse oximeter for over-the-counter use	II	510(k)
QCE	Cutaneous oxygen monitor	II	510(k)

All share regulation number 870.2700, but they describe different intended uses. Product code QKQ is for prescription-use pulse oximeters. Product code OLK is for over-the-counter pulse oximeters. Choosing the wrong one can route your submission to the wrong review team.

Regulation Number Format

Regulation numbers follow the pattern 8XX.XXXX:

Component	Meaning	Example
First three digits	21 CFR Part number, identifying the medical specialty panel	870 = Cardiovascular
Digits after the decimal	Specific device classification regulation	2700 = Oximeter

The regulation text (found in the CFR or at ecfr.gov) provides the official device description, intended use, classification, and — for Class I and II devices — whether the device is exempt from 510(k) and/or GMP requirements.

Practical tip: Always search the Product Classification Database by regulation number in addition to keyword searches. A single regulation number can have dozens of associated product codes with subtly different intended uses. There are approximately 1,700 regulation numbers mapped to over 6,500 product codes.

The 16 Medical Specialty Panels

The FDA organizes medical devices into 16 medical specialty panels, each corresponding to a Part of 21 CFR. These panels determine which review division evaluates your submission. Every product code belongs to exactly one panel.

Panel	21 CFR Part	Two-Letter Code	Example Product Codes
Anesthesiology	868	AN	BZD (Ventilator, continuous, facility use), BSZ (Anesthesia conduction kit)
Cardiovascular	870	CV	QKQ (Pulse oximeter), LLZ (Automated external defibrillator), DQD (Catheter, intravascular)
Clinical Chemistry	862	CH	NFT (Continuous glucose monitor), CDQ (Blood glucose test system), JJE (Cholesterol test system)
Dental	872	DE	DQY (Dental implant), EID (Orthodontic bracket), EOQ (Dental cement)
Ear, Nose, and Throat	874	EN	QDD (OTC hearing aid, self-fitting), MRC (Cochlear implant system), KLW (Nasal splint)
Gastroenterology and Urology	876	GU	FGB (Endoscope, flexible), FEA (Urological catheter), LHN (Lithotripter)
General and Plastic Surgery	878	SU	ORC (Surgical mesh, hernia), GAL (Suture, absorbable), FZP (Wound closure strip)
General Hospital	880	HO	FMF (Examination glove), FLL (Infusion pump), FRN (Clinical electronic thermometer)
Hematology	864	HE	GGN (Blood cell counter), JHS (Coagulation analyzer), KDI (Platelet aggregation system)
Immunology	866	IM	JJX (Pregnancy test kit, home use), BLK (Blood grouping reagent), LAR (Allergy test kit)
Microbiology	866	MI	JOT (Culture medium), JQP (Sensitivity disc), KMC (Staining kit)
Neurological	882	NE	OZO (EEG electrode), GWF (Neurostimulator, implantable), PCC (Cranial electrotherapy stimulator)
Obstetrical and Gynecological	884	OB	HGO (Electronic fetal monitor), HBD (Intrauterine device), HFC (Cervical dilator)
Ophthalmic	886	OP	MRC (Contact lens, daily wear), HQF (Intraocular lens), HJO (Retinoscope)
Orthopedic	888	OR	DXN (Bone screw), MNH (Pedicle screw system), NKB (Hip prosthesis)
Physical Medicine	890	PM	IOR (Powered wheelchair), IYN (Ultrasonic diathermy), IYO (Continuous passive motion device)
Radiology	892	RA	IZL (X-ray system, general purpose), LNH (MRI system), QAS (Radiological CAD software)

Note: Hematology and Pathology share 21 CFR Part 864, and Immunology and Microbiology share Part 866. The two-letter panel codes shown above are used in the Product Classification Database and review division assignments.

How to Search the Product Classification Database

The FDA Product Classification Database is publicly available at accessdata.fda.gov/scripts/cdrh/cfdocs/cfPCD/classification.cfm. It is updated every Sunday. Here is how to search it effectively.

Step 1 — Open the Database

Navigate to the URL above. You will see a search form with multiple fields. Most users only need the "Device" keyword field for initial searches, but the advanced filters are powerful and underused.

Step 2 — Enter a Keyword Search

Type a generic, clinical term for your device in the "Device" field. Use the FDA's language, not your marketing name.

Instead of Searching...	Search For...	Why
Masimo Rad-97	pulse oximeter	Database uses generic device types, not brand names
Smart blood pressure cuff with app	sphygmomanometer	Use the clinical/regulatory term
AI tumor detection software	computer aided detection	Use the FDA's established terminology for the function
Wireless glucose patch	glucose monitor	Focus on function, not form factor
Surgical robot	powered surgical instrument	The database classifies by function, not by marketing category

Step 3 — Review the Results List

The search returns a table of matching product codes. Each row shows:

Column	Description
Device	Short name of the device type
Product Code	The three-letter code
Device Class	1, 2, 3, U (unclassified), or N (not classified)
Regulation Number	The 21 CFR section
Submission Type	Required premarket pathway

Do not stop at the first matching result. Scan all results to identify every product code that could potentially apply to your device.

Step 4 — Click Into the Product Code Detail Page

Clicking a product code opens its detail page, which contains the full regulatory profile for that device type. Here is what each field means:

Field	What It Tells You	Example (QKQ)
Device	Full device name	Pulse oximeter
Product Code	Three-letter code	QKQ
Definition	Expanded description of the device type	Describes what a pulse oximeter does
Device Class	Regulatory risk tier	2 (Class II)
Regulation Number	21 CFR classification regulation	870.2700
Submission Type	Required premarket pathway	510(k)
Review Panel	Medical specialty panel	Cardiovascular
GMP Exempt?	Whether quality system exemption applies	No
510(k) Exempt?	Whether premarket notification is waived	No
Implanted Device?	Whether FDA considers this an implant	No
Life-Sustain/Support?	Whether the device is life-sustaining or life-supporting	No
Third Party Review	Whether an accredited third party can review the 510(k)	Not eligible (for QKQ)
SMR Eligible?	Summary Malfunction Reporting eligibility	Ineligible
TPLC Product Code Report	Link to the Total Product Life Cycle report	Links to all 510(k)s, PMAs, recalls, and adverse events under QKQ
Recognized Consensus Standards	Applicable standards	ISO 80601-2-61, IEC 60601-1, etc.
Special Controls / Guidance	Links to applicable guidance documents	Device-specific FDA guidance

Step 5 — Read the Regulation Text

Click through to the actual 21 CFR regulation text at ecfr.gov. The regulation defines the device type's intended use and scope. Your device must fall within this scope for the product code to apply. If the regulation describes a "pulse oximeter intended for use in clinical settings" and your device is intended for OTC home use, you may need a different product code (in this case, OLK).

Step 6 — Use the TPLC Report

The Total Product Life Cycle (TPLC) report, linked from the product code detail page, is one of the most powerful and most overlooked research tools in the FDA system. It aggregates:

• Every 510(k) clearance, PMA approval, De Novo authorization, and HDE under the product code
• All recall events
• All adverse event reports (MAUDE data)
• All compliance actions

This gives you a complete picture of the product code's regulatory history — which companies have received clearance, what predicates they used, and whether the device type has a history of safety signals.

Step 7 — Use Advanced Search Filters

The database offers several filters beyond keyword search:

Filter	Use Case
Product Code	Direct lookup if you already know the code (e.g., from a competitor's 510(k) summary)
Regulation Number	See all product codes under one regulation — critical because one regulation often maps to multiple codes
Review Panel	Narrow results to a specific medical specialty
Submission Type	Filter to see only 510(k) exempt, PMA, or other specific pathway types
Device Class	Filter by class to find all Class III or Class I devices in a panel
Implanted Device	Find only implantable device types
Life-Sustain/Support	Find life-sustaining or life-supporting device types
Third Party Eligible	Identify devices eligible for faster third-party 510(k) review
SMR Eligible	Check Summary Malfunction Reporting eligibility

Practical tip: When researching a device type, always search by regulation number to see the complete universe of product codes under that regulation. Some regulation numbers have more than 50 associated product codes, each with subtly different intended uses.

Worked Example: Classifying a Blood Pressure Monitor

To make the search process concrete, here is a complete walkthrough for looking up the product code for a home-use digital blood pressure monitor.

1. Open the database. Navigate to accessdata.fda.gov/scripts/cdrh/cfdocs/cfPCD/classification.cfm.

2. Enter a keyword search. Type "sphygmomanometer" in the "Device" field and click "Search." Using the clinical term rather than "blood pressure monitor" or "blood pressure cuff" yields more precise results.

3. Review the results. The database returns multiple product codes:

Product Code	Device Name	Class	Regulation Number	Submission Type
DXN	Sphygmomanometer, electronic, automatic	II	870.1130	510(k)
DSW	Sphygmomanometer, mercury	I	870.1100	510(k) Exempt
DXO	Sphygmomanometer, aneroid	II	870.1120	510(k)

4. Note the differences. A mercury sphygmomanometer (DSW) is Class I and 510(k) exempt. An electronic automatic blood pressure monitor (DXN) is Class II and requires a 510(k). If you are building an electronic home-use device, DXN is your likely product code — not DSW, even though both measure blood pressure.

5. Click into DXN. The product code detail page reveals:

• Device Class: 2
• Regulation Number: 870.1130
• Submission Type: 510(k)
• Review Panel: Cardiovascular
• GMP Exempt?: No
• Third Party Review: Third Party Eligible

6. Read the regulation text. Navigate to 21 CFR 870.1130 to confirm the regulation covers your device's intended use. The regulation describes an "electronic, automatic sphygmomanometer" — confirming this covers digital blood pressure monitors.

7. Check the TPLC report. Click the TPLC link to see all devices cleared under DXN. You will find hundreds of cleared 510(k) devices from major manufacturers, confirming this is an active product code with extensive predicate history.

8. Note the third-party eligibility. DXN is eligible for third-party review, meaning you can use an FDA-accredited third-party organization to review your 510(k) instead of waiting for FDA review. This can significantly reduce review time.

This entire search-to-determination process took under 30 minutes. For well-characterized device types like blood pressure monitors, the product code lookup is straightforward. For novel devices, expect to invest more time and potentially use a Pre-Submission or 513(g).

Worked Example: Looking Up a Novel AI/ML Software Device

For contrast, here is how the process works for a less straightforward device — a machine learning algorithm that analyzes retinal images to detect diabetic retinopathy.

1. Search by function. Type "computer aided" in the Device field. This returns several product codes:

Product Code	Device Name	Class	Panel
QAS	Radiological computer-assisted diagnostic software	II	Radiology
QBS	Radiological computer-assisted triage and notification software	II	Radiology
QDQ	Ophthalmic image analyzer	II	Ophthalmic
PIB	Retinal camera	II	Ophthalmic

2. Evaluate candidates. Product code QAS covers radiological CAD software, but your device analyzes retinal images, not radiological images. Product code QDQ covers ophthalmic image analyzers, which is closer. But your specific device — an AI that detects diabetic retinopathy — may have a De Novo-created product code.

3. Search the De Novo database. Search for "diabetic retinopathy" in the De Novo database. You may find a specific De Novo authorization (such as DEN180001 for the IDx-DR system) that created a product code specifically for autonomous AI diagnostic systems for diabetic retinopathy.

4. Compare product codes. The De Novo-created product code may have specific special controls tailored to autonomous AI diagnostic software for retinal disease, while QDQ has broader special controls for ophthalmic image analyzers generally.

5. Select the best fit. If a De Novo product code exists for your specific device type, it is usually the better choice because:

• The special controls were designed for your technology
• The De Novo device serves as a predicate for your 510(k)
• The review division is already familiar with the technology

6. If no code fits, engage the FDA. If none of the existing product codes accurately describe your device, consider a Pre-Submission to discuss classification, or prepare for a De Novo submission that will create a new product code.

This example illustrates why novel AI/ML devices often take significantly more effort to classify than well-established device types. The product code system is continuously expanding to accommodate new technologies, but there is always a lag between innovation and classification.

How to Determine If Your Device Is 510(k) Exempt

One of the most important pieces of information a product code provides is whether a 510(k) premarket notification is required. Here is how to check.

Check the Submission Type Field

On the product code detail page, look at the "Submission Type" field:

Submission Type	What It Means
510(k) Exempt	No premarket notification required (subject to limitations)
510(k)	A 510(k) premarket notification must be submitted and cleared before marketing
PMA	Premarket Approval application required
De Novo	De Novo classification request is the expected pathway
HDE	Humanitarian Device Exemption pathway
Contact ODE	Contact the Office of Device Evaluation for guidance — classification is ambiguous or in transition

Understanding Exemption Limitations

A 510(k) exemption is not unconditional. Even if your product code is listed as "510(k) Exempt," the exemption does not apply if your specific device meets any of these conditions:

1. Different intended use — Your device has an intended use that differs from the use described in the classification regulation.
2. Different fundamental scientific technology — Your device operates using a fundamentally different technology than what the classification regulation contemplated. For example, a digitally connected or AI-enabled version of a traditionally analog exempt device may not qualify for the exemption.
3. Substantial importance in preventing impairment of human health + potential unreasonable risk — Your device is used for a purpose of substantial importance in preventing impairment of human health and presents a potential unreasonable risk of illness or injury.

These limitations are codified in the ".9" sections of each device classification regulation chapter (e.g., 21 CFR 862.9, 21 CFR 864.9, through 21 CFR 892.9).

Practical tip: Even if your device qualifies for 510(k) exemption, you must still comply with all other applicable requirements: establishment registration, device listing, labeling (21 CFR Part 801), Medical Device Reporting (21 CFR Part 803), and quality system requirements (21 CFR Part 820 / QMSR) unless also GMP-exempt. Document your exemption determination in your regulatory file so you can demonstrate due diligence during FDA inspections.

Exemption Statistics

Class	Approximate Device Types	510(k) Exempt
Class I	~780	~740 (~95% exempt)
Class II	~750	A small subset — certain dental devices, powered exercise equipment, adjustable hospital beds, and others
Class III	~170	None — all Class III devices require PMA or equivalent

Product Codes and Special Controls

Every Class II device is subject to special controls in addition to general controls. Special controls are defined at the product code level and can include:

• FDA guidance documents — Device-specific guidance describing performance expectations, testing requirements, and labeling recommendations
• Recognized consensus standards — Standards (e.g., ISO, IEC, ASTM) recognized by the FDA as relevant to the device type
• Post-market surveillance requirements — Specific post-market data collection obligations
• Patient registries — Required participation in device tracking registries
• Special labeling requirements — Mandatory warnings, contraindications, or specific use instructions

Types of Special Controls by Device Category

Different device categories have different types of special controls. Here are examples of how special controls vary by product code:

Product Code	Device	Special Controls Include
QKQ	Pulse oximeter	Performance standards (ISO 80601-2-61), clinical testing requirements, accuracy specifications, motion artifact tolerance
QAS	Radiological CAD software	Algorithm performance testing, clinical validation, labeling requirements for algorithm limitations, cybersecurity documentation
ORC	Surgical mesh (hernia)	Biocompatibility testing, mechanical testing, animal performance data, specific labeling including material composition
NFT	Continuous glucose monitor	Accuracy requirements (MARD), sensor longevity testing, alarm function validation, cybersecurity, interoperability testing
QDD	OTC hearing aid (self-fitting)	Electroacoustic performance, max sound output limits, self-fitting validation, labeling including age/hearing loss limitations

Where to Find Special Controls for Your Product Code

1. Product Classification Database — The detail page for your product code links to applicable special controls and guidance documents when they exist.
2. 21 CFR regulation text — The classification regulation for Class II devices references the applicable special controls. For example, 21 CFR 870.2700(b) identifies the special controls for pulse oximeters.
3. De Novo authorization orders — For product codes created through De Novo, the special controls are defined in the De Novo authorization order itself. These are available in the De Novo database at accessdata.fda.gov/scripts/cdrh/cfdocs/cfPMN/denovo.cfm.
4. FDA guidance documents database — Search for device-specific guidance at fda.gov/medical-devices/guidance-documents-medical-devices-and-radiation-emitting-products.
5. FDA recognized consensus standards database — Search for standards applicable to your product code at accessdata.fda.gov/scripts/cdrh/cfdocs/cfStandards/search.cfm. You can search by product code to see all recognized standards relevant to your device type.

Practical tip: Failure to identify and address all applicable special controls is one of the most common reasons for 510(k) deficiency letters. Before submitting your 510(k), verify that you have addressed every special control listed for your product code — including consensus standards, guidance documents, and any specific labeling or post-market requirements. For De Novo-created product codes, the special controls are often more specific and prescriptive than those for traditional product codes, because they were designed for a specific device type rather than a broad device category.

New Product Codes from De Novo Authorizations

When the FDA grants a De Novo classification request, it creates a new regulatory framework: a new product code, a new regulation number (or assignment under an existing regulation), and — for Class II devices — a set of special controls. The De Novo device becomes the first device classified under that product code, and all subsequent devices of the same type can use it as a 510(k) predicate.

Why De Novo Product Codes Matter

De Novo-created product codes are critical for manufacturers of novel devices because they:

• Open a 510(k) pathway where none previously existed — once a De Novo product code exists, competitors can file 510(k)s using the De Novo device as a predicate
• Define the special controls that all future devices under that code must meet
• Establish testing expectations — the De Novo authorization documents the performance testing the FDA accepted, creating a benchmark for subsequent 510(k) submissions

How to Find De Novo-Created Product Codes

Search the De Novo database at accessdata.fda.gov/scripts/cdrh/cfdocs/cfPMN/denovo.cfm. Each De Novo entry shows the product code that was created. De Novo numbers follow the format DENYYNNNN, where YY is the two-digit calendar year and NNNN is the sequential request number (e.g., DEN250001 is the first De Novo received in calendar year 2025).

De Novo Product Code Trends

Period	Avg. Novel Product Codes/Year	De Novo Share
2010-2014	~55	~25%
2015-2019	~60	~35%
2020-2024	~70	~46%

The De Novo pathway has become the dominant source of new product codes, driven by digital health, AI/ML-enabled software, and novel diagnostic technologies that do not fit existing classification categories.

Notable De Novo-Created Product Codes

Several De Novo authorizations have created product codes that opened entirely new device categories:

De Novo	Product Code	Device Type	Class	Year	Significance
DEN180001	PIB	Autonomous AI diagnostic for diabetic retinopathy	II	2018	First fully autonomous AI diagnostic device authorized by FDA
DEN200043	QMT	COVID-19 OTC home test	II	2020	Enabled the rapid expansion of consumer COVID testing
DEN220032	QDD	OTC hearing aid, self-fitting	II	2022	Established the OTC hearing aid category
DEN210040	QRZ	Non-prescription software for CBT-based insomnia treatment	II	2021	Established prescription digital therapeutics product code

Each of these De Novo authorizations established special controls that now apply to all future devices of the same type. The special controls documented in the De Novo order serve as the testing and performance blueprint for subsequent 510(k) submissions under the new product code.

Practical tip: When preparing a 510(k) for a device type created through De Novo, obtain the De Novo decision summary and authorization order. These documents detail the specific testing the FDA accepted, the special controls established, and the performance benchmarks your device must meet. They are publicly available in the De Novo database.

Strategic Value of Novel Product Codes

Research published in npj Health Systems has demonstrated that acquiring novel product codes through De Novo confers a competitive advantage to medical device manufacturers. Companies that obtain novel product codes effectively establish the regulatory framework for their device category, giving them first-mover advantage and forcing competitors to use their device as a predicate. This structural advantage persists as long as the product code remains the appropriate classification for the device type.

Multiple Product Codes for Multi-Function Devices

Many modern medical devices perform more than one function. A multi-parameter patient monitor measures ECG, SpO2, blood pressure, and temperature — at least four separate device functions, each with its own product code. How do you handle this?

The Primary Product Code Rule

When a device spans multiple product codes, the FDA requires you to designate a primary product code for your premarket submission. The rules for selecting it:

1. Choose the product code corresponding to the highest regulatory class. If one function is Class II and another is Class III, the Class III product code is primary.
2. If classes are equal, choose the product code corresponding to the most relevant technology — the function that represents the device's principal intended use.
3. Your 510(k) or PMA must address all functions. The other product codes are listed as secondary, and you must demonstrate that each function meets its applicable classification requirements.

Practical Implications

Scenario	Primary Code Selection	Submission Approach
Patient monitor (ECG + SpO2 + NIBP + Temp)	The function with the highest class or most significant clinical use	Single 510(k) addressing all product codes
Diagnostic software with multiple analytical modules	The module with the highest class or most clinically significant output	Single De Novo or 510(k) with all modules documented
Combination imaging system (X-ray + fluoroscopy)	The function with the highest class	Single 510(k) or PMA covering both modalities

Practical tip: When multiple product codes apply, the FDA routes your submission to the review division associated with the primary product code. If you select the wrong primary code, your submission may go to a division without expertise in one of the key functions. Confirm the primary product code with the FDA through a Pre-Submission if there is any ambiguity.

Accessory Devices and Product Code Classification

Medical device accessories are finished devices intended to support, supplement, or augment the performance of one or more "parent" devices. Accessories have their own product codes — they are not automatically classified under the parent device's code.

The 2017 Risk-Based Accessory Classification Policy

Historically, the FDA classified accessories in the same regulatory class as their parent device, regardless of the accessory's actual risk. The FDA Reauthorization Act of 2017 (FDARA) changed this. Under the current policy, accessories are classified based on their own risk profile — not the parent device's class.

This means a simple, low-risk accessory to a Class III device (such as a carrying case for an implantable pulse generator) may be independently classified as Class I. The classification is based on the level of regulatory controls necessary to provide reasonable assurance of the accessory's safety and effectiveness, notwithstanding the classification of the parent device.

Key Definitions

Term	Definition
Accessory	A finished device intended to support, supplement, and/or augment the performance of one or more parent devices
Parent device	A finished device whose performance is supported, supplemented, or augmented by one or more accessories
Component	Raw materials, substances, parts, software, or assemblies intended as part of a finished device — components are not separately classified
Finished device	Any device or accessory suitable for use or capable of functioning

Practical Implications for Product Codes

• Accessories have their own product codes. Do not use the parent device's product code for an accessory. Search the Product Classification Database for the accessory's specific device type.
• Accessories may be in a lower class than the parent. A face mask accessory to a Class III ventilator system could be classified as Class I or Class II based on its own risk profile.
• Each accessory requires its own device listing. When registering your establishment and listing devices, list each accessory with its own product code.
• UDI applies to accessories. Every finished device and accessory must bear a Unique Device Identifier on its label and package. Components and spare parts are exempt from UDI requirements.
• CDRH is actively seeking to reclassify accessories. The FDA has solicited public comment on identifying accessories suitable for distinct classification as Class I devices, potentially reducing regulatory burden for many currently over-classified accessories.

Practical tip: If you manufacture an accessory that is currently classified in the same class as its parent device, evaluate whether the accessory's own risk profile warrants a lower classification. If so, you may be able to petition for reclassification or submit a De Novo to establish a new, lower-class product code for the accessory type.

Product Codes for Software as a Medical Device (SaMD) and Digital Health

Software-based medical devices have their own product codes, but the classification landscape is more complex than for traditional hardware devices due to the rapidly evolving regulatory framework for digital health.

SaMD Product Code Categories

Software as a Medical Device (SaMD) — software intended to be used for one or more medical purposes that performs those purposes without being part of a hardware medical device — is classified using the same risk-based system as traditional devices. The FDA has created numerous product codes specifically for software functions:

Product Code	Device Type	Class	Panel	Notes
QAS	Radiological computer-assisted diagnostic software	II	Radiology	Triage using preset inputs
QBS	Radiological computer-assisted triage and notification software	II	Radiology	Detects and diagnoses non-cancerous pathology
QFM	Radiology AI-based triage and prioritization software	II	Radiology	ML-based, requires >95% AUC performance
QDQ	Machine learning-based breast cancer detection/diagnosis	II	Radiology	Breast-specific cancer detection
POK	Computer-assisted characterization of lesions suspicious for cancer	II	Radiology	Characterizes but does not detect or triage
MYN	Radiological computer-assisted detection	II	Radiology	Detects and marks suspicious lesions
QIH	AI-based image processing for non-cancer pathologies	II	Radiology	Non-cancer AI image processing
QRZ	Prescription digital therapeutic for insomnia (CBT-based)	II	Neurological	Created via De Novo

Many SaMD product codes were created through De Novo authorizations because no predicate devices existed. If your software device does not fit an existing product code, expect to use the De Novo pathway, which will create a new product code for your device type.

Clinical Decision Support (CDS) Software — When No Product Code Is Needed

Not all clinical software is regulated as a medical device. The 21st Century Cures Act (Section 3060) excludes certain clinical decision support (CDS) functions from the definition of a "device." Software that meets all four statutory criteria is not a medical device and does not need a product code:

1. Not intended to acquire, process, or analyze a medical image, signal, or specimen — The software does not directly interface with medical data acquisition.
2. Intended for the purpose of displaying, analyzing, or printing medical information — The software presents information to the healthcare professional.
3. Intended for use by a healthcare professional — The end user is an HCP, not a patient or caregiver.
4. Intended to enable the HCP to independently review the basis for the recommendation — The software does not replace clinical judgment; it provides the underlying data so the HCP can evaluate the recommendation.

If your software meets all four criteria, it is CDS and is not regulated as a device. If it fails any one criterion — for example, it is intended for patients rather than HCPs, or it does not allow the user to independently review the basis for the recommendation — it is SaMD and requires classification and potentially a product code.

Practical tip: The boundary between exempt CDS and regulated SaMD is one of the most actively litigated areas in FDA digital health regulation. The FDA updated its CDS guidance in January 2026, taking a more deregulatory posture toward certain lower-risk HCP-facing software functions. Document your CDS determination carefully, including an analysis of how your software meets each of the four statutory criteria. If there is any doubt, consider a Pre-Submission to confirm the FDA's position before investing in development.

SaMD Classification Gaps

There are currently no FDA product codes for certain categories of AI/ML software, including radiology AI that can find, highlight, and diagnose single non-cancerous pathologies, or software that detects and diagnoses multiple pathologies simultaneously. If your software falls into one of these gaps, a De Novo submission is the expected pathway and will create a new product code for the device type.

Product Codes for In Vitro Diagnostic (IVD) Devices and CLIA Waivers

In vitro diagnostic devices have their own product codes within the FDA classification system, but IVDs add an additional layer of complexity: CLIA (Clinical Laboratory Improvement Amendments) complexity categorization.

How IVD Product Codes Work

IVD product codes follow the same three-letter format as all CDRH product codes and are found in the same Product Classification Database. IVDs are organized under several medical specialty panels, primarily:

Panel	21 CFR Part	IVD Examples
Clinical Chemistry	862	Blood glucose test systems (CDQ), cholesterol tests (JJE), continuous glucose monitors (NFT)
Hematology	864	Blood cell counters (GGN), coagulation analyzers (JHS)
Immunology	866	Pregnancy test kits (JJX), HIV test kits, blood grouping reagents (BLK)
Microbiology	866	Culture media (JOT), sensitivity discs (JQP), rapid diagnostic tests
Toxicology	862	Drug screening tests, therapeutic drug monitoring assays

The CLIA Connection

Beyond the FDA product code and device class, every IVD marketed in the United States receives a CLIA complexity categorization that determines where the test can be performed:

CLIA Category	Where the Test Can Run	Regulatory Implication
Waived	Any CLIA-certified facility, including physician offices, pharmacies, and home use	Lowest operational requirements; broadest market access
Moderate complexity	Laboratories with appropriate CLIA certificates	Requires trained laboratory personnel
High complexity	Laboratories with full CLIA certification	Most restrictive; requires highly trained personnel

How CLIA Categorization Relates to Product Codes

CLIA categorization is determined after FDA clearance or approval — it is not a field in the Product Classification Database. However, the product code drives which CLIA criteria apply:

• Tests cleared or approved for home use are automatically categorized as waived.
• All other tests are categorized as moderate or high complexity based on a seven-criterion scoring system (42 CFR 493.17). Each criterion is scored 1-3, and tests scoring 12 or less are moderate complexity; above 12 are high complexity.
• Manufacturers can request CLIA Waiver by Application (CW) to reclassify a moderate-complexity test as waived. This requires a separate FDA submission demonstrating that the test can be performed accurately by untrained users in non-laboratory settings.

CLIA Waiver Strategy and Product Codes

Many IVD manufacturers pursue dual 510(k) and CLIA waiver applications. The product code drives the 510(k) classification, while the CLIA waiver application addresses the testing environment:

1. Obtain your product code from the Product Classification Database (e.g., JJX for a home-use pregnancy test).
2. Submit your 510(k) under that product code.
3. If your test is not automatically waived (i.e., not intended for home use), submit a CLIA Waiver by Application if you want waived categorization.
4. Check the CLIA Database at accessdata.fda.gov/scripts/cdrh/cfdocs/cfCLIA/search.cfm to see which tests under your product code have been categorized as waived.

Practical tip: CLIA waiver can dramatically expand your market by enabling test use in physician offices, pharmacies, and retail clinics — settings where moderate- or high-complexity tests cannot be performed. If your IVD is intended for point-of-care or near-patient testing, plan your CLIA waiver strategy from the start of product development. The CLIA waiver study requirements (demonstrating accurate performance by untrained users) should be built into your clinical validation plan alongside your 510(k) testing.

Product Codes for Combination Products

Combination products — products that combine a device with a drug, biologic, or both — present unique product code challenges. The device component of a combination product has its own product code, but the regulatory pathway is determined by the product's primary mode of action (PMOA), not by the device product code alone.

How Product Codes Apply to Combination Products

The FDA maintains "device product codes (procodes)" specifically for the device constituent parts of combination products. These procodes are separate from the standard CDRH product codes and are used to identify and track the device component within the combination product framework.

Combination Product Type	Lead Center	Product Code Source	Example
Device-led (PMOA is the device)	CDRH	Standard CDRH product code	Drug-eluting stent — device product code determines the premarket pathway
Drug-led (PMOA is the drug)	CDER	Device procode assigned to the device constituent	Prefilled syringe with drug — device component tracked via procode
Biologic-led (PMOA is the biologic)	CBER	Device procode assigned to the device constituent	Cell therapy delivery kit — device component tracked via procode

Finding Combination Product Device Procodes

• FDA Combination Products page: The FDA publishes a list of device product codes for device constituent parts of ANDA/NDA/BLA combination products at fda.gov/combination-products/device-product-codes-procodes-device-constituent-parts-andandabla-combination-products.
• Product Classification Database: For device-led combination products, use the standard Product Classification Database. The device product code drives the premarket pathway (510(k), PMA, or De Novo).
• Office of Combination Products (OCP): If you are uncertain whether your product is a combination product or which center has jurisdiction, submit a Request for Designation (RFD) to the OCP. The OCP will determine the lead center and the appropriate product code framework.

Practical tip: If your product is a combination product, you need to understand both the device product code (which determines the device-specific regulatory requirements) and the overall combination product pathway (which determines the lead center and primary submission type). A drug-eluting stent is submitted as a PMA to CDRH because the device is the primary mode of action. A prefilled syringe with a drug is submitted as an NDA to CDER because the drug is the primary mode of action — even though the syringe has its own device product code and must meet device-specific requirements.

Unclassified and Not-Classified Devices: Product Code Strategy

The Product Classification Database contains approximately 851 product codes with a device class of "U" (unclassified) and a smaller number with "N" (not classified). Understanding these designations is important for regulatory strategy.

Unclassified (Class U) Devices

Unclassified devices are pre-amendment devices — device types that existed before May 28, 1976 (the date the Medical Device Amendments were enacted) but have never been formally classified into Class I, II, or III. These product codes have no regulation number and no formal classification.

Regulatory strategy for unclassified devices:

• 510(k) is generally required. Until the FDA formally classifies the device type, marketing new devices under an unclassified product code requires a 510(k) premarket notification.
• Enforcement discretion may apply. For some unclassified device types, the FDA has stated on the product classification page that enforcement discretion applies — meaning the FDA does not intend to enforce the 510(k) requirement. Check the product code detail page for any enforcement discretion language.
• Future classification is possible. The FDA can classify these devices at any time through a rulemaking process. Once classified, the device may become 510(k) exempt (if Class I), continue to require 510(k) (if Class II), or require PMA (if Class III).
• Monitor for classification actions. Subscribe to Federal Register notices for your product code's medical specialty panel to be notified when the FDA proposes to classify or reclassify device types.

Not Classified (Class N) Devices

A class of "N" means the device type has not been assigned to any class. This is rare and typically indicates:

• A pending classification action
• A recently created product code where the formal classification process is not yet complete
• A transitional state during reclassification

For Class N devices, contact the FDA (DICE or through a Pre-Submission) to determine the current regulatory expectations before attempting to market.

Practical tip: If your device falls under an unclassified product code, do not assume that the lack of formal classification means no regulatory requirements apply. At minimum, establishment registration, device listing, labeling requirements, medical device reporting, and quality system requirements apply to all marketed medical devices regardless of classification status. The only question for unclassified devices is whether a premarket submission (510(k)) is required — and the default answer is yes, unless the FDA has specifically stated otherwise through enforcement discretion.

Product Codes and International Device Nomenclature

The FDA's three-letter product code system is unique to the United States. Other regulatory jurisdictions use different nomenclature systems to categorize medical devices. Understanding these relationships is important for manufacturers marketing devices globally.

Comparison of Global Nomenclature Systems

System	Jurisdiction	Format	Maintained By	Relationship to FDA Product Codes
FDA Product Code	United States	Three alphanumeric letters (e.g., QKQ)	CDRH / FDA	Primary system — no direct mapping to other systems
GMDN (Global Medical Device Nomenclature)	International (used by FDA in GUDID, TGA, and others)	Five-digit numeric code	GMDN Agency	Required in GUDID alongside the product code; describes the device at a more granular level than the product code
EMDN (European Medical Device Nomenclature)	European Union (EU MDR/IVDR)	Alphanumeric hierarchical code	European Commission (based on Italian CND codes)	No direct mapping to FDA product codes; broader terms than GMDN
UMDNS (Universal Medical Device Nomenclature System)	International	Five-digit numeric code	ECRI Institute	Predates GMDN; less commonly used today

GMDN and FDA Product Codes

The GMDN code is a required data element in the Global Unique Device Identification Database (GUDID). When you register your device's UDI in GUDID, you must provide both the FDA product code and the GMDN code. Effective December 17, 2024, the FDA deprecated the use of four-letter FDA Preferred Terms as an alternative entry for the GMDN field in GUDID — manufacturers must now use five-digit GMDN codes.

Key differences between FDA product codes and GMDN codes:

• Granularity: GMDN codes are generally more granular than FDA product codes. Multiple GMDN codes may map to a single FDA product code.
• Purpose: FDA product codes drive regulatory classification and premarket pathway determination. GMDN codes are primarily used for device identification and international harmonization.
• Maintenance: FDA product codes are updated weekly in the Product Classification Database. GMDN codes are maintained by the GMDN Agency and require a paid subscription to access the full database.
• No direct cross-reference: There is no official FDA-maintained mapping between product codes and GMDN codes. Manufacturers must determine both independently.

Implications for Global Regulatory Strategy

When preparing regulatory submissions for multiple markets, identify the appropriate device nomenclature code for each jurisdiction early in the process:

1. United States: Determine the FDA product code using the Product Classification Database.
2. European Union: Determine the EMDN code using the EU's EUDAMED database (when fully operational) or the EMDN code list published by the European Commission.
3. International (GUDID/UDI): Determine the GMDN code using the GMDN Agency database.
4. Other markets: Check jurisdiction-specific requirements (e.g., Australia's TGA uses GMDN; Japan's PMDA uses its own nomenclature system).

Practical tip: Do not assume that a device classified as Class II under a specific FDA product code will receive an equivalent classification in Europe or other jurisdictions. Each regulatory system has its own classification rules. The product code, GMDN code, and EU MDR risk class are determined independently based on each jurisdiction's criteria. However, the GMDN code can help international regulators understand your device type, so select it carefully and ensure consistency across your global regulatory filings.

Using Product Codes for Competitive Research

Product codes are powerful tools for competitive intelligence. Because every cleared or approved device is associated with a product code, you can use the code to map the entire competitive landscape for your device type.

Step-by-Step Competitive Research Workflow

1. Identify your product code. Use the Product Classification Database to find the correct three-letter code for your device type.

2. Search the 510(k) database by product code. Go to the 510(k) Premarket Notification database at accessdata.fda.gov/scripts/cdrh/cfdocs/cfPMN/pmn.cfm. Enter your product code in the "Product Code" field. The results show every device cleared under that code, including:

• Applicant name (your competitors)
• Device name
• Decision date
• 510(k) number
• Predicate device(s) — visible in the 510(k) summary

3. Review 510(k) summaries. Many 510(k) summaries are publicly available and disclose the predicate device, intended use, technological characteristics, and performance testing approach. This tells you how competitors positioned their devices and what testing the FDA accepted.

4. Use the TPLC report. Access the TPLC report from the Product Classification Database to see all submissions (510(k), PMA, De Novo, HDE), recalls, and adverse events under your product code. This gives you a complete historical view.

5. Check MAUDE for adverse events. Search the Manufacturer and User Facility Device Experience (MAUDE) database for your product code to identify safety signals, failure modes, and common complaints associated with devices in your category.

6. Search the PMA database. If your product code requires PMA, search the PMA database by product code to see approved devices and their Summaries of Safety and Effectiveness Data (SSEDs).

What Competitive Research Reveals

Data Source	Intelligence Gained
510(k) summaries	Predicate chains, testing strategies, indications for use, technological approaches
PMA SSEDs	Clinical study designs, endpoints, safety/efficacy data benchmarks
De Novo authorization orders	Special controls, performance criteria, testing expectations for novel device types
MAUDE reports	Failure modes, safety signals, common complaints, post-market performance
Recall database	Design weaknesses, manufacturing issues, labeling problems in your device category
TPLC report	Complete regulatory history — submissions, approvals, recalls, and adverse events over time

Using Product Codes for Predicate Selection

One of the most critical uses of product code research is identifying predicate devices for your 510(k) submission. The FDA's guidance on predicate selection recommends choosing predicates that:

• Were cleared under the same product code as your device
• Have a similar intended use
• Use similar technology (same fundamental scientific principles)
• Were cleared using well-established testing methods
• Have no unresolved safety concerns or design-related recalls

How to build a predicate chain using product codes:

1. Search the 510(k) database for your product code
2. Sort results by decision date (most recent first)
3. Download or review the 510(k) summaries of recently cleared devices
4. Note the predicate devices cited in each summary — these form a "predicate chain" tracing back through the device type's clearance history
5. Evaluate each potential predicate for similarity in intended use and technological characteristics
6. Select a predicate that has a clean safety record (check MAUDE and the recall database)

Practical tip: The strongest predicates are recently cleared devices under your exact product code with similar technology and no recall history. Avoid using predicates that have been recalled for design-related issues, as the FDA may question your reliance on a device with a known safety problem. Also avoid "predicate creep" — selecting a predicate that is technically in the same product code but has drifted significantly in technology or intended use from the original classified device type.

Market Landscape Analysis

Beyond regulatory strategy, product codes enable market landscape analysis:

• Count clearances by year to understand market growth and competitive density
• Identify market entrants by reviewing recently cleared 510(k)s under your product code
• Track technology trends by reviewing how the testing approaches described in 510(k) summaries have evolved over time
• Assess safety profile by analyzing MAUDE adverse event trends and recall frequency for your product code
• Evaluate acquisition targets by mapping companies with clearances under specific product codes

The openFDA API for Product Classification Data

For regulatory professionals, data analysts, and software developers who need to query product classification data programmatically, the FDA provides a public API through the openFDA platform.

API Endpoint

The base endpoint is:

https://api.fda.gov/device/classification.json

Query Structure

Queries use the syntax search=field:term. For example, to look up product code QKQ:

https://api.fda.gov/device/classification.json?search=product_code:QKQ

To search by device name:

https://api.fda.gov/device/classification.json?search=device_name:"pulse+oximeter"&limit=10

Available Fields

Field	Description
product_code	The three-letter product code
device_name	Generic device name
device_class	Device class (1, 2, 3, U, N, f)
regulation_number	21 CFR regulation number
medical_specialty	Two-letter panel code (e.g., CV, OR)
medical_specialty_description	Full panel name
submission_type_id	Submission type identifier
definition	Device type description
gmp_exempt_flag	GMP exemption status
implant_flag	Whether the device is an implant
life_sustain_support_flag	Life-sustaining/supporting status
third_party_flag	Third-party review eligibility

Rate Limits and API Key

• Without an API key: 240 requests per minute, 120,000 per day
• With an API key (free registration): higher limits
• Maximum results per query: 1,000 records

Bulk Download

For large-scale analysis, the openFDA platform provides downloadable data files at open.fda.gov/data/downloads/. The product classification dataset is updated weekly.

The bulk download files are provided in JSON format and contain the complete product classification dataset. Each record includes all fields available through the API: product code, device name, device class, regulation number, medical specialty, submission type, exemption flags, and more. This is useful for:

• Building internal classification lookup tools — Import the entire dataset into your QMS or regulatory information management system for offline searching.
• Trend analysis — Analyze all product codes by class, panel, or submission type to identify patterns (e.g., which panels have the most De Novo-created codes, which device types are being reclassified).
• Automated alerting — Compare weekly downloads to detect changes in product code classifications, new codes, or updated exemption statuses.
• Cross-database analysis — Combine product classification data with 510(k), PMA, recall, and adverse event datasets (all available as bulk downloads) for comprehensive regulatory intelligence.

Practical tip: The openFDA API is useful for building internal tools — for instance, a regulatory intelligence dashboard that monitors your product code and related codes for new clearances, recalls, or adverse events. Combine the classification endpoint with the 510(k), PMA, recall, and adverse event endpoints for comprehensive monitoring.

Essential FDA Databases for Product Code Research

The Product Classification Database is your starting point, but effective product code research requires cross-referencing multiple FDA databases. Here is a reference of the most important databases and how they connect to product codes:

Database	URL	Product Code Use	What You Learn
Product Classification	accessdata.fda.gov/scripts/cdrh/cfdocs/cfPCD/classification.cfm	Primary lookup	Classification, regulation number, review panel, exemption status, special controls
510(k) Premarket Notification	accessdata.fda.gov/scripts/cdrh/cfdocs/cfPMN/pmn.cfm	Search by product code	All cleared devices under a code; predicate devices; competitor landscape
PMA	accessdata.fda.gov/scripts/cdrh/cfdocs/cfPMA/pma.cfm	Search by product code	Approved PMA devices; SSEDs; clinical study benchmarks
De Novo	accessdata.fda.gov/scripts/cdrh/cfdocs/cfPMN/denovo.cfm	Search by product code	Newly created product codes; special controls for novel device types
MAUDE (Adverse Events)	accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/search.cfm	Search by product code	Adverse event reports; failure modes; safety signals
Recalls	accessdata.fda.gov/scripts/cdrh/cfdocs/cfRES/res.cfm	Search by product code	Recall history; common defects; design and manufacturing issues
Devices@FDA	accessdata.fda.gov/scripts/cdrh/devicesatfda/	Combined 510(k)/PMA search	Quick lookup of clearances and approvals (limited search fields)
GUDID	accessgudid.nlm.nih.gov	Search by product code	UDI data for commercial products; company names; device identifiers
Recognized Consensus Standards	accessdata.fda.gov/scripts/cdrh/cfdocs/cfStandards/search.cfm	Search by product code	Applicable voluntary consensus standards for your device type
openFDA API	api.fda.gov/device/classification.json	Programmatic access	Batch queries, automated monitoring, data analysis

Each of these databases accepts product code as a search parameter, allowing you to build a comprehensive regulatory and competitive picture around any device type from a single three-letter code.

513(g) Requests: When and How to Request a Classification Determination

When you cannot determine the correct product code for your device — or when you are unsure whether your product is even regulated as a medical device — Section 513(g) of the FD&C Act provides a formal mechanism for obtaining a classification determination from the FDA.

When to Use a 513(g) Request

• You have a new or modified device and cannot determine the correct product code
• Your device could fall under two or more product codes with different regulatory requirements
• You are unsure whether your product meets the definition of a "device" under the FD&C Act (e.g., wellness products, general fitness devices, clinical decision support software)
• You want a written FDA response to anchor your regulatory strategy

What to Include

Component	Description
Cover letter	Identifying information, contact details, and a clear statement of the classification question
Device description	What the device is, its materials, principles of operation, physical characteristics
Intended use	The specific medical or clinical purpose
Indications for use	The disease, condition, or patient population the device addresses
Technological characteristics	Materials, energy sources, software, sensors, and any novel technology
Comparison to existing devices	How your device compares to devices in the candidate product codes you identified
Proposed labeling	Any labels, instructions for use, or marketing materials that clarify the intended use

User Fees (FY2026)

Fee Type	Amount
Standard 513(g) fee	$7,820
Small business 513(g) fee	$3,910

Small businesses must be certified through CDRH's Small Business Determination (SBD) Program to qualify for reduced fees.

Submission Format

The FDA recommends electronic submission through eCopy (CD, DVD, or flash drive) or the Electronic Submission Gateway. The FDA has also enabled voluntary submission through the eSTAR template for 513(g) requests. Include Form FDA 3514 (CDRH Premarket Review Submission Cover Sheet) for proper routing.

Response Timeline and Content

The FDA targets a 60-day response time, though actual turnaround frequently ranges from 60 to 120 days depending on complexity. The response letter will identify:

• Whether the product is a medical device
• The applicable product code and device class
• The required premarket submission type (510(k), PMA, De Novo, exempt)
• Any relevant regulatory requirements

The 513(g) response is advisory and non-binding — it represents the FDA's current position but is not a clearance, approval, or legally binding classification decision.

513(g) vs. Pre-Submission: Which to Use

Factor	513(g)	Pre-Submission (Pre-Sub)
Purpose	Classification determination	Classification, testing strategy, predicate selection, clinical study design, and broader regulatory questions
User fee (FY2026)	$7,820 / $3,910	No user fee
Interaction	Written response only	Written feedback + meeting with review team
Scope	Narrow — what is my product code?	Broad — covers any regulatory question
Best for	Simple classification questions, "is this a medical device?" determinations	Complex devices, novel technologies, devices needing testing guidance

Practical tip: If your only question is "what is my product code?", a 513(g) is the right tool. If you have broader questions about testing, predicates, or regulatory strategy, use a Pre-Submission — it is free and provides interactive feedback. Many regulatory professionals default to the Pre-Sub because it addresses classification alongside other critical questions.

The Informal Alternative: DICE

Before committing to a formal 513(g), consider the FDA's Division of Industry and Consumer Education (DICE). DICE accepts email inquiries at DICE@fda.hhs.gov and DeviceDetermination@fda.hhs.gov for straightforward classification questions. Phone support is available at 1-800-638-2041 or 301-796-7100 (9:00 AM to 12:30 PM and 1:00 PM to 4:30 PM ET).

DICE typically responds within 7 business days for simple inquiries. The response is informal and explicitly non-binding, but it is free and can resolve straightforward classification questions without a formal submission.

Common Product Code Lookup Mistakes

Mistake 1: Searching by Brand Name

The Product Classification Database catalogs generic device types, not commercial products. Searching "Dexcom G7" returns nothing. Searching "continuous glucose monitor" returns NFT and related codes. Always use clinical or regulatory terminology.

Mistake 2: Being Too Specific

Searching "wireless Bluetooth-enabled digital blood pressure cuff with smartphone app integration" returns nothing. Searching "sphygmomanometer" returns the relevant codes. Use broad, standardized device names and narrow from there.

Mistake 3: Being Too Broad

Searching "surgical" returns hundreds of product codes. Narrow by function: "surgical laser," "surgical stapler," or "surgical mesh" produces manageable results. Use the review panel dropdown to further filter.

Mistake 4: Stopping at the First Result

Multiple product codes may match your device. A keyword search for "thermometer" returns several product codes with different intended uses (clinical, tympanic, infrared, etc.), different classes, and different exemption statuses. Review all results before selecting a code.

Mistake 5: Confusing CDRH Product Codes with ORA Product Codes

The three-letter CDRH product code (e.g., FRN) is different from the seven-character ORA import product code (e.g., 80F--RN). Use the CDRH code for all classification, registration, and premarket submission purposes. Use the ORA code only for import operations.

Mistake 6: Assuming One Product Code per Device

Multi-function devices may require multiple product codes. A patient monitor combining ECG, pulse oximetry, and blood pressure monitoring spans at least three different product codes. Your submission must address all applicable codes.

Mistake 7: Not Checking for Recent De Novo Product Codes

The product code database changes as new De Novo authorizations create new codes. If your device is novel, check the De Novo database for recently created product codes that may not appear in keyword searches using traditional terminology.

Mistake 8: Ignoring Exemption Limitations

Seeing "510(k) Exempt" on a product code detail page does not mean your specific device is exempt. If your device uses a different fundamental scientific technology than what the classification regulation contemplated, or has a different intended use, the exemption does not apply. Always evaluate the limitations in the ".9" section of the applicable 21 CFR Part.

Product Codes and Establishment Registration

When you register your establishment with the FDA and list your devices (required annually under 21 CFR Part 807), the product code is a required data element for each listed device.

How Product Codes Fit into Registration and Listing

Requirement	Where Product Code Is Used
Establishment registration	Registration identifies the facility. Product codes are not part of registration itself.
Device listing	Each device listed must include its product code, identifying the generic device category.
Annual update	Device listing must be updated between October 1 and December 31 each year. Any product code changes or new devices must be reflected.
Unified Registration and Listing System (FURLS)	Product codes are entered in the FDA's FURLS system when listing devices.

Common Device Listing Errors Related to Product Codes

Several common errors occur when manufacturers list devices with incorrect product codes:

• Using an outdated product code — If a device type has been reclassified or a new, more specific product code has been created, your listing should reflect the current code.
• Using a parent device's product code for an accessory — Accessories to medical devices are classified separately. An accessory to a Class III device may itself be Class I or Class II with its own product code.
• Listing one product code for a multi-function device — If your device spans multiple product codes, list all applicable codes in your device listing.
• Mixing up CDRH and ORA product codes — The FURLS system uses three-letter CDRH product codes. Do not enter ORA seven-character import codes.

Practical tip: If you change the product code for a device — for instance, because the FDA reclassifies the device type or you determine a more accurate code applies — update your device listing in FURLS promptly. Incorrect product codes in your device listing can trigger inspection observations. During FDA inspections, investigators commonly verify that your device listing product codes match the product codes on your 510(k) clearance letters and that all marketed devices are properly listed.

Product Code Changes and Reclassification

Product codes and their associated classifications are not permanent. The FDA can change them through several mechanisms.

How Product Codes Change

Mechanism	What Happens to the Product Code	Example
Reclassification (513(e) petition or FDA-initiated)	The existing product code may retain its letters but change class (e.g., Class III to Class II). Special controls may be added.	AEDs reclassified from Class III to Class II — product code LLZ retained but class changed
De Novo authorization	A new product code is created for a previously unclassified or novel device type	OTC hearing aids — new product codes QDD, QUH, QUG, QUF created
Product code split	An existing product code is split into multiple codes to differentiate device subtypes	When the FDA determines that a broad product code covers devices with meaningfully different risk profiles
515(b) PMA call	The product code remains the same, but the required submission type changes from 510(k) to PMA	Pre-amendment Class III devices called to PMA
Regulation number change	Rarely, a device type is moved to a different regulation, which may involve a new product code	Significant restructuring of device categories

Recent and Notable Reclassification Examples

Understanding how reclassification has changed product codes in practice helps illustrate what to watch for:

OTC Hearing Aids (2022) — One of the most significant product code actions in recent FDA history. The FDA created an entirely new OTC hearing aid category with multiple new product codes:

New Product Code	Device Type	Class	Regulation
QDD	OTC hearing aid, self-fitting	II	874.3325
QUH	OTC hearing aid with wireless technology	II	874.3305
QUG	Preset-based OTC hearing aid with wireless technology	II	874.3305
QUF	Preset-based OTC hearing aid without wireless technology	II	874.3305

This was not a reclassification of existing codes — it created new codes for a new product category, enabling consumers to purchase hearing aids without a prescription.

Hepatitis B Virus Assays (2025) — The FDA reclassified HBV antigen assays (product code LOM), HBV antibody assays (product code SEI), and HBV nucleic acid-based assays from Class III (PMA) to Class II with special controls, subject to 510(k). The product codes were retained but the required submission type changed from PMA to 510(k).

Medical Image Analyzers (2020) — The FDA reclassified medical image analyzers (radiological CAD) from Class III to Class II. This reclassification enabled the 510(k) pathway for a category of AI/ML devices that previously required PMA, significantly accelerating access to market for radiology AI software.

CDRH IVD Reclassification Initiative (Ongoing) — In 2024, CDRH announced its intent to reclassify most high-risk IVDs currently in Class III, particularly infectious disease and companion diagnostic IVDs. This initiative is expected to affect dozens of product codes over the coming years and represents one of the largest reclassification efforts in FDA history.

Monitoring for Changes

• Federal Register — Reclassification orders and proposed rules are published in the Federal Register. Subscribe to email updates for the CDRH docket.
• FDA Reclassification page — The FDA maintains a table of all devices reclassified since 2013 at fda.gov/about-fda/cdrh-transparency/reclassification.
• Product Classification Database — The database is updated weekly. Periodic checks for your product code will reveal any changes to class, submission type, or special controls.
• openFDA API — Automate monitoring by querying the classification endpoint programmatically and alerting on changes to key fields.
• De Novo database — Check periodically for new De Novo authorizations that may create product codes relevant to your device type.

Practical tip: If you manufacture a device type currently classified as Class III via 510(k) (a pre-amendment device), monitor for 515(b) PMA calls. When the FDA issues a PMA call, you will have a defined window (often 12 to 36 months) to submit a PMA or cease marketing. Failing to submit by the deadline makes your device adulterated.

Classification Decision Tree: From Product to Product Code

Before diving into the full workflow, use this text-based decision tree to quickly orient yourself on the classification path for your device:

START: Is your product a medical device under the FD&C Act?
│
├── NO → Not FDA-regulated as a device.
│         Consider: Is it general wellness? CDS software meeting
│         all 4 Cures Act criteria? A component (not a finished device)?
│
├── UNSURE → Contact DICE (free, 7 business days) or file a 513(g) ($7,820).
│
└── YES → Search the Product Classification Database by keyword.
          │
          ├── MATCH FOUND → One or more product codes match.
          │   │
          │   ├── Exactly one code fits your intended use
          │   │   and technological characteristics.
          │   │   → Read the 21 CFR regulation text to confirm.
          │   │   → Check the product code detail page for:
          │   │     • Device class (I, II, III, U)
          │   │     • Submission type (510(k), PMA, Exempt, De Novo)
          │   │     • Special controls
          │   │     • Exemption limitations (.9 section)
          │   │   → DONE. Proceed with the indicated pathway.
          │   │
          │   ├── Multiple codes could apply.
          │   │   → Read the regulation text for each candidate.
          │   │   → Search by regulation number to find related codes.
          │   │   → Compare cleared devices (via TPLC) to yours.
          │   │   → If still ambiguous → File a Pre-Submission or 513(g).
          │   │
          │   └── Your device is multi-function.
          │       → Identify a product code for EACH function.
          │       → Primary code = highest class or most significant function.
          │       → Address all codes in your submission.
          │
          └── NO MATCH FOUND → Your device may be novel.
              │
              ├── Is it similar to an existing device type
              │   but with a different intended use or technology?
              │   → Consider De Novo (creates a new product code).
              │
              ├── Is it an accessory to an existing device?
              │   → Search for accessory-specific product codes.
              │   → Classify based on accessory's own risk profile.
              │
              └── Completely novel device type.
                  → File a Pre-Submission to discuss classification.
                  → Prepare for De Novo (Class I or II) or PMA (Class III).

This decision tree covers the most common scenarios. For edge cases — combination products, IVDs needing CLIA categorization, or software functions near the CDS/SaMD boundary — refer to the dedicated sections in this guide.

Practical Workflow for Product Code Determination

Here is a consolidated, step-by-step process for determining the correct product code for any device:

Step 1 — Define your intended use. Write a precise, unambiguous statement of your device's intended medical purpose before touching any database. This statement is your anchor throughout the process.

Step 2 — Search the Product Classification Database by keyword. Use multiple terms: function, anatomy, device type, clinical application. Avoid brand names.

Step 3 — List all candidate product codes. Do not stop at the first match. Identify every product code whose description could potentially apply to your device.

Step 4 — Read the regulation text for each candidate. Go to the 21 CFR text at ecfr.gov and confirm that the regulation's device description and scope match your device's intended use and technological characteristics.

Step 5 — Search by regulation number. Enter each candidate regulation number back into the Product Classification Database to see all associated product codes. This reveals product codes you may have missed in keyword searches.

Step 6 — Check exemption status and limitations. For each candidate, note the 510(k) and GMP exemption status. Evaluate whether the limitations in the ".9" section apply to your specific device.

Step 7 — Cross-reference with 510(k), PMA, and De Novo databases. Search for cleared or approved devices under each candidate product code. Do those devices resemble yours in intended use and technology? If the cleared devices look nothing like yours, the product code may not be correct.

Step 8 — Check for recent De Novo authorizations. Search the De Novo database for newly created product codes that may better fit your device, especially if it involves novel technology.

Step 9 — Review the TPLC report. Access the TPLC report for your top candidate product codes to understand the full regulatory history and identify potential predicates.

Step 10 — If uncertain, engage the FDA. Use DICE for simple questions (free, 7-day response). Use a 513(g) for a formal written classification determination ($7,820). Use a Pre-Submission for complex questions that go beyond classification (free, but longer timeline).

Step 11 — Document your rationale. Record the search terms used, all product codes considered, the code selected, and the reasoning for the selection. This documentation is essential for your regulatory file and will be reviewed during FDA inspections.

Complete Reference: Product Code Database Fields

For quick reference, here is every data field available in the Product Classification Database with its meaning:

Field	Description	Values/Format
Device	Generic device name	Free text
Product Code	Three-letter identifier	Three alphanumeric characters (e.g., QKQ)
Definition	Expanded device description	Free text
Device Class	Regulatory risk tier	1, 2, 3, U (unclassified), N (not classified), f (HDE)
Regulation Number	21 CFR classification regulation section	8XX.XXXX format
Submission Type	Required premarket pathway	510(k), 510(k) Exempt, PMA, De Novo, HDE, Contact ODE, etc.
Review Panel	Medical specialty panel	Panel name (e.g., Cardiovascular)
GMP Exempt	Whether quality system exemptions apply	Yes/No
510(k) Exempt	Whether premarket notification is waived	Derived from Submission Type
Implanted Device	Whether FDA considers this an implant	Yes/No
Life-Sustain/Support	Whether the device is life-sustaining or life-supporting	Yes/No
Third Party Review	Whether an accredited third party can review the 510(k)	Eligible/Not Eligible
SMR Eligible	Summary Malfunction Reporting eligibility	Eligible/Ineligible
TPLC Report	Link to Total Product Life Cycle report	URL
Recognized Standards	Applicable consensus standards	List of standard references
Special Controls / Guidance	Links to applicable FDA guidance	URL(s)

Frequently Asked Questions

What is an FDA product code?

An FDA product code is a three-letter alphanumeric identifier assigned by the FDA to a generic category of medical device. It links the device type to its classification (Class I, II, or III), regulation number, review panel, premarket submission requirements, and exemption status. There are over 6,500 product codes in the FDA system.

How do I find the product code for my device?

Search the FDA Product Classification Database at accessdata.fda.gov/scripts/cdrh/cfdocs/cfPCD/classification.cfm using generic, clinical terms that describe your device's function. Review all matching results, read the regulation text for each candidate product code, and select the code whose classification regulation most accurately describes your device's intended use and technological characteristics.

What is the difference between a product code and a regulation number?

A product code is a three-letter identifier for a specific device type (e.g., QKQ for pulse oximeters). A regulation number is the 21 CFR section that defines the device category (e.g., 870.2700 for oximeters). One regulation number can map to multiple product codes, each representing a different variant of the device type with different intended uses or regulatory requirements.

Can a device have multiple product codes?

Yes. Multi-function devices — such as patient monitors that measure ECG, SpO2, and blood pressure — may span multiple product codes. The FDA requires you to designate a primary product code (typically the one with the highest regulatory class or most clinically significant function) for your premarket submission, but all applicable product codes must be addressed.

How do I know if my device is 510(k) exempt?

Look up the product code in the Product Classification Database and check the "Submission Type" field. If it says "510(k) Exempt," no premarket notification is required — but only if your specific device does not trigger the exemption limitations (different intended use, different fundamental scientific technology, or substantial importance in preventing impairment of human health with potential unreasonable risk).

What is the Total Product Life Cycle (TPLC) report?

The TPLC report is a consolidated view of all regulatory activity associated with a product code — every 510(k) clearance, PMA approval, De Novo authorization, HDE, recall event, adverse event report, and compliance action. It is accessible from the product code detail page in the Product Classification Database and is one of the most valuable research tools for competitive intelligence and regulatory strategy.

How often is the Product Classification Database updated?

The database is updated every Sunday. New product codes from De Novo authorizations, reclassification orders, and other FDA actions are reflected in the weekly updates.

What is the openFDA API and how can I use it for product code research?

The openFDA API provides programmatic access to product classification data at https://api.fda.gov/device/classification.json. You can query by product code, device name, regulation number, medical specialty, and other fields. It supports up to 1,000 results per query and is useful for building automated monitoring tools, regulatory dashboards, and batch lookups. No API key is required for basic use (240 requests per minute), but a free API key enables higher rate limits.

When should I file a 513(g) instead of a Pre-Submission?

File a 513(g) when your only question is classification — "what is my product code?" or "is this a medical device?" File a Pre-Submission when you have broader questions about testing requirements, predicate selection, clinical study design, or regulatory strategy. The Pre-Sub is free and provides interactive feedback through a meeting with the review team, while the 513(g) costs $7,820 (FY2026) and provides a written response only.

How are new product codes created?

New product codes are created primarily through De Novo classification requests (which establish new device categories) and FDA administrative actions (such as splitting broad codes or reclassification orders). Between 2020 and 2024, De Novo submissions accounted for approximately 46% of all new product codes created annually, making it the leading source of new codes.

What does "Unclassified" mean in the Product Classification Database?

A device class of "U" (unclassified) means the device type existed before the Medical Device Amendments of 1976 and has not yet been formally classified into Class I, II, or III. There are approximately 851 unclassified (pre-amendment) product codes. These devices can generally be marketed through a 510(k), but they may be subject to future classification orders by the FDA. A class of "N" (not classified) means the device type has not been assigned to any class — this is rare and typically indicates a pending classification action.

How do product codes relate to the UDI system?

The product code is distinct from the Unique Device Identifier (UDI) system. The product code identifies a generic device type (e.g., all pulse oximeters are QKQ). The UDI identifies a specific commercial product from a specific manufacturer at a specific version or model level. Both are required — the product code for classification and device listing, the UDI for supply chain tracking and post-market surveillance. When you list your devices in GUDID (Global Unique Device Identification Database), you associate each UDI with a product code.

Can I use a competitor's 510(k) summary to identify my product code?

Yes, and this is a common and effective strategy. If a competitor has a device similar to yours that has been cleared through 510(k), the 510(k) summary will state the product code. You can verify this product code in the Product Classification Database and then evaluate whether it accurately describes your device. However, do not blindly copy a competitor's product code — always confirm it by reading the classification regulation text and verifying that your device's intended use and technological characteristics fall within the regulation's scope.

What happens if I submit a 510(k) under the wrong product code?

If the FDA determines during review that your device belongs under a different product code, several outcomes are possible: your submission may be refused to accept (RTA), it may be redirected to a different review division (adding weeks or months to the timeline), or you may receive an Additional Information (AI) request asking you to justify the product code selection or resubmit under a different code. In all cases, selecting the wrong product code causes significant delays and potential additional costs.

Are there product codes for combination products?

Yes. The FDA maintains "device product codes (procodes)" specifically for the device constituent parts of combination products approved under ANDAs, NDAs, or BLAs. These are separate from the standard CDRH product codes and are managed to ensure that the device component of a combination product is properly identified. If your product is a combination product, check the FDA's combination product device procode list in addition to the standard Product Classification Database.

How do I classify an accessory to a medical device?

Accessories have their own product codes and are classified independently based on their own risk profile — not the parent device's class. Under the FDA Reauthorization Act of 2017, a simple accessory to a Class III device (such as a carrying case) may be classified as Class I if its own risk profile warrants it. Search the Product Classification Database for the accessory's specific device type and do not default to the parent device's product code.

How do FDA product codes relate to GMDN codes?

They serve different purposes and there is no official cross-reference between them. FDA product codes (three-letter, US-only) drive regulatory classification and premarket pathway determination. GMDN codes (five-digit, international) are used for device identification and international harmonization. Both are required when listing devices in GUDID — you must provide both the FDA product code and the GMDN code. As of December 2024, the FDA requires five-digit GMDN codes (not four-letter FDA Preferred Terms) in GUDID submissions.

Is my software a medical device that needs a product code?

Not necessarily. If your software meets all four criteria of the Clinical Decision Support (CDS) exclusion under the 21st Century Cures Act — it does not acquire/process/analyze medical images or signals, it displays or analyzes medical information, it is intended for healthcare professionals, and it enables the HCP to independently review the basis for the recommendation — then it is not a medical device and does not need a product code. If it fails any one criterion, it is Software as a Medical Device (SaMD) and must be classified under an appropriate product code. The FDA updated its CDS guidance in January 2026 with a more deregulatory posture toward certain lower-risk HCP-facing software functions.

How does CLIA waiver relate to my IVD product code?

CLIA complexity categorization is separate from your FDA product code and device class. Your product code determines the premarket pathway (510(k), PMA, etc.), while CLIA categorization determines where the test can be performed (waived sites like physician offices vs. moderate/high complexity laboratories). Tests cleared for home use are automatically categorized as waived. Other tests are scored on a seven-criterion system and categorized as moderate or high complexity. Manufacturers can submit a CLIA Waiver by Application to the FDA to request reclassification from moderate complexity to waived.

What is the FDA's 2013 Product Code Guidance?

In 2013, the FDA published a guidance document titled "Medical Device Classification Product Codes" (available at fda.gov/media/82781/download) that explains how product codes are used across FDA program areas to regulate and track medical devices. The guidance covers how product codes support premarket review, postmarket surveillance, device tracking, establishment registration, and device listing. It remains the primary FDA guidance document specifically addressing the product code system and is essential reading for understanding how the FDA uses product codes internally.

Key Takeaways

1. The product code is your regulatory Rosetta Stone. From a single three-letter code, you can determine your device class, regulation number, review panel, premarket pathway, exemption status, special controls, and competitive landscape.

2. Search the database systematically. Use multiple search terms (function, anatomy, device type), search by regulation number to see all related codes, and never stop at the first result.

3. Read the regulation text. The product code is a pointer — the 21 CFR regulation text is the authoritative source for what the classification covers. Confirm your device falls within the regulation's scope.

4. Exemptions have limitations. A product code listed as "510(k) Exempt" does not mean your specific device is unconditionally exempt. Evaluate the limitations in the ".9" section of the applicable CFR Part.

5. Use the TPLC report. It aggregates all submissions, recalls, and adverse events for a product code. This is essential for competitive research, predicate identification, and understanding the regulatory history of your device type.

6. Check for new De Novo product codes. The De Novo pathway is creating approximately 30 new product codes per year. If your device is novel, a recently created De Novo code may be a better fit than an older, broader code.

7. Multi-function devices need multiple codes. Identify all applicable product codes for your device and designate the primary code based on the highest regulatory class or most clinically significant function.

8. When uncertain, engage the FDA. A DICE inquiry (free), 513(g) request ($7,820), or Pre-Submission (free) is far less costly than submitting under the wrong product code and having your submission refused, redirected, or delayed.

9. Monitor for changes. Product codes can be reclassified, split, or affected by PMA calls. Subscribe to Federal Register notices and check the database periodically for updates to your product code.

10. Document your determination. Record your search process, candidate codes, selected code, and rationale. This documentation supports your regulatory file during FDA reviews and inspections.

11. Product codes connect everything. The same three-letter code links the Product Classification Database, 510(k) database, PMA database, De Novo database, MAUDE adverse event database, recall database, GUDID, and the openFDA API. Master product code research and you can navigate the entire FDA regulatory ecosystem.

12. Establishment registration depends on correct product codes. Your device listing in FURLS requires accurate product codes. Errors here can trigger inspection findings and demonstrate a lack of regulatory awareness to FDA investigators.

---

Product code determination is not a one-time exercise. It is the foundation of your ongoing regulatory strategy — from initial classification through premarket submission, establishment registration, post-market surveillance, and response to reclassification actions. Invest the time to get it right at the outset, document your rationale thoroughly, and monitor the Product Classification Database for changes that could affect your device. The three-letter code drives everything that follows.