SDS authoring software for chemical manufacturers

The 16 sections of a Safety Data Sheet are deterministic. Given an accurate substance record, GHS classification rules and a phrase library, the document writes itself. The reason SDS authoring still consumes weeks of expert time in most chemical businesses isn't the writing. It's the upstream chaos: composition held in Excel, classifications held in a regulatory tool, customer-specific variants held in email.

Worldover collapses that chain. One substance, one classification, one set of phrases, every variant generated on demand.

GHS is the spine: hazard classes, category cut-offs and pictograms. CLP layers the EU and UK overrides and feeds the Poison Centre Notification (PCN) submission with a UFI code generated from the formula. REACH brings registration status, SVHC flags and authorisation/restriction triggers into the same record, so the SDS Section 15 you ship today reflects the regulatory reality this morning.

For the full compliance picture (substance dossiers, customer declarations, ECHA monitoring) pair this with our chemical compliance software.

CLP for the EU and UK. OSHA HazCom 2012 for the US. WHMIS 2015 for Canada. GB CLP. Plus China, Korea, Japan, Brazil and Australia. Each regime uses GHS as the backbone with regional overrides. Worldover holds the overrides as data and generates region-correct SDSs in 40+ languages from one substance record. Translation uses a controlled phrase library so legally significant text never drifts.

Every regime below is built on GHS, so the 16-section structure is constant. What changes is the GHS revision adopted, the hazard classes in force, the language obligation and what has to be notified to an authority alongside the SDS. This is the matrix most teams end up rebuilding in a spreadsheet.

Held as data rather than as nine document templates, this matrix stops being a maintenance burden. A classification change updates once and every regional variant regenerates against the rules in force for that market.

Under GHS Annex 4 (and REACH Annex II in the EU) an SDS has 16 sections in a fixed order. Roughly two-thirds are deterministic from a well-maintained substance master. The rest need a human decision, and those are the ones worth an expert's time.

1. Identification. Product identifier, recommended use, supplier details, emergency telephone. Derived from the product and legal-entity records, per market.
2. Hazard identification. Classification, label elements, pictograms, signal word, hazard and precautionary statements. Derived from composition by the GHS mixture rules.
3. Composition and information on ingredients. Components, CAS and EC numbers, concentration ranges, classification of each component. Derived from the formula, with confidentiality ranges applied by rule.
4. First aid measures. Phrase library, selected by hazard class and route of exposure.
5. Firefighting measures. Phrase library, driven by flammability and decomposition data.
6. Accidental release measures. Phrase library, driven by physical state and environmental hazard.
7. Handling and storage. Phrase library plus any product-specific handling instruction. Partly manual.
8. Exposure controls and personal protection. Occupational exposure limits per region, DNELs and PNECs. Derived from substance data, but the region-specific limit tables must be current.
9. Physical and chemical properties. Measured values from the specification and test records. Derived, provided the lab data is in the system.
10. Stability and reactivity. Substance-level data plus incompatibility rules. Mostly derived.
11. Toxicological information. Acute toxicity estimates, irritation, sensitisation, CMR, STOT. Derived from component data where complete; expert judgement where read-across is used.
12. Ecological information. Aquatic toxicity, persistence, bioaccumulation, mobility. Derived from component data.
13. Disposal considerations. Waste codes vary by market. Partly derived, partly local knowledge.
14. Transport information. UN number, proper shipping name, class, packing group, marine pollutant status for ADR, IMDG and IATA. Derived from the dangerous goods classification.
15. Regulatory information. Inventory status, SVHC and authorisation flags, restrictions, national registers. This is the section that goes stale fastest, and the one that most benefits from live regulatory monitoring.
16. Other information. Revision number, date of issue, changes since the previous version, full text of hazard statements. Derived from version control.

The practical implication: if Sections 2, 3, 14 and 15 are generated from structured data rather than copied between documents, the expert review shrinks from days to an hour, and the failure mode of a stale Section 15 disappears.

An SDS is required to be re-issued when:

• The hazard classification changes (composition, new evidence, regulatory update).
• New information becomes available on safe handling or risk management.
• An authorisation is granted or refused.
• A restriction is imposed.

