FDA device product codes are not hidden identifiers; they are assigned through several public systems, but each system answers a different question. A regulatory specialist may need the three-character classification product code for a 510(k), the seven-character import product code for an entry filer, or a database query to confirm which code belongs on a malfunction report. Starting with the right tool avoids mixing code structures. The Product Classification database links device names to product codes, panels, and submission types. The Product Code Builder supports import and industry coding. openFDA offers a monthly-refreshed machine-readable route. Understanding the structure and each tool's limits is the fastest way to find the correct code and avoid downstream listing or reporting errors.

The Code Structure: Why Device Codes Look Different

The term “FDA product code” can describe two related but different strings. The import product code is five to seven characters built from Industry, Class, Subclass, Process Indicator Code, and Product components [1]. For medical devices, Subclass and PIC fields do not apply; they are represented by hyphens, and the Class letter is combined with the Product code to make a three-character code that uniquely identifies a device within an industry [2]. This is why a device product code such as 79L--RR includes hyphens where a food or drug code would carry subclass and process letters. The Product Code Builder Help page also describes medical device and in vitro diagnostic product codes as five characters consisting of two numeric and three alpha characters, with the first two digits indicating the medical specialty under which the device was originally classified [4].

CDRH assigns the three-character classification product codes referenced in device regulation, and those codes appear in the Product Classification database and in openFDA [3][7]. The FDA guidance states that classification product codes are assigned by CDRH to support their regulation [3]. The guidance separately describes adverse event reporting and listing as contexts in which those codes are used [3]. A product code therefore is not a random lookup key; its format depends on whether the identifier came from the import-entry system or from CDRH's classification hierarchy. Confirming which system generated the code prevents using an import string in an MDR field that expects a classification code.

Lookup Path 1: The Product Classification Database

For a known device name, the Product Classification database at accessdata.fda.gov returns the associated product code, review panel, regulation number, submission type, device class, and additional regulatory attributes [5]. The search screen includes filters for review panel, submission type, implanted device, life-sustaining device, and malfunction reporting eligibility [5]. The database page states that it includes a list of all medical devices with their associated classifications, product codes, FDA Premarket Review organizations, and other regulatory information [5]. A user can search by device or product code and then inspect whether the record is linked to a 510(k), PMA, HDE, or exemption.

This path is useful when a manufacturer is confirming the code that should appear in FURLS/DRLM or in a 3500A adverse event report. The guidance states that reporters should use the primary product code associated with the device and recommends including the premarket submission number in section G5 when applicable [3]. The limitation is that the database is oriented to CDRH classification, not import entry. If a user searches by a partial import code or a packaging-related term, the classification database may return no match, because device codes of that type lack subclass and PIC fields.

How to Verify a Medical Device Product Code in the Product Code Builder

Select the verify option, then enter the product code in the appropriate fields and click Next [4]. If the complete code is valid, the next screen displays the primary product name assigned to that code [4]. FDA warns that there may be secondary products associated with the same code; to see both primary and secondary products, use the partial-code search option instead [4]. This verification step is especially useful before submitting an import line item or checking an existing entry record against the code in the invoice description [4].

Lookup Path 2: The Product Code Builder for Import and Entry

The Product Code Builder is a tool for constructing or verifying the product code used in FDA import line items [1][6]. It offers four entry options: search by industry, search a partial code, search by product name or keyword, and verify a complete product code [2]. Selecting a medical device product in the builder automatically inserts hyphens for Subclass and PIC, reflecting the device-specific code structure [4].

A keyword search is usually the fastest method. FDA advises entering one word at a time because entering multiple words may not return a match [2]. After the search, the system lists all industries with product names containing that word, and the user chooses a product from the matching dropdown [2]. The Product Code Builder Help page states that Option 3, Search Product Name, is generally the easiest method to use [2]. For a complete code, the verify function confirms whether a code remains valid and returns the primary product name; FDA notes that secondary products may share a code and suggests using the partial-code option to view both primary and secondary products [2][4]. The builder does not provide the full classification record shown in the Product Classification database.

Lookup Path 3: openFDA's Device Classification API

openFDA provides the Product Classification Database in JSON through the Device Classification API [8]. The API includes medical device names, associated product codes, medical specialty panels, and classification, with monthly updates and records from 1976 [7][8]. This route is appropriate when a team needs to query codes programmatically or cross-reference the classification data across other openFDA device datasets. The openFDA page states that the API contains medical device names, their associated product codes, their medical specialty areas, and their classification [8].

The monthly update frequency is a practical decision point. A source page's “page last updated” date may be newer than the API snapshot, so a user needing the most current code should verify against the live FDA database [7][8]. openFDA also states that its data should not be used to make medical care decisions and should not be used to issue public alerts or track a recall lifecycle [8]. For regulatory submissions, the API is a retrieval convenience, not the authoritative source of record. The openFDA disclaimer states that the data should not be used as a method to collect data to issue alerts to the public, nor should it be used to track the lifecycle of a recall [8].

A Concrete Lookup Suggestion: Locating and Documenting a Code

Suppose a regulatory affairs analyst is preparing a device listing for a convenience kit and needs the product code before entering data in FURLS/DRLM. One documented workflow is to check whether the kit matches a type listed in the Convenience Kit Interim Regulatory Guidance, then search the Product Classification database for the kit by name [3]. If the search returns no suitable code, FDA advises contacting the Program Operations Staff, and a 513(g) request may also be submitted when no fitting code is found [3]. The guidance states that the Program Operations Staff is in the Office of Device Evaluation [3].

This suggested workflow should be treated as an editorial demonstration, not as tested guidance. The actual sequence depends on the kit's components, labeling, and prior classification history. For import work, the same analyst might take the invoice product description and enter a single descriptive keyword in the Product Code Builder [2]. If the code is already on an entry document, the verify function can confirm validity. Documenting the search date and the tool version matters because classification data can change, even though the code structure itself remains stable. The Product Code Builder Help page advises reviewing information provided by the manufacturer or exporter, including product label, invoice papers, or entry documents [2].