10 Expensive Mistakes International Medical Device Manufacturers Make Entering the US Market
- Beng Ee Lim
- 35 minutes ago
- 21 min read
International medical device manufacturers often run into the same avoidable U.S. market-entry mistakes: assuming CE-mark experience will translate cleanly to FDA, choosing the wrong predicate strategy, trying to reuse EU clinical data without reframing it for substantial equivalence, misunderstanding when a U.S. Agent is needed, missing U.S.-specific testing expectations, underestimating the burden of Additional Information requests, overlooking remaining QMSR gaps after ISO 13485 alignment, underpreparing for FDA interactions, and missing U.S. labeling requirements. These mistakes may not always kill a submission, but they can create expensive delays, rework, and regulatory dead ends.
This guide breaks down the most common mistakes, why international manufacturers make them, and how to avoid them before they turn into lost time, extra testing, or the wrong regulatory strategy.
Mistake 1: Assuming CE-Mark Experience Translates to FDA Success
The mistake
A lot of international manufacturers assume FDA 510(k) will feel like the U.S. version of CE marking. It won’t.
The core problem is regulatory logic. Under EU MDR, the manufacturer is building a conformity case around safety, performance, and benefit-risk. Under FDA 510(k), the manufacturer is building a substantial-equivalence case to a legally marketed U.S. predicate. That difference changes how the submission should be structured, how clinical evidence is framed, how testing is justified, and how risk is discussed.
When teams miss that, the whole submission can drift in the wrong direction. The data may be solid, but the argument is not built for the FDA question.
Why international manufacturers make it
The mistake is easy to make because the systems sound more similar than they are. Both talk about classification, risk management, clinical evidence, and post-market obligations. But those terms do not function the same way in each system.
The second problem is false confidence. A manufacturer that already spent significant time and money getting CE-marked may assume the hard part is done. In reality, 510(k) often requires new work around predicate selection, side-by-side comparison, substantial-equivalence framing, and U.S.-specific testing logic. FDA’s own description of 510(k) makes this clear: the submission has to provide enough detail for FDA to determine that the device is substantially equivalent to a legally marketed device.
What it costs in practice
The cost is usually not that the underlying device data are useless. The cost is that the submission is built around the wrong structure.
That can show up as:
FDA asking for more information because the predicate comparison is weak or unclear
the team having to rework sections that were written like MDR technical documentation instead of a 510(k)
a failed predicate strategy that forces the company to reconsider whether De Novo is the more appropriate path
It can also create post-market compliance confusion. EU vigilance experience does not automatically prepare a company for FDA’s Medical Device Reporting obligations under 21 CFR Part 803.
How to avoid it
The fix is simple in principle, even if it takes work in practice:
treat FDA 510(k) as a predicate-driven submission, not a translated CE-mark file
review likely predicates early using the public 510(k) database and releasable summaries
structure the submission around the substantial-equivalence case, not just device performance in the abstract
assume that U.S. post-market and labeling obligations need their own review, even if the product is already marketed in Europe
Instead of guessing your way from a CE-mark file into a 510(k), teams can use Complizen’s Product Code Finder and Predicate Intelligence to narrow likely U.S. classifications, compare potential predicates, review linked 510(k)s, and see how successful devices in the same product code framed their substantial-equivalence argument. That is much more useful than forcing EU MDR logic into an FDA submission and hoping it translates.
Mistake 2: Selecting an EU Competitor Instead of the Right FDA Predicate
The mistake
A common U.S. market-entry mistake is assuming that the European device most similar to yours is also the right FDA predicate.
It often is not.
For a 510(k), FDA wants comparison to a legally marketed U.S. device that supports a substantial-equivalence argument. That means the real question is not, “Who is our closest competitor in Europe?” The real question is, “Which U.S. predicate has the right intended use, regulatory classification, and comparison logic for this submission?”
Why international manufacturers make it
This mistake is easy to make because international teams usually know the EU market far better than the U.S. predicate landscape.
They often start with a familiar competitor name, search FDA’s database by brand or model, and assume that whatever appears must be the right predicate. That is backwards. FDA’s system is built around product codes, classification, intended use, and legal market status, not just the commercial name the manufacturer already knows.
The second trap is assuming a device marketed globally has the same indication everywhere. It may not. A product can have one scope in Europe and a narrower or different intended use in the United States. In a 510(k), that difference matters. Intended use alignment is one of the core pieces of substantial equivalence.
What it costs in practice
When the predicate strategy is weak, the submission can start falling apart early.
That usually shows up as:
FDA questioning whether the chosen predicate is actually appropriate
extra review cycles because the intended-use match or technology comparison is weak
the team having to restart predicate research after too much of the 510(k) has already been built around the wrong comparison
in some cases, realizing too late that 510(k) may not be available at all, and that De Novo is the more realistic path
A weak predicate can also make the submission harder to defend if the comparator has a messy post-market profile. That does not automatically make the device unusable, but it can make the overall comparison story less comfortable. This is why checking both recall history and MAUDE adverse-event patterns is worth doing early, not after the strategy is already locked.
How to avoid it
The better process looks like this:
start with the device’s intended use, not the EU competitor’s brand name
identify the likely FDA product code and classification early
search for predicates using FDA classification and 510(k) databases
read the predicate’s public 510(k) summary closely, especially the intended use and comparison logic
check recalls and MAUDE before committing too hard to one predicate
keep backup predicate options in case FDA pushes back on the primary choice
Instead of doing all of this manually, teams use Complizen’s Product Code Finder to narrow the likely FDA classification first, then use Predicate Intelligence to compare likely U.S. predicates side by side, review linked 510(k)s, and surface relevant recall and adverse-event signals before the submission strategy gets built around the wrong device.
Mistake 3: Using CE-Mark Clinical Data Without FDA-Specific Analysis
The mistake
A common international-market mistake is assuming that if a clinical study was good enough for CE marking, it can simply be dropped into a 510(k) unchanged.
Usually, it cannot.
The issue is not always the quality of the underlying data. The issue is the regulatory question the data are being used to answer. An MDR clinical package is usually built to support clinical evaluation, safety, performance, and benefit-risk. A 510(k) is built to support substantial equivalence to a legally marketed U.S. predicate. If the analysis is not framed around that FDA question, the submission can still feel incomplete even when the study itself is strong.
Why international manufacturers make it
This mistake usually comes from a reasonable assumption: good clinical data should be good clinical data everywhere.
But for FDA, the data do not just need to be credible. They need to be usable in the 510(k) comparison. That means the endpoints, study population, follow-up, and analysis all have to help answer the substantial-equivalence question FDA is actually reviewing. FDA can accept clinical investigations conducted outside the U.S., but the study still has to meet FDA’s foreign-clinical-data requirements and be relevant to the U.S. regulatory case.
A second reason manufacturers get this wrong is that the EU clinical package often feels more comprehensive. A full CER plus supporting study documentation can look more thorough than what a U.S. reviewer might need. But “more comprehensive” is not the same as “better aligned.” A long MDR-style package can still miss the predicate logic that matters most in a 510(k).
What it costs in practice
The usual consequence is not that FDA automatically rejects foreign clinical data. The usual consequence is that the data package creates extra work because it does not answer the FDA question cleanly.
That can show up as:
FDA asking for a clearer predicate comparison
FDA questioning whether the endpoints are actually relevant to the substantial-equivalence case
the team having to reanalyze the study after submission instead of designing the analysis correctly from the start
in some cases, realizing too late that the existing EU study does not carry enough weight and that supplemental evidence is still needed
How to avoid it
The fix is not to throw away the European data. The fix is to translate the evidence into the right regulatory logic.
That usually means:
identify the likely FDA predicate before finalizing the study strategy
make sure the endpoints and follow-up can still support the 510(k) comparison
prepare a separate FDA-facing analysis, even if the underlying data are the same
document study conduct clearly enough to support FDA’s foreign-clinical-data expectations under 21 CFR 812.28
use a Pre-Submission when the clinical-data strategy is still uncertain, instead of waiting until the 510(k) is already built
Mistake 4: Designating a U.S. Agent at the Wrong Time
The mistake
A common mistake for international manufacturers is treating the U.S. Agent like an EU Authorized Representative.
That leads to two opposite errors:
appointing a U.S. Agent far too early, as if it were required to submit a 510(k)
waiting too long, then discovering the device cannot be imported because the foreign establishment is not fully registered and listed yet
For most commercial-market-entry situations, the right sequence is simpler:
submit the 510(k) → receive clearance → designate the U.S. Agent → complete establishment registration and device listing → begin commercial import
FDA’s U.S. Agent requirement for foreign device establishments is part of the registration and listing process under 21 CFR 807.40, not a prerequisite to filing a 510(k).
Why international manufacturers make it
The confusion usually comes from using the wrong mental model.
In Europe, international manufacturers are used to the idea that the authorized representative is part of the formal path to market. In the U.S., the U.S. Agent serves a different function. FDA describes the U.S. Agent as the foreign establishment’s U.S.-based contact for communications, imported-device questions, and inspection scheduling.
That means the U.S. Agent matters, but not in the same place in the sequence.
A second reason teams get this wrong is that they mix up 510(k) clearance with registration and listing. FDA treats those as separate processes. You can obtain 510(k) clearance without first appointing a U.S. Agent, but a foreign establishment must register and list before exporting or importing commercial devices into the United States.
What it costs in practice
The practical risk is operational, not philosophical.
If a company appoints a U.S. Agent too early, it may pay for a service it does not yet need. If it waits too long, it can create avoidable launch friction because registration, listing, and import readiness are not in place when the device is finally cleared.
The real mistake is not just timing. It is failing to understand what the U.S. Agent is actually for and where it fits in the broader U.S. market-entry workflow.
How to avoid it
For most foreign manufacturers entering the U.S. commercial market:
do not assume a U.S. Agent is required just to file a 510(k)
plan the U.S. Agent step around post-clearance registration and listing
identify likely U.S. Agent options during the review period, so you are not scrambling after clearance
make sure the foreign establishment is ready to complete registration and device listing before first export/import to the U.S.
Mistake 5: Missing U.S.-Specific Testing Requirements
The mistake
A common international-market mistake is assuming that a strong CE-mark testing package will translate directly into a strong FDA 510(k) testing package.
Sometimes it does. Often it does not.
The issue is not that ISO and IEC standards suddenly stop mattering in the United States. The issue is that FDA uses its own framework of recognized consensus standards, including specific versions, recognition details, and device-specific expectations layered through 510(k) content requirements and product-area guidance. A test package that looked complete for Europe can still leave gaps for FDA if the standard version, test method, or documentation does not line up with what FDA expects.
Why international manufacturers make it
This mistake usually starts with a reasonable assumption: international standards are international standards.
That assumption breaks down in practice because FDA does not just ask whether testing was done to a well-known standard. FDA asks whether the submission uses the FDA-recognized version, whether the standard is recognized with limitations or U.S. national differences, and whether additional device-specific evidence is still needed. FDA’s own standards database makes that clear.
A second trap is relying on a testing lab’s statement that a package is “FDA-compliant” without independently checking the FDA-recognized standards database or the relevant device guidance. A strong test report is useful, but 510(k) review still depends on whether the evidence fits the FDA-recognized standards framework and the specific product code expectations.
What it costs in practice
The most common consequence is not total failure. It is avoidable rework.
That usually shows up as:
FDA asking for testing to a different recognized version of a standard
FDA asking for clearer justification of how the testing supports substantial equivalence
FDA expecting additional device-specific testing scenarios or documentation
the team having to revise reports or run supplemental testing late in review
For some devices, this can also show up in specific areas like biocompatibility interpretation, endotoxin or pyrogen considerations, EMC expectations, or sterile barrier/package validation, depending on the product and intended use. Those are not universal add-ons, but they are exactly the kinds of gaps that appear when teams assume the EU testing plan is automatically enough for FDA.
How to avoid it
The better process is straightforward:
check the FDA-recognized consensus standards database early
confirm the exact version FDA recognizes for each key standard
review any product code-specific guidance before locking the test plan
make sure the test package is built not just to show safety and performance, but to support the 510(k) substantial-equivalence case
ask the lab for reporting detail that will actually hold up in a U.S. submission, not just the minimum needed for a generic standards report
Instead of forcing teams to piece this together across FDA databases, guidance PDFs, and lab emails, Complizen’s Tests and Standards workflow can help connect the likely product code, the relevant FDA-recognized standards, and the likely testing burden earlier, so manufacturers are less likely to discover version mismatches or missing U.S.-specific expectations halfway through a 510(k).
Mistake 6: Weak GCP and Trial Documentation for EU Clinical Studies
The mistake
A common international-market mistake is assuming that a European clinical study accepted for CE marking will automatically have the documentation depth FDA needs for a later 510(k).
That is not always true.
FDA can accept clinical investigations conducted outside the United States, but under 21 CFR 812.28 the agency still expects the study to be conducted in accordance with good clinical practice and documented in a way that allows FDA to validate the data through records review or onsite inspection if needed. In other words, the problem is often not the study result. The problem is whether the study conduct and records are traceable enough for FDA to rely on them.
Why international manufacturers make it
This mistake usually comes from assuming that ISO 14155-compliant clinical documentation is automatically enough for every regulator. FDA does recognize ISO 14155:2020 as consistent with its good clinical practice framework for medical device investigations, which is why many EU trials can be a strong starting point. But FDA still evaluates whether the records are sufficient for its own review and validation needs. A study that satisfied a notified body may still create extra work later if the monitoring records, audit trails, consent documentation, or study oversight trail are too thin for FDA.
A second trap is electronic documentation. If the trial relied heavily on electronic systems, FDA’s expectations around electronic records, auditability, and data integrity can matter. That does not make 21 CFR Part 11 the main rule for foreign clinical data transfer, but it does mean teams should not treat electronic study records casually if they may later be submitted to FDA.
What it costs in practice
The usual consequence is not that FDA automatically throws the data out. The more common problem is that the sponsor ends up doing a lot of avoidable cleanup work late in the process.
That can show up as:
FDA asking for more detail on study oversight, monitoring, or consent documentation
extra effort to pull together scattered records from CROs, sites, and archived systems
questions about whether the available documentation is enough to let FDA validate the data
in the worst case, the study carrying less regulatory weight than the sponsor expected because the documentation trail is too weak
How to avoid it
The best fix is to design the documentation standard, not just the clinical protocol, with future FDA use in mind.
That usually means:
maintain a study file that clearly supports GCP compliance and study traceability
keep monitoring, consent, protocol-change, and oversight records organized enough for later FDA review
make sure electronic systems and records are preserved in a way that supports auditability
do not assume a CE-mark clinical package can simply be repackaged later without extra work
if the study may support a future 510(k), pressure-test the documentation plan early instead of waiting until submission assembly
Mistake 7: Underestimating the Burden of an FDA Additional Information Request
The mistake
A common mistake is treating an FDA Additional Information, AI, request like a quick clarification round.
It often is not.
In a 510(k), an AI request can touch the core of the submission, especially predicate choice, substantial-equivalence logic, testing justification, clinical-data relevance, or labeling. When that happens, a short memo or a few pages of explanation usually will not solve the problem. FDA needs a response that actually closes the gap in the review, not just a response that acknowledges it.
Why international manufacturers make it
This mistake is especially common for international teams because they often expect FDA review to behave more like a notified body back-and-forth.
It does not.
In FDA’s 510(k) process, an AI request pauses the review clock while the submitter prepares a response. That means a weak response does not just create extra paperwork. It can materially extend the review because FDA cannot move forward until the missing issues are addressed well enough for substantive review to continue.
The second trap is psychological. “Additional information” sounds like a small gap. In reality, the request may be pointing to a deeper weakness in the submission, such as:
unclear predicate logic
incomplete testing support
weak comparison to the predicate
foreign clinical data that do not yet answer the FDA question cleanly
What it costs in practice
The main cost is usually compounding delay and rework.
If the first AI response is too narrow, FDA may have to ask again because the underlying issue was never really solved. That can leave the submission fragmented across the original 510(k) plus one or more follow-up response packages, which makes the review harder for everyone.
The bigger the unresolved issue, the more dangerous it is to respond minimally just to “keep things moving.” In many cases, that instinct backfires.
How to avoid it
The smarter approach is to assume that an AI request is asking for a complete resolution, not a quick note.
That usually means:
respond to the underlying regulatory problem, not just the wording of the question
include the supporting analysis, data, and justification FDA will likely need to move forward
avoid drip-feeding information across multiple cycles
prepare for common pressure points early, especially predicate selection, testing logic, and foreign clinical-data relevance
use a Pre-Submission if the device has obvious complexity before the 510(k) is filed
If a team can review likely predicate weaknesses, compare testing expectations, and see where the substantial-equivalence argument is thin before submission, it is much easier to strengthen the original 510(k) and reduce the chance of a messy AI cycle later. And if an AI request does come, having the predicate logic, tests, standards, and source-linked FDA evidence already organized in Complizen’s Strategy Workspace makes it easier to respond comprehensively the first time.
Mistake 8: Assuming ISO 13485 Alone Covers FDA Quality Requirements
The mistake
A common international-market mistake is assuming that an ISO 13485-certified quality system automatically means the company is fully ready for FDA.
That is not how FDA sees it.
As of February 2, 2026, FDA’s Quality Management System Regulation, QMSR, incorporates ISO 13485:2016 by reference. That is a major alignment step. But FDA also added requirements to make sure the incorporation of ISO 13485 does not create inconsistencies with other FDA obligations. FDA has also been explicit that an ISO 13485 certificate does not exempt a manufacturer from FDA inspection and does not by itself prove compliance.
Why international manufacturers make it
This mistake usually comes from hearing the word harmonization and assuming the problem is basically solved.
It is true that QMSR moves FDA much closer to ISO 13485. But “closer” does not mean “identical,” and it definitely does not mean “certificate equals compliance.” FDA still enforces U.S.-specific obligations that sit outside a simple ISO-certificate mindset, especially in areas like Medical Device Reporting, complaint handling, post-market processes, and inspection readiness.
A second trap is timing. Many manufacturers assume FDA must have already accepted their quality system because the device received 510(k) clearance. That is the wrong inference. 510(k) is a premarket substantial-equivalence decision, not a quality-system approval. FDA inspections are a separate process and now follow the updated compliance program 7382.850.
What it costs in practice
The practical risk is post-clearance friction.
If the quality system looks fine from an ISO 13485 perspective but is weak in FDA-specific execution, the company can run into problems in exactly the places FDA cares about most, like:
complaint handling
MDR reporting
post-market follow-up and corrective action processes
inspection readiness and documentation quality
That does not mean every foreign manufacturer will immediately face a major enforcement event. But it does mean that relying on the ISO certificate alone is a weak compliance strategy.
How to avoid it
The better approach is to treat ISO 13485 as the foundation, not the finish line.
That usually means:
run an FDA-specific QMS review even if the system is already ISO 13485-certified
verify that complaint handling, MDR, servicing where applicable, and post-market processes actually meet FDA expectations
do not assume the certificate answers the inspection question
prepare the quality system for the reality that FDA may inspect separately from the 510(k) process and may focus on how the system actually works in practice, not just whether it passed a certification audit
Mistake 9: Poor FDA Pre-Submission Meeting Preparation
The mistake
A common international-market mistake is using the FDA Pre-Submission, Pre-Sub, process like a general consultation meeting.
That usually leads to weak results.
Instead of bringing a focused regulatory problem, some teams send long background documents and ask broad questions like:
Will FDA accept this device under 510(k)?
Is our testing enough?
Will FDA accept our clinical data?
Those questions feel natural, but they rarely produce the kind of feedback teams actually need. FDA’s Q-Submission program is designed to give feedback on specific proposed approaches, not to pre-clear a future submission in the abstract.
Why international manufacturers make it
This mistake often comes from carrying over the wrong regulatory culture.
Many international manufacturers are used to more iterative or consultative interactions elsewhere. So they treat Pre-Sub as a place to present the device broadly and ask FDA to point them in the right direction.
FDA does not use it that way.
The Pre-Sub process works best when the manufacturer has already narrowed the real decision points and is asking FDA to react to specific options, not just to the device in general. FDA can give useful feedback on questions like pathway, predicate approach, testing strategy, or clinical-data plan. But FDA is not there to promise clearance or replace the sponsor’s regulatory thinking.
What it costs in practice
The cost is usually not the meeting itself. The cost is the missed opportunity.
A weak Pre-Sub can leave the team with the same uncertainty it had before the meeting:
still unsure about the best predicate strategy
still unclear on whether the proposed testing plan is enough
still not confident about whether foreign clinical data will carry the 510(k)
That means the team ends up filing the 510(k) with unresolved strategic questions that should have been pressure-tested earlier. And if FDA later raises those same issues during review, the Pre-Sub did not actually reduce risk.
How to avoid it
The best Pre-Sub packages are usually shorter, sharper, and more decision-oriented.
That means:
ask a small number of high-value questions
frame each question around a specific proposed approach
where possible, show FDA the options you considered and which one you currently recommend
focus on issues that would materially change the 510(k) strategy, such as predicate choice, testing scope, or clinical-data use
make sure the written feedback and meeting record are captured clearly for later submission planning
A good Pre-Sub question is not:
“Will FDA accept this predicate?”
A better Pre-Sub question is:
“We are considering Predicate A and Predicate B. Predicate A has the closer intended use, while Predicate B has the closer technological profile. Based on the attached comparison, does FDA have feedback on which approach is more appropriate for our planned 510(k)?”
That is the difference between asking FDA to do your thinking for you and asking FDA to react to a well-prepared regulatory strategy.
This is also one of the places where Complizen can add real value. Before a Pre-Sub is drafted, teams can use Complizen’s Product Code Finder, Predicate Intelligence, and Tests and Standards workflows to narrow the actual decision points first. That makes it much easier to walk into the meeting with focused questions, a stronger comparison table, and a clearer recommendation, instead of wasting the meeting on broad background and vague uncertainty.
Mistake 10: Assuming CE-Mark Labeling Will Work for the U.S.
The mistake
A common international-market mistake is assuming that once device labeling is compliant for EU MDR, it will mostly work for the U.S. with only small edits.
That assumption is risky.
FDA’s device-labeling rules sit under 21 CFR Part 801, and U.S. labeling review is not just a translation exercise. A label that works well for Europe can still create problems in a 510(k) or later in U.S. commercialization if it misses U.S.-specific wording, prescription-device statements, directions for use, warning expectations, or symbol conditions.
Why international manufacturers make it
This mistake usually comes from two assumptions.
The first is that MDR labeling already feels strict and comprehensive, so it must be enough for FDA too. The second is that both systems use international standards and symbols, so the label should mostly transfer.
But FDA’s labeling framework is its own system. For example, FDA’s rules around prescription-device labeling and the use of stand-alone symbols follow U.S.-specific regulatory conditions, not just whatever was accepted in Europe.
A second trap is underestimating labeling as a regulatory issue. Teams often focus on predicates, testing, and clinical data, while treating labeling like an administrative finishing step. FDA does not see it that way. Labeling is part of the compliance package, and weak labeling can create avoidable review questions or post-clearance risk.
What it costs in practice
The usual cost is avoidable rework.
That can show up as:
labeling revisions during review
delays because warnings, directions for use, or prescription-device statements are not aligned with FDA expectations
artwork or packaging needing to be updated later than planned
post-clearance compliance risk if the marketed labeling still does not match U.S. requirements
The problem is usually not that the EU label was “bad.” The problem is that it answered the wrong regulatory system.
How to avoid it
The better approach is simple:
review 21 CFR Part 801 early, not at the end
confirm whether the device is prescription or nonprescription for U.S. purposes
check whether the label needs “Rx only” or related prescription-device wording
make sure the U.S. version of the label and IFU are built for FDA’s framework, not just translated from the CE-mark version
confirm that any symbols used on the U.S. label fit FDA’s symbols rule and its conditions for stand-alone use
The Fastest Path to Market
Frequently Asked Questions
Do all international manufacturers make these mistakes when entering the U.S. market?
No, but many first-time U.S. entrants make at least some of them. The most common problems usually involve predicate selection, testing strategy, foreign clinical data use, labeling, and post-clearance compliance assumptions. The risk is highest when a team treats FDA like a translated CE-mark process instead of a separate regulatory system.
Which mistake is usually the most damaging?
Usually the most expensive mistakes are the ones that break the core regulatory strategy, especially choosing the wrong predicate, building the wrong substantial-equivalence argument, or assuming EU clinical or testing work automatically answers FDA’s questions. Those mistakes can force major rework or even a pathway rethink, including whether De Novo is more appropriate.
Can Complizen prevent all of these mistakes by itself?
Not by itself. A platform does not replace sound regulatory judgment. But Complizen can reduce avoidable mistakes by helping teams narrow likely product codes, compare likely predicates, review linked 510(k)s, map likely tests and standards, and organize the evidence trail before those assumptions get locked into the submission strategy.
How much should a first FDA 510(k) cost for an international manufacturer?
There is no single reliable number that fits every device. Cost depends heavily on the device type, predicate strength, testing burden, whether clinical data are needed, and how much rework the company creates by starting with the wrong strategy. The better budgeting question is not “What is the average?” It is “What are the likely cost drivers for this device?”
Should we use a U.S.-based FDA consultant or an EU consultant with FDA experience?
What matters most is not geography alone. It is whether the person has real FDA submission experience, especially with international manufacturers. For many teams, the best setup is an FDA-focused lead who understands U.S. submission logic, paired with someone who understands the existing EU documentation and evidence base.
How long does FDA clearance usually take for international manufacturers?
There is no special FDA timeline just because a manufacturer is international. What usually makes international submissions slower is not nationality, but translation effort, weak predicate strategy, incomplete testing logic, foreign clinical data issues, and slow responses to AI requests. A well-prepared international 510(k) can move on a similar timeline to any other well-prepared 510(k).
What should we do if we already made some of these mistakes in a submitted 510(k)?
Start by identifying whether the problem is administrative, evidentiary, or strategic. Administrative issues may be fixable quickly. But if the real problem is the wrong predicate, weak substantial-equivalence logic, or a testing package that does not support the FDA question, the response needs to solve the underlying issue, not just patch the wording. That is where many teams lose more time.
Are CE-mark holders more likely to make FDA mistakes than companies with no regulatory experience?
Sometimes, yes. The reason is not lack of sophistication. It is false transfer. Teams that already succeeded in Europe often assume that enough of the regulatory logic carries over to the U.S. when, in reality, the FDA submission still needs its own predicate, testing, labeling, and post-market logic.
How do we know if our predicate is strong enough?
A strong predicate usually has a closely aligned intended use, a defensible regulatory classification, and a comparison story that FDA can follow clearly. Reading the public 510(k) summary, checking the product code, and reviewing the device’s recall or adverse-event context can all help stress-test the choice before you build the whole submission around it.
Can we use the same testing lab for CE marking and FDA?
Often, yes, if the lab can support the FDA-recognized standards framework and produce documentation that works for a U.S. submission. The bigger issue is not whether the lab is in Europe or the U.S. The bigger issue is whether the testing plan, standard versions, and reporting style actually fit FDA’s expectations.
Should we pursue CE marking first or FDA first?
That depends on the device, the target market, the likely predicate situation, and whether clinical evidence is likely to be needed. If a strong FDA predicate exists and the U.S. is the priority market, FDA-first may make sense. If the device is more likely to need clinical evidence either way, Europe may be the better place to build the first evidence base. There is no universal right sequence.
What is the single most important thing to do differently for the U.S.?
Do the FDA-specific strategy work early. That means pressure-testing the likely product code, predicate set, testing burden, foreign clinical-data usability, labeling logic, and post-clearance compliance obligations before submission work starts. That is where most preventable mistakes begin.
