Chemical (CLP) Compliance

SDS Translation: Which Languages Your Safety Data Sheet Needs in the EU

REACH requires a safety data sheet in the official language of every Member State where you sell. Which languages you need, why translation is really localisation, and how to keep versions in step.

Laboratory bottles with GHS hazard pictograms on a shelf

You have a compliant safety data sheet in English, your first order from a French distributor is ready to ship, and the buyer asks for the SDS in French. This is the moment most chemical sellers discover that SDS translation is a legal requirement rather than a customer service gesture. Under REACH, a safety data sheet has to be supplied in an official language of every Member State where the product is placed on the market, and an English file only satisfies that rule in a handful of countries.

This guide explains exactly what the law requires, which languages you need country by country, why a good translation is closer to localisation than to word for word rendering, and how to keep a set of language versions consistent as your SDS changes over time. It is written for makers, importers and distributors of candle fragrances, diffuser bases, cleaning products, raw materials and other chemical mixtures who are expanding beyond their home market.

Key takeaways

  • REACH Article 31(5) requires the SDS in an official language of each Member State where you place the product on the market, unless that Member State provides otherwise.
  • Selling into several countries usually means several language versions, and some countries with more than one official language expect more than one.
  • A translated SDS must be localised, not only translated: the emergency telephone number, occupational exposure limits and national legislation sections change per country.
  • Translation does not fix errors. A non-compliant source SDS produces non-compliant translations in every language.
  • The SDS language must match the CLP label language for the same market, with identical hazard statements and precautionary statements.
  • Every revision of the source SDS triggers a revision of every language version, and recipients from the previous 12 months must receive the update.
  • Most finished cosmetic products do not need an SDS at all, but the raw materials and fragrance oils behind them usually do.

What the law actually says

The safety data sheet is governed by Article 31 of REACH, Regulation (EC) No 1907/2006, with its format and content set out in Annex II as replaced by Regulation (EU) 2020/878. The language rule is short. Article 31(5) states that the SDS shall be supplied in an official language of the Member State or States where the substance or mixture is placed on the market, unless the Member State or States concerned provide otherwise.

Three consequences follow from that sentence.

The obligation follows the market, not the supplier

It does not matter where you are established or what language your company works in. What matters is where your customer receives the product. A Dutch manufacturer shipping to Poland owes a Polish SDS. A UK or Turkish exporter selling through an EU importer still needs the importer to be able to pass on an SDS in the right language, and in practice the importer will ask the manufacturer to provide it. Our guide to importing chemicals into the EU covers how those duties are split.

The default is the national language

English is not a lingua franca under REACH. It is an official language only in Ireland and Malta. Some Member States formally accept English for professional or industrial users, but that is a national exception you have to confirm, not a general rule you can assume.

The duty is to supply, at the latest on first delivery

Article 31(8) requires the SDS to be provided free of charge, on paper or electronically, no later than the date the product is first supplied. A translation that arrives a month after the goods is a late SDS, and a late SDS is treated the same way as a missing one.

Which languages you need, country by country

For most Member States the answer is simply the national language. The countries that catch sellers out are those with more than one official language, and those that have formally relaxed the rule for certain users. The table below is a planning aid rather than a legal opinion: national rules change, and you should confirm the current position before relying on any exception.

Market Language expected on the SDS Watch out for
Germany, Austria German National exposure limits in section 8 differ between the two countries
France French Section 1.4 should give the French poison centre number (ORFILA)
Belgium Dutch, French and German, depending on the region of delivery Many suppliers provide Dutch and French as standard to cover both main regions
Luxembourg French or German Customers frequently ask for both
Netherlands Dutch Check whether English is accepted for your specific professional customers before relying on it
Italy, Spain, Portugal Italian, Spanish, Portuguese Spain has co-official regional languages, but Spanish satisfies the REACH rule
Finland Finnish and Swedish Both national languages are commonly required
Poland, Czechia, Slovakia, Hungary, Romania The national language English is not accepted as a substitute
Ireland, Malta English (Irish or Maltese also official) An English SDS normally satisfies the rule

If you sell through a marketplace or a distributor that ships across borders, the question is not where your warehouse is but where the product ends up. A distributor in Germany reselling into Austria and Switzerland needs German versions localised for each country, and the Swiss version sits under Swiss chemical law rather than REACH.

The SDS and the CLP label move together. Article 17(2) of CLP requires the label in the official language of each Member State where the mixture is placed on the market, so the French SDS and the French label must carry exactly the same hazard statements, precautionary statements and signal word. A mismatch between label and SDS is one of the easiest findings for an inspector to make. See our guide to CLP label requirements.

Why SDS translation is really localisation

A safety data sheet is not a brochure. Several of its 16 sections contain information that is specific to the country of supply, so a literal translation of the source file can be accurate word for word and still wrong in law. If you need a refresher on the structure itself, start with what a safety data sheet is.

Section 1.4: emergency telephone number

Annex II requires an emergency number, and where the Member State has an appointed body under Article 45 of CLP, that body’s number. A French SDS that lists the German poison centre is not a French SDS. Each language version needs the right national number, plus the hours of availability if the line is not staffed around the clock.

Section 2: label elements

Hazard statements and precautionary statements have official, fixed wording in every EU language, published in the CLP annexes. A translator who paraphrases H317 instead of using the official text has produced a non-compliant SDS, however fluent the result. The same statements must also appear on the label in that language.

Section 8: exposure controls

Occupational exposure limits are partly harmonised through EU indicative values and partly national. Each language version should list the limits that apply in the country of supply, which means the German version, the French version and the Polish version may legitimately show different numbers for the same substance.

Section 15: regulatory information

This section points to the EU and national rules that apply to the product, such as national water hazard classes, worker protection rules or restrictions. Copying the source country’s references into another country’s SDS is a common and easily spotted error.

Units, decimals and terminology

Flash points, vapour pressures and concentration ranges must stay numerically identical across versions, but decimal separators, date formats and chemical nomenclature follow local conventions. Substance names should use the identifiers recognised in that language, with CAS and EC numbers unchanged.

Stacked chemical drums with orange lids in storage
The same mixture shipped to three countries needs three SDS versions, each with its own emergency number and exposure limits.

Translation cannot fix a non-compliant SDS

The most expensive mistake in this area is translating a source SDS that was never compliant to begin with. Older files still in circulation often follow the pre-2023 format, lack the nanoform and endocrine disruptor fields introduced by Regulation (EU) 2020/878, list a UFI in the wrong place or omit it entirely, or carry a classification that no longer matches the current CLP annexes. Every one of those defects is copied faithfully into every language version, and each translation then has to be corrected separately.

That is why a sensible workflow starts with a check of the source document. If the SDS came from your own regulatory provider and is current, translation can begin immediately. If it came from a supplier, a contract manufacturer or a previous consultant, it should be reviewed against Annex II first. The relationship between SDS, UFI and poison centre filings is covered in from SDS to PCN, and the UFI itself in what a UFI code is.

Machine translation is not a shortcut. Automated tools paraphrase hazard and precautionary statements that must be quoted in their official wording, translate trade names that should stay untouched, and have no way of knowing which national emergency number or exposure limit belongs in the file. A machine translated SDS that reaches an inspector or a poison centre is treated as the supplier’s own document, with the supplier’s liability.

Keeping language versions in step

Producing the first set of translations is the easy part. Keeping them aligned is where multilingual compliance usually breaks down.

Revisions cascade

Article 31(9) requires the SDS to be updated without delay when new hazard information becomes available, when an authorisation is granted or refused, or when a restriction is imposed. The updated version, marked as a revision with the date, must go to every recipient supplied in the preceding 12 months. If you hold six language versions, a single change to the source means six revisions and six distribution lists.

Version control

Each language version should carry the same revision number and date as the source, so that anyone comparing them can see they describe the same formula. Keep a simple register listing every product, every language, the current revision and the date it was sent to customers in that market.

Triggers worth watching

  • Classification changes. An adaptation to technical progress that reclassifies one of your ingredients can change the mixture classification, the label and every SDS at once.
  • Formula changes. A new supplier for a fragrance component or a different solvent can move the mixture across a classification threshold.
  • New markets. Entering a new country adds a language version and, for hazardous mixtures, usually a poison centre notification as well. See what poison centre notification is.
  • National updates. A change to a national exposure limit only affects that country’s version, which is easy to miss if versions are maintained by different people.

Who needs an SDS in the first place

Before commissioning translations, confirm that the product needs an SDS at all. Under Article 31, an SDS is required for substances and mixtures classified as hazardous under CLP, for PBT and vPvB substances, and on request for certain unclassified mixtures that contain hazardous components above set thresholds.

Finished cosmetic products intended for the end user are outside the REACH information duties, so a face cream or a shampoo sold to consumers does not need an SDS, translated or otherwise. The picture changes upstream: fragrance oils, essential oils sold in bulk, surfactant blends and other raw materials supplied to cosmetic manufacturers usually do. Our comparison of CPSR, PIF and SDS explains which document belongs to which product.

Products that sit squarely in CLP scope, such as reed diffusers and candles and detergents and cleaning products, are where translation requests arrive most often, because they are sold through multi-country retail and wholesale channels.

Bringing it all together

An SDS is only compliant in a market if it is in that market’s language and carries that market’s information. Article 31(5) makes the language a legal requirement, and Annex II makes several sections country specific, so selling into five Member States typically means five localised documents rather than one English file and a good intention.

The work is manageable when it is approached in the right order: confirm the source SDS is current and compliant, translate using the official CLP wording, localise the emergency number, exposure limits and national legislation for each country, match the label, and then keep every version on the same revision as the formula and the regulations change.

Lexora translates and localises safety data sheets into any EU language, with official hazard wording and country specific sections checked for each market. Order an SDS translation for an existing document, commission a new compliant source file through safety data sheet preparation, or cover the label, UFI and notifications at the same time with the CLP compliance suite.

Frequently asked questions

Does an SDS have to be in the local language?

Yes. Article 31(5) of REACH requires the safety data sheet to be supplied in an official language of each Member State where the substance or mixture is placed on the market, unless that Member State has provided otherwise. An English SDS only meets the rule automatically in Ireland and Malta.

Can I supply one English SDS for the whole EU?

Generally not. A few Member States accept English for professional or industrial users under national rules, but this is an exception you must confirm for each country. For consumer and retail channels, and for most Member States, you need a version in the national language.

Is translating the text enough, or does the content change?

The content changes. The emergency telephone number in section 1.4, the occupational exposure limits in section 8 and the national legislation in section 15 are country specific, and the hazard and precautionary statements must use the official CLP wording in that language. A literal translation of the source file is often not compliant.

Can I use machine translation for an SDS?

It is risky. Machine tools paraphrase hazard statements that must be quoted verbatim, translate trade names and cannot insert the correct national emergency numbers or exposure limits. The supplier remains legally responsible for the translated document, so any errors carry the same liability as errors in the original.

Do I need to update every language when my SDS changes?

Yes. Article 31(9) requires an updated SDS to be sent without delay to everyone supplied in the previous 12 months, and that applies to each language version. All versions should share the same revision number and date so they can be matched to the same formula.

Can you translate an SDS prepared by another company?

Yes, but it should be reviewed first. Translating a non-compliant SDS copies its errors into every language, so a third-party file is checked against Annex II as amended by Regulation (EU) 2020/878 before translation. If the source needs substantial correction, a new SDS preparation is usually the cleaner route.

Do cosmetic products need a translated SDS?

Finished cosmetics sold to consumers do not need an SDS at all, because they are outside the REACH information requirements and are covered by the Cosmetic Regulation instead. Cosmetic raw materials, fragrance oils and bulk ingredients supplied to manufacturers usually do, and those SDSs follow the same language rule.