AccessGUDID vs FDA Listing: Which Record Answers Your Question?

Which public record answers this question?

When a medical device regulatory professional, hospital procurement officer, or supply-chain auditor holds an identifier—such as a barcode on an outer carton, an establishment name, a product code, or a registration number—they frequently confront two distinct Food and Drug Administration (FDA) public web interfaces: AccessGUDID and the Establishment Registration and Device Listing search database. The two portals look superficially interchangeable to external observers, leading many teams to mistake one for the other or assume a record missing from one database is unapproved, unregistered, or counterfeit.

The core identity rule is unambiguous: Open AccessGUDID for the identifier physically printed on the device label or packaging; open FDA's Establishment Registration and Device Listing database for the commercial establishment and its listed medical devices. Neither catalog constitutes an FDA clearance, approval, or marketing authorization determination.

Understanding the statutory separation between 21 CFR Part 830 UDI requirements and 21 CFR Part 807 establishment registration prevents false alarms during vendor audits, customs clearance checks, and hospital incoming inspection. Below, this worksheet maps every reader question to its authoritative record, details statutory confidentiality gating, reconciles catalog discrepancies, and walks through a labeled fictional audit packet.

What AccessGUDID is, and what it is not

To use AccessGUDID accurately, regulatory teams must differentiate among three related concepts: the Global Unique Device Identification Database (GUDID), the AccessGUDID public search engine, and the GUDID submission account within the FDA Unified Registration and Listing System (FURLS).

GUDID is the central database administered by the FDA Center for Devices and Radiological Health (CDRH) to store device identification records submitted by medical device labelers under 21 CFR Part 830. AccessGUDID is the no-account public search web portal and downloadable data repository developed and hosted by the National Library of Medicine (NLM) in collaboration with the FDA. Labelers never edit data in AccessGUDID directly; they enter data through their secure FURLS GUDID account or HL7 SPL automated transmission, after which validated records flow to NLM for public dissemination.

A vital architectural boundary is the distinction between Device Identifiers (DI) and Production Identifiers (PI), which together comprise a complete Unique Device Identifier under 21 CFR 801.3:

• Device Identifier (DI): The mandatory, fixed numerical or alphanumeric string specific to a model, version, or packaging level of a medical device (e.g., a GS1 GTIN, HIBCC LIC, or ICCBBA code). The DI is the primary key in GUDID.

• Production Identifiers (PI): Dynamic data applied to the label, including lot or batch numbers, serial numbers, expiration dates, manufacturing dates, or distinct identification codes for human cell, tissue, or cellular and tissue-based products (HCT/P). GUDID never stores actual production identifiers. Instead, GUDID records boolean flags indicating which PI categories are required to appear on the physical label.

The legal entity obligated to submit GUDID records is defined by 21 CFR 801.3 as the labeler: any person who causes a label to be applied to a device, or who causes the label of a device to be replaced or modified, with the intent that the device will be commercially distributed without any subsequent intended replacement or modification of the label. An entity that simply adds its name and contact information as a domestic distributor is explicitly excepted from the labeler definition. In GUDID, labelers are identified by their Dun & Bradstreet Data Universal Numbering System (DUNS) number, and company names are mirrored from Dun & Bradstreet records.

Furthermore, published GUDID records are subject to a mandatory 7-calendar-day grace period. When a labeler publishes a new or edited DI record in GUDID, the record enters a 7-day grace window starting the day after the DI Record Publish Date (shortened from 30 days on March 11, 2019, per NLM system notices). During these 7 days, the labeler can correct typographical errors or field entries without creating a formal revision history, but the record remains invisible on AccessGUDID. Once the grace period expires, the record is published to AccessGUDID during the next business-day release cycle.

What FDA device listing is, and what it is not

Medical device establishment registration and device listing are governed by Section 510 of the Federal Food, Drug, and Cosmetic Act (FD&C Act) and codified under 21 CFR Part 807. Unlike GUDID, which is centered on unit-of-use and packaging barcodes, Part 807 is an establishment-based regulatory accounting system.

Under 21 CFR 807.20, the owner or operator of any establishment engaged in the manufacture, preparation, propagation, compounding, assembly, or processing of a device intended for human use and commercial distribution in the United States must register its establishment and submit a list of all devices in commercial distribution. That owner/operator duty covers, among other establishment types, manufacturers, specification developers, contract manufacturers, contract sterilizers, and repackagers or relabelers. Foreign establishments that manufacture devices imported or offered for import into the United States must register, list, and designate one U.S. agent under 21 CFR 807.40.

