Start a request
Blog

What does a contract manufacturer need to build a 510(k) medical device?

As of November 2026, a contract manufacturer building your finished 510(k) device must run a quality system that meets FDA's Quality Management System Regulation (QMSR), in force since February 2, 2026 and built on ISO 13485, and must register with FDA, list the device and pay $13,785 a year. FDA does not require an ISO 13485 certificate.

As the specification developer, the company that sets the design and holds the 510(k), you need your own quality system, scaled to your work but including management review, internal audits, corrective action, training and document control. You also register, pay the same fee, and are responsible for the design file, the label and its unique device identifier (UDI), complaints, adverse-event reports and recalls. The manufacturer is responsible for production: its quality system, its suppliers, a record of every build, and validation of steps a final test can't check. Registration and listing for the device wait until FDA clears the 510(k).

Facts as of November 2026. FDA rules and fees change, and this is general information, not regulatory or legal advice. Before you rely on it, confirm what your device needs with FDA or a regulatory consultant.

Who does what: the specification developer (OEM) or the contract manufacturer?

FDA's quality rule treats you both as manufacturers. 21 CFR Part 820 covers anyone who designs, makes, assembles or processes a finished device, including a specification developer (contracts and industry guides often say OEM or brand owner), and each company meets the requirements that fit its work. The table shows the usual split when you design the device and a contract manufacturer (CM) builds, tests and labels it; a written quality agreement settles the details.

Task You (specification developer, 510(k) holder) Contract manufacturer Rule
Registration and listing Register your company, list the device with its 510(k) number, pay the fee Register its site, list the device, pay its own fee 21 CFR 807.20
Quality system A full quality system scaled to your work: management review, internal audits, corrective action (CAPA), document and record control, training, risk management, design controls, complaints, MDRs, recalls and purchasing (the CM is your supplier) Its own full quality system, centered on production: training, calibrated equipment, nonconforming product, corrective action 21 CFR 820.1(a), 820.10, ISO 13485
Design controls and design transfer Own the design and every change; hand over released drawings, parts list, firmware, test specifications and labels Confirm the design can be built and tested as specified; propose changes through your change control ISO 13485 clause 7.3, required for Class II by 21 CFR 820.10(c)
Purchasing and supplier controls Evaluate and monitor the CM; approve critical parts and their makers Control the suppliers of parts it buys; tell you before changing a part, process, sub-supplier or site ISO 13485 clauses 4.1.5 and 7.4
Production records Set what each record must show; get copies or access Keep a record for each unit or batch: quantity built and released, test results, UDI ISO 13485 clause 7.5.1, 21 CFR 820.35
Process validation Approve protocols and reports for critical steps Validate the steps whose result a later test can't fully check ISO 13485 clause 7.5.6
Labeling and UDI Usually the labeler: get the device identifier, submit it to FDA's GUDID database, approve artwork Apply labels, check labeling and UDI accuracy before release for use, prevent mix-ups 21 CFR 801, 830, 820.45
Complaints and MDR reports Take complaints; file Medical Device Reports (MDRs) within 30 calendar days, or 5 work days in some cases Investigate returned units and production records when you ask 21 CFR 803
Recalls (corrections and removals) Decide, and report to FDA within 10 working days when the action reduces a risk to health Trace lots and serial numbers, quarantine stock, rework 21 CFR 806

Part 820 doesn't apply to makers of components, and they don't register (807.65), so a board assembler or a molder supplying your CM is controlled through the CM's purchasing controls.

If you also sell a non-medical version, ask early whether its factory can build the medical one, which needs a QMSR quality system, an FDA registration and the records above.

The reports fall to you: FDA's reporting guidance says a contract manufacturer that doesn't distribute or market the devices it builds has no duty to file MDRs under 803.50. Your clock starts when you learn of an event, so how fast the CM sends records matters.

