How Should a Company Handle Customer Requirements That Go Beyond Legal Minimums?

Separate the source of the requirement before making a commitment：A legally compliant product can still fall short of a customer's commercial specification

Customers may ask for broader substance lists, lower limits, newer test reports, a prescribed method or reporting limit, a supplier-declaration template, or commitments such as PFAS-free, halogen-free, RSL, MRSL, recycled content or future regulatory readiness. Some requests reflect an applicable law. Others are procurement conditions, brand policies or preparation for a future market expectation. A statement that a product meets RoHS or REACH may therefore leave the customer's actual evidence question unanswered.

The practical starting point is not an immediate acceptance or rejection. Classify each item as a legal requirement, a contract or customer specification, or an internal company policy. Legal compliance is a necessary baseline; an accepted contract or specification can create an additional commercial obligation; internal policy may set a stricter control threshold. Each layer needs its own evidence, timing, cost and change-control decision. One layer does not automatically replace the others.

Bottom line first

• Meeting an applicable legal requirement does not automatically meet a customer contract, purchasing specification or brand restricted-substance list; first check the quotation, contract, drawing and specification hierarchy.
• A customer may request broader substance coverage, lower limits, newer reports, a specified method or reporting limit, a declaration format, or evidence for a future requirement.
• PFAS-free, halogen-free, RSL and MRSL need written definitions covering substance scope, threshold, product scope, evidence route and exceptions.
• Feasibility includes engineering design, supplier capability, material data, test method, detection limit, production change control, cost and delivery timing, not simply the existence of a report.
• Where full fulfilment is not feasible, record the evidence gap, alternative approach, cost allocation, exception request or deviation process in writing rather than relying on verbal understanding.
• Review customer commitments when the specification, product, material, supplier or market changes so that an old response is not reused outside its scope.

Information needed before deciding

• 01 Legal baseline: identify the regulations, limits, exemptions, dates, product scope and market that actually apply rather than naming a regulation only.
• 02 Contract or customer specification: locate the requirement in the RFQ, quotation, purchase order, quality agreement, drawing, RSL, MRSL or technical specification, including version and precedence.
• 03 Internal policy: identify whether the company has a stricter substance, recycled-content, test-cycle, supplier-management or declaration-control threshold.
• 04 Definition of the request: translate PFAS-free, halogen-free, lower-than-a-limit or newer-report wording into substance scope, concentration, product scope, sampling, acceptance criterion and exceptions.
• 05 Method and detection limit: confirm that the requested method can answer the question and compare reporting and quantification limits with the stated threshold; a Pass label alone is not enough.
• 06 Supply-chain and engineering feasibility: assess formulation, material, process, alternative material, supplier information, change notification and production control before committing.
• 07 Commercial treatment: confirm responsibility for testing, rework, material change, data collection, timing and cost, together with authority for exceptions and deviations.

Practical decision flow

Collect the original requirement

Retain the RFQ, contract, purchase order, drawing, RSL, MRSL, test specification and version date as well as the email request; do not decide from a forwarded summary alone.

Classify the requirement

Mark each item as a legal baseline, customer or contractual specification, or internal policy, and record where they overlap, conflict or impose a stricter condition.

Turn wording into verifiable conditions

Clarify substance or substance group, limit, product or material scope, market, method, reporting limit, declaration format and delivery date.

Map existing evidence

Compare BOMs, material specifications, supplier declarations, reports, upstream data and change records against each condition rather than relying on a general statement.

Test feasibility and gaps

Have engineering, procurement, quality and compliance assess material alternatives, supplier capability, method limitations, sample representativeness, cost, schedule and production risk.

Respond and control change

Document what is accepted, partly supported, pending or not applicable. Use formal clarification or deviation approval for exceptions and set review triggers for later changes.

What different evidence can support

Evidence	What it can support	Important limitation
Customer specifications, RSLs, MRSLs and contract terms	The customer's stated substance scope, format, limit, version, delivery date and potentially contractual responsibility.	Documents can conflict or have different versions. Confirm precedence, model scope and whether the condition has been formally accepted.
Regulatory applicability matrix	A traceable comparison between legal baseline, product scope, restrictions, dates and existing evidence.	It does not settle a stricter commercial requirement and must be updated when regulations or products change.
Supplier declarations and material specifications	Written supply-chain information for a stated material, substance or product scope.	Check part number, grade or formulation, version, substance scope and change control; a generic declaration may not cover the customer specification.
Test reports and method information	Results for a stated sample, analyte, method, reporting limit and test date.	A report supports only its sample and analytical scope. It should not be extended to a lower limit or broader substance group without evidence.
BOMs, drawings and engineering-change records	Whether a customer requirement maps to actual parts, materials, revisions and process controls.	A BOM normally does not prove chemical composition, and coatings, inks, adhesives and process aids need separate review.
Written clarification, exception and deviation records	A formal basis for an agreed scope, alternative evidence, transition period or acceptance criterion.	An unapproved internal interpretation or verbal agreement should not be treated as a contract change or customer acceptance.

Common mistakes

Mistake：State that legal compliance means the customer requirement is met.

**Risk：**The customer may require a different substance list, lower limit, newer evidence or prescribed format and can still reject the delivery.

