Your Supplier SDS Is Not in English: What to Do

Ordering a small batch of a specialty extract from a supplier overseas is usually the easy part. Then the SDS arrives, and it's entirely in German, or Mandarin, or Korean, and you're staring at a document you need to extract regulatory data from and can't read a word of.

This happens more than people expect, especially with niche botanical suppliers, and it's worth having a plan for it rather than reaching for a browser translation plugin and hoping for the best.

Why machine translation alone is risky here

Running an SDS through automatic translation will usually get you something readable, and for general orientation that's fine. The problem is precision. Chemical and regulatory documents are dense with specific terms where a slightly-off translation changes the meaning: hazard classifications, concentration ranges, exact substance names. A translation tool that renders a chemical term into a near-synonym instead of the exact recognized name can send you down the wrong path when you're trying to match a CAS number or confirm a restricted-substance status.

Machine translation is a fine first pass for getting oriented. It is not a substitute for an authoritative document when the numbers matter.

What to actually request from the supplier

The cleanest fix is going back to the source. Most suppliers who export internationally already maintain SDSs in multiple languages, because plenty of their other customers have needed exactly what you need. A short, direct request usually works:

• Ask specifically for the English-language version of the SDS for the exact product code you purchased.
• If you're filing in Canada, ask whether they also have a French version, since Canadian labels need to be bilingual and having both on hand up front saves a second round of requests later.
• Confirm the version date matches or is more recent than the foreign-language copy you already have, so you're not comparing two different revisions.

Larger suppliers with regulatory affairs teams can often turn this around quickly. Smaller or highly specialized suppliers, especially single-origin botanical producers, may only have the SDS in their local language and may need to generate an English version specifically for you. Build a little lead time into your sourcing timeline for this rather than assuming it lands in your inbox the same day you ask.

If an official translation genuinely isn't available

Sometimes a small supplier simply doesn't have the resources to produce a certified English version, and you're stuck working with what you have. A few things help in that situation:

1. Get the composition section translated professionally, even if nothing else is. Section 3, with its CAS numbers and concentration data, is the part you actually need to be precise. If budget or time only allows translating one section, that's the one.
2. Verify CAS numbers independently. CAS numbers are not language-dependent. If the foreign-language SDS includes them, you can confirm the corresponding INCI name and substance identity through the CAS number itself rather than relying entirely on the translated text.
3. Ask your supplier for a certificate of analysis (COA) as a cross-check. COAs are often more standardized and numeric, with less prose to mistranslate.
4. Document what you did. If a regulator or reviewer ever asks how you confirmed an ingredient's identity, having a clear paper trail of what you requested, what you received, and how you verified it matters more than people expect.

The Canada-specific angle

Because Canadian cosmetic labels must be bilingual in English and French, some makers assume a French-language SDS is automatically "good enough" for a Canadian filing since French is one of the two official languages. It's worth being careful here. A French SDS from a European supplier is still a foreign document from Health Canada's perspective if it doesn't match Canadian labeling and terminology conventions, and you'll still want an accurate English (or English and French) reading of the composition data before relying on it for your CNF.

Where this fits into the bigger filing picture

A hard-to-read SDS is exactly the kind of friction point that causes people to guess instead of verify, and guessing on ingredient identity is where problems start. If you're already working through Cosmetic Comply for the INCI and CAS mapping side of a filing, flag a translation issue early. A reviewer looking at incomplete or uncertain supplier documentation before filing is a much better outcome than a notification going out built on a best-guess translation of a chemical composition table.