Chemical compliance for manufacturers.

Start with where the substance is placed on the market, not where it is made. If you manufacture or import into the EU above one tonne per year, EU REACH registration applies. Place the same substance on the GB market and UK REACH applies separately, with its own registration and its own timetable. Classification, labelling and packaging is governed by CLP in the EU and GB CLP in the UK, both built on the UN GHS system but adopted at different revisions.

For mixtures classified for health or physical hazards, Poison Centre Notification under CLP Annex VIII requires a submission with a UFI printed on the label. In the US, new substances need a TSCA Premanufacture Notice, existing ones must be on the TSCA Inventory, hazard communication follows OSHA HazCom 2012 (aligned to GHS Rev 7), and California Proposition 65 adds a separate warning obligation for listed substances above safe-harbour levels.

Beyond that, most manufacturers also carry sector rules: cosmetics under EU 1223/2009 or MoCRA, food contact, biocides under BPR, transport classification under ADR and IATA. The pattern is always the same: one substance, many overlapping regimes, each with its own trigger.

Legally, the obligation sits with the legal entity that manufactures, imports or places the product on the market. Practically, it is usually split: a regulatory affairs lead owns registrations and classifications, QA owns documentation and audit readiness, and technical or R&D owns formulation data. In smaller manufacturers all three roles are one person, often part time.

This split is where things break. The formulation changes in one system, the SDS lives as a PDF in another, and the customer declaration is a Word template on someone's desktop. Nobody is wrong, but nothing is synchronised. The fix is structural rather than procedural: one substance record that every document is generated from.

An SDS is not a document, it is a rendering of substance data against a jurisdiction's rules. The sixteen sections are fixed, but the classification logic, the phrase wording and the required national annexes are not. A mixture sold into the EU, the US, Canada, China, Korea and Brazil needs six correct renderings, each in the local language, each using legally significant phrasing that must not drift in translation.

Doing this in a document tool means every regulation change becomes a re-authoring backlog. Doing it from a substance master means a change to a hazard classification flags every affected SDS, in every language, automatically. The detail of that workflow is set out on SDS authoring software.

Distribution matters as much as authoring. You need to prove which customer held which version on which date, which means read receipts and a version history, not an outbox.

Use a short test. Does it hold a substance master keyed on CAS and EC numbers with synonyms and INCI cross references? Does it calculate GHS and CLP classification from composition rather than storing a classification someone typed in? Does it author and reissue SDSs from that data? Does it monitor the SVHC Candidate List, Annex XIV and Annex XVII, the TSCA Inventory and Prop 65, and tell you which products and customers are affected when something changes? Does it generate the customer-specific declarations your buyers demand, TSE/BSE, GMO, RoHS, conflict minerals, allergen and microplastic?

If the answer to any of those is no, you are looking at a document repository. Full functional detail is on chemical compliance software.

Three cost lines. Regulatory fees, which are fixed by the authority: REACH registration fees scale with tonnage band and company size, and joint submission costs include letter of access charges that often dwarf the ECHA fee itself. Testing and dossier work, which is where the money usually goes for new substances. Then software and headcount.

The hidden line is rework. Manufacturers routinely spend more staff time re-authoring documents after a formulation or regulation change than they do on the original submissions. That cost is invisible on any budget line, which is precisely why it persists.

An inspector follows a chain: this drum, this batch, this supplier lot, this specification, this SDS version, this classification, this registration. If any link is a spreadsheet, the chain has a gap you will spend the audit explaining.

Practically: keep lot-level traceability from raw material receipt to finished goods dispatch, keep SDS version history with distribution evidence, keep classification decisions with the data they were derived from, and keep change control on formulations with who approved what and when. If those four are in one system, an audit is a query rather than a project.

The valuable use is monitoring and triage, not authoring in a vacuum. Regulatory feeds from ECHA, EPA, HSE and national authorities change constantly, and the manual job of reading them and mapping changes onto a portfolio is slow and easy to miss. An agent that reads the change, matches it against your substance master and returns the affected SKUs, customers and documents with a draft action plan removes the search, not the judgement.

Every consequential decision should still carry human sign-off, and every action should be logged. That is how Worldover runs it, and it is the only version an auditor will accept.