FDA Manufacturer Registration Database: M&A Source Matrix

Executive Summary

There is no single FDA manufacturer registration database that identifies every regulated manufacturer, factory and corporate owner. The correct source depends on the activity and on whether the analyst needs a facility, a registered operator, a product listing or product licensure. The first distinction is between an establishment and a company; Census expressly notes that these units are not necessarily equivalent. Registration also differs from approval under both drug and device regulations. ^{[1] [2] [3]}

For current drug-establishment evidence, DECRS is updated each business day, with program-specific exclusions. For devices, FDA's interactive registration/listing search is normally updated weekly and returns no more than 100 establishments per search. Those are different evidence systems with different coverage limits, not interchangeable routes to a complete manufacturer universe. ^{[4] [5]} Broader research needs documented extraction and joins, rather than an assumption that displayed results exhaust the market.

Public access is unequal. Food registration disclosure is restricted, including specified derived identifying information. Cosmetic law makes product listing numbers nonpublic and protects specified facility-product information, while allowing one contract-facility registration to serve multiple responsible persons. ^[6] Device disclosure rules can withhold fields that reveal confidential commercial relationships. The absence of a public customer-brand link therefore does not establish that no manufacturing relationship exists. ^{[7] [8] [9]}

For acquisition research, the recommended output is an entity-facility-product crosswalk, with source URL, query, identifier namespace, operation, status, dates, matching evidence and unresolved conflicts. D-U-N-S Numbers can be branch-level; a CIK identifies a disclosure filer; GLEIF parent relationships follow accounting consolidation. These keys support different joins. ^{[10] [11] [12]} FDA's cosmetic totals, dated June 30, 2026, were 16,398 active facility registrations and 1,298,361 active product listings. ^[13] These program units cannot be read as company or acquisition-target counts. ^[1] The report supplies a program selector, worksheet and freshness rules. It treats registration as scoped regulatory evidence and keeps ownership, production scale, profitability and willingness to sell as separate questions. No full FDA file was processed and no acquisition-market population is claimed.

Introduction and Background

The query FDA manufacturer registration database names a research need rather than a single authoritative directory. The Food and Drug Administration (FDA) administers program-specific records. An analyst must first identify the regulated activity, then decide whether the relevant record describes an establishment, an operator, a listed product or a licensed product. Registration itself does not establish approval: the drug and device regulations expressly separate those concepts. ^{[2] [3]}

For private equity (PE) origination, the useful question is narrower than whether a business is “FDA registered.” It is whether a dated record identifies a facility performing an activity within the acquisition mandate, and whether that facility can be connected to the correct operating entity. The Census Bureau's distinction between an establishment and a company illustrates the counting problem: a company can encompass multiple establishments. Its statistical definition should not replace an FDA program definition, but it warns against treating site rows as independent acquisition targets. ^[1]

A brand creates another identity problem. The United States Patent and Trademark Office (USPTO) defines the trademark owner as the legal entity owning the trademark; GS1 assigns responsibility for trade-item numbering principally to the brand owner regardless of who manufactures the item. Neither relationship, standing alone, identifies the production operator. ^{[14] [15]}

This report therefore treats registration searches as inputs to target identification and corroboration. It proposes a maintained source selector, an entity-facility-product crosswalk and a freshness calculation. These are analyst procedures, not a filing guide or a regulatory-compliance opinion. Docket describes its research output as answers accompanied by a source, supporting excerpt and collection date; that evidence format is useful here because registration, identity and ownership require separate support.

Key Changes

The changes below concern the research process an origination team should adopt. They do not imply that every underlying regulation changed recently.

Replace the universal-register assumption with a program selector

Public disclosure differs by program. Device registration and listing information is generally open subject to specified exceptions. Food registration documents and the registered-facility list have a confidentiality rule, including protection for derived information identifying or locating a registered person. A missing public food lookup therefore calls for a different evidence path, rather than more variations of a device search. ^{[9] [16]}

Cosmetics require particular care. The statute bars publication of cosmetic product listing numbers and protects specified registration and listing information. That is a selective disclosure rule; it does not justify saying that every cosmetic facility field is confidential. A searchable facility identity and proof of a current cosmetic registration are different research outcomes. ^{[8] [6]}

Separate operational roles from brand visibility

Drug registration contents include business names, physical address and operations performed. Device requirements can extend to businesses that develop specifications for devices manufactured by another party. Analysts should retain the role attached to a record rather than assigning “manufacturer” from the company name alone. ^{[17] [18]}

Public device records also withhold certain proprietary names and premarket submission numbers where disclosure would reveal a confidential business relationship involving contract manufacturers, sterilizers or private label manufacturers. A public search is consequently unsuitable for proving every brand-to-factory relationship. ^[9]

Make ownership an independent question

An identifier's meaning determines what a match supports. A Securities and Exchange Commission (SEC) Central Index Key (CIK) identifies disclosure filers. A Global Legal Entity Identifier Foundation (GLEIF) Legal Entity Identifier (LEI) record identifies a legal entity, while parent relationships follow accounting consolidation. Neither key should silently replace a facility identifier. ^{[11] [12]}

State records can add legal identity without resolving ownership. California expressly says that owner, shareholder and employee information is not made of record, even though its business search provides other entity and management information. The correct response is an open ownership question, not an assumption of independence or founder ownership. ^[19]

Registry Selection Across Programs

Table 1 is the source selector, checked during this research session on October 11, 2026. “Not established” means that the session did not verify the stated public capability. It is not a claim that the capability cannot exist. Registration renewal and public database refresh are recorded separately.

The practical divide is between public candidate-generation sources, restricted registration evidence, and product-level corroboration. For food, the registration statute covers a broader activity set than manufacturing alone, including packing and holding, while excluding specified categories such as farms and retail food establishments. That scope prevents an analyst from equating the underlying registration population with a thesis-specific manufacturing market. ^{[7] [22]}

The matrix also explains why identifiers must carry their program. A D-U-N-S Number can operate at branch level; an LEI describes a legal entity; a trademark owner is a brand-related legal entity. Storing only a number without its source namespace makes those distinctions disappear. ^{[10] [12] [14]}

Drug and Medical Device Searches

Drug establishment registration search

Start a drug search with the facility's recorded names and location. Current drug registration rules require names used in business and other known names, along with the physical address and operations. Preserve the original spelling before creating normalized aliases; the normalized value should help find records without overwriting the evidence. ^[17]

DECRS excludes sole human-drug outsourcing-facility registrations, although other registered operations can bring a facility into scope. Annual wholesale-distributor and third-party-logistics licensure reports are also outside its coverage. Initial or annual registrations submitted during October through December remain current through the following calendar year; submissions outside that window do not extend expiry beyond the current calendar year. ^[4] Record the facility class before interpreting a non-result, and treat the excluded-status download as another evidence path.

The drug rules also separate registration from lawful marketing. Registration or listing can evidence an intention to perform, or performance of, specified drug-related operations; it does not itself establish approval or that a product may legally be marketed. A PE screen should therefore phrase the result as “current establishment record found for the documented activity,” rather than “approved manufacturer.” ^[2]

The final rule's explanation assigns registration/listing duties to entities performing the relevant operations, rather than solely acting as private label distributors. ^[33]

Product corroboration belongs in a separate branch. The National Drug Code (NDC) Directory is a listing source whose labeler may be a manufacturer, repackager or relabeler; its published exclusions include drugs manufactured under contract. DailyMed, maintained by the National Library of Medicine (NLM), supplies recent company-submitted, in-use labeling and includes some FDA-regulated products that are not FDA-approved. ^{[34] [35]}

Those sources can add a product name, labeler or declared relationship to the worksheet. They cannot independently establish which site currently produces commercial volume. NLM says it does not review Structured Product Labeling (SPL) content before publication. Preserve the distinction between a company-submitted labeling statement and an independently verified production relationship. ^[35]

Medical device establishment registration database

Search the device form using separate identity and category passes. First try establishment/trade name, location and registration/FEI information; then examine owner/operator fields and device product codes. The public form's update notice describes weekly updates generally completed by Monday evening and warns of a submission-to-publication delay. A search date is therefore not necessarily a record's effective date. ^[20]

Establishment role is a decisive filter. FDA defines a contract manufacturer as manufacturing a finished device to another establishment's specifications; a specification developer can distribute devices under its own name while doing no manufacturing. A component business can also fall outside the finished-device registration categories. These distinctions matter when the mandate calls for physical manufacturing operations rather than brand ownership or design activity. ^[36]

For broad work, move from interactive search to documented exports instead of treating the displayed results as a population. The proposed extraction procedure is:

• Define the scope: record establishment role, product category, geography and exclusions before extraction.
• Retain the query: save the exact fields and filters used, including aliases and partial-name searches.
• Check saturation: treat a result at the interface cap as potentially truncated, not as a complete segment.
• Choose the route: use the official download path for broader work, retaining each file's version and layout.
• Join deliberately: preserve facility, owner/operator and listing tables separately until keys are reconciled.
• Measure processing: record rows loaded, rejected, joined and left unresolved for the actual extraction.
• Qualify the outcome: describe an enumerated file-based result only after the relevant complete file set has been processed.

