Operational notes Regulation

Safety data sheets: when they must be updated, who receives them again, and in which language

7 min read

Arm of an industrial agitator stirring a thick mash inside a steel vessel, shot from above in black and white
Inside the vessel the recipe barely changes. Outside it, that variation rewrites a document in every language of destination.

A firm in Sassuolo selling ceramic glazes, engobes and inks into six Member States does not just keep a price list: it keeps an archive that has to stay true. Every hazardous mixture travels with its own safety data sheet, in the language of the State where it is placed on the market — six versions for every product code. The day the classification of a single raw material changes, all of them go wrong together, and the law does not ask you to correct them going forward: it asks you to send them back, free of charge, to everyone who bought in the preceding twelve months.

The format is not an industry convention

Annex II to Regulation (EC) No 1907/2006, which prescribes how a sheet is compiled, was replaced in full by Regulation (EU) 2020/878, applicable from 1 January 2021. Article 2 allowed one window only: “safety data sheets not complying with the Annex to this Regulation may continue to be provided until 31 December 2022”. It has been shut for nearly four years.

In the consolidated REACH text at 22 June 2026 that annex carries one amendment marker, the one from 2020: of the eighty-five acts that have amended the Regulation — the latest (EU) 2026/1168 of 1 June 2026 — none has touched it. The format stands still; the classification of the substances that go into it does not.

Part B fixes “the following 16 headings in accordance with Article 31(6) and in addition the subheadings also listed”: fifty subsections per sheet. Point 0.4 closes the loophole — “The safety data sheet shall not contain blank subsections.” And under 9.1, where a property does not apply or no information is available, “this shall be clearly indicated, giving the reasons where possible”. An empty field is not an omission: it is a defect.

The update does not go forward, it goes back

Article 31(9) requires suppliers to update “without delay” in three cases: new information on hazards or affecting risk management measures, an authorisation granted or refused, a restriction imposed. Then the part no business system does by itself: the new dated version, identified as “Revision: (date)”, must be provided free of charge “to all former recipients to whom they have supplied the substance or mixture within the preceding 12 months”.

Annex II adds the version apparatus: on the first page the revision date “as well as one or more indications of which version is replaced”, and in Section 16 “a clear indication of where changes have been made to the previous version”. This is not an obligation to rewrite, it is an obligation to differ: you must be able to say what changed between one revision and the next, and whom you sent each to. Anyone who has faced the same question about delivered machinery will recognise the shape: backward propagation is a silence there, written down here.

Language multiplies everything

Article 31(5): the sheet “shall be supplied in an official language of the Member State(s) where the substance or mixture is placed on the market, unless the Member State(s) concerned provide otherwise”. The official languages of the Union, under Article 1 of Regulation No 1 of 1958, number twenty-four.

In Italy it reads from the penalty side. Legislative Decree No 133 of 14 September 2009, Article 10(3), sets a fine of EUR 3,000 to 18,000 for a supplier who fails to provide the sheet in Italian on the national market, and the same fine for a sheet that is undated, incomplete or inaccurate. Paragraph 2 weighs more: EUR 10,000 to 60,000 for failure to comply with paragraphs 1, 3, 8 and 9 of Article 31. Paragraph 9 is the update.

Two hundred product codes in six languages make one thousand two hundred documents. Every reclassification touches a subset nobody holds in their head, and the penalty is counted per document.

The UFI and the thresholds that restart everything

Three documents run on the same mixture, on three clocks. The label: Article 30 of CLP, replaced by Regulation (EU) 2024/2865 and applicable in that version from 1 July 2026, allows six months from the new evaluation results where the change brings “the addition of a new hazard class or in a more severe classification”, eighteen otherwise. The poison centre submission: Annex VIII to CLP, Part B, Section 4.1 wants it updated before the changed mixture goes on the market, and Table 4 fixes the permitted “Variations (±) of the initial component concentration” where an exact concentration was given — 5 % above 25 %, 10 % between 10 and 25, 20 % between 2.5 and 10, 30 % below 2.5. Past the threshold a new UFI is created, which for unpackaged mixtures “shall be indicated in the Safety Data Sheet”. That submission too goes into the languages of destination: a second archive. And with pigments in nanoform, point 0.1.3 requires that the sheet “shall mention in each relevant section whether and which different nanoforms it covers”: not one line more, one column more.

Why a closed system here is not a preference

Section 3 of every sheet is the composition: identifiers, concentrations or ranges, classification of every component above threshold. It is the recipe. Whoever formulates glazes, adhesives or paints defends it as their single advantage; CLP allows at most an alternative chemical name (Article 24), but the formula is still written there. Any assistant helping you compile or translate a sheet is working, by definition, on a trade secret.

The volume is real and long-lived: hundreds of codes, per language, per revision, and Article 36 of REACH wants that information available “for a period of at least 10 years” after the last supply. Translation has to be repeatable: the same sentence must come out identical at the next revision, or the changed-points indication in Section 16 turns into noise. And the work on your own corpus — the settled renderings of the hazard statements, the correspondences between formulations and classifications — is the asset: if it matures inside an outside service, you have paid to create value that stays with someone else.

An open-weight model inside your own perimeter holds all of them together. The two delivery modes remain: on-premises, on autonomous machines that need no deep integration into your network, or dedicated cloud with a dedicated VPN and a data centre in Italy staffed by us, always with shared management — a glaze formulator should not also have to keep AI model administrators in house.

What we do not know

We do not give legal advice. We read the consolidated texts on Cellar — REACH at 22 June 2026, CLP at 1 July 2026 — each of which “is meant purely as a documentation tool and has no legal effect”: the authentic versions are in the Official Journal. We have not checked which Member States have used the option to provide otherwise on language; for Italy we infer it from the penalty decree. The ECHA site answered us with a 403 and we did not open the Agency’s guidance on safety data sheets, which is guidance, not obligation: the obligation sits in Annex II. We did not look for penalties actually imposed.

The two axes, applied to this case

Complying. The duties become controls over your archive: every sheet compared against the current classification of the substances it contains, the revision date and wording in the right place, Section 16 actually pointing at the changed points and, for every revision, the recipients of the preceding twelve months with the date sent. Not an opinion: a dated trail to put in front of an inspection, as with the CBAM thresholds.

Deciding. The same system holds the company’s scattered data together — formulations, laboratory, business applications, delivery notes and customers, labels — in a single operating model, on which AI agents execute decisions with a human operator in command, for large companies, defence, public administration and healthcare. In the Emilian districts it already carries predictive maintenance: the data changes, not the architecture. Compliance is the way in; the system you decide with is what remains.

From the first session, at no cost, you get the dated list of what actually holds for your catalogue: how many sheets, in how many languages, which are stuck on a superseded classification, which revisions never went back. It stays yours even if we do not go on. Talk it over with one of our engineers.

Sources