OSHA HazCom + DOT hazmat + per-SKU SDS, how is it all managed in Magento?

Every chemical SKU on a B2B jan/san store needs a Safety Data Sheet (SDS) attached. OSHA HazCom 2012 (aligned with GHS) requires the SDS be available to the buyer in the language of the workplace within seconds of request. DOT hazmat regulations require the UN number, packaging group, and proper shipping name on every shipment.

The data + workflow:

• SDS per-SKU: stored as a PDF attribute on the product. PDP renders a “Download SDS” button visible without login (OSHA requires no-friction access).
• SDS multi-language: English + Spanish minimum for US; English + French for Canada; multi-EU for cross-border. Stored as separate attribute slots.
• Verisk 3E / Aspen / MSDSonline integration: enterprise jan/san distributors typically pull SDS PDFs from a managed library so updates auto-sync. Magento module ships as a custom integration; ~$8k, $15k to wire.
• OSHA training-record attestation: optional checkbox at checkout where the buyer confirms their facility has received the required HazCom training on the listed chemicals. The attestation is stored on the order for audit trail.
• DOT bill-of-lading auto-generation: the order ship-confirm includes a printed BOL with UN number, hazmat class, packaging group, and proper shipping name. Required for ground LTL.

For multi-region: EU REACH compliance (ECHA registration number on SDS, no SVHC chemicals over threshold without exemption) and UK COSHH (Control of Substances Hazardous to Health) require region-specific SDS variants. Magento store views per region handle this cleanly.

Pro move: the SDS download is the strongest top-of-funnel intent signal on a B2B jan/san store. A facility manager downloading the SDS for an unfamiliar chemical is research-mode. Capture the download event (with login encouraged but not required), tag it as an intent signal in the CDP, and route to a sales rep for follow-up.