OBSEVIABack to blog

7 July 2026

GHS Labeling Gaps: Where Document Inconsistency Creates Real Exposure

GHS symbols and SDS text can look fine alone and still conflict across pack sizes, languages, and logistics data. How to find and fix inconsistency systematically.

GHS · labeling · SDS

GHS was designed to harmonize hazard communication. Inside real operations, inconsistency still appears: different pack sizes carry drifted label text, translations lag the master SDS, and transport information in section 14 does not match what logistics books.

Each artifact can be “correct enough” in isolation. The exposure appears when a customer, carrier, or inspector compares them.

Common inconsistency patterns

  • Pictograms or signal words updated on SDS but not on printed labels still in stock
  • Section 2 hazards not reflected in workplace instruction sheets
  • Mixture classification updated while related intermediates still show old categories
  • Multi-language packs where one language was revised and others were not
  • ERP dangerous-goods fields out of sync with SDS transport section

These are process failures, not chemistry failures.

Build a reconciliation habit

Treat labeling and SDS as a linked change set:

  1. Identify the controlled master (usually the approved SDS/classification record)
  2. List dependent outputs (labels, inner packs, outer packs, workplace cards, customer PDFs)
  3. Update dependents as one release package
  4. Quarantine old print stock intentionally, not by hope

If print stock quarantine is informal, inconsistency is inevitable.

How to sample without reviewing everything

For SMEs, full reconciliation every week is unrealistic. Use risk-based sampling:

  • Top shipped SKUs by volume
  • Materials with recent classification changes
  • Customer-critical or highly hazardous products
  • SKUs with prior labeling complaints

Document the sample plan. Auditors care that sampling is deliberate.

AI-assisted comparison

Document comparison tools can highlight textual and structured differences between SDS versions and between SDS and label source files. That reduces the chance a human misses a single H-statement change across a long file.

Human reviewers still decide whether a difference is material and how to stage the rollout.

Practical takeaway

If your team only “stores” SDS and “prints” labels as separate jobs, you will eventually ship a mismatch. Link them in change control, sample for drift, and treat inconsistency as a leading risk indicator, not a paperwork nuisance.