{"id":4021,"date":"2026-11-04T09:00:00","date_gmt":"2026-11-04T01:00:00","guid":{"rendered":"https:\/\/sayoon-dc.com\/?p=4021"},"modified":"2026-11-09T00:18:32","modified_gmt":"2026-11-08T16:18:32","slug":"dc-contactor-reach-svhc-document-review","status":"publish","type":"post","link":"https:\/\/sayoon-dc.com\/it\/blog\/dc-contactor-reach-svhc-document-review\/","title":{"rendered":"DC contactor REACH and SVHC declarations: document scope before approval"},"content":{"rendered":"<p>A DC contactor REACH SVHC declaration should identify the supplied model, the materials or articles covered, the relevant substance-list reference, the issuer and the issue date. A statement that merely says \u201cREACH compliant\u201d leaves the buyer unable to connect the document to the actual contactor. Begin with identity and scope, then ask the responsible compliance reviewer whether the evidence answers the destination-market requirement. This guide explains a purchasing document review; it does not certify Sayoon products, establish their substance content or replace a legal applicability assessment.<\/p>\n<h2>What question should the declaration answer?<\/h2>\n<p>For a contactor purchase, the useful question is whether the supplier has provided substance information for the exact configuration being ordered. That includes the ordered variant and any separately supplied accessories within the request. An electrical rating describes switching duty. A material declaration describes a different subject. Neither document substitutes for the other.<\/p>\n<p>The European Chemicals Agency guidance published through the EU Publications Office explains obligations concerning substances in articles. Ireland&#8217;s Health and Safety Authority also explains SVHCs and authorisation. Use these sources to understand the framework, then have the responsible party identify the duties applicable to the actual transaction. Do not assume that every party in the supply chain has identical obligations.<\/p>\n<p>For example, a non-European manufacturer can supply useful composition evidence while an importer must still assess its own market obligations. A buyer should record who is supplying information, who is assessing it and who is responsible for the resulting declaration to a customer. A supplier signature does not automatically transfer every downstream responsibility.<\/p>\n<h2>Match the document to the delivered configuration<\/h2>\n<p>Collect the full part number, drawing revision and ordered options before reviewing the declaration. If the purchase order describes a contactor family while the drawing specifies a different terminal arrangement, resolve that identity mismatch first. The same enclosure appearance does not establish identical plastics, plating, contact materials or accessory composition.<\/p>\n<p>A family-level document can be useful when its scope explicitly includes the ordered part. Ask for the family-to-part mapping if that relationship is unclear. Conversely, do not demand a new document merely because a file uses a family title when the actual coverage is already explicit and adequate. The aim is traceable evidence rather than a larger folder.<\/p>\n<p>Retain the source file with its original filename and issue details. A screenshot copied into a quotation can omit exclusions or annexes. Preserve the full document, including referenced product lists and any conditions. If a translation is supplied, retain the source-language version so that a reviewer can resolve ambiguous substance names or scope wording.<\/p>\n<figure><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/05\/czw100a_s1-1-2.webp\" alt=\"SAYOON DC contactor product view\"><\/figure>\n<h2>Use a practical declaration review table<\/h2>\n<div class=\"sy-table-wrap\">\n<table>\n<thead>\n<tr>\n<th>Review item<\/th>\n<th>Evidence to collect<\/th>\n<th>Decision boundary<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Product identity<\/td>\n<td>Ordered model, suffix and revision<\/td>\n<td>Clarify family-to-part coverage<\/td>\n<\/tr>\n<tr>\n<td>Reference date<\/td>\n<td>List reference and assessment basis<\/td>\n<td>Request refresh for an unresolved update<\/td>\n<\/tr>\n<tr>\n<td>Document scope<\/td>\n<td>Included articles and accessories<\/td>\n<td>Keep uncovered items pending<\/td>\n<\/tr>\n<tr>\n<td>Decision<\/td>\n<td>Issuer response and qualified review<\/td>\n<td>Record conditions and refresh trigger<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>This is a qualitative procurement checklist, not a legal threshold table. The source guidance explains the underlying article and substance concepts. Your compliance procedure should specify the actual list reference, evidence level and decision authority required for the intended destination and customer contract.<\/p>\n<h2>List date and declaration date are different<\/h2>\n<p>Record both the declaration issue date and the list or regulatory reference on which the assessment relies. A newly signed letter may repeat an older assessment. An older file may still be useful background, but its age alone cannot establish coverage of later additions or material changes. Ask the issuer to explain the relationship rather than guessing from the file creation timestamp.<\/p>\n<p>Do not copy a numerical count of Candidate List substances into an evergreen purchasing requirement without a revision reference. Lists change, and an unexplained count can become misleading. A controlled request should identify the reference being used and state what event requires refresh. The appropriate refresh event might be a list update, a product material change or a customer requirement.<\/p>\n<p>Avoid treating every different date as evidence of noncompliance. A supply-chain assessment can legitimately predate a signed summary. The reviewer needs to understand whether the underlying information still represents the ordered product and the applicable reference. Record that reasoning in the approval note so that the next buyer does not repeat the same investigation.<\/p>\n<h2>Read substance scope without inventing composition<\/h2>\n<p>A DC contactor can contain multiple materials, but appearance cannot identify their chemical composition. A silver-coloured terminal does not prove a particular plating system. A black housing does not identify a polymer grade or additive package. Request the supplier&#8217;s evidence when the declaration depends on those details.<\/p>\n<p>If the document reports the presence of a substance, do not immediately translate that into a universal statement that the product is prohibited. Different provisions address communication, notification, authorisation and restrictions, with different conditions and responsible parties. Escalate the specific information to the qualified reviewer instead of collapsing these questions into one pass-or-fail label.<\/p>\n<p>Similarly, the absence of a named substance from a short marketing declaration is not necessarily evidence that it was assessed and absent. Ask whether the statement is intended to cover the requested list, the specific product and the relevant scope. Preserve an unknown result as unknown until the supplier supplies a defensible answer.<\/p>\n<h2>Keep REACH, RoHS and electrical approval separate<\/h2>\n<p>A RoHS document addresses a different regulatory framework. A product safety certificate addresses another set of questions. An ISO management-system certificate addresses the organisation and its processes within a defined scope. Putting these documents in one folder is convenient, but treating them as interchangeable weakens the review.<\/p>\n<p>For a battery-system contactor, electrical selection still requires the intended voltage, current, switching duty, operating environment and manufacturer instructions. A strong material declaration cannot compensate for an unsuitable breaking duty. Equally, a successful electrical test does not establish substance-list coverage. Maintain separate approval fields with the relevant evidence attached to each.<\/p>\n<p>This separation also makes supplier communication clearer. Send a material question to the responsible materials or compliance contact and an interruption-duty question to engineering. A combined email can be appropriate, but label the requested answers so that a general sales response is not mistaken for a technical conclusion.<\/p>\n<figure><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/05\/czw100a_s1-1-2.webp\" alt=\"SAYOON DC contactor product view\"><\/figure>\n<h2>Resolve incomplete or conflicting statements<\/h2>\n<p>When information is missing, identify the precise gap. \u201cPlease provide compliance\u201d is less useful than asking whether a named part and revision are covered by a specified declaration. Include the order reference and explain which annex, date or material scope is unresolved. Give the supplier a question that can be answered with evidence.<\/p>\n<p>If two files conflict, retain both and request a controlled replacement or written clarification. Do not silently choose whichever statement is more favourable. Check whether one document covers an older configuration, a different manufacturing site or only an accessory. Those differences may explain the apparent conflict without establishing the answer for your order.<\/p>\n<p>Assign an owner and an approval deadline to unresolved requests. If the evidence is required before purchasing or shipment, the responsible authority must decide whether the order remains on hold. A buyer should not release an incomplete compliance review simply because the delivery date is approaching.<\/p>\n<h2>Build the RFQ evidence request<\/h2>\n<p>Ask Sayoon for the current model identification, the applicable declaration or material-information document, its coverage and issue details, and a contact for technical clarification. Include destination market and customer-specific requirements so that the supplier understands why a generic letter may be insufficient.<\/p>\n<p>Request notification when a relevant material or product revision changes. Specify how a replacement declaration should be associated with the new configuration and how transition stock will be identified. This is particularly useful when repeat orders span multiple production periods and the purchasing system otherwise retains only the first approved file.<\/p>\n<p>Keep the request proportionate. A complete material breakdown may be unnecessary for one decision and essential for another. Define the information needed to answer the actual requirement, respect legitimate confidentiality arrangements and agree a secure way to exchange supporting documents when needed. Unnecessary document volume can obscure the relevant evidence.<\/p>\n<h2>Save an approval record that another buyer can use<\/h2>\n<p>The closing record should identify the order, part, document revision, reference list, reviewer and conclusion. State any exclusions and the event that will trigger reassessment. Attach the supplier response rather than relying on an email subject line or an unexplained green status in a spreadsheet.<\/p>\n<p>For a hypothetical order, a defensible note might say that the supplier declaration covers the ordered suffix and specified list reference, while a separately supplied accessory remains under review. That is more useful than saying the entire assembly is approved when the evidence only covers one component. Keep procurement release aligned with the actual boundary.<\/p>\n<h2>Educational video<\/h2>\n<p>ECHA explains communication about substances in articles. This educational webinar supplies regulatory background; check current applicable requirements separately.<\/p>\n<div style=\"aspect-ratio:16\/9;position:relative\"><iframe src=\"https:\/\/www.youtube-nocookie.com\/embed\/sj6yoAxn7Tg\" title=\"Communicating about substances in articles - what you need to know \u2014 EUchemicals\" loading=\"lazy\" allowfullscreen style=\"border:0;width:100%;height:100%\"><\/iframe><\/div>\n<p><a rel=\"noopener nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=sj6yoAxn7Tg\" target=\"_blank\">Watch the educational video.<\/a><\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Is a REACH declaration the same as a certificate?<\/h3>\n<p>No. Read what the issuer actually declares and which products and references it covers. Do not describe a supplier statement as independent certification unless evidence supports that description.<\/p>\n<h3>Can I use a declaration for another contactor in the same family?<\/h3>\n<p>Only when the document or a controlled supplier clarification establishes coverage of your exact ordered configuration. Similar appearance or a shared current rating is insufficient.<\/p>\n<h3>Does a RoHS statement answer an SVHC request?<\/h3>\n<p>It does not automatically answer that request. Keep the regulatory frameworks and evidence scopes separate and obtain the information required for the actual question.<\/p>\n<h3>What should I do when the supplier cannot confirm scope?<\/h3>\n<p>Record the unresolved part, reference and information gap, then refer the release decision to the responsible compliance authority. Do not convert missing information into a negative substance finding or an approval.<\/p>\n<h2>Product documentation and complementary guides<\/h2>\n<p>Discuss the <a href=\"https:\/\/sayoon-dc.com\/product\/czw100a-normally-open-dc-contactor\/\">CZW100A contactor construction reference<\/a> with Sayoon and request current documentation for the exact ordered configuration. Use the <a href=\"https:\/\/sayoon-dc.com\/blog\/dc-contactor-selection-guide-key-factors-for-reliable-motor-control\/\">DC contactor selection guide<\/a> for the separate technical selection process. Complementary documents include <a href=\"https:\/\/sayoon-dc.com\/blog\/dc-contactor-rohs-compliance-document-review\/\">How to Review RoHS Documents for a DC Contactor RFQ<\/a>, <a href=\"https:\/\/sayoon-dc.com\/blog\/how-to-review-dc-contactor-test-report\/\">How to Review a DC Contactor Test Report<\/a>.<\/p>\n<h2>Primary references and scope<\/h2>\n<p>The official sources support the document and management concepts discussed above. Their jurisdiction and publication context remain distinct. They do not certify or endorse the pictured product.<\/p>\n<ul>\n<li><a rel=\"noopener nofollow\" href=\"https:\/\/op.europa.eu\/en\/publication-detail\/-\/publication\/a59c2214-b2e4-11e7-837e-01aa75ed71a1\" target=\"_blank\">Official primary reference 1<\/a><\/li>\n<li><a rel=\"noopener nofollow\" href=\"https:\/\/www.hsa.ie\/your_industry\/chemicals\/legislation_enforcement\/reach\/svhcs_and_authorisation\/\" target=\"_blank\">Official primary reference 2<\/a><\/li>\n<\/ul>\n<p><script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Is a REACH declaration the same as a certificate?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. Read what the issuer actually declares and which products and references it covers. Do not describe a supplier statement as independent certification unless evidence supports that description.\"}}, {\"@type\": \"Question\", \"name\": \"Can I use a declaration for another contactor in the same family?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Only when the document or a controlled supplier clarification establishes coverage of your exact ordered configuration. Similar appearance or a shared current rating is insufficient.\"}}, {\"@type\": \"Question\", \"name\": \"Does a RoHS statement answer an SVHC request?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"It does not automatically answer that request. Keep the regulatory frameworks and evidence scopes separate and obtain the information required for the actual question.\"}}, {\"@type\": \"Question\", \"name\": \"What should I do when the supplier cannot confirm scope?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Record the unresolved part, reference and information gap, then refer the release decision to the responsible compliance authority. Do not convert missing information into a negative substance finding or an approval.\"}}]}<\/script><\/p>\n<style>.sy-pro-article-main{min-width:0;max-width:100%}.sy-pro-article-main>*{max-width:100%}.sy-table-wrap{max-width:100%;overflow-x:auto}.sy-table-wrap table{min-width:650px;width:100%;border-collapse:collapse}.sy-table-wrap th,.sy-table-wrap td{padding:12px;border:1px solid #d5dce4;vertical-align:top;text-align:left}figure{margin:24px 0}figure img{max-width:100%;height:auto}<\/style>\n","protected":false},"excerpt":{"rendered":"<p>Review DC contactor REACH and SVHC declarations by model, reference date and material scope before accepting supplier evidence.<\/p>","protected":false},"author":4,"featured_media":4389,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_gspb_post_css":"","footnotes":""},"categories":[1],"tags":[61],"class_list":["post-4021","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-dc-contactor-engineering"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"_links":{"self":[{"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/posts\/4021","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/comments?post=4021"}],"version-history":[{"count":6,"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/posts\/4021\/revisions"}],"predecessor-version":[{"id":5077,"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/posts\/4021\/revisions\/5077"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/media\/4389"}],"wp:attachment":[{"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/media?parent=4021"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/categories?post=4021"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sayoon-dc.com\/it\/wp-json\/wp\/v2\/tags?post=4021"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}