ERP for Chemicals & Hazmat

An ERP for chemicals and hazardous-materials trading has to do far more than manage item, quantity and price: it must map dangerous-goods classification, safety data sheets, batches and recipes, storage classes with segregation rules, plus REACH and customs requirements in one end-to-end process - while keeping every batch fully traceable. Unlike in standard trade, these aren't optional add-ons but legal obligations: CLP classification, ADR transport rules, TRGS 510 for storage and the REACH regulation decide whether your operation holds up under an official inspection. In this article we show you, vendor-neutrally, which requirements a chemicals and hazmat ERP absolutely has to cover and what to look for when choosing one.

Why chemicals and hazmat impose special ERP requirements

Trading in and processing chemicals is among the most densely regulated activities in the DACH region. Four factors drive the requirements: the hazardous-materials classification and labelling of each product, the mandatory provision of up-to-date safety data sheets, physically correct and legally compliant storage, and complete traceability of every batch across the entire supply chain.

A standard trading system that only knows item number and stock fails here. You need batch management and robust inventory management that carry not just quantity but also batch, concentration, dangerous-goods class and storage location through every posting. This data foundation is nearly impossible to retrofit cleanly later - which is why it belongs at the start of any system selection.

Dangerous goods, hazardous substances and safety data sheets

First an important distinction that many systems blur. A hazardous substance refers to the material danger of a product (classification under the CLP regulation with H and P statements and hazard pictograms). Dangerous goods, by contrast, refers to the transport of dangerous goods (classification under ADR for road, with UN number, packing group and hazard label). A product can be a hazardous substance and dangerous good at the same time - but not necessarily both.

For the ERP this means: both classification levels must be maintained in a structured and versioned way in the item master.

Dangerous goods in the transport process

For shipment-relevant dangerous goods, the system must hold the UN number, the dangerous-goods class, the packing group and the limited quantity per item. From this follow transport documents, correct labelling of packages and the 1000-point rule for exemption quantities. When choosing, check whether the ERP automatically transfers this data into the delivery note and transport documents, and whether quantity limits are checked during picking.

Labelling and CE

Beyond hazardous-substance labelling, certain products - such as mixtures for professional use or equipment - also require CE marking. The ERP should document the associated conformity data on the item so it is available at delivery and inspection.

Safety data sheets: versioning and mandatory supply

The safety data sheet (SDS) is the central document in hazmat trading. Under REACH (Article 31) it must be provided to the commercial buyer free of charge on first purchase and with every update - in the national language and in the current 16-section format.

This translates into concrete ERP requirements:

• Versioning: Every SDS version must be stored on the item with a validity date; old versions remain traceably archived.
• Automatic supply: On order delivery, the currently valid SDS must be attached automatically - digitally or as a document.
• Change logic: When an SDS is updated, the system must identify the affected customers of the last twelve months so they receive the new version.
• Proof of record: It must be provable who received which SDS version and when.

An ERP that treats the SDS merely as a static file attachment does not fulfil this supply obligation cleanly. Look for a genuine link between SDS version, item and delivery.

Batches, recipes and traceability

The core of every chemicals ERP is end-to-end traceability. In a recall or complaint, you have to know within minutes which raw-material batches a container came from - and which output batch went to which customers.

Recipes and production batches

Anyone who produces or fills mixtures themselves needs recipe management that generates a production batch of the finished product from the input batches of the raw materials and links the two. Only then can batch-to-batch tracing be shown in both directions: from the finished product back to every raw-material batch, and from the raw material forward to every customer supplied. Concentration, density and purity belong here as batch attributes, because they influence classification and further use.

Shelf life and blocked stock

Many chemicals have a limited expiry date or a deadline until requalification. The system should maintain a best-before date per batch and control withdrawal according to the FEFO principle (First Expired, First Out). Blocked and quarantine stock for batches to be inspected, blocked or returned is mandatory, so that defective goods are not shipped by mistake.

Storage classes and segregation