Your company's name goes on the label with a phrase such as "Manufactured for" (801.1). Every Class II label and package needs a UDI, and the compliance dates have all passed, so a new device carries one from the first unit. A device meant to be used more than once and to undergo high-level disinfection or sterilization before each use also needs the UDI marked on the device itself (801.45); FDA doesn't count cleaning or lower-level disinfection alone. If yours needs it, the CM plans that marking before the mold is made.

Which production steps does the manufacturer have to validate?

A contract manufacturer validates the steps whose output a test of the finished unit can't fully check, as ISO 13485 requires. The usual method, from the Global Harmonization Task Force's process validation guidance, has three stages:

  1. Installation qualification (IQ): the equipment is installed to its approved specification.
  2. Operational qualification (OQ): the process limits are set so that product made inside them meets every requirement.
  3. Performance qualification (PQ): the process, under normal conditions, makes good product consistently.

The guidance lists injection molding, sterilization and sterile packaging sealing among processes that should be validated, and visual inspection of circuit boards and the making and testing of wiring harnesses among those that checking can cover. For a supplier's part, such as a molded housing, the CM or you either require the molder, in the purchase order, to validate its process (IQ, OQ and PQ for critical parts), or inspect the parts and record why that is enough.

For an electronic device, steps often validated include reflow soldering, conformal coating and potting, ultrasonic welding and adhesive bonding; firmware loading is usually checked by reading back a checksum. The CM also validates its test-station and programming software and its test methods, since they decide which units pass; for the software, FDA's guidance on production and quality system software points to ISO 13485 subclauses 4.1.6, 7.5.6 and 7.6. The CM normally writes and runs the protocols; you approve them for critical steps and keep the reports referenced in your files.

What changed when the QMSR took effect on February 2, 2026?

FDA's final rule, published February 2, 2024, replaced most of the old Quality System Regulation with a reference to ISO 13485:2016, the international standard for medical device quality systems, and added FDA's own rules where the standard is silent. What changed for you and your CM:

  • The design history file (DHF) becomes the design and development file; the device master record (DMR) moves into the medical device file (MDF), the specifications and procedures in use on the floor; and the device history record (DHR) becomes the record for each device or batch.
  • FDA investigators can now read management reviews, internal audits and supplier audits at your CM and your company; the old rule kept those records out of inspections.
  • FDA stopped using its old inspection technique (QSIT) on February 2, 2026 and now inspects under a program aligned with ISO 13485.
  • ISO 13485 applies risk management from design through purchasing and production; most teams use ISO 14971.
  • Design controls, which cover firmware, apply to every Class II device and to Class I devices automated with software.
  • FDA added requirements of its own: complaint records must hold set items, including the UDI; each device or batch record carries its UDI; and labeling, including the UDI, is checked for accuracy before release for use, with the check and release recorded. Where ISO 13485 and FDA's rules differ, FDA's rules apply.

Does the contract manufacturer need ISO 13485 certification?

Not for FDA: the QMSR makes the contract manufacturer meet ISO 13485, but in the final rule FDA says it "does not intend to require" certification, won't rely on certificates for oversight, and won't issue one after an inspection. A certificate from an accredited registrar is still a useful first screen: it shows the CM's system has passed outside audits, and regulators outside the US lean on certificates more. FDA may also accept reports from the Medical Device Single Audit Program (MDSAP), one audit shared by five countries' regulators, in place of routine inspections. Check a certificate's scope (which site, which work) and its expiry date, and keep asking questions; FDA notes that certification "may not provide adequate assurances of supplier quality without further evaluation."

What are FDA's registration and 510(k) fees for fiscal 2027?

FDA's fiscal 2027 runs from October 1, 2026 to September 30, 2027. From its fee notice:

  • Registration costs $13,785 a year for each establishment (FDA's word for a registered site), up from $11,423 in fiscal 2026, with no small-business rate. The fee covers a site, however many devices or customers it serves, so a CM that already builds devices is already paying it; a CM outside the US pays too.
  • A 510(k) costs $28,653, or $7,163 for a small business, one with $100 million or less in gross receipts or sales in its latest tax year, counting affiliates. Request small-business status at least 60 days before the fee is due, every fiscal year.
  • Since fiscal 2026, FDA may waive the yearly registration fee for a small business with $1,000,000 or less in gross receipts or sales if paying would be a financial hardship. The waiver excludes the initial registration, so the first year is paid in full.

With small-business status, a company that submits its 510(k) and first registers in fiscal 2027 pays FDA $20,948: $7,163 for the 510(k) and $13,785 for its own registration. The 510(k) fee is the one in force when you submit, and registration renews every October 1 to December 31 (807.22), so a first registration late in a fiscal year brings the next year's fee within months.

Do you register before or after FDA clears the 510(k)?

You register and list after FDA clears the 510(k): FDA's page on when to register and list says to wait for clearance, then register and list within 30 days of putting the device into commercial distribution, paying the fee first. The listing carries the 510(k) number, and both are renewed each year (807.22). A factory outside the US must be registered before it exports the device.

Building units before clearance is normal; ISO 13485 asks for design validation on units representative of production, often the first pilot build. Selling has to wait. Where you can, choose the CM before verification testing, since your 510(k) test reports describe the units you tested and units built differently may need retesting.

Under its current user-fee agreement (MDUFA V, running through September 30, 2027), FDA's goal is a decision on 95% of 510(k)s within 90 FDA days, which leave out time spent waiting for your answers. FDA and industry also share a goal of an average of 112 calendar days from submission to decision for 510(k)s received in fiscal 2025 to 2027. Both are targets, not deadlines, so plan the production date around a decision that can slip and changes FDA's questions may cause.

Which standards touch the manufacturer, and which stay with your design team?

Declaring conformity to FDA-recognized standards in a 510(k) is voluntary but common. The standards are mostly the design team's work, but they reach the factory because a test report describes one build. From FDA's recognized standards database, as of November 2026:

  • IEC 60601-1 (basic safety and essential performance; edition 3.2 of 2020, recognition number 19-49) and its US version, ANSI/AAMI ES60601-1. The test report lists the critical components it was tested with, such as the power supply, fuses, battery and the housing plastic's flammability rating, and the CM swaps none of them without your approval. Production often adds safety tests on every unit, such as dielectric strength (hi-pot) and leakage current, as your risk file calls for.
  • IEC 60601-1-2 (electromagnetic compatibility; edition 4.1 of 2020, recognition number 19-36, partly recognized). A substitute part, a new board revision, rerouted cables or a changed ground can change the result.
  • ISO 10993-1 (biological evaluation) for parts that touch the patient, such as electrodes, straps and housings held against skin. FDA partly recognized the 2025 edition in May 2026 and will accept the 2018 edition until July 1, 2029. It covers the finished device, so the CM controls what ends up on those parts, from mold release and adhesives to the material supplier.
  • The design team's own standards: ISO 14971 (risk management), IEC 62304 (software), IEC 62366-1 (usability) and, for home use, IEC 60601-1-11. The CM loads the released firmware and feeds production risks into your risk file.

If the device has a radio, FCC rules still apply; see Which US tests does an electronic product need before you sell it? FDA's cybersecurity guidance (reissued February 3, 2026) counts Bluetooth, Wi-Fi, cellular and even an internet-capable USB port as ways to connect to the internet, so a device with firmware and any of these is likely a "cyber device" under section 524B of the FD&C Act. Its 510(k) needs cybersecurity documentation, including a software bill of materials (SBOM), and loading signed firmware and locking debug ports become controlled steps at the CM.

What changes if the device is made outside the US?

A factory outside the US registers, lists and pays like a US one, and names one US agent, based in the US, who helps FDA reach the factory and schedule inspections (807.40).

In May 2025 FDA announced more unannounced inspections at foreign sites, saying it does about 3,000 foreign inspections a year across food, drugs and devices in more than 90 countries, and that foreign sites had serious deficiencies more than twice as often as US ones. It can act against a firm that delays, denies or limits an inspection.

Each customs entry carries FDA data. FDA's list of entry codes includes the foreign manufacturer's registration number (DEV), which must be the factory's and not yours; the device listing number (LST); and the 510(k) number (PM#), which must match the listing. Data that don't match can hold the shipment, so all three have to be in place before the first one ships. If your company brings the devices in, it also registers as the initial importer; FDA's chart of who must register shows which roles register, list and pay.

Customs duty depends on the device's tariff code and origin, as for any import; see US tariffs on electronics from China, Korea, Vietnam and Mexico.

Does a non-sterile electronic device need a clean room?

Usually not: neither Part 820 nor ISO 13485 calls for a clean room for an electronic device sold non-sterile. ISO 13485 asks the manufacturer to document work-environment and cleanliness requirements where they affect the product. For most electronic devices, that means the controls a good electronics line already uses: static control (ANSI/ESD S20.20), handling of moisture-sensitive parts (IPC/JEDEC J-STD-033), controlled flux residue (washed boards, or no-clean flux within a cleanliness limit), and controlled storage. If parts touch skin, your specification can set cleaning steps or limits on microbial contamination (bioburden).

A device sold sterile is different. Sterilization, such as ethylene oxide (ISO 11135) or radiation (ISO 11137-1), and the sealing of the sterile barrier packaging (ISO 11607-2, with the packaging itself under ISO 11607-1) have to be validated; assembly and packaging usually happen in a classified clean room (ISO 14644-1, often class 7 or 8); and the 510(k) needs the sterility information described in FDA's sterility guidance. A contract sterilizer counts as a manufacturer and registers too. Agree in writing who owns the sterilization validation, routine dose audits or residue tests, and clean room monitoring.

Example: a first run of 500 handheld Class II devices

This is an illustration, not a customer project. The product is made up, and so are the numbers, except the FDA fees taken from the fiscal 2027 fees above.

In this made-up case, a startup's battery-powered handheld device, with Bluetooth and two stainless-steel electrodes that touch the skin, is headed for a Class II 510(k). It chose a US CM before testing, so the made-up 30 pilot units it tested for 60601-1, EMC and biocompatibility came off the CM's line with production parts. After clearance it plans a made-up first run of 500 units.

At design transfer, before that pilot build, the startup hands over a released set of files, each with a revision number:

  1. Drawings and 3D models of every made part, with tolerances and critical dimensions marked.
  2. The parts list with approved makers, flagging the 60601-1 critical components: battery cell, charger, fuse and housing plastic.
  3. Board files (Gerber or ODB++), schematics, the pick-and-place file, and the firmware image with its version and checksum.
  4. Label, packaging and instructions-for-use artwork, with the UDI layout.
  5. Test specifications with pass limits, and the workmanship standard (IPC-A-610, with the class stated).
  6. Extracts from the risk file: what production has to control, and which steps to validate.
  7. A no-change list: parts, materials, suppliers and processes that can't change without the startup's written approval, including the electrode metal and its supplier.

Before the first build, the CM has in place:

  • A quality system that meets the QMSR, trained operators, calibrated test equipment and a static-safe line.
  • A signed quality agreement, work instructions, and validation reports for the reflow profile and the ultrasonic weld that closes the housing.
  • Purchasing controls for the parts it buys, including the electrodes.
  • A batch record for each made-up lot of 100 units: quantity built and released, test results by serial number, the lot, serial number and manufacturing date in each UDI, and the label checks.
  • Records of nonconforming units and corrective actions.
  • Its FDA registration and the device listing, once the device is cleared.

Submitting and first registering in fiscal 2027, the startup pays FDA $7,163 for the 510(k) at the small-business rate plus $13,785 for its own registration, $20,948 in all, or about $42 a unit over the made-up 500 units. FDA fees are only part of the cost: the 60601-1, EMC and biological tests, the CM's validation work and the startup's own quality system are paid for separately, and the CM pays its own registration fee.

In a made-up third month of production, the battery cell goes on a long lead time and the CM proposes a substitute. That's a design change. The startup checks it against the risk file and the 60601-1 report, which named the original cell, repeats the affected tests, gets the new cell's IEC 62133-2 safety report and the UN 38.3 test summary that shipping lithium cells requires (49 CFR 173.185), and records whether it needs a new 510(k), using FDA's page on device changes. The CM switches only after written approval and a new parts-list revision, and each lot is checked before it ships, as in How do you inspect a first production run before it ships?

What should you ask a contract manufacturer before signing?

  • Is your site registered with FDA, and which devices do you list? You can check FDA's registration and listing database.
  • When did FDA last inspect you? Did you receive inspection observations (Form FDA 483) or a warning letter, and how did you close them?
  • Does your ISO 13485 certificate cover this site and this kind of work, and when does it expire? Are you audited under MDSAP?
  • Which Class II electronic devices do you build now, and at what quantities?
  • What is the smallest run you take, and which one-time charges, such as validation, test fixtures and first-article checks, come before the first build?
  • Which of our steps would you validate, and can we see a validation report for a similar process?
  • How do you control part substitutions, and how will you tell us before changing a part, process, sub-supplier or site?
  • What does a batch record look like, with its UDIs, and how fast can you trace a serial number to its parts, tests and shipment?
  • For a factory outside the US: who is your US agent?

For choosing a production partner more broadly, see How to choose a partner to take your hardware into production.

What should the quality agreement settle?

ISO 13485 requires written quality agreements for outsourced work that affects the product. A useful one settles:

  • The scope: which operations, at which sites, and who does what, row by row, as in the table above.
  • That no part, material, process, sub-supplier or site changes without your written approval.
  • Who buys which parts, from which approved makers, and how critical parts are checked on arrival.
  • Who releases finished units, and who decides on rework or scrap.
  • How fast the CM investigates a returned unit and sends records, given your 30-day and 5-work-day MDR clocks.
  • Which records are kept, by whom and for how long. ISO 13485 asks for at least the device's lifetime as you define it, and not less than two years from release; records of corrections and removals not reported to FDA are kept two years beyond the device's expected life (806.20).
  • Your right to audit, and prompt notice when FDA inspects or issues observations.
  • Who prints and checks labels, and who keeps the GUDID data.

For the handoffs that fall between suppliers in any first run, see What falls between suppliers in a first production run, and who should own it.

Where we come in

If you're choosing who will build a device that FDA regulates, put the questions above to every manufacturer you consider, us included, and run any change made for production through your own design change control. Tell us where you are and what you need; if we're not the right fit, we'll tell you plainly.

Anamor takes US hardware teams with a working prototype into their first production run: we redesign the product for production, line up partner factories and suppliers in the US and overseas, price it at your quantities, and run the build through to shipping.

Send what you have: photos of the prototype, CAD if you have it, the parts list, and how many you plan to make. Need an NDA? We'll send our mutual NDA, or review yours, before you send files. Within two business days, a real person on our team will reply with a free first look at your production run and a few times to talk.

Frequently asked questions

Does a contract manufacturer need ISO 13485 certification to make medical devices for the US?

No. Since February 2, 2026, FDA's Quality Management System Regulation has required a documented quality system that meets ISO 13485, but FDA says it doesn't intend to require certification and won't rely on certificates; it inspects instead. A certificate still shows the manufacturer's system has passed outside audits, and regulators outside the US lean on certificates more.

Does a contract manufacturer have to register with FDA?

Yes, if it makes the finished device. As of November 2026, a contract manufacturer registers its site, lists the device and pays the annual fee for the site, $13,785 in fiscal 2027, and so does the specification developer that holds the 510(k). For a 510(k) device, registration and listing come after clearance. Component makers don't register.

Who files MDR reports when a contract manufacturer builds the device?

Usually the specification developer that markets the device. FDA's reporting guidance says a contract manufacturer that doesn't distribute or market the devices it builds has no duty to file reports under 21 CFR 803.50. The contract manufacturer still investigates returned units and its production records, so the quality agreement should set how fast it responds.

Tell us what you're building and how many you plan to make.

A real person on our team will reply with a first look at your production run and a few times to talk.

Free first look. We reply within two business days. Sending a request doesn't commit you to a project.