Certive Solutions / RoHS Compliance

    RoHS compliance.From supplier request to verified evidence.

    Collect, validate and track RoHS compliance documentation across your entire product BOM — without chasing suppliers or manually monitoring every certificate.

    The Problem

    RoHS compliance is more than collecting declarations.

    Managing RoHS means knowing which products are in scope, which components need evidence, whether supplier documents are valid — and when they need renewing. Spreadsheets and email reminders can't keep up as products and suppliers change.

    Missing or expired component compliance evidence.

    Suppliers who do not respond or submit unsuitable documents.

    Disconnected product, component, supplier and document records.

    Missed document renewals and exemption expiry dates.

    BOM-Level Coverage

    RoHS coverage that follows your product structure.

    Set RoHS once on a product category — Certive carries it down to every component in the BOM.

    Inherited down the BOM

    Components inherit RoHS from the products they belong to — even when their own category has no RoHS assigned.

    See why a component needs it

    View which products require RoHS for each component.

    Justified exclusions

    Mark RoHS as not applicable to a component, with a mandatory reason — and reverse it if RoHS applies after all.

    Always in sync

    Inherited requirements update as product categories and BOM relationships change.

    Automated Supplier Requests

    Automate supplier outreach. Stay in control of every request.

    Certive identifies components with missing RoHS evidence and prepares supplier requests automatically. Choose when requests should be sent, review the planned queue, send individual requests immediately, or stop requests that are not needed. When multiple components need evidence from the same supplier, Certive can consolidate them into a single email.

    A request is prepared when a component:

    • Has an applicable RoHS requirement.
    • Has no RoHS evidence yet.
    • Has an assigned supplier with an email address.
    • Meets your automation and request eligibility conditions.

    Initial waiting period

    Set how long Certive waits before automatic requests go out.

    Sending window

    Requests go out once a day on working days, from the hour and time zone you choose.

    Review the queue

    See planned requests and their scheduled send times.

    Send now or cancel

    Send a request immediately, or cancel one you don't need.

    Automatic skip

    Requests are skipped if evidence is already uploaded or conditions no longer apply.

    One email per supplier

    Several requests due to the same supplier on the same day are consolidated into one email.

    Reminders

    Configure the reminder interval and the maximum number of reminders.

    Automatic sending and reminders are not on by default — they follow your company settings and eligibility conditions.

    How it works

    The life of a RoHS evidence request.

    From the moment a requirement applies to the day the evidence needs renewing.

    Requirement

    1. 1

      RoHS requirement assigned

    2. 2

      Component identified as missing evidence

    Request

    1. 3

      Request scheduled

    2. 4

      Supplier receives request

    Evidence

    1. 5

      Supplier uploads evidence

    2. 6

      Document validation

    Outcome & renewal

    1. 7

      Outcome

      AcceptedRejectedNeeds review
    2. 8

      Renewal monitoring

    If the supplier doesn't respond

    1. Awaiting supplier
    2. Reminder scheduled
    3. Follow-up sent according to settings
    Validation

    Validate the evidence, not just the upload.

    Supplier documents go through your configured validation workflow. Clear cases are handled automatically; uncertain ones go to a person.

    Automated checks

    • Every supplier document runs through your configured validation workflow.
    • Relevant details are extracted, including expiry dates when detectable.
    • Failed documents can trigger an automatic explanation to the supplier, when that setting is on.

    Human review when needed

    • Documents that look relevant but can't be confidently matched to the requested component go to review.
    • The same applies when the supplier can't be confidently matched.
    • A human reviewer decides the outcome of every manual case.

    Accepted evidence types include

    RoHS Declaration Material Declaration Test Report Exemption Documentation

    A supplier can submit a different evidence type than the one requested — it's assessed where the RoHS evidence rules support it.

    AI supports your team — it doesn't accept every document automatically or guarantee legal compliance.

    Expiry & Renewal

    Know when evidence needs renewing — before it expires.

    Certive tracks document expiry dates and RoHS exemption deadlines, and requests updated evidence ahead of time.

    Document expiry dates

    Extracted during validation or entered manually.

    Exemption deadlines

    Recorded expiry dates for applicable RoHS exemptions.

    Advance renewal requests

    Request updated evidence a set number of days before a document or exemption expires.

    Reminders

    Follow-ups sent according to your configured workflow.

    1. Evidence available
    2. Expiry approaching
    3. Renewal request
    4. Updated evidence received
    Benefits

    Know what is covered, what is missing, and what needs attention.

    Less Manual Work

    Fewer repetitive supplier emails, follow-ups and document admin.

    Better Visibility

    See missing, unsuitable and expiring evidence across the BOM.

    Connected Documentation

    Clear links between products, components, suppliers and evidence.

    Proactive Renewals

    Renewals start before documents or exemptions expire.

    Explore the full platform on the Product page.

    FAQ

    Frequently asked questions about RoHS compliance management

    Yes. Automatic requests go out once a day in your sending window: on working days, from the hour you set, in your time zone. After RoHS starts to apply to a component, Certive waits a grace period (two days by default) before asking, so your team can upload evidence you already hold, remove a requirement added by mistake, or switch the request off. Automatic requests are off until you turn them on.

    Yes. The planned requests list shows every request waiting to go out. You can stop the request for a component, or for every waiting component of a product at once, and allow it again later. Send now sends it immediately without waiting for the sending window. A planned request is also dropped if RoHS evidence is uploaded in the meantime or the component has already been asked.

    The daily batch sends one email per supplier and document type, listing every component that needs evidence, each with its own upload link. Reminders for that email go out as one email too, covering only the components still waiting.

    Certive sends reminders at the interval you set, up to the maximum number you choose. Reminders are off until you set a maximum. They go out only for requests whose email was delivered and whose link is still valid, and stop once the requested document is on file. A supplier with an open request past its response deadline is shown as non-responsive.

    The document is marked Failed and does not count as RoHS evidence, so the component and the products that contain it show as failing RoHS. Certive reopens the original request and drafts a follow-up that tells the supplier, in the audit's own findings, what was wrong and what to send instead. By default a person reads it and sends it with one click; you can set follow-ups to go out automatically.

    A document goes to Needs review when the audit raises a concern without rejecting the declaration: a section it could not confirm, a part number that does not match the component, or an issuing company that does not match the component's supplier. It also goes there when the audit could not run. A reviewer accepts it as evidence or rejects it, and a rejection sends the same follow-up as a failed audit.

    A document's expiry date is read from the declaration during validation or entered at upload. Exemption codes cited in a declaration are recorded on the component, with their deadlines taken from RoHS Annex III. When either date passes, the component's status is updated automatically. With a lead time set, Certive asks the supplier for updated evidence that many days before a document expires or an exemption's deadline passes, once for each.