How to Find the Right FDA Product Code for Your Medical Device (And Why Getting It Wrong Is Costly)

The Product Code Problem Nobody Talks About Until It Is Too Late

You have spent months -- maybe years -- developing your medical device. You are ready to engage with FDA, file your 510(k), or pursue De Novo classification. Then someone asks: What is your FDA product code?

For many founders and even seasoned regulatory professionals, this question triggers a scramble. Product codes are deceptively simple on the surface and dangerously consequential when chosen incorrectly. Selecting the wrong one can misdirect your entire regulatory pathway, invalidate your predicate device selection, trigger a Refuse to Accept (RTA) decision from FDA, or land your submission in the wrong review division entirely.

At ADB Consulting and CRO Inc., we see product code errors in a significant percentage of early-stage submissions we are brought in to rescue. Here is what you need to know to get it right from the start.

What Is an FDA Product Code, and Why Does It Matter?

FDA product codes are three-letter alphanumeric identifiers assigned to specific device types within the agency's classification system. They are embedded in the FDA Product Classification Database and tied directly to the device classification regulations under 21 CFR Parts 862 through 892.

Each product code links to a device class (Class I, II, or III), a regulation number, a specific FDA review panel (e.g., Cardiovascular, Radiology, Neurology), and the submission type required -- whether that is a 510(k), De Novo, PMA, or an exemption. Choosing the wrong product code is not merely a paperwork issue. It shapes every downstream regulatory decision you will make.

How FDA Product Codes Are Structured

Under 21 CFR Parts 862 through 892, devices are organized by medical specialty panel. Within each part, devices are assigned to a specific classification regulation -- for example, 21 CFR 880.5860 for a non-powered patient examination glove. FDA then assigns one or more product codes to device types within those regulations.

A single regulation can have multiple product codes reflecting variations in technology, intended use, or risk profile. This is where precision matters. Two codes under the same regulation may carry different special controls, different predicate pools, and different review timelines.

Step-by-Step: How to Find the Right Product Code

Step 1: Start with FDA's Product Classification Database

FDA's publicly accessible Product Classification Database at accessdata.fda.gov allows you to search by device name, regulation number, or panel. Start with broad descriptive terms related to your device's intended use and indication. Do not search by your commercial product name -- search by the generic device type FDA would recognize.

Step 2: Cross-Reference the 510(k) Database

Once you have candidate product codes, search FDA's 510(k) database for cleared devices sharing those codes. Review the predicate devices. Are their indications for use, technological characteristics, and intended patient populations reasonably aligned with yours? This dual-database approach is not optional -- it is essential for building a defensible substantial equivalence argument under 21 CFR 807.87(f).

Step 3: Review the Applicable Classification Regulation

Pull the actual text of the classification regulation associated with your candidate code. Read the device definition carefully. FDA reviewers will hold you to that definition. If your device does not fit cleanly, you may be looking at the wrong code -- or you may have a De Novo candidate on your hands.

Step 4: Check for Existing Guidance Documents

FDA has issued device-specific guidance documents for many product types that explicitly reference applicable product codes. The FDA Guidance Database is searchable by topic. Relevant guidances may also identify special controls under 21 CFR 860.107 that will govern your 510(k) or De Novo submission.

Step 5: Consult the Device Advice and Q-Submission Pathway

When product code selection is genuinely ambiguous -- particularly for novel combination technologies, software as a medical device, or devices that straddle multiple panels -- FDA's Q-Submission (Pre-Sub) program is the formal mechanism to get agency feedback before you file. Do not guess when you can ask.

Common Product Code Mistakes and Their Consequences

• Selecting a code that is too broad: This can misrepresent your device's risk profile and draw regulatory requirements that were never intended to apply.
• Selecting a code that is too narrow: Your predicate pool shrinks, weakening your substantial equivalence argument or eliminating viable predicates entirely.
• Choosing an obsolete or superseded code: FDA periodically retires and replaces product codes. Using a deprecated code signals to reviewers that your regulatory intelligence is out of date.
• Mismatching product code to review division: FDA is organized into Offices and Divisions by specialty. A mismatched product code routes your submission to a reviewer who does not have subject matter expertise in your device category -- slowing review and increasing the likelihood of substantive questions.

Software and Combination Products Add Complexity

If your device includes software functionality, AI/ML components, or is part of a combination product, product code selection becomes even more nuanced. FDA's 2023 guidance on predetermined change control plans and the Digital Health Center of Excellence guidance documents introduce additional considerations for Software as a Medical Device (SaMD). Under 21 CFR Part 3 and the combination products framework, you may also need to determine which FDA Center has primary jurisdiction before you can accurately assign a product code.

The Bottom Line

Product code selection is one of the earliest and most consequential regulatory decisions you will make. It is also one of the most underestimated. The three-letter code you choose will shape your predicate strategy, your review timeline, your special controls obligations, and the expertise of the FDA staff evaluating your submission.

Get it right before you file -- not after FDA issues an Additional Information request or, worse, an RTA.

Work With Experts Who Know the Database Cold

At ADB Consulting and CRO Inc., we help medical device startups, emerging growth companies, and established manufacturers navigate the full complexity of FDA product classification -- from initial product code identification through submission strategy and FDA interactions. Andre Butler and the ADB team bring direct regulatory experience to every engagement, so you are not guessing when you go to the agency.

Ready to confirm your product code and build a submission strategy that holds up under FDA scrutiny? Book a free discovery call with ADB Consulting and CRO Inc. today at adbccro.com. Let us get your regulatory foundation right from day one.

For related guidance, see our annual registration renewal service.