ChemGes alternatives for EU chemical SMEs

ChemGes gets a different opening from the enterprise platforms, because it isn’t one. It’s a compact Austrian desktop program that has been quietly authoring safety data sheets since 1989, is sold by a small independent firm rather than a private-equity platform, and, unusually among the established vendors, includes poison centre notification and UFI generation at no extra module cost. If any of the big-four compliance products is shaped for an SME, it’s this one. That makes the remaining question sharper: is an SDS-authoring package the right buy at all when the job is submissions? As of July 2026, here’s the split.

What ChemGes is

ChemGes is Windows desktop and network software from DR-Software GmbH of Sollenau, Austria: a small firm (directories report roughly 20-49 employees) publicly claiming more than 1,800 customers in 70 countries, sold directly and through regional resellers. The package authors SDSs in 39 languages (vendor-stated), prints labels with up to 30 languages on one label, classifies under CLP, UN GHS and the US/Canadian systems, generates transport classifications, and keeps a raw-materials database of some 25,000 substances. For poison centre work it includes a built-in UFI generator and prepares notifications for fully automatic single and bulk upload to the ECHA portal, with manual submission also available, all covered by the maintenance contract rather than sold as a separate module. It remains actively maintained; updates ship frequently. There is no cloud version: remote use runs over Citrix, RDP or VMware.

When ChemGes is the right call

The best case is the in-house formulator: you create and revise your own safety data sheets, sell into several language markets, run a Windows environment, and want classification, SDS, label, transport document and notification to fall out of one substance database maintained on your own machines. For that company ChemGes is arguably the most cost-shaped of the established products: the notification capability rides on authoring work you were doing anyway, and the maintenance-contract model keeps the recurring cost in small-vendor territory rather than enterprise-licence territory (quoted case by case; no public list exists). If that’s you, evaluate it with the standard checklist in hand, above all S2S coverage and data export.

When it is more than you need

The mismatch is subtler than with the enterprise suites, but it’s the same kind: ChemGes is an authoring package, and its notification feature assumes your mixtures live inside its database. For an importer or private-label seller whose SDSs arrive from suppliers, adopting ChemGes for PCN work means:

• Recreating data you already have. The workflow starts from compositions entered into the ChemGes substance database. If the SDSs and classifications already exist on paper, that’s re-keying an authoring dataset to reach the submission step.
• Committing to the desktop. Installation on Windows machines or a corporate network, updates applied under the maintenance contract, remote access via Citrix or RDP: reasonable for a lab that lives in the program, friction for a company that would open it monthly to file one notification.
• A licence against per-notification arithmetic. With no public price list, the comparison to make in procurement is: a licence quoted by scope, against ECHA’s own portal, which costs nothing in cash, with per-notification tools in between. The quote has to justify itself against both numbers. It may, if authoring is part of the job. For submissions alone, it’s a harder case.

The alternatives, side by side

UFI Number is the focused-tool column: browser-based, charged per notification, built to create the UFI, prepare the notification in the current PCN format and send it through ECHA’s official system-to-system route under your own legal entity. It’s in private beta. The full decision logic, including when the free portal is the right answer, is in the four-option comparison; costs are broken down in how much a PCN costs, and hard cases belong with a consultant.

What no vendor changes

As with every option on this page, Article 45 and Annex VIII of CLP keep the notification duty with the importer or downstream user placing the mixture on the market. A software licence, desktop or cloud, doesn’t carry it, and neither does a reseller relationship. File under your own legal entity, keep the submission numbers and update trail, and check that whatever tool you choose, you could answer an inspector’s questions without the vendor in the room.