**Better approach：**Separate legal baseline, customer specification and confirmed or pending evidence in the response.

Mistake：Treat PFAS-free or halogen-free as self-defining marketing language.

**Risk：**Supply-chain scope, testing scope and customer interpretation can differ, creating an unsupported commitment.

**Better approach：**Request a written definition of substance scope, threshold, sample, method, detection limit and exceptions.

Mistake：Read only the Pass conclusion of a report.

**Risk：**The analytes, reporting limit, sample representativeness or test date may not answer the customer question.

**Better approach：**Compare the full report, method, scope, sample identity and customer acceptance threshold.

Mistake：Commit to the customer before checking supplier capability.

**Risk：**Material substitution, confidentiality, testing lead time or production change can make the commitment unworkable.

**Better approach：**Complete cross-functional feasibility and supplier-capability review before making the external commitment.

Mistake：Ignore cost, change and exception terms in the quotation or contract.

**Risk：**Extra testing, data collection or material change responsibility and timing surface only after the order is underway.

**Better approach：**Confirm cost allocation, delivery impact, change notice, deviation and acceptance routes as commercial conditions.

Mistake：Resolve unclear or infeasible requirements by verbal discussion only.

**Risk：**There may be no record of accepted scope, alternative evidence or exception after personnel or product changes.

**Better approach：**Use written clarification, deviation approval or an updated specification linked to the relevant model and revision.

Company action checklist

• Create a customer-requirement register showing the legal, contractual or internal-policy source, version, product scope and accountable owner.
• Ask the customer to define PFAS-free, halogen-free, RSL, MRSL, newer-report or lower-limit expectations and their evidence route.
• Map every requirement to BOMs, material specifications, supplier data, reports, samples and engineering revisions.
• Before testing, confirm that analytes, method, sample preparation, reporting limit and customer threshold are compatible.
• Have engineering, procurement, quality, compliance and commercial owners approve assumptions on material alternatives, supplier capability, cost and timing.
• Use written exceptions, deviations, supplementary evidence or staged plans where a full requirement cannot yet be met.
• Set review triggers for customer-specification updates, material and supplier changes, regulatory updates and new product models.

Manager summary

Customer requirements above the legal minimum are a commercial and evidence-management issue as well as a regulatory one. The company should translate each request into a defined substance, limit, method, sample and document condition, then check engineering feasibility, supply-chain capability, cost and timing. Where evidence is incomplete, manage the gap through written clarification, deviation or an agreed alternative rather than treating a legal-compliance statement as a substitute for the customer specification.

Frequently asked questions

If a product meets RoHS or REACH, must we still answer a customer RSL?

First check whether the RSL is part of the purchasing, quality or contractual requirement. RoHS or REACH evidence can be important, but it does not automatically cover a customer-defined substance list, lower limit, product scope or document format.

What should we ask first when a customer asks for PFAS-free?

Request a written definition: covered PFAS or substance groups, whether the request is limited to intentionally added substances, threshold, material and product scope, test or declaration route, detection limit, exceptions and report format.

Can a customer require a lower limit than the law?

A customer can propose a stricter commercial condition in a purchasing or contract specification. Decide whether to accept it only after checking feasibility, test method, supplier capability, cost and delivery timing.

Is a newer report always better evidence for the customer?

Date is one factor only. Confirm sample identity, material, product revision, analytes, method, reporting limit and customer specification. A newer report with insufficient scope may still not answer the request.

Can we state compliance if the method reporting limit is above the customer limit?

Do not make that conclusion without checking method suitability, reporting and quantification limits, and the customer's acceptance rule. Written clarification, a different method or supplementary evidence may be needed.

Is verbal customer approval of an exception sufficient?

It is not a robust long-term record. Obtain written clarification, deviation approval or a contract or specification update through the applicable company process and link it to the product revision.

Official legislation and reference material

Directive 2011/65/EU on the restriction of hazardous substances in electrical and electronic equipment

European Union

• Legal status: EU Directive. Check the applicable consolidated text, national transposition and product scope for the placing-on-market context.

• Last checked: 2026-08-08

• Publication / update date: Publication/update date not stated on the linked official page; checked 2026-08-08.

• Used for: legal baseline, technical documentation, customer requirement comparison

Regulation (EC) No 1907/2006 (REACH)

European Union

• Legal status: EU Regulation. Consult the consolidated text and current ECHA lists for the applicable version.

• Last checked: 2026-08-08

• Publication / update date: Publication/update date not stated on the linked official page; checked 2026-08-08.

• Used for: legal baseline, substance scope, supply-chain evidence

Regulation (EU) 2025/40 on packaging and packaging waste (PPWR)

European Union

• Legal status: EU Regulation. It entered into force on 11 February 2025 and applies from 12 August 2026, subject to the Regulation's specific provisions and later measures.

• Last checked: 2026-08-08

• Publication / update date: 2025-01-22 (Official Journal publication)

• Used for: customer specification comparison, packaging expectations, future requirements

Commission Implementing Decision (EU) 2020/659 on EN IEC 63000:2018

European Commission

• Legal status: EU implementing decision citing a harmonised standard for assessment of RoHS technical documentation.

• Last checked: 2026-08-08

• Publication / update date: 2020-05-15 (Official Journal publication)

• Used for: evidence package, technical documentation, workflow