An Application Programming Interface (API) adds another limit rather than removing all limits. The openFDA registration/listing endpoint allows at most 1,000 records per call. Pagination, export scope and dataset timing still require explicit handling. This report verified documentation; it did not download or count the full registration datasets. ^[37]

Food, Cosmetics and Other Program Boundaries

For an FDA food facility registration search, the central constraint is disclosure. The food registration statute protects the facility list and registration documents; the implementing rule also protects specified derived identifying information. The rule does not extend that restriction to information obtained by other means or previously disclosed publicly. A company-published plant page can consequently corroborate a location without becoming a public registration-status record. ^{[22] [7]}

The proposed food evidence path is to collect a dated copy of the facility's registration evidence where available through the operator, and separately match the operating entity and location. For animal food, FDA confirms that the same registration framework covers food for human or animal consumption, subject to exemptions. Do not route feed facilities to animal-drug records merely because the customer market is veterinary. ^[38]

For an FDA cosmetic facility registration search, distinguish what is known from what was not verified. This session verified FDA's Cosmetics Direct submission description, FEI identity requirements and aggregate reporting, but did not establish an unrestricted public MoCRA facility-registry search. The Modernization of Cosmetics Regulation Act (MoCRA) statute protects specified links and makes product listing numbers nonpublic. That supports a limitation on disclosed relationships, not blanket confidentiality of every field. ^{[8] [6]}

Contract production reinforces the distinction. The cosmetic statute permits a single registration for a contract facility manufacturing for multiple responsible persons. A site-to-brand relationship therefore requires additional evidence; one registration row cannot be counted once for every customer as though it were a separate factory. ^{[8] [6]}

Apply the blood or tissue source's status filter before adding a candidate to the target universe. Keep the displayed status in the research record, rather than deleting it from the extracted fields. For HCT/Ps, registration under the tissue pathway is distinct from licensure or approval, and location-specific registration numbers remain facility keys. ^[26]

The FDA biologics establishment database query also needs a product-versus-site distinction. Purple Book can support licensure questions. A tissue establishment register supports a different unit and program relationship. Combining them may help corroborate a business's activities, but neither record alone provides a complete corporate ownership tree. Corporate consolidation evidence belongs in a legal-entity source such as GLEIF, interpreted within its accounting scope. ^{[28] [12]}

Animal drug and veterinary biological sources should be partitioned before matching. APHIS expressly notes that multiple manufacturers or permittees may share the same product code and true name, and distinguishes true names from firm-assigned trade names. Preserve the establishment license number alongside product attributes; joining on the product code alone can create unsupported firm links. ^[30]

Implementation Considerations and Process Changes

Resolve the establishment row to a company

The proposed crosswalk has separate objects for legal entity, facility, registered role, brand and product. Edges between them need their own evidence. A shared word, address or website is a candidate match; it becomes an accepted relationship only when the supporting material explains what the relationship is.

Table 2 defines the worksheet. Each cell is a field specification or a source limitation, rather than a prefilled answer about an actual target.

The crosswalk's value is that it makes a join inspectable. A legal registered address, an operating plant address and a branch identifier can all be valid while pointing to different units. For foreign establishments, consult the applicable jurisdiction's corporate evidence rather than assuming U.S. disclosure patterns apply. Companies House's available registered-address information illustrates one jurisdiction's identity path, not a universal ownership standard. ^[41]

The proposed match-review sequence is:

• Compare names: use normalized aliases to find candidates while preserving the original record.
• Compare locations: distinguish a plant, registered office, branch and mailing address.
• Confirm roles: accept an operating relationship only where the evidence supports that role.
• Record the edge: attach the supporting source and date to the facility-to-entity relationship.

Preserve uncertainty rather than forcing a merge

Use the following triage outcomes as a proposed analyst convention:

• Matched facility and entity: a program row and independent entity evidence support the same identified operating relationship.
• Matched facility, parent unresolved: the location and operator match, while ultimate ownership remains open.
• Matched brand, factory unresolved: trademark or product evidence identifies a brand relationship without a supported production-site link.
• Possible match: names or addresses overlap, but the relationship remains unsupported.
• No result in a scoped search: the record was not found in the specified source using recorded queries.
• Restricted public evidence: the program does not expose the required field through the verified public route.
• Outside source scope: the candidate's activity belongs to another program or an excluded class.
• Conflicting records: available observations disagree on a material field and require reconciliation.

Ownership uncertainty is particularly important. California's explicit absence of recorded owner/shareholder information is a reason to seek other evidence. GLEIF's accounting-parent relationship is a different kind of answer, not a substitute for every question about beneficial ownership or an acquisition perimeter. ^{[19] [12]}

Refresh the matching evidence as well as the FDA evidence. EPA states that business updates may not immediately appear in FRS because it refreshes periodically. A recent corporate page and an older facility record may therefore need a temporal reconciliation rather than an immediate duplicate decision. ^[40]

Data Analysis and Evidence

The quantitative core is freshness and denominator control, not an unsupported estimate of the acquisition market. Table 3 separates publication timing from the registrant's obligations. An observed download date should not overwrite an establishment's status or a legally defined renewal window.

The table highlights distinct clocks. Define publication age as collection date minus the source's stated data-current-through date. Define observation age as collection date minus the underlying record's dated observation, if available. Define renewal relevance as the relationship between the record's registration period and the applicable program window. These are proposed research calculations, not FDA status determinations.

For the observed DECRS dates, publication age is two calendar days, calculated from the reported data date and this session's collection date. ^[46] That calculation does not imply a missed update: the program's documented schedule uses business days, while this calculation uses calendar days. Neither age establishes when an individual facility changed its operations. The legal drug update requirement addresses certain changes on a separate clock. ^[43]

Other systems reinforce the need to label time correctly. EPA describes a lag between a business update and its appearance in FRS. A cross-source match should record both dates if they are available, and show an unknown where they are not. Replacing every timestamp with the analyst's most recent visit makes older underlying evidence appear newly observed. ^[40]

For population analysis, distinguish rows, locations, entities and potential transaction perimeters. Census explicitly separates establishments from companies. A broad facility file may include multiple sites belonging to one business, while a branded product may be numbered by a company that outsources production. Count each unit separately before explaining how the target universe was consolidated. ^{[1] [15]}

A simple proposed reconciliation records raw rows, distinct facility keys, accepted facility-to-entity edges and distinct resolved entities. Report unresolved edges alongside the accepted count. Do not divide a PE shortlist by a register's row count and call the result market coverage unless the source scope, units and thesis perimeter actually align. The establishment/company distinction is the evidence for that warning; the measurement convention is analytical. ^[1]

No full FDA download was processed for this report. It makes no measured claim about the number of acquirable manufacturers, ownership concentration, revenue or production capacity. Product-labeling sources supply a different kind of evidence: DailyMed itself cautions that its in-use labeling can differ from the most recent FDA-approved labeling. ^[35]

FDA's cosmetic summary reports 16,398 unique active facility registrations and 1,298,361 unique active product listings as of June 30, 2026. ^[13] These are different reporting units, not acquisition-target counts. Exemptions and contract production also prevent a direct manufacturer-to-product interpretation.

Case Studies and Real-World Examples

Brand, contract manufacturer and facility (Hypothetical Example)

The following companies and relationships are fictional. Harborwell Brand LLC markets a diagnostic accessory. Pinebridge Devices Inc. operates a contract-manufacturing site. The analyst finds a device establishment row associated with Pinebridge and a trademark record associated with Harborwell. The task is to determine whether the companies are connected and which, if either, matches a manufacturing acquisition mandate.

Begin with separate records. The trademark supports a brand-owner relationship, consistent with USPTO's definition; it does not place Harborwell at the manufacturing site. The establishment row supports only its documented program role. A device contract manufacturer's role is distinct from a specification developer's role, and public disclosures may withhold confidential customer relationships. ^{[14] [9]}

Suppose both fictional companies use the same distributor's mailing address on product materials. The analyst retains that observation but does not merge the legal entities. A registered corporate address can identify an entity without identifying its production location; jurisdiction-specific corporate sources must be read on their own terms. ^[41]

Suppose a trade-item number is assigned through Harborwell. GS1's brand-owner rule makes this consistent with outsourced manufacturing, but it does not prove that Pinebridge is the supplier. The tentative brand-to-factory edge remains unresolved until a source expressly connects the two. ^[15]

The fictional handoff then has several distinct outcomes:

• Pinebridge facility: retain the matched site and its documented establishment role.
• Pinebridge entity: attach the independently matched legal identity and keep parent ownership open if unsupported.
• Harborwell brand: retain the trademark-owner relationship separately from physical production.
• Commercial relationship: mark the proposed Harborwell-Pinebridge manufacturing edge unresolved.
• Acquisition fit: ask for separate evidence on ownership, scale, capabilities and the contemplated transaction perimeter.

This avoids counting a brand, a contractor and a site as interchangeable targets. It also avoids treating absent public parent evidence as proof of independence: the California source illustrates why a registry can identify an entity while lacking recorded shareholder information. ^[19]

Implications and Future Directions

A maintained FDA selector should be a small operational reference, rather than a universal “registered manufacturer” flag. For every program, store the verified entry point, recorded unit, disclosure limitations, renewal rule, observed public cadence, download path and last-checked date. Where public refresh or export capabilities remain unverified, preserve the unknown instead of transferring a schedule from another program.

Maintenance should also track the legal basis for interpretation. Device registration's nonapproval rule, food disclosure restrictions and the cosmetic product-number restriction answer different questions. A change to a page's interface should trigger a review of the selector without silently changing the underlying conclusion about approval or ownership. ^{[3] [22] [8]}

Origination teams should make the investment evidence a separate workstream. A SEC identifier helps locate disclosure-filer evidence; GLEIF can add a defined accounting-parent relationship; a trademark record identifies ownership of a mark. Each can contribute to the target file, but none converts a facility registration into a supported estimate of profitability, capacity or willingness to sell. ^{[11] [12] [14]}

Where the mandate concerns contract manufacturing, research effort should focus on verified operations and on the limits of customer linkage. FDA's disclosure exceptions prevent a public device listing from serving as a comprehensive customer list. This is a source limitation to record in a handoff, rather than a gap to fill through inference. ^[9]

The proposed ongoing process is:

• Recheck entry points: verify that saved search and download links still lead to the intended program.
• Version the selector: retain the previous scope and cadence statements when they change.
• Refresh material fields: prioritize identity, operational role and registration evidence before lower-impact descriptive fields.
• Preserve prior observations: record the source and date of a correction instead of erasing the earlier observation.
• Review unresolved joins: revisit facility-to-entity and entity-to-parent links using field-appropriate evidence.
• Separate conclusions: report registration corroboration, identity resolution and acquisition fit as distinct findings.

Frequently Asked Questions (FAQs)

How can an analyst verify a manufacturer's FDA registration?

Choose the program from the activity and product category, then search the verified public source where one exists. Match facility name, location, identifier, role and status rather than only the brand. Where food registration evidence is restricted, record the limitation and seek operator-provided evidence. Registration and approval remain separate conclusions under the drug and device rules. ^{[7] [2] [3]}

Can an FDA registration number reveal who owns a manufacturer?

Treat the number as a program key. Resolve the facility to a legal entity before researching parent ownership. GLEIF's parent information follows accounting consolidation, and California's registry explicitly lacks recorded owner/shareholder information. A successful identifier match therefore does not finish the ownership analysis. ^{[12] [19]}

Is a product listing enough to identify the factory?

It depends on the source and role. Recent submitted labeling can identify a label-related entity, while a trade-item number can be assigned by a brand owner regardless of manufacturing party. These sources can corroborate a declared relationship but should not be treated as universal production-site keys. ^{[35] [15]}

Does a search non-result prove a business is unregistered?

No general conclusion follows without source scope and access. Food registration disclosure is restricted; corporate and facility identifiers also describe different units. Record the source, query and date of the non-result, then determine whether the required evidence was publicly searchable and within that program's scope. ^{[22] [1]}

Conclusion

An FDA manufacturer registration database search becomes useful to PE origination when it is framed around a specific activity, a defined record unit and an explicit evidence question. The report's source matrix separates public establishment searches, restricted registration evidence and product-licensure corroboration. Its crosswalk keeps the facility, operating entity, brand and product distinct until the supporting relationship is established.

The strongest practical output is a dated, reviewable target record: what was searched, what matched, the program role and status, how the facility was connected to the entity, and which ownership or investment questions remain unresolved. The entity-establishment distinction is fundamental because multiple facilities can belong to a company; brand ownership is also a different relationship from physical manufacturing. ^{[1] [14]}

The same discipline applies to time. Database publication, record observation and registration renewal are different clocks. An analyst can calculate publication age and explain search or API limits without representing those calculations as a regulatory determination or an estimate of acquisition-market completeness.

Registration is therefore evidence to interpret within its program. It does not supply an acquisition thesis, profitability assessment or sale intention. A maintained selector, explicit source limits and reversible matching decisions allow an origination team to use FDA records for the questions they can support while keeping the remaining diligence questions visible.