iDistributor setup
Print
Modified on: Wed, 13 May, 2026 at 1:45 PM
Welcome as a customer
Getting started with iDistributor
This guide helps you understand the legal requirement, prepare your organisation, and connect your business system — step by step.
1 Legislation 2 Things to consider 3 Technical implementation 4 Overview & follow-up
Background
Why do I need to send SDS?
The REACH regulation sets clear requirements for everyone who distributes chemical products. Here is what you need to know.
REACH (EC) No 1907/2006 — Article 31:8
Safety Data Sheets must be provided free of charge, on paper or in electronic form. Publishing an SDS on a website is not sufficient — a more active approach is required, such as sending a direct link or attaching the SDS by email.
Who is affected?
The obligation applies to these roles
Manufacturer
Companies that manufacture chemical products and sell them to professional customers.
Importer
Companies that import chemical products into the EU/EEA for onward sale.
Distributor
Companies that purchase and redistribute chemical products to professional end customers.
Agent (Only Representative)
Companies acting as legal representative in the EU for a non-EU manufacturer of chemical products.
The two obligations
When must an SDS be sent?
1. At the first delivery
An SDS for the product must be actively provided to the customer no later than the first delivery of a chemical product. This applies to all chemical products classified as hazardous that are sold to professional customers.
2. When an SDS is updated
When an SDS is updated with a new revision, it must be automatically sent to all customers who have purchased the product within the last 12 months — regardless of whether they have placed a new order.
Why iDistributor? Keeping track of who has received which SDS, in which language, and ensuring updates reach the right customers — manually — is practically impossible at scale. iDistributor automates the entire flow and gives you full traceability.
Record-keeping
How long must SDS be retained?
10-year retention requirement
REACH requires that SDS — both those you create and those you receive — are retained for at least 10 years. They may need to be presented during an inspection. In iDistributor, all current and previous revisions are stored on each product's information page.
Important to understand
Products and SDS are not always 1 to 1
Multiple products — one SDS
The same chemical composition can be sold in several packaging sizes, resulting in multiple article numbers in your ERP. Since the chemical mixture is identical, there is only one SDS in the system.
Art.no 1001 — Paint 1L
Art.no 1002 — Paint 5L
Art.no 1003 — Paint 10L
→
1 SDS
One product — multiple SDS
A product can also require multiple SDS. An adhesive consisting of a base and a hardener has one article number in the ERP — but since the base and hardener are separate chemical mixtures, iDistributor handles them as two distinct SDS.
Art.no 2001 — Adhesive (base + hardener)
→
Practical implication: When you send an article number to iDistributor, the system may need to send one or several SDS depending on the product's composition. This is also why suppliers do not provide unique identifiers on SDS — the same data sheet can cover multiple product variants.
Things to consider →
Things to consider
Before going live, there are a number of decisions and preparations you need to make. Go through these carefully with your IT, ERP manager, and EHS team.
Remember: iDistributor connects to your business system via Intersolia's web API. Intersolia can only receive information — adapting the business system and communication is the customer's responsibility.
Identification
Choose the right unique identifiers
Delivery ID — must be unique per request
You need to decide which field in your ERP system will serve as delivery_id. For example, an order number combined with a date. Important: the same delivery_id can never be reused — if you send an already used ID, the request will be ignored.
Recipient ID — link history to the customer
recipient_id is a unique ID that identifies the email recipient. It is used to preserve history if you change a customer's email address — same customer, new address, and iDistributor remembers what has already been sent.
Products in ERP
Flag chemical products
Flag chemicals in your business system
You need a method to identify which products in your ERP are chemicals. iDistributor should only receive requests for chemical products — not office supplies, spare parts, or similar. Add a field or flag in your ERP if you do not already have one.
Email addresses
Ensure access to customer email addresses
Which email address will the SDS be sent to?
iDistributor sends the SDS to the email address you include in the API call. You need a process to:
- ✓Collect and store email addresses for buyers/purchasers at your customers
- ✓Decide which email field in your ERP to extract
- ✓Have a routine for updating addresses when they change
Country settings
Configure language per country
Country code determines the SDS language
You provide a country code (e.g. SE, FI, PL) in each API call. Intersolia then configures rules for which language(s) are sent for each country, as well as a fallback language if a specific SDS is unavailable.
| Country | Primary language | Fallback |
|---|
| SE — Sweden | Swedish | English |
| FI — Finland | Finnish + Swedish | English |
| PL — Poland | Polish | English |
| DK — Denmark | Danish | English |
Contact Intersolia to set up or change country rules — a maximum of 4 language options per country is possible.
Product list
Prepare your product information
Send a product list to Intersolia
Before go-live, you need to send a list of your chemical products. The list must include at least:
- ✓Product name (trade name)
- ✓Your own article number
- ✓Supplier's article number
- ✓Supplier / manufacturer
Intersolia then matches the products against the global database and sources any missing SDS. You will be notified when the products are ready to be added to iDistributor.
← Legislation Technical implementation →
Technical implementation
An overview of the API integration, the most important endpoints, and the implementation flow.
System architecture
How does it all fit together?
Key API endpoints
Three endpoints to get started
POSTapi/v1/Auth/Login
Authentication. Send customer_id, username and password. Returns a token_id used in all subsequent calls.
POSTapi/v1/Distribution/DistributeBulk
The main endpoint for SDS distribution. Send a list of article numbers for all chemical products in an order. iDistributor automatically determines what needs to be sent.
GETapi/v1/Distribution/List
Retrieve distribution status — useful for troubleshooting and checking what has been sent to a specific customer or delivery.
Example
What an API call looks like
POST /api/v1/Distribution/DistributeBulk — JSON body
{
"token_id": "81D8170D-51F9-41F1-85DC-DE1FC712242E",
"art_no_list": ["1234", "4567", "8910"],
"country": "SE",
"delivery_id": "ORDER-20240415-9981", // Unique per request!
"recipient_id": "CUST-00421", // Unique per end customer
"email": "purchasing@customerco.com"
}Implementation flow
From setup to go-live
1
Product matching
You send your product list (product name, article number, supplier) to Intersolia. We match against the global database, source missing SDS, and upload the products with your own article numbers.
Intersolia2
ERP configuration & API integration
You flag chemical products in your ERP, set up the email collection process, and build the integration against iDistributor's REST API. Intersolia provides technical documentation and can assist with testing.
Customer (with support from Intersolia)3
Email template & country rules
You customise the text in the SDS email that end customers receive (body text). Intersolia configures language and country rules according to your preferences.
Intersolia4
Test & go-live
Test with different products and email addresses (NOTE: the delivery_id and recipient_id combination is checked — always test with unique values). Intersolia will follow up at go-live.
Intersolia + CustomerImportant during testing: Since the system checks whether the same recipient_id and article number combination has already received an SDS, you must test with different products and/or email addresses for each test call. Otherwise the response will be "already distributed".
Optional features
Additional capabilities
Product Links API Add-on
Always retrieves up-to-date SDS links for your webshop or intranet. The link always points to the latest version — you never need to update it manually.
ProductData API Add-on
Provides access to structured chemical information (sections 1, 2, 3, 9 from the SDS) plus GHS pictograms and ADR information — perfect for webshop integration.
← Things to consider Overview & follow-up →
Overview & follow-up
iDistributor provides two reports for tracking distribution status — available under Reports → Custom.
Reports
How do you track distributions?
Requested Distributions — all requests
Found under Reports → Custom. Provides a complete overview of all distribution requests sent from your ERP, with information about the recipient, the product, and whether the SDS was actually sent.
| Column | Description |
|---|
| DeliveryID | Unique number sent from your ERP system |
| DateRequested | Date when the product was sent from your ERP |
| RecipientID | Unique ID for the recipient's email address |
| E-mail | Email address where the SDS was sent |
| Requested ArtNo | Your article number in your ERP and iDistributor |
| Requested country | Country where the SDS should be sent |
| Was SDS sent? | Yes or No — with an error message if No |
Note 1: SDS already sent to the customer previously. Note 2: No document matched the rules — no SDS available for the country. Note 3: No error — SDS sent!
Successful Distributions — successful sends
Found under Reports → Custom. Shows all successful distributions and which language the SDS was sent in — useful for checking whether you are sufficiently compliant for certain products and markets.
| Column | Description |
|---|
| DeliveryID | Unique number sent from your ERP system |
| Date | Date when the SDS was sent |
| Sent art No | Your article number |
| Sent language | Language the SDS was sent in (e.g. SV, FI, EN) |
| Requested country | Country the SDS was requested for |
Note: Email sends triggered by SDS updates (new revision) are not included in these reports.
← Technical implementation
Did you find it helpful?
Yes
No
Send feedback Sorry we couldn't be helpful. Help us improve this article with your feedback.