01
One source of truth
Substances, concentration ranges, contact details, classifications, labels, and SDS versions stay connected to each mixture.
EU chemical compliance workspace
From formula to market, without the compliance guesswork.
Deterministic CLP classification, all 16 SDS sections, labels, and market-access checks — connected to one structured source of truth, with the rationale for every decision.
Built around CLP, REACH Annex II, and the realities of multi-market product work.
CLP Annex I
REACH Annex II
24 EU languages
PCN / Annex VIII
ADR transport
CLP Annex I
Classification logic
REACH Annex II
16-section SDS
24 EU languages
Official phrase packs
Audit trail
Decision rationale
/01
One connected system
Compliance work should not live in twelve spreadsheets and someone’s memory.
A formula change ripples into classification, labels, SDS content, transport data, and market readiness. SDS Labs keeps those decisions tied to the same structured source.
02
Deterministic by design
ATEmix, cut-off, and summation logic run without LLM calls, external lookups, or random output.
03
24 EU languages
Use official H- and P-phrase translations instead of asking a model to reinterpret regulated wording.
04
Living compliance
Surface readiness gaps and future-dated rule impacts before they become a launch-day surprise.
05
Evidence, not a black box
Each classification keeps contributing substances, intermediate values, thresholds, and trigger decisions together.
Coverage
CLP Annex I — deterministic
REACH Annex II
24 EU languages
16 / 16 SDS sections
PCN / Annex VIII
ADR transport
Audit-ready rationale on every classification
/02
Explainable, not a black box
A deterministic engine does the regulated math. AI never classifies.
SDS Labs splits regulatory calculation from text generation. The classification engine computes the hazard result and shows its rationale; the AI layer only writes narrative for the non-regulated sections.
Layer 01 · Calculation engine
Structured, deterministic, auditable
- ATEmix by exposure route
- Cut-off and summation rules
- H/P phrases, pictograms, signal word
- Stored rationale per hazard class
Layer 02 · SDS content engine
Controlled prose from approved facts
- Structured classification as input
- All 16 REACH Annex II sections
- Per-section generation and review
- PDF, DOCX, and HTML delivery
The content layer cannot classify, recalculate, or translate regulated H, P, or EUH phrases.
/03
Explore the product
A focused workflow for every compliance output.
Start with your mixture and move through the work without rebuilding the context at every step.
01
SDS authoring
Create, review, translate, version, and export all 16 sections from structured product data.
02
CLP classification
Calculate mixture hazards with transparent thresholds and a complete rationale.
03
Compliance monitoring
Connect product readiness to current and future-dated regulatory requirements.
04
Labels and packaging
Carry classification outputs into consistent, market-ready label content.
05
Market access
Turn regulatory rules into a clear product-by-market readiness view.
Full platform
See how every workflow connects.
/04
The workflow
A clear path from composition to controlled document.
Every step leaves the next one better prepared, with less re-keying and fewer disconnected decisions.
-
01
Build the mixture
Add substances, CAS and EC identifiers, concentration ranges, physical properties, and supplier details.
-
02
Classify under CLP
Run deterministic calculation routes and review the rationale behind every triggered or non-triggered hazard.
-
03
Resolve labels and access
Generate hazard communication content and check the product against the markets that matter.
-
04
Publish and maintain
Generate SDS sections, review the result, export the document, and keep future revisions connected.
/05
Built for the real hand-offs
Useful to the people who formulate, review, and release the product.
Regulatory teams
Review decisions, evidence, translations, and document history from one workspace.
Formulators
Understand the downstream impact of concentration and ingredient changes earlier.
Manufacturers
Keep product data, supplier communication, and market outputs aligned across teams.
Consultancies
Separate tenant work cleanly while applying one repeatable quality process.
/06
Questions from regulatory buyers
The answers a compliance team actually asks first.
Are H, P, and EUH phrases machine-translated?
No. Hazard and precautionary statements use the exact official EU wording from static language packs (CLP Annex III/IV). The AI layer never rewrites or translates a regulated phrase. Only substance names are translated, and that runs through a review-and-commit step.
Which languages are covered?
All 24 official EU languages, with a dedicated German/DACH template. Regulated phrases come from official packs per language; classification codes stay identical across every translation.
Is the classification auditable?
Yes. The deterministic engine stores a rationale for every hazard class — contributing substances, concentrations, intermediate values, the applied threshold, and the trigger decision — so any result can be defended in review.
What about PCN and Annex VIII?
Poison Centre Notification is supported. Note that PCN and SDS Section 3.2 use different composition thresholds, so the two views are derived separately rather than assumed to match.
How is our data isolated?
The platform is multi-tenant with per-tenant scoping. Product records — mixtures, contacts, SDS versions, and generation history — are bound to the active workspace and separated from global regulatory reference data.
Make compliance operational
Bring your next mixture from formula to market in one traceable flow.
Start with structured product data and keep the classification, label, SDS, and market decision connected.
CLP Annex I · REACH Annex II · 24 EU languages · Audit-ready rationale