Technically, if we fail REACH Restricted, it is illegal for us to ship our product. Unlike REACH Candidate, where the legal requirement behind REACH Candidate is a notification process, REACH Restricted is a legal restriction. We’d like to include REACH Restricted as part of our compliance roll-up, but currently cannot.
To support the ability to use the REACH Restricted specifications in WPA 10.1, we need the ability to insert exemptions across large groups of parts, where no exemption currently exists. Initial review has shown part failures in the hundreds of thousands range. This number of “failing” parts renders the specification useless to us. It is critical for us to have the ability to programmatically insert the appropriate exemptions.
We feel that with a specification rollout affecting this many CAS Numbers and this many parts require an associated tool set to be able to manage exemption insertion / update.
