Module

GHS Labels

Hazard labels in the size the pack needs and the languages your customer reads, every word from the standard.

Running in production₹12,000 / month
See pricing

What it produces

  • A GHS/CLP label per material from its SDS codes: pictograms, signal word, H, P and EUH statements
  • Any size — 90 × 200 mm tins, A7 to A3, cartons, drums, IBCs, jumbo bags — with the CLP minimum for the container checked
  • One language or several on the same label, printed only once a responsible person has reviewed the phrase set
  • Supplier block, net quantity, batch, dates and UN transport line from the masters and the batch
  • Refusals by name: no classification, a code with no wording in that language, a blank the supplier has not filled

A worked example

INK-2041 Process Cyan — 90 × 200 mm, English and German
GHS02 GHS07 · DANGER / GEFAHR
H225 Highly flammable liquid and vapour. Flüssigkeit und Dampf leicht entzündbar.
P370+P378 In case of fire: Use alcohol-resistant foam to extinguish.
2.5 L tin: 90 × 200 clears the 52 × 74 mm CLP minimum; pictograms 16 mm

Illustrative figures. On your tenant the same page shows yours.

Why it is hard

The part that is not a report.

A hazard label is the one document a customs officer, a customer's safety officer and a warehouse hand all read, and each of them notices when the wording is off, the pictogram is small, or the label is the wrong size for the drum. This prints the label from the codes on the Safety Data Sheet, in the size the pack needs and the languages the destination reads, and refuses a language nobody has reviewed rather than translating a hazard on the fly.

Opened by the logistics manager, COMPLIANCE and the supply chain manager — what each of them sees first.

Said before you ask

What is not finished.

The composer, the phrase library and the size rules are built and tested. Three things are true and printed on the page. English is transcribed from the UN GHS text and reviewed; the German set is transcribed from CLP Annex III and marked unreviewed, so it prints only once a tenant's responsible person lists it as reviewed — and no other language exists yet, because a hazard statement is never translated on the fly. The pictogram artwork is a close approximation; the UNECE files drop into public/ghs/ and replace it. And classifications are codes imported from the SDS with the SDS reference required: SIAARU classifies nothing.

Where this sits

One of 19 modules, on one engine.

GHS Labels reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 18 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.

Get started

Bring one month of data. Leave with your own control tower.

A demo runs on your material master, your purchase orders and your stock — not on ours. Thirty minutes, and you see your own exceptions rather than a scripted one.

Ask a question

Book a demo

Thirty minutes, on your own data. Six fields — the rest only helps us prepare.

Not binding. Tell us the size and we will say which one fits.

The demo connects to it, so this shapes the whole session.

Add context, and the demo runs on your problem rather than a scripted one

We reply within one working day.