Listing data are submitted electronically via the Device Registration and Listing Module (DRLM) within FURLS. The public search interface—accessible at FDA's CDRH database search page (rl.cfm)—displays releasable registration and listing records. In accordance with FDA public statements, the online listing database is rebuilt and refreshed weekly, typically on Mondays, resulting in a multi-day propagation latency between FURLS submission and public appearance. The online search interface also imposes an operational constraint: a single query will return a maximum of 100 establishments.

Under 21 CFR 807.25(g), each device listing must report: the current registration number and name of each establishment under the owner or operator where the device is manufactured, repackaged, relabeled, otherwise processed, or where specifications are developed; the product code for each device that is exempt from premarket notification and approval or that was in commercial distribution before 28 May 1976; proprietary or brand name(s); the FDA-assigned premarket submission number for listed devices subject to FD&C Act sections 505, 510(k), 513(f)(2), 515, or 520(m); and each activity or process conducted on the device at each establishment.

Question-to-record map

Regulatory affairs professionals, hospital materials managers, and compliance auditors regularly ask practical questions about devices in inventory. The flowchart below outlines the triage pathway based on the initial identifier or evidence need held by the reviewer:

flowchart TD
    Start["Identifier or Regulatory Question in Hand"] --> Triage{"What type of identifier or inquiry?"}

    Triage -->|"Barcode, GTIN, DI, or Package Label"| GUDIDBranch["Open AccessGUDID (NLM / FDA)"]
    Triage -->|"Establishment, FEI, Owner/Operator, or US Agent"| ListingBranch["Open FDA Establishment Registration & Listing (rl.cfm)"]
    Triage -->|"Premarket Clearance, Safety/Efficacy, or Approval"| PremarketBranch["Open FDA 510(k), De Novo, or PMA Database"]
    Triage -->|"FDA-Assigned Device Listing Number"| PrivateBranch["Request FURLS DRLM Output from Registrant"]

    GUDIDBranch --> GUDIDResult["Yields: DI, Brand/Model, GMDN, MRI Safety, Latex, Package Count, PI Types"]
    ListingBranch --> ListingResult["Yields: Registration Status, Facility Address, Declared Activities, Listed Brands, US Agent"]
    PremarketBranch --> PremarketResult["Yields: Substantial Equivalence, Summary of Safety & Effectiveness, Cleared Indications"]
    PrivateBranch --> PrivateResult["Non-Public: Statutorily withheld from public web by 21 CFR 807.37(b)(2)"]

To resolve specific inquiries, consult the detailed question-to-record mapping matrix below. Every entry identifies the authoritative public record, the governing Code of Federal Regulations citation, and the specific claims the record can and cannot support:

The listing number that GUDID requires and the public listing website withholds

One of the most persistent sources of confusion during regulatory audits and customs entry filing is the search for the FDA listing number. Regulatory checklists commonly instruct buyers: "Obtain the FDA listing number and verify it on the FDA website." When auditors search AccessGUDID or the public establishment registration database, they find no listing number field whatsoever. Many conclude that the manufacturer provided an invalid number or failed to list the device.

This confusion stems from a statutory paradox: The FDA listing number is mandatory submission input for GUDID, but federal law expressly prohibits the FDA from publishing it on the web.

Consider the interlocking regulatory requirements:

• Mandatory Submission in GUDID (21 CFR 830.310(b)(12)): When a labeler creates a DI record in GUDID, 21 CFR 830.310(b)(12) requires the labeler to provide 'the FDA listing number assigned to the device.' That number is GUDID input, not a public AccessGUDID search field.

• Assignment of Listing Numbers (21 CFR 807.28(f)): FDA assigns listing numbers through DRLM. Specifically, FDA assigns one alphanumeric listing number for all devices exempt from premarket notification under a single product code, and one distinct listing number for each FDA premarket submission number (e.g., 510(k), PMA) for non-exempt devices.

• Statutory Public Withholding (21 CFR 807.37(b)(2)): 21 CFR 807.37(b) states that specified listing information 'will not be available for public inspection or posted on the FDA Web site,' and 21 CFR 807.37(b)(2) identifies 'FDA-assigned listing numbers' as one of those withheld items. The regulation states the withholding rule; it does not publish a separate rationale for why listing numbers are withheld.

