Exempt from GMP. Not from complaints.

Look up a product code in FDA’s own classification database and one field answers a single yes-or-no question: gmp_exempt_flag. Y means, in openFDA’s own words, exempt due to Good Manufacturing Practice or Quality System requirements under Part 820. Read that as exempt from the quality system, full stop, and the regulation itself disagrees with you — on exactly two things it never let go of.

What the flag is actually shorthand for

The Y is not FDA’s invention for the API; it republishes a designation that predates openFDA by decades — the asterisk FDA’s own classification listings have long used to mark a Class I device as exempt from the manufacturing-controls portion of the quality system regulation, provided it is not labeled or represented as sterile. Most of Part 820’s design, production, and process controls simply do not apply to a code carrying that mark. That is a real, substantial exemption, and for most of what a quality system regulation asks a manufacturer to do, it holds.

The two things the exemption was never written to reach

FDA’s own exemption language has always carried a carve-back, not a footnote: even a GMP-exempt Class I device stays bound by the regulation’s requirements for records and for complaint files. Before the 2026 Quality Management System Regulation, those two obligations sat in 21 CFR 820.180 and 820.198 by name, sitting outside the exemption while everything around them fell inside it. The QMSR’s own technical-amendments notice, effective the same February 2, 2026 date as the rule itself, updated that cross-reference rather than retiring it — the non-exempt activity for these codes now points to 21 CFR 820.35, Control of records, the QMSR’s home for the same two duties. The number moved. The carve-back did not.

“Exempt” was never one boolean underneath the boolean the database actually stores. It was always exempt from most of the regulation and bound by a specific, named piece of it — the flag just doesn’t say which piece.

Why that specific carve-back, and not some other one

The logic is not arbitrary. A complaint file is where a manufacturer’s first knowledge of a problem with a marketed device has to land, investigated and recorded, whether or not that device was ever subject to design controls or process validation in the first place. Exempting a low-risk device from proving how it was built was never the same question as exempting it from listening when something goes wrong after it ships. FDA drew that line decades ago and the QMSR’s technical amendments preserved it on purpose, moving the citation without touching the substance.

The practice

A product profile built from a single flag is accurate exactly as far as the flag goes, and no further. Reading gmp_exempt_flag: Y as “no quality-system obligation on this code” overstates what FDA’s own database claims. The honest reading is narrower and more specific: most of Part 820 does not reach this code, and 820.35’s records and complaint-file requirements still do, regardless of the flag. Confirming which of a portfolio’s product codes carry that mark, and treating the mark as a partial exemption rather than a complete one, is a five-minute check against FDA’s own classification record.

FDA Radar’s own onboarding lookup reads this same field — the one that turns a product code into the profile a portfolio is built from — and renders it as a single “GMP exempt” tag, exactly as specific as the flag itself and no more. Which obligations survive a specific exemption for a specific device is a question for the regulatory professional reading the full record, never a determination this product makes for you; see our editorial standards for the line between what a field states and what a person concludes from it.