SDS authoring software is one of those categories where the marketing pages all look identical. Everyone has multi region support, everyone has a phrase library, everyone has translations, everyone has a compliance dashboard. The differences are architectural, and they only show up once you put a real portfolio through the tool.

There are roughly three tiers. Template engines, which give your regulatory writer a better Word document. Phrase library tools, which add a controlled vocabulary of regulated phrases and translations. And substance first platforms, which treat the SDS as a generated output of structured substance and mixture data. The price difference between the tiers is much smaller than the difference in what your regulatory team will actually do with their time.

Ask the vendor to show you what happens when a substance classification changes. In a document first tool, the answer is that the affected SDSs need to be opened and re authored, one by one, or in a batch that still requires per document review. In a substance first tool, the substance record changes once, every affected mixture is recalculated, every affected SDS is flagged for review and draft versions are generated automatically.

Multiply by the cadence at which CLP, GHS and the national variants actually move. A portfolio of three hundred products in twenty markets will see dozens of relevant regulatory changes a year. The document first answer scales linearly in regulatory team headcount. The substance first answer doesn't.

Hazard statements (H codes), precautionary statements (P codes) and section headings are controlled vocabularies. The regulator publishes official translations. Any serious SDS tool should pin those to a translation memory keyed off the phrase ID (H315, P302 plus P352, and so on), so translation is one time and reused across every product and every revision.

The wrong answer is that the vendor sends free text translations to a third party agency every time you author a new SDS. That's expensive, slow, and a source of drift between markets. The right answer is that the only fields a human translator ever touches are the free text fields (supplier identity, emergency contact, product specific use instructions), which are a small fraction of the document.

Most products on the market are mixtures, not substances. The mixture rules under CLP Annex I and GHS chapter 3 are deterministic but non trivial, with cut off values, additivity formulas, M factors for the environmental classifications and bridging principles for related mixtures. A serious SDS tool has the mixture calculator built in and audited. A weak tool asks your regulatory writer to make the call in a spreadsheet and type the result into section 2.

The spreadsheet path is unsustainable above a few dozen products, and it's the first thing that breaks under audit. Ask the vendor to walk through a mixture classification, end to end, on screen, and to show the rule trace behind the final classification.

An SDS is a regulated document with a customer obligation. When a new version is issued, the previous recipients (typically within the last twelve months) must receive the updated document. Email attachments don't satisfy this in practice, because there's no record of who received what, and no read receipt.

The right architecture is a customer portal. Every customer has an account. Every SDS they have received is logged with version, lot and date. New versions are pushed, old versions archived with provenance, read receipts captured. When the regulator asks you to demonstrate that you updated your downstream users, the answer is a query, not a panic.

SDS authoring is downstream of substance data. The classifications, the hazard statements, the exposure limits, the regulatory flags (SVHC, Annex XVII, Prop 65, TSCA) all originate elsewhere, typically with the supplier or with the regulator's published lists. Ask the vendor whether they ingest regulator feeds (ECHA, EPA, MHRA, METI, NMPA) directly into the substance master, and whether supplier SDSs can be parsed into the substance master as a first class workflow.

If the answer is that you upload supplier SDSs as attachments and re key the classifications, you've bought a document editor. If the answer is that the supplier portal captures structured data and the regulator feeds keep it current, you've bought a platform.

Six concrete asks. One, a live demo of a substance classification change propagating to every affected SDS. Two, the phrase library coverage list per region, with the most recent regulator update date for each. Three, a mixture calculator walkthrough with a rule trace. Four, the distribution and read receipt workflow. Five, the supplier and regulator data ingestion model. Six, the customer references in your size band and your market footprint, with permission to talk to their regulatory lead unsupervised. If a vendor won't give you all six, you don't have enough information to sign.