What Is an FDA Product Code? How to Find the Right One for Your Device

2026-10-03 · Caduvo Team

A guide to the three-letter FDA device product code: what it dictates across review panels and submission types, how to avoid the import builder trap, and how to pinpoint yours.

Before you draft a 510(k), run verification testing, or assess reimbursement, you need three letters. An fda product code anchors your device inside the agency's regulatory structure. If you select the wrong one, you will base your premarket submission on the wrong performance benchmarks, target an invalid predicate device, or misjudge whether your device requires a Premarket Notification (510(k)) or Premarket Approval (PMA). Identifying this code early removes guesswork from testing protocols, premarket review preparation, and downstream market access.

Anatomy of an FDA Product Code: What Three Letters Dictate

An FDA device product code consists of a three-letter combination (such as DQK or LLZ) assigned by the Center for Devices and Radiological Health (CDRH) or the Center for Biologics Evaluation and Research (CBER). As outlined in the FDA's medical device classification product codes guidance, these codes identify the generic category of a device based on medical device product classifications designated under 21 CFR Parts 862 through 892.

The agency has established classifications for approximately 1,700 generic types of devices and grouped them into 16 medical specialties referred to as panels, as detailed in the agency's medical device classification overview. Each three-letter code links directly to regulatory attributes that govern your path to market:

Device Class: Determines whether the product is Class I (General Controls, with or without exemptions), Class II (General Controls and Special Controls, with or without exemptions), or Class III (General Controls and Premarket Approval).
Submission Type: Identifies whether the technology requires an FDA 510(k) clearance, a PMA, or is exempt.
Review Panel and Regulation Number: Matches the device to an advisory committee (such as Cardiovascular under Part 870 with code CV, or Orthopedic under Part 888 with code OR) and a premarket review organization.
Special Controls and Exemptions: Shows whether good manufacturing practice (GMP) exemptions apply, if the code is eligible for third-party review, or if summary malfunction reporting is permitted.

+-------------------------------------------------------------+
|                  FDA Product Code Record                    |
+-------------------------------------------------------------+
| Medical Specialty: Cardiovascular (CV)                      |
| Regulation Number: 21 CFR Part 870                          |
| Device Class:      Class II                                 |
| Submission Type:   510(k)                                   |
| Tracking Flags:    Implant Flag (Y/N) | Life Support (Y/N)  |
+-------------------------------------------------------------+

According to the classification file documentation, downloadable files parse each code into 18 distinct data elements. These include explicit flags for implant status, life-sustaining or life-supporting designation, unclassified reason codes, and medical specialty codes. The 19 medical specialty advisory committee codes include "AN" for Anesthesiology under Part 868, "CV" for Cardiovascular under Part 870, "DE" for Dental under Part 872, "OR" for Orthopedic under Part 888, "RA" for Radiology under Part 892, and "SU" for General & Plastic Surgery under Part 878.

Device Product Codes vs. the FDA Product Code Builder: The 7-Character Trap

A frequent stumbling block for regulatory leads and founders is conflating the CDRH three-letter classification code with the 5- to 7-character code generated by the FDA Product Code Builder.

The Product Code Builder is an import program tool used for commercial entries entering the United States. It applies across FDA-regulated commodities, including food, cosmetics, and medical devices. An import product code describes a specific product through a combination of five to seven numbers and letters across five components:

Industry Code: Two numbers from "02" to "98" determining the broadest area into which a product falls (such as dental for dental-related devices).
Class Code: One letter (a-z) directly related to an industry, designating category, use, or product group.
Subclass Code: One letter (a-z) representing container type or packaging material. Medical devices do not have subclass codes and are represented by a hyphen (-).
Process Indicator Code (PIC): One letter (a-z) describing the process, storage, or dosage form. Medical devices do not have a PIC and are represented by a hyphen (-).
Product (Group): Two characters (letters or numbers) identifying the specific product. For medical devices, the product (group) element is two letters, and when combined with the class element letter, those three letters identify the specific medical device.

Premarket documents submitted to CDRH or CBER require the exact three-letter classification identifier from the fda product code database, not the 5- to 7-character import string. Confusing the import tool with your classification product code causes errors during regulatory preparation.

