Tonnage per substance SDS version per customer Twelve months back

Custom software development for REACH registration and safety data sheets

If you update a safety data sheet, the new version with its revision date must be sent free of charge to all customers you supplied in the preceding twelve months. This is not a chemical question but an administrative one: can you produce that list, and is it correct?

Appfront
Live

What REACH asks of your administration

The registration obligation applies from one tonne per substance per registrant per year. The minimum information requirements depend on the quantity produced or imported within the European Union and are set out in Annexes VI to X. A chemical safety report is only required at ten tonnes or more per year.

That makes the tonnage per substance per year a figure with legal consequences. Anyone who grows across a threshold without noticing discovers this afterwards, while the obligation already applied at that point. In practice this threshold is hard to monitor, because a single substance arrives through several products and several suppliers.

The safety data sheet follows its own rhythm. The sheet always has sixteen fixed sections and must be drawn up in the language of the country where you supply. An extended safety data sheet additionally contains the exposure scenarios for specific uses as an annex.

Updating is mandatory when new information becomes available about the hazards or the risk management measures, when an authorisation is granted or refused, and when a restriction is imposed. This is followed by forwarding to everyone who purchased in the preceding twelve months.

How we build this

The core is the substance and the supply. A substance without supplies creates no obligations; a supply without a substance is just an invoice line. The obligations arise where the two meet.

1
Substances across products

Which substance is in which product, at what concentration, so that volumes that would otherwise stay scattered come together.

2
Tracking tonnage per year

What has been produced or imported this year, and how that compares with the thresholds that trigger obligations.

3
Managing SDS versions

Each version with its revision date and language, linked to the products it applies to.

4
Directing forwarding

When a new version is issued, the system delivers the list of customers from the past twelve months and keeps track of who has been reached.

What the software actually does

The integration between substance, product and delivery holds the whole thing together. What else you need depends on your role in the supply chain and on the number of markets you operate in.

Substance register with concentrations

The same substance across different products, so the total annual quantity becomes visible instead of staying scattered.

Thresholds monitored

When a substance approaches one tonne or ten tonnes per year, that should be a signal, not a discovery after the fact.

SDS per language and per version

Sixteen sections, the language of the country of supply, and the revision date that determines which version is current.

Twelve-month recipient list

Who received this substance or mixture in the past year. That is the list on which the obligation rests.

Extended SDS with exposure scenarios

Exposure scenarios belong as an annex to the SDS and must be updated whenever the SDS changes.

Tracking the candidate list

When a substance is added to the candidate list, obligations arise. The system shows which of your products are affected.

Who we build for

Who works with this differs by company. Four situations.

Regulatory affairs

They monitor the obligations and need the delivery records, which are usually kept somewhere else.

Importers

For them, the quantity entered per year determines which obligations apply, and that adds up across suppliers.

Formulators

They process substances into mixtures and must pass on the information from the chain to their own customers.

Distributors

They do not manufacture anything themselves, but must supply a current and complete SDS and pass on updates.

Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

Technology and integrations

Candidate lists grow, requirements for the SDS are revised and restrictions are added. Substances, thresholds and document types should be configurable rather than hard-coded.

Substance register with concentrations per product Tonnage calculation per substance per year Version control on safety data sheets Multiple languages per document Delivery records with customer history Alerts on thresholds and list changes Integration with your ERP or order management Roles for regulatory, sales and logistics Demonstrable follow-up per customer Audit trail on every change

Why Appfront

Looking back twelve months is an administrative question

The obligation is clear; compiling the list is the problem. We build that list as a feature rather than an annual search.

One substance appears in several products

As a result, a tonnage threshold remains invisible until it has been exceeded. We aggregate at substance level, not product level.

Language belongs to the market

The SDS is prepared in the language of the country of supply. That makes version control a matter of both language and date.

We do not write your sheets

The content remains yours and your toxicologist's. We make sure the right version reaches the right customer on time.

Security and privacy

Your substance and formulation data is commercially sensitive, and your delivery records show who your customers are and what they buy. Few companies want those two combined and widely accessible. We set up role-based access, show sales the customers without the formulation and regulatory the substances without the commercial terms, and log every access. Integrations run through secure connections to your existing software.

For this subject, the reliability of the moment is the crux. A follow-up distribution ticked as sent after the fact is no proof that the customer received the SDS. We record shipments and versions immutably, with timestamp and person, and make any correction a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.

Frequently asked questions about REACH and safety data sheets

The registration obligation applies from one tonne per substance per registrant per year. The information requirements depend on the tonnage and are set out in Annexes VI to X. A chemical safety report is required from ten tonnes per year.

On new information about the hazards or the risk management measures, when an authorisation is granted or refused, and when a restriction is imposed.

To all customers to whom you have supplied the substance or mixture in the previous twelve months, free of charge, on paper or electronically, marked with the revision date.

A sheet that, in addition to the sixteen mandatory sections, includes the exposure scenarios for specific uses as an annex.

In the language of the country where you supply the substances or mixtures. As a result, a single product can have different current versions in different markets.

This creates information obligations towards customers and, for articles, towards consumers and the ECHA. We describe that side on our page about the REACH app for on-site use.

Who received this product in the past twelve months?

Pick one substance whose sheet has been recently revised and compile the list of customers from the past year. If that takes more than an afternoon, you will not meet that obligation within a reasonable timeframe. We build this as a standalone application and as part of a wider custom software development project.

Edit content