The manufacturer who owns no factory

A small device company that outsources every physical step of making its product — molding, assembly, sterilization, packaging — can read “establishment registration” and reasonably conclude the duty belongs to whoever actually runs the line. FDA’s own registration framework draws the boundary somewhere else. The company that only wrote the specifications the contract manufacturer builds to is, in the regulation’s own vocabulary, a manufacturer in its own right — and it registers alone.

A name the regulation reaches, not one it defines

Look for “specification developer” as its own defined term in 21 CFR 807.3 and you won’t find a lettered paragraph with that exact heading. What you find instead is 807.3’s definition of “owner or operator” — the person whose registration duty the rest of Part 807 turns on — written broadly enough to catch a party that never touches the device at all. FDA’s parallel Quality System Regulation makes the same reach explicit rather than implicit: 21 CFR 820.3 states that “manufacturer includes, but is not limited to, those who perform the functions of contract sterilization, installation, relabeling, remanufacturing, repacking, or specification development.” Specification development sits on that list as its own function, on equal footing with sterilizing or assembling. “Specification developer” is the name FDA’s own registration materials and its FURLS database give to the party that performs it — a working label for a function the definitions reach, not a term the definitions coin.

FDA’s own introduction says it plainly

FDA’s registration-and-listing introductory guidance spells out the scenario by name: a specification developer is an establishment that develops the specifications for a device marketed under its own name, performs no manufacturing itself, and uses a contract manufacturer to produce the finished device. The same guidance lists who is required to register under 21 CFR 807.20(a)(1) — and the specification developer sits on that list beside the manufacturer, the remanufacturer, the contract manufacturer, and the contract sterilizer, not behind any of them. Nothing in the requirement waits for the specification developer’s contract manufacturer to register first, and nothing lets one registration stand in for the other. Two parties, two establishments, two registrations — even when only one of them ever has the device in its hands.

Where it shows up in the public record

The distinction isn’t just a filing technicality; it is visible in the record openFDA republishes. The device registrations and listings endpoint carries an establishment_type field on every establishment record — an array, because one establishment can hold more than one role at once — and Specification Developer is one of the values that field actually takes, distinct from Manufacturer and from Contract Manufacturer. Reading a competitor’s or a supplier’s registration record, that field is the fast, correct way to tell which role you’re actually looking at — a firm listed only as a specification developer is telling you, in FDA’s own words, that it owns the design and someone else owns the equipment.

The practice

For a device company weighing whether to build in-house or design-and-outsource, the registration duty is not a reason to pick one structure over the other — it attaches either way, and knowing that early avoids discovering it at the same moment a 510(k) is due. For anyone reading someone else’s record — a supplier being vetted, a competitor being watched — the establishment_type field is the one that actually answers “who makes this,” where a bare firm name on a label does not. Whether a specific company’s own structure triggers this duty, and how it should register, is a determination for that company’s own regulatory counsel working its own facts; this is a description of how the public record is built and what it discloses, regulatory intelligence and method, never regulatory advice.