Imagine a competent authority in Germany asking for the technical file behind a device manufactured in California. In practice, it is not the factory that gets the call — it is whoever holds the mandate in Europe. That single point of contact, and how quickly it can produce documents on request, is largely what a European authorized representative is meant to provide, far more than the paperwork that creates the role in the first place.
In one sentence: an EU Authorized Representative is the EU-established person or company that a non-EU medical device or IVD manufacturer designates, under a written mandate it has accepted, to carry out specified MDR/IVDR compliance tasks on its behalf.
When you need one:
- You manufacture devices or IVDs outside the EU and intend to place them on the Union market.
- The law requires a sole authorized representative — not several appointed in parallel — and the mandate is valid only once accepted in writing.
- One mandate must cover, at minimum, all devices within the same generic device group.
What an EU Authorized Representative is (and what it is not)
Under Regulation (EU) 2017/745 (MDR) and Regulation (EU) 2017/746 (IVDR), a manufacturer not established in a Member State may only place a device on the Union market if it designates a sole authorized representative. The designation takes the form of a mandate, and that mandate is valid only once the representative has accepted it in writing. EU guidance (MDCG 2022-16) describes the authorized representative as any natural or legal person established within the Union who has received and accepted such a written mandate to act on the manufacturer’s behalf for specified regulatory tasks.
The role does not generate technical documentation — it verifies that such documentation exists and appears complete, and keeps a copy available for authorities. It is also distinct from the person responsible for regulatory compliance (PRRC): under MDR Article 15(6), the authorized representative must have at least one PRRC permanently and continuously at its disposal, with the regulatory expertise the Regulation requires. In practice, that means assured, ongoing access to that expertise, not a one-off credential on file.
The reason this role exists is reachability. A useful way to think about it: market surveillance authorities need an accountable party established in the Union that can be approached directly, and the appointment under Article 11 is what creates that legal point of contact. An address on a label satisfies the formal requirement; whether the organization behind it can actually produce a working file on request is a separate, practical question — and that gap tends to be where operational risk concentrates.
When appointment is required — and the edge cases that catch manufacturers off guard
The trigger is straightforward: any manufacturer not established in a Member State that intends to place devices or IVDs on the Union market must designate a sole authorized representative. The mandate must be effective at least for all devices of the same generic device group. The Regulation does not spell out how that principle maps onto every portfolio structure, so confirming how a given generic device group is defined — and whether one mandate genuinely covers the full product range — is a conversation worth having directly with the representative rather than assuming.
The guidance also clarifies that the Union market, for this purpose, covers EU Member States and, through the EEA, extends to Norway, Liechtenstein and Iceland, and through the Customs Union Agreement, to Turkey. A manufacturer selling into Oslo or Ankara sits inside the same perimeter as one selling into Lisbon, a detail that corporate groups structuring regional distribution sometimes overlook.
Private-label and OEM arrangements raise a recurring practical question: which entity in the chain actually appoints the representative, and which one holds the rights to release the technical documentation? The Regulation does not resolve this in operational terms for every supply arrangement, and assuming an answer based on commercial convention rather than confirming it with regulatory counsel is a common source of friction later, usually discovered only when an authority asks who is legally accountable for the file.
One exception is worth flagging because it is widely misunderstood: devices intended for clinical investigation or performance studies do not fall under the authorized representative requirement. The same guidance specifies that sponsors not established in the Union must instead appoint a legal representative under Article 62(2) MDR or Article 58(4) IVDR — a related but legally distinct figure, with its own mandate and scope, not a shortcut around the market-access requirement that applies once a device moves from investigation to commercial distribution.
Core legal tasks under MDR/IVDR Article 11
Article 11(3) sets out the minimum content of the mandate, and it reads less like a formality and more like an operational job description. At minimum, the authorized representative must verify that the EU declaration of conformity and technical documentation have been drawn up and that an appropriate conformity assessment procedure has been carried out. It must keep available a copy of the technical documentation, the declaration of conformity and, where applicable, the relevant certificate — including amendments — at the disposal of competent authorities for the retention period set by Article 10(8).
The mandate must also require the representative to comply with its own registration obligations under Article 31 and to verify that the manufacturer has met its registration duties under Articles 27 and 29. On request, the representative must provide authorities with all information and documentation needed to demonstrate conformity, in an official Union language determined by the Member State making the request — a requirement that, in practice, benefits from translation capacity arranged in advance rather than improvised once a letter arrives, even though the Regulation itself does not prescribe how that capacity is organized. The mandate must further require cooperation with competent authorities on preventive or corrective action, and immediate forwarding to the manufacturer of complaints and reports from healthcare professionals, patients and users concerning suspected incidents.
Two provisions are easy to miss on a quick read but shape everything downstream. Article 11(4) states plainly that the mandate cannot delegate the manufacturer’s own obligations under Article 10 — the representative verifies and facilitates, it does not absorb the manufacturer’s core duties. And Article 11(3)(h) requires the representative to terminate the mandate if the manufacturer acts contrary to its obligations under the Regulation, meaning the relationship is not purely commercial; it carries a built-in obligation to walk away when compliance breaks down.
In practice, because these obligations are specific, time-bound and tied to liability rather than symbolic, many non-EU manufacturers choose to formalize the role through a specialised provider rather than treat it as an internal side task. Manufacturers that prefer working with such a provider rather than building this capacity internally can appoint a European authorized representative — ALTRION is one such provider — to formalise the written mandate and the document-availability workflows that Article 11 requires.
The interface model: plugging the EU AR into your QMS and post-market system
Reading Article 11 as a checklist misses the point. Each of those minimum tasks is, in practice, a communication route that has to work under pressure — often during an incident, not during a quiet audit week. Designing that interface deliberately, rather than discovering its gaps when a request lands, tends to separate a functioning arrangement from a purely nominal one.
A reasonable starting point is contact architecture. In practice, many manufacturers and representatives agree on a single named contact with a backup, rough response-time expectations, and language coverage matched to the Member States where the manufacturer actually sells — none of this is mandated in those exact terms by the Regulation, but it addresses the Article 11(3)(d) duty to respond in whichever official language the requesting Member State determines.
Vigilance workflow is often, in practice, the sharpest test of the arrangement. A workable interface tends to move a complaint from intake through triage, manufacturer assessment, a reportability decision, and — where needed — support for the authority submission, with each step attributable to a named person. Field safety corrective actions add another layer in practice: templates for customer communications, a distribution list that is genuinely current, and some way of checking whether the action had its intended effect, not merely whether the notice went out.
Document control underpins all of it. In practice, having a secure, version-controlled way to exchange documentation — rather than attachments passed around informally — tends to shorten retrieval time, though the Regulation does not prescribe a specific method. What it does require, under Article 11(3)(d), is that the information and documentation be produced on request; how a representative organizes itself to meet that deadline is an operational choice worth asking about before signing a mandate, not after an incident.
Liability under Article 11(5): what the regulation actually creates
Article 11(5) is the clause that turns the role from administrative convenience into shared exposure. Where the manufacturer is not established in a Member State and has not complied with its Article 10 obligations, the authorized representative is legally liable for defective devices on the same basis as, and jointly and severally with, the manufacturer. That liability is conditional, not automatic — it attaches to non-compliance with Article 10, not to the mere existence of the mandate — but it explains why the appointment is treated as more than a box-ticking exercise.
The Article 11(3) list doubles as a retrieval list. If a question about a device’s conformity is raised, the representative needs to be able to produce the technical file, the declaration of conformity, the registration records required under Articles 27, 29 and 31, and the record of complaints and reports it is required to forward under Article 11(3)(g). A representative who holds a copy of the mandate for inspection, as required, but cannot actually retrieve the underlying documents has satisfied the letter of the appointment without satisfying its purpose.
Common operational risks include a representative who is nominally appointed but difficult to reach, a mandate that leaves document formats and response expectations undefined, limited real access to the technical documentation beyond a cover letter, and no clear path for deciding when a complaint warrants a reportability decision. None of these breach a single line of Article 11 on their own, which is part of why they tend to surface only once something goes wrong.
Choosing an EU Authorized Representative: signals beyond a postal address
A compliant address solves nothing if the organization behind it cannot operate the workflows described above. Scope fit matters first — familiarity with the manufacturer’s device or IVD risk class, and some practical experience interacting with competent authorities rather than theoretical knowledge of the Regulation. Operational capacity is just as relevant: how quickly the representative tends to respond, which Member States it actually covers, and whether it uses a secure way of exchanging documents rather than passing attachments informally.
Independence deserves scrutiny too. A representative with commercial ties to an importer or distributor handling the same products can face conflicts when a corrective action implicates that same supply chain — a structural tension worth asking about directly before signing anything. Finally, auditability: a representative willing to be audited, with evidence of its own procedures and some experience of market surveillance interactions, is a different proposition from one that simply issues a mandate letter and little else.
What belongs in the written mandate
The mandate is the document regulators ask to see, and MDR Article 11 requires the representative to provide a copy to a competent authority on request. Beyond the statutory minimum tasks, a mandate built for operational use typically defines the boundary between what the representative can decide alone and what requires manufacturer sign-off; specifies which documents must be accessible, in what format, on what update cadence, and for how long, consistent with the retention period in Article 10(8); and sets escalation rules for complaints and vigilance triggers, including who owns the reportability decision.
Confidentiality and data handling deserve their own clause given the sensitivity of clinical and technical files changing hands across borders. Change management matters too — how the representative is kept current when a Notified Body changes, when labeling or UDI information is updated, or when a significant device change occurs. Every mandate should also anticipate its own end: Article 12 requires that a change of authorized representative be governed by a clear agreement between the manufacturer and, where practicable, the outgoing representative, addressing mandate start and end dates, how long the outgoing representative may still appear in the manufacturer’s information, transfer of documents including confidentiality and property rights, and forwarding of complaints and reports received after the mandate ends. A mandate silent on exit terms risks a gap in coverage precisely when continuity matters most.
A practical readiness checklist
Before appointing a representative, it is worth mapping the full chain of EU economic operators involved — importer, distributor, any private-label partner — and confirming in writing who receives complaints first and who holds the authoritative copy of the technical documentation. Confirming that the documentation is genuinely retrievable, not just archived somewhere internally, tends to matter more in practice than the mandate’s wording alone.
After appointment, some manufacturers find it useful to simulate an authority request and see how long it actually takes to produce the declaration of conformity, a vigilance record, or traceability data for a specific device. The gap between the answer on paper and the answer in practice is where operational risk tends to concentrate. Indicators worth tracking over time include response time to information requests, completeness of documentation on first request, and vigilance cycle times from intake to reportability decision, alongside a periodic governance conversation between manufacturer and representative rather than contact only when something goes wrong.
This work also needs to sit alongside the manufacturer’s broader EU registration planning. EUDAMED, the European Database on Medical Devices established by the MDR and IVDR, has four modules — actor registration, UDI/device registration, Notified Bodies and certificates, and market surveillance — that became mandatory to use as of 28 May 2026, following Commission Decision (EU) 2025/2371 of 26 November 2025, which triggered a six-month transition period under Regulation (EU) 2024/1860. A representative that has not planned for the registration obligations under Articles 27, 29 and 31 ahead of that date carries additional operational work exactly when the manufacturer most needs a smooth registration record.
Frequently asked questions
Can a manufacturer appoint more than one authorized representative in the EU? No — MDR/IVDR requires designation of a sole authorized representative, with the mandate effective at least for all devices within the same generic device group.
Does the EU AR requirement apply to devices used only in clinical investigations? No — sponsors of clinical investigations or performance studies not established in the Union instead appoint a legal representative under Article 62(2) MDR or Article 58(4) IVDR, a role distinct from the market-access authorized representative.
What documents must the representative keep available, and for how long? At minimum, the technical documentation, the EU declaration of conformity and, where applicable, the relevant certificate including amendments, for the retention period set out in Article 10(8).
Is the representative always liable for defective devices? Liability under Article 11(5) is conditional: it applies where the manufacturer is not established in a Member State and has not complied with its Article 10 obligations, in which case the representative is liable jointly and severally with the manufacturer.
Who can act as an authorized representative — an individual or a company? Both can, provided the establishment and mandate conditions are met: the guidance defines the role as open to any natural or legal person established within the Union that has received and accepted a written mandate.
What is the Union market for authorized representative purposes? It covers EU Member State territories and, under the same guidance, is extended through the EEA to Norway, Liechtenstein and Iceland, and through the Customs Union Agreement to Turkey.
Conclusion: a compliance interface, not a formality
Treating the authorized representative as an address that satisfies a labeling requirement misreads what Article 11 actually asks for: a party capable of verifying documentation, retrieving it on request, cooperating on corrective actions, and forwarding complaints without unnecessary delay. Manufacturers that get the most out of the arrangement tend to be the ones that revisit the mandate and the underlying workflows on a recurring basis, particularly after a portfolio change, a Notified Body switch, or any incident that tests the interface under real conditions rather than in theory.