Step-by-Step FDA Product Code Lookup and Predicate Mapping

Finding your three-letter code involves evaluating intended use, indications for use, and technological characteristics against established regulatory categories. The FDA updates the Product Code Classification Database every Sunday, making it the primary reference.

Follow this four-step process for an accurate fda product code lookup:

Step 1: Identify Established Predicates in Premarket Databases
                    │
                    ▼
Step 2: Query the Product Classification Database
                    │
                    ▼
Step 3: Verify 21 CFR Parts 862-892 Regulation and Exemptions
                    │
                    ▼
Step 4: Evaluate Downstream Coding and Reimbursement Links

1. Identify Established Competitor Predicates

Review 510(k) clearance summaries for devices with the same intended use. If you are developing a surgical tool, locate marketed competitors in CDRH premarket databases. Clearance records specify the assigned three-letter product code along with the corresponding classification regulation.

2. Query the Product Classification Database

Open the CDRH Product Classification simple search. When querying device names, search by the primary noun first rather than descriptive adjectives. Database names use the format of a noun followed by one or more adjectives separated by commas. For example, to find an infusion pump, search on the word "pump" rather than "infusion pump" to retrieve all entries containing that term.

3. Cross-Check the Regulation and Exemption Status

Once you locate a candidate code, examine its complete database record. Verify which regulation under 21 CFR Parts 862–892 governs the device. Check the Submission Type ID to see if a 510(k) is required or if the device is exempt. If exempt, review whether any limitations of exemptions under 21 CFR xxx.9 apply (where xxx refers to Parts 862 through 892), and check the GMP Exempt flag to confirm whether Good Manufacturing Practice requirements are modified.

4. Evaluate Regulatory Panel and Downstream Reimbursement Impact

Your product code identifies your premarket review organization and determines your review panel standards. It also influences commercial strategy. Hospital committees and market-access teams examine device categories when evaluating novel technologies. For example, Caduvo maps all 7,063 FDA device product codes directly to historical clearance counts and candidate HCPCS billing codes, helping manufacturers review regulatory classification and reimbursement pathway feasibility in one place.

What to Do When No Product Code Fits

An innovative intended use or novel technology may not match an existing generic device type in the fda product code database. When a search yields no applicable code, evaluate these regulatory situations:

General Controls and Premarket Approval (Class III)

Under FDA classification policy, Class III covers devices with the greatest risk where General Controls and Special Controls are insufficient to assure safety and effectiveness. A Premarket Approval application (PMA) is required for Class III devices unless the device is a preamendments device (on the market prior to May 28, 1976, or substantially equivalent to one) and PMAs have not been called for, in which case a 510(k) serves as the route to market.

Reviewing Unclassified Device Categories

The downloadable database file foiclass.zip includes a dedicated data element for "Unclassified Reason Code." Certain preamendments medical devices remain commercially distributed without a formal classification regulation under 21 CFR Parts 862–892. These devices still carry assigned three-letter product codes that govern their premarket submission requirements.

Actionable Product Code Checklist

Before finalizing your regulatory submission or commercial timeline, verify each of the following items against primary records:

[ ] Three-Letter Confirmation: Confirm you are using a 3-character CDRH/CBER classification code (e.g., DQK, LLZ) rather than a 5- to 7-character code from the import fda product code builder.
[ ] Weekly Database Refresh: Cross-reference your candidate code against the Product Code Classification Database, which updates every Sunday.
[ ] Data Elements Review: Download and inspect the 18 data elements in foiclass.zip to review third-party review eligibility, summary malfunction reporting eligibility, and implant or life-support tracking flags.
[ ] Panel Alignment: Verify the 2-letter medical specialty code (such as AN, CV, HO, NE, OR, or SU) and ensure your testing data satisfies the appropriate advisory review panel.
[ ] Predicate Verification: Confirm that your selected predicate device is classified under the exact product code you intend to cite.

Sources

General information, not regulatory, legal or reimbursement advice. Company and product names belong to their owners; a mention does not imply affiliation or endorsement. Report an error. Data and corrections policy.