Skip to content
Quality, standards & compliancePumps & ValvesElectronics & SensorsMachinery & Plant EngineeringPlastics & Packaging+3

Find RoHS and REACH substances in your BOMs

You see every product with listed substances and can answer customers with evidence.

Today

Customers ask whether your products contain listed substances. Answering takes a declaration for every purchased part, and those are missing, outdated or buried in PDFs. Every update to a substance list starts the search over.

An example

A new substance is added to the candidate list. At Wallner+Hardt Sensortechnik the agent finds it in the declarations for 2 purchased parts used in 11 products, including the WS-420 pressure sensor with M12 connector. It also lists 37 purchased parts with outdated declarations.
Fictional company, typical workflow.

Your data, wherever it lives

Today BOMs sit in the PLM and purchased parts in the ERP, supplier declarations sit as PDFs in e-mails, folders and supplier portals, and the authorities publish the current substance lists on the web. demi reads, understands and links them per purchased part and product, with your rights. With every list update the AI shows every affected product and every missing declaration in minutes, rolled up across the whole BOM, instead of the search starting over, and the compliance owner approves the statement.

Where the data lives today

  • PLM
  • ERP
  • PDFs
  • E-mails
  • Folders & drives
  • Web & portals
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the PLM, ERP, e-mail and supplier portals. demi replaces nothing and links BOMs, purchased parts, supplier declarations, material data and substance lists per part. demi only writes back after approval.

  2. 2 · PermitPermission Layer

    The compliance owner makes the evaluation, and purchasing and quality see the supplier declarations. A statement goes to a customer only once compliance has approved it, and the approval is recorded.

  3. 3 · ActIntelligence Layer

    The agent checks declarations, rolls them up exactly through the BOM to the finished product and compares them with the current substance lists, each statement with its declaration and location. Missing declarations show as gaps, never as compliant.

How it runs

  1. 1

    Link BOMs and purchased parts from the PLM and ERP

  2. 2

    Read in supplier declarations and check their validity

  3. 3

    Roll them up through the BOM to the finished product

  4. 4

    Re-check every BOM whenever a list changes

  5. 5

    Draft the customer statement and send it for release

What changes

  • Fast customer statements backed by evidence

  • Gaps in declarations visible

  • Every list update checked against every BOM

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+192 hfreed per year

Assumptions and calculation

demi reads supplier declarations across the whole bill of materials and shows affected products; you act.

60 min → 36 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

40 product checks × 60 min × 40% × 1.0 (manual) × 12 months = 11,520 min = 192 h

Value per year, before demi costs

Freed per year+192 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€12,480

gained per year

192 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Which substance lists are covered?

The lists that apply to you: legal lists such as RoHS and the REACH candidate list as well as lists from your customers or your industry. demi keeps them as data and re-checks every BOM whenever one changes.

How are missing declarations handled?

A part without a valid declaration counts as open, never as compliant. The agent shows which products are affected and ranks the requests by how many products depend on the part.

Can demi request declarations from suppliers?

Yes. The agent prepares the requests per supplier, sends them once purchasing releases them and follows up on the answers. It reads incoming declarations and assigns them to the right part.

Does this make our customer statement legally safe?

demi collects the evidence, rolls it up through the BOM and drafts the statement. The legal assessment and the signature stay with your product compliance experts. Every claim in the statement links to the declaration it rests on.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases