Declaration of Conformity translation requirements — every EU language explained

A signed Declaration of Conformity does not satisfy CE marking obligations on its own — it must reach the end user in the language of the EU member state where the product is sold. This article walks through the language obligation, which document the manufacturer drafts in (the master language), how translations are produced and distributed, what counts as a valid translation, and the costs.

The legal obligation

Article 27 of the Cyber Resilience Act:

"The EU declaration of conformity shall be drawn up in or translated into the language or languages required by the Member State in which the product with digital elements is placed on the market or made available on the market."

Article 10(11) of the Radio Equipment Directive:

"Manufacturers shall ensure that the radio equipment is accompanied by […] the EU declaration of conformity […] in a language which can be easily understood by consumers and other end-users, as determined by the Member State concerned."

Article 10(11) of the Medical Device Regulation imposes the same obligation for medical devices.

Pattern across all major directives:

1. The manufacturer drafts the DoC in any of the 24 official EU languages
2. A translation into the official language(s) of the member state of sale must accompany the product on first delivery to the end user
3. Member states determine which of their official languages applies (Belgium has three official languages — Dutch, French, German — but distributors typically supply the regional language)

The 24 official EU languages

The DoC may be drawn up in or translated into any of:

For EEA states (Norway, Iceland, Liechtenstein), English is in practice accepted but each state can require its own language. Switzerland is not in the EEA; CE marking is accepted under bilateral agreements and Swiss official languages (German, French, Italian) are practically honoured.

Three practical approaches to compliance

Approach 1 — Single master + per-country translation on demand

The manufacturer drafts the DoC in one language (typically English). When a distributor in Germany orders product, a German-language translation accompanies that shipment. The translation is produced once per country and reused.

• Pros: Minimal physical bulk; simple master document
• Cons: Distribution complexity; risk of shipping a product to a market without prepared translation
• Best for: Products with a few large markets

Approach 2 — Multi-language DoC booklet

The manufacturer produces a single multi-language DoC containing all 24 official EU languages in one document. The same booklet ships with every product regardless of destination.

• Pros: One product configuration for the whole EU; no per-country logistics
• Cons: Physical document is larger; updating one language version requires reprinting the whole booklet
• Best for: Consumer products distributed across many EU member states

Approach 3 — DoC published online (CRA Article 28(2))

For products with digital elements covered by CRA Article 28(2):

"Where the Union legislation applicable to a product with digital elements requires that the EU declaration of conformity accompany the product, manufacturers shall […] include in such product with digital elements information enabling the end user to obtain easy access to that declaration."

The DoC translations are hosted at a publicly accessible URL and a QR code or printed URL accompanies the product. End users in any EU member state scan the QR code and retrieve the DoC in their official language.

• Pros: Single source of truth; updates propagate instantly; no physical bulk; aligned with how Cenitia operates
• Cons: Requires permanent hosting; QR or URL must remain valid for the retention period
• Best for: Connected products under CRA — the natural format

Cenitia produces multi-language DoCs by default and hosts them at a public verification URL per the Article 28(2) model. Each language version is updated atomically when a regulation amends.

What counts as a valid translation

There is no requirement that the translation be produced by a certified translator. The directive requires the DoC be in the relevant language — the translation method is not prescribed.

In practice, market surveillance authorities have rejected DoCs where the translation contained material errors:

• Incorrect directive citation — the German translation cites Regulation 2014/53/EU as Richtlinie 2024/53/EU instead of Richtlinie 2014/53/EU (digit error)
• Incorrect product identification — the model number changed in translation
• Mistranslated statement of sole responsibility — element 4 deviates from the literal directive text in translation
• Incorrect Notified Body number — typographic error in translation introduces a non-existent NB number

For elements 1, 3, 4, 5, 6, 7, 9 of the DoC, the translation should be professionally reviewed even when produced by machine translation as a starting point. The legal claim is what matters; the prose around it less so.

Specifically:

• Element 1 — manufacturer name and address — typically not translated (company names and addresses are proper nouns)
• Element 3 — product identification — typically not translated (product names and model numbers are not translated)
• Element 4 — statement of sole responsibility — translation must match the directive's official-language version verbatim; check Article 27 of CRA for example, which provides equivalent wording in each official language
• Element 5 — applicable directives — directive titles are translated to their official-language EUR-Lex titles; do not retranslate informally
• Element 6 — harmonised standards — typically NOT translated (standard codes like "EN 18031-1:2024" are not localised)
• Element 7 — Notified Body — name and address typically not translated
• Element 9 — place, date, name, function — translated; the signature is what it is

Cost of multi-language DoCs

Order-of-magnitude ranges for a one-page DoC translated into all 24 EU official languages, first translation:

• Machine translation (DeepL, Google) with no review — €0 in tooling, ~30 min of internal time
• Machine translation with native-speaker review per language — €300 to €800 total for all 24 languages
• Professional translation agency — €1 500 to €4 000 for all 24 languages
• Certified translation — €5 000 to €12 000 for all 24 languages, typically required only for medical devices and certain regulated sectors