If the listing number is withheld from the public, why does GUDID require it? The GUDID User Manual Version 2.1 (December 2024) explains the internal mechanism: GUDID uses the submitted listing number behind the scenes to query DRLM confidentiality flags before releasing premarket numbers to the public. Under 21 CFR 807.37(b)(1), an owner/operator may mark proprietary names confidential if disclosure would reveal a trade secret or confidential business relationship (such as a contract manufacturing arrangement). If any proprietary name associated with a listing number is marked confidential in DRLM, GUDID's automated validation engine suppresses the public release of the premarket submission number in AccessGUDID.

Public API schemas corroborate this statutory barrier. The NLM AccessGUDID Download Schema (updated through 2018 additions) and the openFDA Unique Device Identifier searchable fields list expose brand names, labeler DUNS numbers, GMDN terms, and premarket submission numbers—but omit the listing number entirely. Similarly, importing entities filing commercial customs entries via CBP ACE must obtain the listing number directly from the manufacturer's internal FURLS confirmation document, as documented on FDA's How to Register and List guidance page.

When one catalog is silent and the other is not

During compliance verifications, auditors frequently encounter a 'miss'—a device record that appears in one database but cannot be found in the other. A failure to locate a record does not necessarily indicate regulatory evasion. Distinct regulatory mechanisms, publication calendars, and statutory exceptions explain why valid devices appear in only one catalog.

Scenario A: Listed on FDA Listing Search, but absent from AccessGUDID

If a medical device is actively listed on FDA's Establishment Registration and Device Listing database under a valid product code and proprietary name, but yields zero results in AccessGUDID, five legitimate regulatory explanations must be evaluated:

1. General UDI Exceptions under 21 CFR 801.30: Section 801.30 exempts specified categories of devices from bearing a UDI on their labels. Most notably, 21 CFR 801.30(a)(2) excepts Class I devices that the FDA has by regulation exempted from the good manufacturing practice requirements of 21 CFR Part 820. Following the December 4, 2025 Quality Management System Regulation (QMSR) technical amendments (90 FR 55978, effective February 2, 2026), the regulatory cross-reference in 801.30(a)(2) was updated to cite continuing recordkeeping under 21 CFR 820.35 (replacing legacy 820.180/820.198). This technical amendment did not create a new UDI exception, but reaffirmed that GMP-exempt Class I devices remain legally excepted from UDI labeling and GUDID submission.

2. The 7-Calendar-Day Grace Period: When a labeler creates or edits a GUDID DI record, the record enters a mandatory 7-calendar-day grace period starting the day after the Publish Date. The device is fully compliant in GUDID, but NLM will not release it to AccessGUDID until the grace period concludes and the daily sync executes.

3. Voluntary UDI Placement (21 CFR 830.300(b)): Under 21 CFR 801.40, a manufacturer may voluntarily choose to apply a UDI to a device that is otherwise excepted under 801.30. In such cases, 21 CFR 830.300(b) states that GUDID data submission remains entirely optional. The device bears a physical UDI and is legally listed, but the labeler has no legal duty to enter it into GUDID.

4. FDA Enforcement Discretion for Class I Consumer Health Devices: Under FDA's July 2022 guidance (Unique Device Identification: Policy Regarding Compliance Dates for Class I and Unclassified Devices), FDA does not intend to enforce GUDID submission under 21 CFR 830.300 for Class I devices considered consumer health products that are still required to bear a UDI. That policy is FDA guidance, not a substitute for 21 CFR 801.30 or 830.300. Implantable, life-supporting, or life-sustaining (I/LS/LS) devices are outside the consumer-health GUDID discretion. A separate, now-expired December 8, 2022 delay for certain Class I and unclassified devices other than I/LS/LS is not the current consumer-health policy.

5. FDA GUDID Rejection or Removal (21 CFR 830.300(c)): FDA may reject or remove GUDID data under 21 CFR 830.300(c), including where the product requires but does not have required premarket approval, licensure, or clearance. That action would keep the DI out of AccessGUDID even when a listing row exists or is being corrected. Separately, 21 CFR 801.30(d) provides that a Class I UDI need not include a production identifier; that rule explains label content, not an AccessGUDID miss.

Scenario B: Present in AccessGUDID, but absent from FDA Listing Search

Conversely, if an active DI record appears on AccessGUDID with detailed packaging and brand metadata, but searching the proprietary name or establishment on FDA's rl.cfm listing page yields no matching records, several procedural conditions explain the discrepancy:

1. Weekly Refresh vs Daily Sync: AccessGUDID is updated by NLM every business day, whereas FDA's public Establishment Registration and Device Listing database is rebuilt on a weekly cadence, typically over the weekend for Monday publication. A newly listed device published in FURLS midweek may appear in GUDID once submitted, but remain absent from the public listing search until the following Monday's batch job.

2. Confidential Business Relationships (21 CFR 807.37(b)(1)): Federal regulations provide that FDA will withhold proprietary names and premarket submission numbers from the public listing database for contract manufacturers, contract sterilizers, and private-label manufacturers if public disclosure would reveal a confidential business relationship. The device is legally listed under a private FURLS registration, and the brand appears on AccessGUDID under the private labeler's DUNS, but the manufacturing facility's public listing page suppresses the brand name.

3. Initial Importer Listing Rules (21 CFR 807.20(a)(5)): Under 21 CFR 807.20(a)(5), an initial importer who is not the manufacturer, repackager, or relabeler fulfills its listing obligation by submitting the name and address of the foreign manufacturer. The initial importer does not generate an independent proprietary name listing, meaning a search for the importer's name paired with the brand will return no records on the public listing site.

4. Failed-to-Register or Failed-to-List Status (21 CFR 807.22(c)): Medical device establishments must complete their annual registration and listing confirmation between October 1 and December 31 of each fiscal year. If an establishment fails to renew its registration, misses the annual fee deadline, or fails to submit required 30-day updates, FDA systems flag the establishment. Under 21 CFR 807.22(c), an establishment that fails to register or list is dropped from the public website until the defect is cured, even while historical DI records remain active in AccessGUDID.

5. Discontinued Commercial Distribution (21 CFR 807.28(d)): When a manufacturer discontinues commercial distribution of a device, it must discontinue the DRLM listing under 21 CFR 807.28(d). Once discontinued, the device no longer represents current commercial distribution on the public listing search. Devices already in the supply chain may still appear in AccessGUDID with a commercial-distribution status and, where submitted, a commercial-distribution end date—not a public 'listing number' or a field named Delisting Date.

6. Not an AccessGUDID-hit explanation (21 CFR 830.300(c)): If FDA rejects or removes GUDID data under 21 CFR 830.300(c)—including where required premarket approval, licensure, or clearance is missing—the DI would be absent from AccessGUDID. Do not use that removal authority to explain a public AccessGUDID hit with a listing-search miss.

Fees, refresh clocks, and the third records

To establish robust standard operating procedures for vendor qualification and supplier file maintenance, regulatory teams must separate fee structures, understand publication clocks, and recognize when to exit these two catalogs in favor of third-party public records.

User fees and financial boundaries

A common misconception among early-stage medical device companies is that submitting a device to GUDID incurs an FDA user fee, or that paying the annual establishment fee grants marketing clearance. Both assumptions are incorrect:

• FY 2026 Establishment Registration Fee: Published in the Federal Register on July 30, 2025 (90 FR 35895), the annual establishment registration fee for Fiscal Year 2026 (effective October 1, 2025 through September 30, 2026) is set at $11,423. This fee is mandated by the Medical Device User Fee Amendments (MDUFA). Crucially, reduced small-business rates are not available for the annual establishment registration fee. Most establishments that must register pay that amount. FDA's Small Business Determination program may waive the annual registration fee, excluding the initial registration, only for certain small businesses that meet a $1 million receipts threshold, show financial hardship, and have paid the fee in a prior fiscal year.

• GUDID Submission Fee ($0): The FDA charges no fee for creating a GUDID account, submitting DI records, or maintaining product data in AccessGUDID. Similarly, listing individual devices in DRLM does not carry an incremental fee beyond the base establishment registration.

• Vendor Broker Tables: Regulatory teams must exercise caution when reviewing third-party regulatory consulting or broker rate sheets. Third-party firms often publish aggregated fee tables that bundle the statutory $11,423 registration fee with commercial US Agent retainers, translation fees, and document review charges. Only the Federal Register notice governs the official statutory fee.

Publication and synchronization clocks

Understanding the update cycles of each public record prevents premature escalations when onboarding new suppliers:

• AccessGUDID (NLM): Updated every business day. NLM processes daily release files containing DI records that have exited the 7-calendar-day grace period. NLM also provides a cumulative weekly archive of these daily files for enterprise batch synchronization.

