EU CLP, REACH, OSHA HazCom, GHS Rev.10, and national annexes. A practical compliance guide for EHS directors managing safety data sheets across multiple markets.
Jump to jurisdiction comparison ↓Each of these gaps is individually auditable. In combination, they represent systemic compliance risk across every market where you supply chemicals.
CLP Regulation Annex III and Annex IV prescribe the exact wording for each H-code and P-code in every EU language. A "translation" of a hazard statement is non-compliant if it does not match the legally prescribed text word for word. Many SDS operations translate these phrases generically instead of looking up the official text.
Paraphrased H/P-codes = non-compliant SDSSection 8 must reference the OELs applicable in the target country. Germany uses MAK values (DFG). France uses VME/VLE (INRS). Spain uses LEP (INSST). The UK post-Brexit uses WELs (HSE). Copying the source SDS exposure limits into all language versions creates non-compliance in every market except the source.
Generic OELs = wrong in every countryAdaptations to Technical Progress (ATPs) to the CLP Regulation periodically reclassify substances and update hazard communication. When an ATP changes a classification, every language version of every SDS containing that substance needs updating. SDS operations without version tracking across languages accumulate compliance drift with every ATP.
Each ATP = potential update across all languagesBeyond EU harmonization, individual member states add requirements. France requires specific poison center phone numbers and INRS references. Germany has additional water hazard classification (WGK). Nordic countries have specific labeling for consumer products. A "standard EU translation" misses these local obligations.
CLP requires that the classification, hazard statements, and precautionary statements on the label match those in the SDS. When labels and SDS are translated by different processes or at different times, inconsistencies appear. An inspector who finds different hazard statements on the label and in the SDS will flag a non-compliance regardless of which version is correct.
Label says one thing. SDS says another.The 16-section GHS format is the same. The content requirements within those sections vary by jurisdiction. Here is where the differences matter most.
| SDS Element | EU (CLP/REACH) | US (OSHA HazCom) | Key Difference |
|---|---|---|---|
| Language requirement | Official language of each member state where product is placed on market | English required; other languages recommended but not mandated | EU: up to 24 languages mandatory. US: English only legally required. |
| Hazard statements | Exact text from CLP Annex III (legally mandated per language) | GHS-aligned with some US-specific modifications | EU text is prescribed. US allows minor wording variation. |
| Section 8 (OELs) | National OELs of target country (varies by member state) | OSHA PELs, ACGIH TLVs | EU: different values per country. US: single federal system. |
| Section 14 (Transport) | ADR/RID (road/rail), IMDG (sea), IATA (air) | DOT 49 CFR, IMDG, IATA | Different transport classification systems. |
| Section 15 (Regulatory) | REACH registration, SVHC, national restrictions | TSCA, state-specific (Prop 65, etc.) | Completely different regulatory frameworks. |
| Update trigger | REACH Art. 31(9): new info, authorization, restriction, reclassification | HazCom: within 3 months of new significant info | Different timelines and trigger criteria. |
Each approach handles the complexity differently. The question is whether your current approach catches all five gaps above.
EHS staff or internal translators handle SDS translation using phrase libraries and reference documents. Quality depends on the individual translator's regulatory knowledge. Version tracking is typically manual (spreadsheets). Works for small portfolios in few languages. Breaks at scale.
SAP EHS, Lisam, Sphera, or similar tools generate SDS from regulatory databases. Phrase libraries handle standard H/P-codes. Limitations: phrase libraries may lag behind ATP updates, free-text sections still require human translation, and country-specific OELs need manual verification. The tool handles structure, not linguistic compliance.
A dedicated team with regulatory terminology expertise translates SDS using validated phrase databases for mandated text (H/P-codes), country-specific OEL references, and professional translation for free-text sections. Automated validation catches discrepancies. Complete audit trail per document, per language, per revision.
Three phases: regulatory mapping, structured translation, and ongoing compliance monitoring. Built for audit readiness from day one.
Audit your SDS portfolio: how many products, which markets, which languages. Map the regulatory requirements per jurisdiction: mandated H/P-code text, country-specific OELs, national annexes, and local requirements. Identify which SDS are current and which have compliance gaps from recent ATP updates.
Each SDS is translated section by section. Mandated text (H/P-codes) is looked up from validated regulatory databases, not translated. Country-specific values (OELs, poison center numbers, transport classifications) are sourced from national references. Free-text sections are translated by specialists with regulatory terminology knowledge. Every section is validated before delivery.
When a source SDS is updated (new classification, ATP change, formulation change), the system identifies which language versions need revision. Updates are propagated to all affected languages. Each revision is documented with a complete audit trail: what changed, why, when, and who validated the change.
Published metrics from long-term operations handling regulated healthcare and pharmaceutical content, including safety-critical materials.
*Terminology consistency measures approved-term usage in regulated content. Distinct from overall terminology accuracy (97%) across all content types.
A pharmaceutical company with operations across 25+ markets relied on the same specialist team for years to handle regulated content including safety communications, clinical documentation, and compliance materials. Zero regulatory rejections due to translation errors to date. 99%+ terminology accuracy across all pharmaceutical and cosmetic terms. Every document validated against the relevant regulatory framework before delivery. The team that handled the first regulatory submission still handles the portfolio today.
"AI liability forces risk-based quality models. Organizations are investing in formal governance for AI-generated content. A major legal case involving harm from faulty AI translation is likely in 2026."CSA Research, Prediction #8, 2026
"Global content becomes a CX/UX differentiator. Content must be locale-ready, regulation-aware, and culturally tuned."CSA Research, Prediction #4, 2026
"Speed and scale matter less than auditability, explainability, governance, and trust."CSA Research, Human-at-the-Core Prediction, 2026
Under REACH Regulation (EC) No 1907/2006, Article 31(5), an SDS must be provided in the official language(s) of each EU member state where a substance or mixture is placed on the market. This means up to 24 official languages across the EU/EEA. Each translation must use the legally mandated hazard and precautionary statement text from CLP Regulation Annex III and Annex IV.
The EU follows CLP Regulation 1272/2008 with mandatory translations into each member state's official language. The US follows OSHA HazCom 2012 (updated 2024), which aligns with GHS but has US-specific requirements. The 16-section format is the same, but content within sections (especially Sections 8, 11, 14, and 15) varies by jurisdiction.
In the EU, supplying a substance without an SDS in the official language of the receiving member state violates REACH Article 31. Enforcement varies by country but can include market withdrawal orders, fines, and regulatory holds. Downstream users must have SDS in their workers' language. If they cannot because you supplied an untranslated SDS, liability traces back to you.
Under REACH Article 31(9), SDS must be updated when new risk management information becomes available, when a substance receives an authorization or restriction, or when a new classification is assigned. ATP updates to CLP also trigger mandatory revision. Each update must be propagated to all language versions. An updated English SDS with outdated translations creates a compliance gap in every other market.
Five most common: incorrect or paraphrased H/P-code statements (must match exact legally mandated text), wrong country-specific OELs in Section 8, outdated classifications after ATP amendments, missing translations for active markets, and inconsistency between SDS and label. Each can be caught with proper controls but is frequently missed in high-volume operations.
Three systems working together: a regulatory terminology database for mandated H/P-code text per language, a country-specific reference database for OELs and national requirements, and version control tracking which SDS version has been translated into which languages. When a source SDS is updated, the system identifies which translations need revision.
EHS tools (SAP EHS, Lisam, Sphera) handle SDS generation and some regulatory data. They include phrase libraries for H/P-codes. Limitations: phrase libraries may not cover all languages or lag after regulation changes, country-specific OELs need manual verification, and free-text sections still require professional translation. The tool handles structure. Linguistic compliance requires additional expertise.
GHS provides the international framework: 16-section format, classification criteria, hazard/precautionary statement system. But GHS is implemented through national or regional regulations (EU CLP, US HazCom, Brazil NR 26) that may add requirements or modify classifications. GHS compliance alone does not guarantee compliance in any specific market. You must meet the implementing regulation of each jurisdiction.
Send us one SDS from your portfolio. We review the translated versions against regulatory requirements for your target markets and identify compliance gaps.
Prefer email? ricard@kobaltlanguages.com