Under REACH Article 31(9) the updated SDS must be supplied free of charge, on paper or electronically, to every recipient supplied with the substance or mixture in the preceding twelve months. That's the obligation most businesses can't evidence: not authoring the new version, but proving who received it. It's why the re-issue trigger and the distribution log have to live in the same system.

Worldover detects these triggers, queues the affected SDSs for review and pushes new versions to every customer who holds the previous one. No spreadsheet of who got what.

Demos all look similar. These are the questions that separate the tools once you're two years in.

1. Where does composition live? Good: one substance and formula master, with the SDS as an output. Weak: composition re-keyed into each document, so the SDS and the production BOM can silently disagree.
2. Is classification calculated or entered? Good: GHS mixture rules applied automatically, with an expert review gate before release. Weak: a free-text classification field and a consultant.
3. How are regional overrides maintained? Good: rules held as data and updated by the vendor as regimes change. Weak: a separate document template per country that your team maintains.
4. What triggers a re-issue? Good: composition change, regulatory change, new toxicological data and inventory changes all raise a task automatically. Weak: an annual review reminder.
5. Can you prove distribution? Good: per-customer, per-version delivery log with receipts, exportable for an inspection. Weak: sent email, no record.
6. How good is the translation control? Good: a controlled phrase library where legally significant text is fixed and reviewed once, reused everywhere. Weak: machine translation per document.
7. Does it connect to the systems that hold the truth? Good: native links to ERP for customers, orders and shipments, and to the lab for physical properties. Weak: CSV in, PDF out.
8. What does the audit trail show? Good: who changed which value, when, on what evidence, at substance level and document level. Weak: document version numbers only.

Score any tool against those eight and the shortlist tends to resolve itself. Most of the market is strong on document production and weak on everything upstream and downstream of it.

Worldover connects to SAP, NetSuite, Sage and Microsoft Dynamics for product, customer and order data, so SDSs travel with the shipment, the order acknowledgement and the customer portal without manual lookup. For teams running everything in one place, our chemical ERP software uses the same substance master, so inventory, batch records and SDS issuance never diverge.

Lot- and batch-level data flows both ways: an inbound goods receipt updates supplier SDS coverage; an outbound shipment triggers the right customer-portal release.

Worldover serves chemical manufacturers (REACH dossiers, CLP labels, TSCA inventory) and cosmetics manufacturers (CPNP/SCPN notifications, PIF and CPSR, MoCRA listings) from the same substance and formula model. SDS authoring sits inside both worlds: ingredient suppliers and personal care brands run on the same engine, with the regional and sector-specific overrides held as data.

Customers access SDSs through a branded portal with login, read receipts and version history. For customers who insist on email, Worldover sends and logs delivery automatically. Either way you can prove, in an audit, which customer held which version on which date.

Every major market has adopted GHS, and every one of them has adopted a different revision with local additions. The 16-section skeleton is shared; the classification thresholds, the occupational exposure limits and the mandatory local content aren't. This is the matrix teams end up rebuilding in a spreadsheet.

Worldover holds these as data, not as templates. One substance record, one classification, and each region's rendering derived at generation time, which is what makes multi-market issuance a single action rather than eight parallel authoring jobs. See multi-market SDS at scale for how that plays out across a portfolio.

The reason SDS authoring is slow isn't the writing. It's that roughly half the document is a restatement of data you already hold somewhere else, and the other half is boilerplate that's identical across hundreds of products. Only a handful of sections need genuine judgement.

Sections 2, 3, 8, 13, 14, 15 and 16 are fully derivable if the substance master is complete. Sections 11 and 12 need a toxicologist. Everything else comes from a phrase library. That split is the whole business case: a good system removes the derivable 60% and gives the author time for the parts that actually carry liability.

Under REACH Article 31(9) the SDS has to be updated without delay once new information affecting risk management or hazard becomes available, and the updated version must be supplied free of charge to everyone who received the substance or mixture in the preceding 12 months. That obligation, not the authoring, is what teams get caught on in an inspection.

The practical test is whether you can answer, for any customer and any date, which version they held. If proving that means searching an inbox, the process isn't defensible. Read the SVHC candidate list page for how a single ECHA update propagates through this table.

Most SDS tools demo identically. These are the questions that separate them, with what a good answer looks like.

Two questions worth asking in any demo: show me a product with eight regional versions and change one raw material; and show me the audit trail proving what a named customer received last March.