• FDA Establishment Registration & Listing (rl.cfm): Rebuilt and published weekly, usually on Mondays. Submissions completed in FURLS DRLM during the week typically appear the following Monday.

• openFDA APIs: The openFDA Device Registrations & Listings API is documented by FDA as a machine-readable mirror updated on a monthly cadence. In contrast, the openFDA Unique Device Identifier API updates on a weekly cycle. RA professionals must never use openFDA API endpoints as a real-time regulatory check; openFDA is a delayed analytical mirror, not a live compliance verification system.

The third records for consequential decisions

AccessGUDID and the Device Listing database are identification and registration tools; they cannot answer consequential safety, efficacy, or premarket authorization questions. When evaluating supplier claims, regulatory teams must route their inquiries to dedicated third records:

• Premarket Authorization Databases: To verify whether a medical device has demonstrated substantial equivalence or gained marketing approval, consult FDA's dedicated premarket databases: the 510(k) Premarket Notification Database, the De Novo Classification Database, or the Premarket Approval (PMA) Database. A premarket number appearing in AccessGUDID is labeler-submitted and subject to DRLM confidentiality suppression; the authoritative clearance letter and Summary of Safety and Effectiveness exist exclusively in the premarket databases.

• Post-Market Surveillance and Safety: To assess product malfunction rates, clinical complications, or patient injury reports, query the Manufacturer and User Facility Device Experience (MAUDE) database. To verify whether a lot or model has been subject to safety corrections or removals, query the FDA Medical Device Recalls database.

• International Market Access: AccessGUDID and FURLS apply strictly to devices entering United States commercial distribution. For European Union market access under EU MDR 2017/745 or EU IVDR 2017/746, verify CE marking, Notified Body certificates, and UDI Basic-UDI-DI data in EUDAMED.

Fictional lookup packet

To illustrate how to navigate these complementary databases without relying on sensitive commercial files, the following labeled synthetic packet exercises a complete supplier audit workflow. All identifiers, company names, and registration numbers in this packet are entirely fictional and cannot be mistaken for real regulatory determinations.

1. Step 1 — Verify the Physical Package in AccessGUDID: The auditor enters Primary DI 00899999000018 into AccessGUDID. In this fictional walkthrough, that is the portal for labeler-submitted identification fields such as brand name, version/model, GMDN term, MRI safety status, latex flag, and package quantity. Do not treat the synthetic identifiers in this packet as a live GUDID row. What this proves: This step tests whether the identifier on the label corresponds to a public GUDID identification record. What this does NOT prove: It does not prove the plant is inspected, does not disclose the FDA listing number, and does not verify active marketing clearance.

2. Step 2 — Verify the Manufacturing Establishment in rl.cfm: The auditor navigates to FDA's Establishment Registration and Device Listing database (rl.cfm) and searches for 'ApexPulse Healthcare Technologies LLC' or FEI 9999999999. The public database returns one establishment matching the physical plant address. It indicates: Status = 'Active'; Declared Activities = 'Manufacturer' and 'Contract Sterilizer'; Listed Product Codes = 'MWI'; Listed Proprietary Names = 'ApexPulse 500'. What this proves: The facility appears as Active for the current public weekly build and has listed product code MWI. That appearance is consistent with a processed annual registration; it is not a fee receipt and is not marketing authorization. What this does NOT prove: It does not verify whether K999999 was legally cleared or whether the device is 'FDA approved.'

3. Step 3 — Reconcile the Listing Number Requirement: The hospital procurement checklist requires an 'FDA Listing Number.' The auditor does not find this number in AccessGUDID or on rl.cfm. Recognizing that 21 CFR 807.37(b)(2) statutorily withholds listing numbers from public view, the auditor requests a copy of the manufacturer's official FURLS DRLM listing confirmation page. The manufacturer provides the internal DRLM PDF showing assigned listing number D999999, satisfying the supply-chain documentation standard.

4. Step 4 — Verify Marketing Authorization in the 510(k) Database: To confirm substantial equivalence, the auditor opens the FDA 510(k) Premarket Notification database and searches submission number K999999. The database returns the official substantial equivalence determination letter, cleared indications for use, and Summary of Safety and Effectiveness, confirming lawful marketing authorization.

By following this structured, four-step investigative workflow, regulatory affairs and quality teams avoid false non-conformance citations, adhere strictly to statutory confidentiality boundaries, and maintain audit files that withstand rigorous regulatory inspection.