This guide is for product stewards and EHS teams at chemical manufacturers selling or planning to sell in multiple countries. It outlines a four-part process and concludes with a checklist for evaluating SDS authoring software.
This article is for informational purposes only and does not constitute legal advice. Please consult the primary sources linked below and confirm details with your regulatory professional.
Why translating a finished SDS does not work
An SDS is more than translated text. Each market may require different content, not just different wording.
Classifications vary by country. Different GHS revisions and building blocks mean the same mixture may have different hazard classes in different markets.
Required sections also differ. The EU requires REACH and CLP details, Canada mandates English and French, and Section 8 exposure limits vary by country.
Regulated phrases must use fixed wording. H-statements and P-statements have official translations. A paraphrase may be accurate in meaning but still non-compliant.
Updates become complex. When a formula or regulation changes, each translated version must be located and updated manually.
This leads to documents diverging over time, with no single record confirming accuracy.
Step 1: Author from one source product record
Each language and country version should be built from a single master product record, not from another SDS. This record contains market-invariant data such as composition, CAS numbers, concentrations, physical and chemical properties, and test data.
When the formula changes, update the record once. All market versions are then rebuilt from it, ensuring translations remain current.
Best practice: maintain one record per product that feeds all outputs, with each input source documented, whether from a supplier SDS, your own data, or a regulatory database.
Step 2: Map each market to its GHS revision and country rules
Before producing any language version, apply each target market's regulatory profile to the source record. This profile determines the required content, not just the wording.
| Market | Language requirement | Examples of country-specific content | Source for the language rule |
|---|---|---|---|
| United States (OSHA HCS 2024) | English | OSHA hazard classes, US exposure limits | 29 CFR 1910.1200(g)(2) |
| Canada (WHMIS 2015) | English and French | Canadian exposure limits, supplier identifier rules | Hazardous Products Regulations, s. 6.2 |
| Mexico (NOM-018-STPS) | Spanish | Mexican exposure limits and format requirements | NOM-018-STPS-2015, 9.1 b) |
| European Union (CLP and REACH) | Official language of each member state where it is sold | UFI codes, REACH registration numbers, EU exposure limits | REACH Regulation, Article 31(5) |
| United Kingdom (GB CLP) | English | GB-specific classification and exposure limits | UK REACH, Article 31(5) |
Classification should be determined for each market based on rules using the same inputs. This ensures that differences in hazard classes between the EU and the US result from regulatory rules, not translation choices.
Step 3: Build each language from a human-reviewed phrase library
The most reliable way to produce an SDS in another language is to assemble it from approved phrases rather than translating free text. A phrase library stores each standard statement once, with a reviewed version in every supported language.
Regulated statements use official wording. H-statements, P-statements, and other standard phrases come from the library in each language's approved form.
Each phrase is reviewed by technical specialists and professional translators before it is included in the library.
A single phrase update applies to all SDSs. When a phrase is corrected or regulations change, every affected SDS can be rebuilt automatically.
Machine translation of free text is the weak point in most multilingual processes. The more of the SDS that comes from a reviewed library, the less of it depends on an unchecked translation.
Step 4: Connect SDS authoring to the systems you already run
Multilingual SDSs remain current only if product data is imported automatically and finished documents are distributed without manual re-entry. Formula data typically resides in an ERP, and completed SDSs must reach customers, distributors, and labeling systems.
Select SDS software with a documented REST API to enable integration with ERP systems such as SAP and Oracle, as well as any other system that supports a REST API. Request that vendors demonstrate a working integration rather than providing only a list of compatible systems.
Checklist: evaluating multilingual SDS authoring software
Use these questions to compare platforms such as Lisam ExESS, UL Solutions, Verisk 3E, SDS Manager, and Valenc.
| Capability | What to ask the vendor | Why it matters |
|---|---|---|
| Single source record | Are all languages and countries built from one product record? | Prevents versions from drifting apart |
| Per-market classification | Is classification determined separately for each market's rules? | Hazard classes can legally differ by country |
| Phrase library review | Who reviews each phrase, and in which languages? | Regulated wording must be exact |
| Languages supported today | Which languages are live now, and which are on the roadmap? | Roadmap languages cannot ship today |
| Change propagation | When a phrase or regulation changes, which SDSs are flagged? | Avoids hunting for affected documents |
| Input traceability | Can you see where every input value came from? | Needed to defend an SDS in an audit |
| Integrations | Is there a documented REST API? Can you show an ERP connection? | Keeps formula data and SDSs in sync |
| Pricing and users | Is pricing per user, per SDS, or flat? | Multilingual programs add users and documents fast |
How Valenc handles multilingual SDS authoring
Valenc creates each SDS from a single product record, determines market-specific classifications using a deterministic rules engine, and assembles each language version from a phrase library reviewed by experts.
Phrase library: 28 locales currently supported. Each phrase is reviewed by Valenc's technical team and professional technical translators before use.
Languages in development: expansion to over 55 languages, including Chinese, is underway.
Regions currently supported: United States, Canada, Mexico, European Union, United Kingdom, and UN GHS.
Regions in development: support for Brazil, Argentina, Chile, Colombia, Ecuador, Costa Rica, China, Japan, Korea, South Africa, Australia, and New Zealand is in progress.
Our REST API connects to SAP, Oracle, and any other system that supports REST APIs.
AI is used optionally to extract data from supplier SDSs and to review finished documents. It does not classify products or translate regulated phrases.
When regulations change, Valenc checks each product and flags any affected SDSs in all languages as out of date.
Frequently asked questions
Can I simply translate my English SDS into other languages?
Not reliably. Other markets may need different classifications, sections, or exposure limits, so the content changes as well as the language.
What languages does an SDS need?
It depends on where you sell the product. Canada requires English and French, Mexico requires Spanish, and EU member states require their official languages.
Is machine translation okay for SDSs?
It is risky for regulated statements, which must use official wording. Using a phrase library reviewed by people is safer.
How do I keep translated SDSs up to date?
Create every version from a single product record. This way, one change updates all languages. Use software that flags affected SDSs when regulations change.
Can SDS software connect to SAP or Oracle?
Yes, if it supports a REST API. Ask your vendor to show you a working ERP integration.
