REACH Compliance for Cylinder Sleeve: Buyer Checklist
REACH compliance for cylinder sleeve sourcing is rarely blocked by the iron sleeve body alone. The real exposure usually sits in what is added later: phosphate layers, rust-preventive oils, VCI paper, label adhesives, seal rings, and undocumented packaging changes. That is why buyers should treat compliance as a source-qualification exercise, not a document-collection exercise. The goal is simple: prove that the declaration matches the exact shipped part number, drawing revision, finish, packing method, and batch. This article breaks down a practical way to assess reach compliance for cylinder sleeve programs without slipping into vague supplier templates or approval files that fail under audit.
Start with the decision: what does REACH compliance for cylinder sleeve actually cover?
For sourcing teams, REACH compliance for cylinder sleeve comes down to three decisions:
1. Does the delivered article contain any SVHCs above 0.1% w/w? 2. Does anything in the delivered part or pack create an Annex XVII restriction issue for the target market or application? 3. Can the supplier prove that the declaration applies to the exact part and batch shipped?
Under Regulation (EC) No 1907/2006, a finished cylinder sleeve is generally treated as an article. That matters because the compliance check is not limited to the substrate. It has to cover whatever arrives with the part in saleable condition.
The iron body is often straightforward. Typical substrates include grey cast iron, alloy cast iron, and centrifugally cast grades built around a controlled pearlitic structure. Buyers may already be managing technical requirements such as 180-260 HB hardness, bore tolerances in the 0.01-0.03 mm range, outer diameter tolerance around 0.02-0.05 mm, and wall-thickness limits defined by drawing. None of that proves compliance by itself, but it tells you what exact article must be named in the file.
The risk profile changes once the sleeve includes secondary materials such as:
- phosphate or conversion coating
- anti-rust oil, wax, or storage film
- VCI packaging media
- carton inks, labels, and adhesives
- seal rings or other kit components
A workable buyer standard is traceability from melt or base casting lot -> machining lot -> preservation or packing lot -> shipment lot. If that chain is missing, the declaration is weaker than it looks.
Where approvals usually fail: the five weak points in supplier files
Most approval problems are not legal-theory problems. They are control problems.
The most common failure modes are:
- the declaration is issued for a generic sleeve family rather than a specific part number and revision
- the supplier declares the bare sleeve but excludes oil, coating, VCI paper, labels, or kit items
- the SVHC statement references an outdated Candidate List
- the supplier cannot show lot-level linkage between the declaration and shipped batches
- finishing or packaging is subcontracted, but those sub-suppliers sit outside the document trail
This is why buyers should start with the file, not with verbal assurances. A signed declaration on letterhead is useful, but only if it is anchored to real manufacturing control.
For wet sleeves and sleeve kits, the risk usually increases because the delivered product may include sealing grooves, corrosion-sensitive surfaces, and elastomer parts with a different material profile from the cast iron body. For repair sleeves, the chemistry may be simpler, but the packaging and preservation system can still break the compliance chain.
If a supplier says, "the material is standard," that is not a complete answer. You need to know whether the shipped condition is standard.
Document pack comparison: what is merely acceptable and what is approval-ready?
Not all supplier responses are equal. A practical way to judge reach compliance for cylinder sleeve is to separate a minimum file from a file that is actually usable in sourcing, import, and customer audit workflows.
Minimum acceptable
- REACH declaration on supplier letterhead, signed and dated
- statement on SVHC status against the current Candidate List
- statement on relevant Annex XVII restrictions
- material specification for the sleeve substrate
- basic traceability explanation
Approval-ready
- part-number- and revision-specific declaration
- named surface treatment or preservation specification
- packaging declaration covering VCI, bags, labels, and carton materials
- sub-supplier visibility for oils, coatings, and packaging inputs
- documented change-control procedure for chemistry or source changes
- lot traceability from foundry or casting stage through shipment
- evidence of system discipline such as ISO 9001:2015 or IATF 16949:2016
A stronger file also identifies the actual trade name or internal code for the anti-rust oil, wax, phosphate chemistry, VCI paper, and adhesive label. That level of detail matters because broad phrases like "protective oil applied" do not hold up well when a customer or importer asks what changed.
If a supplier offers multiple packaging variants for private-label business, confirm whether they can support part-specific records through custom manufacturing. The machined sleeve may be identical, while the compliance file is not.
As a purchasing rule, many buyers treat declarations older than 12 months as stale unless the supplier can show a documented review against the latest Candidate List date.
A step-by-step verification flow that sourcing teams can repeat
Use a repeatable workflow. That matters more than having a perfect template.
| Step | What to verify | Acceptable evidence | Common gap |
|---|---|---|---|
| 1 | Part identity | Drawing number, revision, internal SKU | Declaration covers only a broad family |
| 2 | Material definition | Grade, metallurgical spec, process route | Base metal listed, finish omitted |
| 3 | REACH statement | Current declaration and SVHC statement | Old Candidate List reference |
| 4 | Ancillary materials | Oil, coating, VCI, labels, packaging | Pack materials excluded |
| 5 | Traceability | Lot code from production to shipment | No retained batch record |
| 6 | Change control | Revalidation trigger for chemistry changes | No formal trigger |
| 7 | Record retention | File stored by part and revision | Documents buried in email |

