msds-tds/docs/msds-tds-regulatory-compliance-framework.md
2026-07-04 10:56:48 +00:00

204 lines
16 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Project: MSDS/TDS Regulatory Compliance Framework for Solvent Trading
**Status:** Ready
**Tags:** [compliance, trading, solvents]
**Cron:** Email reminder scheduled for Mon 2026-07-06 09:00 EEST
**Started:** 2026-07-03
**See also:** [[meta/Project Dashboard]]
## Goal
Establish a compliant, auditable system for providing MSDS (Safety Data Sheets / SDS) and TDS (Technical Data Sheets) to customers across the EU, North Macedonia, and Serbia — without simply forwarding supplier documents. The system must guarantee documents are always relevant to the latest regulations and branded under the trading company's own identity.
## Jurisdictional Scope
| Country | EU Member | Chemical Law Base | SDS Language | Special Requirements |
|---------|-----------|-------------------|-------------|---------------------|
| **EU (all 27)** | Yes | REACH (EC 1907/2006) + CLP (EC 1272/2008) | Official language of each member state | UFI code required (PCN); Annex II format; EU-based supplier address on label (CLP 2024/2865) |
| **Serbia** | No (candidate) | Aligned with EU REACH/CLP format since Sept 2024 | Serbian | NO UFI/PCN requirement; otherwise EU-equivalent SDS format |
| **North Macedonia** | No (candidate) | Chemicals Act + Consumer Protection Act | Macedonian (Cyrillic) + Albanian | **Bilingual labels and SDS** — both languages mandatory since 2022; fines up to €10K |
## Your Specific Profile (Confirmed)
| Parameter | Your Situation | Implication |
|-----------|---------------|-------------|
| **REACH role** | Importer from outside EU (but quantities are REACH-registered → supplier likely has an Only Representative) | You are **downstream user** IF each supplier's OR covers your tonnage. **Must verify** — get a REACH Certificate of Compliance & Tonnage Coverage Certificate from each supplier's OR. Without it, you are the **importer** and must register. |
| **Packaging** | Tank (bulk) → re-pack into IBCs and drums | You are the **supplier** under CLP. Your company name & EU address go on every label. YOU need PCN/UFI submission (not just forward the manufacturer's). |
| **Composition data** | Cannot always provide full w% — can get supplier SDS version | Pure self-authoring (option C) limited. **Re-branding** (option B) is the practical path for most products. |
| **Product portfolio** | ~10 products, ~10 deliveries each (~100/yr total) | Small portfolio — perfect for consultancy batch approach. No need for expensive software license yet. |
| **Insurance** | None specifically for SDS liability | Needs assessment — see Insurance section below |
| **Territory** | Bulgaria-based → EU + Serbia + North Macedonia | 27+ languages needed for full EU. Balkans-focused consultant ideal (BENS, REGARTIS). |
## Key Regulatory Framework (Current + Upcoming)
### 1. REACH (EC 1907/2006)
- **Article 31**: SDS must be provided by the supplier to the recipient when a substance/mixture is hazardous or contains SVHC ≥0.1%
- **Annex II**: Mandates the 16-section SDS format
- **Distributor role**: You are a **downstream user** — you must ensure your supplier is REACH-registered, pass new hazard info upstream (Articles 34/38), and maintain records for **10 years**
- **REACH Recast**: Stalled (Regulatory Scrutiny Board rejected impact assessment Sept 2025). Expected Q2 2026 at the earliest. Will introduce 10-year registration validity, expanded scope (polymers, low-tonnage)
### 2. CLP (EC 1272/2008) — Amended by EU 2024/2865
- **In force**: 9 December 2024
- **Key changes affecting distributors/traders**:
- **EU-based supplier address mandatory** on labels — if you re-brand/re-package, YOUR address must be on the label
- New hazard classes (endocrine disruptors — ED, PBT, vPvB, PMT, vPvM): apply to **substances from 1 May 2025**, to **mixtures from 1 May 2026**
- Online sales must display CLP Article 17 labelling elements
- Digital labels now permitted (optional)
- Label update deadline: 6 months after classification/labelling change that adds a new hazard class or more severe classification
### 3. Poison Centre Notification (PCN) — UFI Code
- **Current**: Manufacturers/importers must submit PCN with UFI code for hazardous mixtures
- **Starting 1 January 2027**: **Distributors** will also need to notify poison centres in certain situations (new EU rule)
- UFI code appears on SDS Section 1.1 and on the label
- **Serbia**: UFI/PCN does NOT apply
### 4. TDS (Technical Data Sheet) — Unregulated
- **TDS is a commercial/technical document, NOT regulated by REACH or CLP**
- No specific EU regulation mandates TDS format or content
- Contains: physical/chemical properties, typical values, application guidelines, storage, packaging info
- Freedom to design your own TDS format — this is the easiest document to own and control
## Strategic Options for Providing Your Own SDS
| Option | Effort | Control | Supplier Identity Hidden? | Cost |
|--------|--------|---------|--------------------------|------|
| **A) Forward supplier's SDS as-is** | Zero | None | No | Free |
| **B) Re-brand supplier's SDS** (with permission) | Low | Low | ✅ Yes (~€500-2K/yr per substance) | Low |
| **C) Author your own SDS via software** | Medium-High | Full | ✅ Yes (~€3-15K/yr for software license) | Medium |
| **D) Outsource to SDS consultancy** (MSDS-Europe, BENS, REGARTIS, etc.) | Low (you feed data) | Medium | ✅ Yes (~€200-800 per SDS + annual maintenance) | Medium |
### Recommended Path: Hybrid (Option C + D)
Given you trade solvents (relatively simple, well-characterized chemistries) and want independence from suppliers:
**Phase 1 (Immediate)**: Use an SDS consultancy to author the first batch of SDS/TDS for your top 10-20 solvents. They handle classification, language translations, and regulatory updates. Cost: ~€3,000-8,000 one-time + ~€500-1,500/yr for updates.
**Phase 2 (Scale-up)**: Subscribe to SDS authoring software (CHEMDOX, TotalSDS, or 3E) and bring authoring in-house. Feed from supplier data + ECHA public databases. Hire or train one person as Responsible Person for chemical compliance.
**Phase 3 (Integration)**: Build a document management system with version control, expiry tracking, and customer portal for self-service download.
## What You Need From Suppliers
To author your own compliant SDS, you MUST obtain from each supplier:
1. **Full composition** (exact % w/w of all ingredients) — this is the hardest part, suppliers often guard it
2. **Supplier's classification** (hazard classes, categories, H/P statements)
3. **Physical-chemical data** (boiling point, flash point, vapour pressure, density, solubility, etc.)
4. **Toxicological data** (LD50, LC50, skin/eye irritation, sensitisation, etc.)
5. **Ecotoxicity data**
6. **REACH registration number(s)** for all substances
7. **Exposure scenarios** (if substance ≥10 t/y per registrant)
8. **Current SDS of the product** (as reference baseline)
> **Practical note**: Many solvent suppliers (INEOS, Shell, BASF, Brenntag) already provide composition data via their own SDS. For re-branding you can use their classification directly — you're not re-classifying, you're re-publishing with the same classification under your own company name.
## Language Requirements per Destination
| Destination | SDS Language | Label Language |
|-------------|-------------|----------------|
| Bulgaria | Bulgarian | Bulgarian |
| EU member states | Official language of each MS | Official language of each MS |
| Serbia | Serbian | Serbian |
| North Macedonia | Macedonian (Cyrillic) + Albanian | Macedonian (Cyrillic) + Albanian |
**Practical implication**: You need at minimum 29+ language variants for full EU+MK+RS coverage. SDS authoring software handles this with translation databases.
## Insurance: What You Need
Since you re-package (tank → IBC/drums) and put YOUR name on the SDS and label, you assume **supplier-level liability**. Here's what you should know:
### The Actual Risk Profile
- **Practical risk is LOW** for simple solvents (toluene, xylene, acetone, MEK, etc.) — hazards are well-characterized, classifications are harmonized (CLP Annex VI), and hundreds of traders re-brand the exact same data without issues.
- **Meaningful risk** comes from: (a) an incorrect classification that leads to improper handling → accident → injury claim, or (b) missing a regulatory deadline (e.g., PCN/UFI) → administrative fines.
- **New EU Product Liability Directive** (Dec 2026) expands liability scope — but again, your risk with well-known solvents is low relative to, say, a custom-formulated specialty chemical.
### Recommended Insurance Check
You likely already have a **General Liability / Product Liability** policy as a trading company. Ask your broker to confirm:
1. **Does your current policy cover "chemical products" and "hazardous substances"?** Many general liability policies exclude chemicals or have carve-outs.
2. **Does it cover "errors and omissions in technical documentation"** (SDS liability)? This is usually under **Professional Indemnity / E&O**, not general liability.
3. **What about environmental liability?** (spill, improper disposal instruction on SDS)
### Typical Cost
- Adding a chemical products rider to an existing policy: **~€500-2,000/yr** for a small trader with 10 products
- Standalone Professional Indemnity for SDS/documentation: **~€1,000-3,000/yr**
- **Not expensive relative to the risk** — well worth doing once you decide to re-brand.
### Risk Mitigation Without Insurance
Even without dedicated insurance, you can substantially reduce risk:
| Measure | How |
|---------|-----|
| Use supplier classification faithfully | Don't re-classify — use the exact H/P statements from the supplier's SDS |
| Outsource SDS authoring to a specialist | They carry their own PI insurance and indemnify their work |
| Keep 10-year records | You're already required to — this protects you in case of a retrospective claim |
| Include a disclaimer on the SDS | "This SDS is based on information provided by the manufacturer. The user must determine suitability for their specific use." |
| Use a Bulgarian chemical consultant | Local language, local regulatory knowledge, typically €1-3K/yr retainer |
> **Bottom line**: For 10 simple solvent products, the practical liability risk of re-branding the supplier's SDS under your name is low. But getting a product liability rider from your current insurer is cheap and recommended before you start. Do NOT let the insurance question block the project — it's a side track.
## Risk Areas & Open Questions
- [ ] **Composition data**: You confirmed — can't always provide full w%. However, since you trade **pure solvents** (not formulated blends), this is much less of an issue than for a blender. Pure solvents (toluene, xylene, acetone, MEK, etc.) are mono-constituent — 100% w/w of one substance. Their CLP classification is **harmonized** in Annex VI, meaning ALL suppliers classify them identically. No recipe to reverse-engineer. **For pure solvents, re-branding the supplier's SDS is straightforward — just replace their company name with yours on Section 1.3.** The w/w problem only matters if you later start blending your own mixtures.
- [ ] **Liability shift**: When you put YOUR company name on the SDS, you assume supplier-level liability for the document's accuracy. **Mitigated** by: using supplier classification faithfully, outsourcing authoring to insured specialists, and adding a product liability rider (~€500-2K/yr).
- [ ] **REACH registration check**: Do you have written confirmation from each supplier's Only Representative that your tonnage is covered? Get a **REACH Certificate of Compliance** from each OR. If any supplier doesn't have an OR, **you are the importer** and must register.
- [ ] **CLP 2024/2865 supplier address**: Since you re-package (tank → IBC/drums), YOUR company address goes on the label as the EU-based supplier. This is mandatory.
- [ ] **PCN for distributors (Jan 2027)**: Since you re-package AND re-brand, you are already the "supplier" under CLP — you need PCN/UFI **now**, not just in 2027. The Jan 2027 rule extends this to pure distributors (no re-packing), but re-packagers are already covered.
- [ ] **TDS format**: Since it's unregulated, propose a standard format to be designed.
## Execution Plan
### Phase 0 — Audit & Verify (Week 1)
- [ ] List all 10 products: product name, CAS#, supplier, country of origin
- [ ] Collect current supplier SDS for each
- [ ] **CRITICAL**: Contact each supplier's Only Representative (OR) — request REACH Certificate of Compliance & Tonnage Coverage Certificate proving your tonnage is covered
- [ ] Identify which suppliers WILL share full composition data (for those, you can author proper SDS)
- [ ] For suppliers that won't share composition data — confirm they allow re-branding of their SDS (most do)
- [ ] Check your current insurance policy: does it cover hazardous chemical products?
- [ ] Check if you already have a Bulgarian chemical consultant or regulatory advisor
### Phase 1 — First Batch via Consultancy (Weeks 2-4)
- [ ] Choose a Balkans-specialist SDS consultancy (recommended: **BENS Consulting** in Slovenia — they know MK/RS natively, or **REGARTIS** for Serbia/CEE)
- [ ] Send them: 10 supplier SDSs + your company details + target markets (EU+MK+RS)
- They will re-brand → your company name/address on Section 1.3
- They will translate → all required languages
- They will update classifications → compliant with CLP 2024/2865 new hazard classes
- They will generate UFI codes → for PCN submission
- [ ] Expected cost: **~€3,000-6,000** for 10 products × 3 regional variants (EU core + MK + RS)
- [ ] Author your own **TDS** in-house (no regulation — just compile physical properties, application, storage, packaging data per product)
- [ ] Once consultancy returns draft SDS — review with them, confirm accuracy, then distribute
### Phase 2 — Annual Maintenance (Ongoing from Month 1)
- [ ] Subscribe to regulatory change alerts: ECHA newsletter, choose consultancy's maintenance package
- [ ] **Critical upcoming deadlines**:
- **May 2026** (already passed): New CLP hazard classes apply to **mixtures** — verify consultancy updated your documents
- **Nov 2026**: Existing substances compliance deadline
- **Dec 2026**: New EU Product Liability Directive takes effect
- **Jan 2027**: Distributor PCN obligations (already covered if you do it now)
- [ ] Schedule **annual SDS review cycle** — consultancy re-issues updated versions
- [ ] Add new products to system as you expand portfolio
- [ ] Track document expiry & version history
### Phase 3 — Optional: Bring In-House (Year 2+)
- [ ] If portfolio grows beyond ~30 products → evaluate SDS authoring software (CHEMDOX, TotalSDS)
- [ ] Until then — consultancy is cheaper and transfers liability to them
## Reference
- REACH Regulation (EC 1907/2006): https://reachonline.eu/reach/en/title-iv-article-31.html
- CLP Regulation (EC 1272/2008) as amended by EU 2024/2865
- ECHA Guidance on SDS compilation: https://echa.europa.eu/guidance-documents/guidance-on-reach
- MSDS-Europe: https://www.msds-europe.com
- BENS Consulting (Balkans expertise): https://www.bens-consulting.com
- REGARTIS (Serbia/CEE): https://www.regartis.com
- Serbia SDS format alignment (Sept 2024): https://www.regartis.com/en/menu/events/293/
- North Macedonia bilingual requirement: https://www.bens-consulting.com/en/blog/497/
## Notes
- **Serbia** follows EU SDS format but NO UFI/PCN requirement — simplifies things
- **North Macedonia** requires bilingual (Macedonian-Cyrillic + Albanian) — the only non-EU market with this dual-language burden
- **TDS** is the easy win — completely under your control, no regulation, just good technical data
- The biggest blocker for "owning" your SDS is getting full composition data from suppliers — most solvent manufacturers will share this under NDA with a downstream trader, but it's not automatic
- Consider working with a Balkan-region consultancy (BENS in Slovenia, REGARTIS in CZ/SK) that already knows MK and RS requirements natively