Chemical Traceability Software: Raw Materials, Blends, SDS and Shipment

A chemical traceability record covers eight things. (1) Every raw-material lot received with its supplier CoA and SDS version. (2) Every transformation — reaction, blend, dilution, neutralisation — as a parent-child lot transaction with quantities and reaction parameters. (3) Every intermediate stored with its hazard class, storage location and incompatibility list. (4) Every finished blend with the cited SDS version, the regulatory composition and the CLP/GHS label content. (5) Every package — drum, IBC, pail, tanker — with its UN number, packing group and net/gross weight. (6) Every certificate of analysis and certificate of conformity issued to a customer with lot, batch and SDS version cited. (7) Every shipment with the transport classification, the placard, the consignee and the lot detail. (8) The full SDS revision history so a customer query about an old shipment returns the SDS that was actually shipped, not today's version.

EU REACH (Regulation 1907/2006) requires registration of substances manufactured or imported above one tonne per year, with traceability of the supply chain via the Article 33 Substance of Very High Concern declaration. US TSCA (15 USC §2601) requires inventory listing of every chemical manufactured or imported, with §8(a) reporting on production volumes and §8(c) records of significant adverse reactions. CLP (Regulation 1272/2008) requires GHS classification, labelling and packaging — with the SDS chain documented under Article 31. The unifying record-keeping expectation: every substance, every supplier lot, every customer shipment, with the version of the SDS that was current at the time of shipment retrievable on demand. Most chemical recalls and most enforcement actions trace back to a broken SDS-version chain.

Chemical operations rarely preserve a clean lot identity through processing. A raw lot of solvent feeds three reactors over a week. Two batches of intermediate are blended into one finished tank. A finished tank is diluted with water and topped off with a stabiliser from a different lot. Each event is a parent-child lot transaction that has to record proportions, reaction parameters, timestamps and operators. ERPs that record blends as a single inventory move with no contributing-lot detail produce a genealogy graph with structural holes. A real chemical traceability system enforces parent-child lot links with proportion at every blend, dilution and top-off — and treats reactor cleanout between batches as its own audit event.

Chemical shipping is where traceability and transport compliance collide. 49 CFR (US DOT), ADR (EU), IATA (air) and IMDG (sea) require the shipping paper, the package marking, the placard and the SDS to match — and the lot detail has to be retrievable. The most common enforcement failure is a package label that cites an old hazard class because the SDS was revised mid-week and the label engine wasn't updated. A real chemical traceability system links the SDS revision, the CLP/GHS classification, the package label, the transport paper and the lot record as one event — and blocks a shipment from leaving the dock if any of the five is stale.

Chemical recalls are different from food recalls because the customer usually still has the product — in their reactor, on their line, on their warehouse rack. The query that lands is 'which batch did you ship us on this date, and what was the composition at that time?' — sometimes years after the shipment. A real chemical traceability system answers that query by returning the lot record with the SDS revision that was current on the ship date, the CoA that travelled with the shipment, and the regulatory composition that applied at the time. Programs that hold only the current SDS, or only the current composition, fail the audit when the question is about a 2022 shipment.