CLP needs four linked chemical-compliance records

Classification needs a versioned identity and evidence basis

The classification record should identify the legal entity and supply-chain role, substance or mixture, identifiers and composition range, impurities or additives relevant to classification, physical form, intended market, evidence set, test or study reference, data owner, classification method, hazard class and category, specific concentration limit or multiplying factor where applicable, reviewer, decision date, and source versions. For a mixture, retain the formulation version and calculation or bridging basis rather than attaching a classification only to a trade name.

Record whether each classification comes from a current harmonised entry or a self-classification decision and retain the cited table entry, index number, notes, applicable amendment, application date, and any unresolved interpretation. A harmonised entry can cover named hazard classes without necessarily settling every other hazard. Conversely, a supplier's self-classification is evidence to assess, not an automatic substitute for the duty holder's own applicable decision. Conflicting classifications should remain visible until an authorized disposition is recorded.

The released label and package need implementation evidence

The label record should link the approved classification to the product identifier, supplier details, hazard pictograms, signal word, hazard and precautionary statements, supplemental information, nominal quantity where applicable, language set, label dimensions and layout, revision, approval, print specification, and effective market date. The package record should identify the container and closure, material, size, child-resistant fastening or tactile-warning requirement where applicable, compatibility evidence, artwork, production site, and release status.

A label template or approved artwork does not prove that the correct version reached each unit. Retain the item and batch relationship, printer or line, source artwork hash, variable data, inspection method, rejected population, rework, reconciliation, distribution market, and changeover evidence. When a classification or formulation changes, perform impact assessment across labels, packages, safety data sheets, stock, translations, transport information, workplace procedures, customer communications, and already distributed product without overwriting the prior released state.

Inventory notification and poison-centre submission are separate

A Classification and Labelling Inventory notification should retain the notifier legal entity and role, substance identity, classification and labelling values, market event that triggers the duty, due date, dossier or submission version, submission channel, validation result, receipt or reference number, accepted date, correction history, and linked classification record. A prepared file, successful local validation, or displayed inventory entry should not be confused with the submitter's authoritative receipt and current obligation state.

Poison-centre information has a different object and purpose. Preserve the responsible submitter, market and appointed body, mixture and formulation version, product categories, toxicological information, packaging and use information, language, submission format and version, unique formula identifier, label relationship, submission event, validation messages, receipt, effective dates, and update trigger. The same commercial name can cover multiple formulas, while one formula may appear in several products. A UFI printed on a label is not proof that the corresponding current submission was accepted.

Test one formulation through a classification change

A representative evaluation should follow one mixture sold under two names, in two package sizes and three languages, by related legal entities in different markets. Change a component concentration across a classification threshold, add a harmonised entry with a later application date, correct a supplier identifier, revise precautionary statements, generate a new formula version and UFI, and hold old stock. Reviewers should reproduce the classification basis and show which label, package, inventory notification, and poison-centre record applies to every product-market-time combination.

Then recall one submission, reject one artwork at line clearance, and verify that exceptions do not collapse the four controls into a single red or green status. ECHA's page establishes the described CLP purpose, classification, harmonised and self-classification, labelling and packaging, Inventory notification, poison-centre information, and UFI concepts. It does not establish an organization's role, formulation identity, classification, label, package, notification, submission, receipt, workplace control, market eligibility, enforcement position, or compliance.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Safety Operations Standard will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.