FDA device classification: how to find your device class and product code
How FDA device classification works, how to find the right product code, and what Class I, II and III mean for your premarket pathway.
Every US premarket decision starts with one question: what class is the device, and under which product code? Get that wrong and the rest of the plan — pathway, evidence, timeline, budget — is built on the wrong foundation.
What FDA device classification actually is
FDA classifies medical devices by risk and by the controls needed to give reasonable assurance of safety and effectiveness. Class I devices carry the lowest risk and are largely subject to general controls, and most are exempt from premarket notification. Class II devices need special controls and usually a 510(k). Class III devices support or sustain life, or present a potential unreasonable risk of illness or injury, and generally require premarket approval (PMA).
Classification is not a judgement about how novel the technology feels. It is tied to the intended use and indications for use, and to how closely those match an existing regulation and product code.
Product codes are the practical unit of work
A three-letter product code sits under a classification regulation in 21 CFR Parts 862 to 892. The product code is what determines the review panel, the applicable special controls, and — critically — which cleared devices are realistic predicates.
Two devices with similar hardware can sit under different product codes because their indications differ. A search that starts from technology rather than intended use tends to land on the wrong code.
A workable classification sequence
Write the intended use and indications for use in one plain paragraph before searching anything. Then search the FDA product classification database for regulation descriptions that match that intended use, not the technology. Shortlist two or three candidate product codes and read the classification regulation text for each. Pull recent clearances under each code and check whether those devices resemble yours in use, users and setting. Choose the code whose cleared devices you could credibly stand beside, and record why the alternatives were rejected.
Where teams get it wrong
The most common failure is anchoring on a product code someone mentioned early and never revisiting it after the indications changed. The second is treating an exemption as permanent — many Class I and some Class II exemptions carry limitations in the regulation that pull a device back into 510(k) territory once claims expand.
How DevicePath helps
DevicePath is an open-source regulatory triage tool. Describe the device in plain language and it returns the likely FDA class, candidate product codes, the probable premarket pathway, real 510(k) predicate candidates with K-numbers, and high-level EU MDR and UK (UKCA / MHRA) considerations — in seconds. It is built for medical device start-ups, digital health and Software as a Medical Device teams, and small-to-mid-size manufacturers who need a defensible starting point before committing consultant hours.