Subsequent revisions (when a directive amends or product changes) — typically 20-40% of initial cost depending on whether re-translation of unchanged elements is needed.

Most consumer-product manufacturers use the machine translation + native-speaker review model. Professional translation is reserved for elements 4, 5, and 7 where a translation error has direct legal consequence.

What about technical user documentation?

The DoC translation obligation is separate from the obligation to translate user documentation. Under RED Article 10(8):

"Manufacturers shall ensure that the radio equipment is accompanied by instructions and safety information in a language which can be easily understood by consumers and other end-users, as determined by the Member State concerned."

Both obligations exist in parallel. Both apply to the same languages. Both must accompany the product on first delivery. The DoC is one document; the instructions and safety information are separate documents.

User manuals are typically much longer than the DoC, so user-documentation translation costs dominate the budget for consumer products — often €10 000 to €50 000 for a 50-page manual into all 24 EU languages.

Common translation mistakes

From the Inovasense compliance practice:

• English-only DoC sold in non-English markets. Most common Asian-OEM mistake. Customs at first import to Germany or France impounds shipments without language-of-market DoC.
• Outdated translation referencing a superseded directive version. The English master is updated; the German translation is from 2024 and still cites 2014/53/EC (old enumeration).
• Element 4 wording paraphrased in translation. "We declare under our sole responsibility…" instead of the official-language verbatim from the directive. Audit risk.
• Multi-language booklet missing one language. The booklet covers 23 of 24; the product reaches Maltese market without Maltese-language DoC.
• Machine translation introducing digit errors in directive citations. "2014" becomes "2024" — a one-digit error invalidates the citation.
• Online URL for the DoC behind authentication or a paywall. The URL must be publicly accessible; behind a login it does not satisfy CRA Article 28(2).
• URL valid at time of sale but offline a year later. Hosting must persist for the retention period.

How Cenitia handles translations

Cenitia generates the DoC in 24 official EU languages by default, hosted at a public QR-verifiable URL. The same QR code on the product resolves to the correct language for the visitor's locale. When a regulation amends and the DoC is reissued, all 24 language versions update atomically. Hosting persists for ten years per CRA Annex VII retention requirements.

For products with custom regulatory contexts (UKCA mark, US FCC marking, Swiss requirements), Cenitia can extend the language set on request.

Frequently asked questions

In what language must the Declaration of Conformity be drawn up?

In any of the 24 official languages of the European Union. The original drafting language is the manufacturer's choice — English is by far the most common, but Slovak, German, French, or any other official language is equally valid. Each member state's authorities can request a translation into the language(s) determined by that member state at the time of inspection.

Does the DoC have to accompany the product in the language of the country of sale?

Yes. Under CRA Article 27, RED Article 10(11), MDR Article 10(11), and parallel provisions in other directives, the DoC (or its translation) must accompany the product and must be in the official language(s) of the EU member state where the product is made available to the end user. Selling a product in Germany requires a German-language DoC; in France a French-language DoC; in Italy an Italian-language DoC.

Can I attach all 24 EU language translations to every product?

Yes, this is the simplest approach for products sold across the EU. Many manufacturers produce a single multi-language DoC booklet that contains the document in all 24 official languages. The downside is bulk; the upside is that a single product configuration ships to every market without per-country DoC management. For online-distributed software products, hosting the DoC translations on a publicly accessible URL is also acceptable per CRA Article 28(2).

What languages are 'official' in the EU?

The 24 official EU languages as of 2026: Bulgarian, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Irish, Italian, Latvian, Lithuanian, Maltese, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish, Swedish. Norwegian and Icelandic are not EU official but EEA states (Norway, Iceland) accept English-language DoCs in practice. Switzerland is not in the EEA but accepts CE marking under bilateral agreements — Swiss member-state language requirements (German, French, Italian) are honoured by most exporters.

Is a machine-translated DoC acceptable?

Legally there is no requirement that the translation be human-verified — the directives require the DoC be in the relevant language, not that the translation method be certified. In practice, market surveillance authorities have rejected machine-translated DoCs where the translation contained material errors (incorrect directive citations, incorrect product identification, incorrect Notified Body number). Use professional translation or qualified internal review for the elements that carry legal weight; machine translation as a starting point is acceptable.

What about technical user documentation — does that also need translation?

Yes, but the legal basis is separate. Under Article 10(8) of the Radio Equipment Directive, Article 10(8) of MDR, and similar provisions, instructions for use and safety information must accompany the product in the official language(s) of the member state of sale. The DoC translation requirement is one obligation; the user documentation translation requirement is a parallel obligation under the same directive but it covers different documents.

Related from the Library

• Declaration of Conformity 101 — pillar context
• Sample DoC walkthrough — the structure that gets translated
• CE Marking 101 — umbrella CE marking process

Further reading

• Cyber Resilience Act Article 27 and Article 28
• Radio Equipment Directive Article 10
• Medical Device Regulation Article 10
• Regulation 1/58 on the EU language regime
• Your Europe — language requirements for CE marking

Last reviewed: 25 June 2026. Cited regulations watched continuously by Cenitia — when one amends, this article is flagged for update.