Physically correct storage is safety-critical in the hazmat area and legally binding - in Germany above all through TRGS 510 (Technical Rules for Hazardous Substances: Storage). Every hazardous substance is assigned to a storage class (LGK), and not all storage classes may be stored together.

A chemicals ERP must maintain the storage class per item and, on put-away, check whether a storage location permits co-storage. The segregation matrix broadly distinguishes:

Check whether the system has this matrix stored and whether it warns or blocks when posting to an impermissible storage bin. In addition, maximum quantities per storage section and fire-protection zone should be monitored. An ERP replaces neither a storage concept nor a risk assessment - but it prevents the most common errors in daily put-away and removal.

REACH, customs and cross-border trade

Anyone who imports chemicals into the EU or trades within the EU must map additional obligations in the ERP.

REACH requires that substances are registered and that substances of very high concern (SVHC) as well as restrictions and authorisation requirements (Annex XIV/XVII) are observed. The ERP should hold a REACH registration number and SVHC flag per item, so that blocked or authorisation-requiring substances don't reach sales unchecked.

In cross-border trade, customs and statistical obligations come on top:

• Customs tariff number (HS code): per item for import and export.
• Incoterms: clear rules on the transfer of risk and cost per order - especially relevant in hazmat trading.
• Intrastat: reporting of intra-EU goods movements once the reporting threshold is exceeded.
• Preference proofs and permits for certain chemicals (such as dual-use goods).

Clarify early whether your ERP maintains these fields as standard or whether additional modules are needed. For connecting to customs and forwarding systems, a clean integration is worth more than manual double entry.

Compliance in the DACH region: what is mandatory in 2026

Alongside the industry-specific requirements, the general accounting and tax obligations apply. Two points are non-negotiable.

First, the system must work in a GoBD-compliant way - documents and postings unalterable, complete and traceable. For batch traceability this is a double benefit, because the same principles apply: an audit-proof audit trail documents seamlessly who changed which record and when.

Second, the e-invoice. In Germany, the obligation to receive structured B2B e-invoices has been in force since 1 January 2025. The obligation to issue comes in stages: as a rule from 1 January 2027 for companies with more than 800,000 euros in prior-year turnover, then from 1 January 2028 for all remaining companies. The format must comply with the European standard EN 16931 (such as XRechnung or ZUGFeRD).

The following overview summarises the must-have criteria by area:

Suitable systems for chemicals and hazmat trading

There is no single best chemicals ERP - the choice depends on manufacturing depth, dangerous-goods volume, export share and process individuality. As a starting point, a vendor-neutral overview; the details are in the profiles in the ERP directory.

• Trade and distribution without in-house production: Cloud systems such as xentral or weclapp cover batches, inventory management and document processing and can be introduced comparatively quickly. Dangerous-goods, SDS and storage-class logic often require additional modules or connections here.
• Operations with filling, mixing and individual process needs: Odoo offers batch, recipe and manufacturing logic via modules, but demands more configuration and integration effort.
• Regulated mid-market and corporate environments: Suites such as Dynamics 365 Business Central, Oracle NetSuite or SAP S/4HANA Cloud bring extensive batch, quality and compliance functions - at higher complexity and higher cost. For deep hazmat logic, many operations rely on specialised industry add-ons.

This mapping is a starting point, not a test-winner ranking. Use the system comparison to mirror candidates against your concrete requirements, and bring in neutral ERP consulting to assess the scope of hazmat functionality.

Conclusion

An ERP for chemicals and hazmat trading stands or falls with clean CLP and ADR classification, versioned and automatically supplied safety data sheets, seamless batch and recipe tracing, correct storage-class and segregation checks, and solid REACH, customs and Intrastat data. Standard trading systems most often map these functions only half-heartedly, so check them first. Draw up a prioritised requirements list, match it against concrete systems, and factor in GoBD and the e-invoice deadlines of 2025/2027/2028 from the start. When in doubt, align your storage concept and risk assessment with an occupational-safety specialist and a tax advisor - those who take the regulated industry's proof obligations seriously early are able to act in the event of an inspection or recall.