Material Compliance guide
How Do We Build a REACH SVHC Information File for Cosmetic Packaging?
A single broad declaration can leave a beauty pack exposed when its coating, adhesive, pump, label, and insert come from different component chains.
We build a component-level file for the exact cosmetic pack. We request supplier information, record each article and version, and route threshold or role questions to qualified compliance owners. We do not treat a generic statement as proof for a changed component.
We use three questions to convert a complex packaging bill of materials into a practical REACH information trail without claiming legal conclusions for a buyer.
Which Cosmetic-Pack Articles Belong in the File?
A buyer may call the package one SKU, but a carton, pump, cap, adhesive, label, and insert can each arrive as separate articles or assemblies.
We create a bill of materials for the finished consumer unit and identify each supplied article or component. We record material, supplier, version, weight where available, and how the item joins the pack. We then ask the compliance owner how REACH duties apply to the business role and market route.
We make the physical pack visible to procurement
We begin with the actual pack on a table. We photograph the carton, primary container, pump, cap, label, decorative sleeve, insert, protective tray, adhesive strip, and any applied finish sample. We give every item a unique component ID. We record who supplies it, the supplier specification code, the production version, and the relationship to the final SKU. A carton is not a complete description if it includes a coated surface, a laminated window, or a separate label. A pump is not a single material just because it arrives assembled. We do not use the map to decide whether every small piece creates the same legal duty. We use it to prevent the more common failure: asking one supplier to answer for a component it does not control. ECHA explains that REACH obligations for substances in articles can include supply-chain communication and that role matters. The business importing or supplying the article needs the proper legal assessment.
We also record changes as changes. A supplier may alter a coating, adhesive, pigment, resin grade, spring, or insert without changing the consumer-facing product name. That does not automatically prove a new obligation, but it does mean the previous declaration needs a relevance check. We ask the supplier to identify the component and version covered by its statement. We retain the issue date, market scope, contact, and any exclusions. We do not ask for a vague promise that the whole package is compliant with every law. That language hides the facts a responsible assessor needs. A current Candidate List change can create immediate questions for articles, so we keep the source date and the reviewed list version visible. This file is a procurement control, not a substitute for legal counsel, laboratory analysis, or the formal duties of the EU actor placing an article on the market. It gives that responsible person a reliable starting point.
| Pack article | What we record | Why it matters |
|---|---|---|
| Carton and finish | Board, coating, supplier and revision | A surface treatment can change |
| Bottle and closure | Assembly, material and supplier code | Components may have separate chains |
| Label and adhesive | Face stock, adhesive and placement | Applied parts are easy to omit |
| Insert or sleeve | Material, function and market SKU | Launch extras can change the unit |
How Do We Request Supplier Information That Stays Usable?
A declaration without a part number, scope, date, or responsible contact cannot tell a future buyer whether it covers the pump or coating now in production.
We request information against each component ID and supplier version. We keep the response, source date, Candidate List reference, scope, and exclusions together. We escalate any reported SVHC, missing scope, or threshold question to the responsible compliance owner instead of editing the answer into a marketing claim.
We ask for traceable answers, not reassuring phrases
We use one short supplier request template. It names the customer component ID, supplier part number, material description, production revision, intended market, and quantity context where the compliance owner requests it. It asks the supplier to state what its document covers, the date, the Candidate List reference used, and the authorised contact. We do not ask a converter to invent information about a bought-in pump or bottle. We ask that supplier separately or ask the converter to coordinate an identifiable response. ECHA states that suppliers of articles containing a Candidate List substance above 0.1 percent weight by weight must provide sufficient information to allow safe use to recipients, with the substance name as a minimum. The threshold and article definition need careful application. We therefore keep any calculation or legal interpretation with the appropriate specialist instead of changing a supplier’s answer into a simple yes or no.
We review completeness before we celebrate a file. A blank statement is not evidence. A statement that names a product family may be useful only if it clearly covers the exact part. A certificate can be authentic and still be outside its claimed material or date range. We compare the supplier’s covered part number with the purchase order and approved sample. We log an expiry or review date so procurement knows when a new declaration is needed after a formula, coating, or component change. The file should be easy to audit: component ID, document link, received date, scope, owner, and next action. A Reddit supply-chain discussion about PPWR procurement questionnaires describes requests for adhesive and REACH declarations. That reflects a current industry concern about documentation burden, not an authority on legal obligations. We use it as a reminder to make supplier requests specific and timely. ECHA, the regulatory text, and a qualified compliance owner remain the sources for the actual decision.
| Request field | Good evidence | Weak evidence |
|---|---|---|
| Component identity | Part number and revision | General product family |
| Scope | Material and article covered | Unqualified compliance promise |
| Date | Issue date and list reference | Undated PDF |
| Owner | Named authorised contact | No escalation route |
What Information Path Should We Keep After Supply?
A good procurement folder still fails when no one can answer a distributor or consumer question after the pack has changed suppliers or entered a new market.
We retain the component map, supplier evidence, version history, and responsible owner with the SKU release record. We define an intake path for downstream questions. We treat consumer requests and SCIP or other reporting questions as role-specific compliance work, not as a carton-print decision.
We keep the evidence connected to the released SKU
We put the file beside the released specification, not in a personal inbox. The record names the finished SKU, market, component IDs, supplier documents, change dates, and the person who owns the next review. A buyer can then see whether a request relates to the exact unit that shipped. ECHA says consumers can request information about Candidate List substances in articles and that suppliers must respond within 45 days free of charge when the Article 33 condition applies. This is not a reason to put unverified chemical statements on a carton. It is a reason to retain the technical evidence and the response route. We give customer service a clear escalation contact rather than asking them to interpret a supplier declaration. We also separate a material statement from an environmental or safety marketing claim. Those claims need their own substantiation and review.
We add a change trigger to every release. A new pump supplier, adhesive, coating, material grade, label, insert, or EU import route triggers a file review. The team checks whether the old evidence still covers the changed article. When a party that supplies articles in the EU meets SCIP conditions, ECHA explains that information on Candidate List substances above 0.1 percent weight by weight may require a SCIP submission. The duty depends on the actor and exact circumstances. We do not state that every cosmetics brand or packaging converter must file. We route that question to the actual importer, producer, or supplier with its adviser. This careful boundary helps a buyer use the packaging file without turning it into unsupported legal advice. The practical outcome is simple: a released cosmetic pack has identifiable components, current supplier evidence, and a responsible person who can review a question when the system changes.
| Record | Operational use | Review trigger |
|---|---|---|
| Component map | Find the relevant supplied article | Pack configuration changes |
| Supplier evidence | Support a recipient question | Part or list version changes |
| Release owner | Route a role-specific decision | New EU supply-chain actor |
| Consumer request path | Escalate within controlled timing | Question names an SVHC or component |
Sources and Related Reading
- 1 Folding cosmetic cartons. Internal route for carton materials, finishes, and component planning.
- 2 Cosmetic packaging manufacturing. Internal route for controlled specifications and production release.
- 3 Contact Finer Pack. Internal route for a component-level packaging brief.
- 4 ECHA Article 33 supply-chain communication. Primary ECHA guidance on information for recipients and consumers.
- 5 ECHA SCIP database. Primary ECHA explanation of SCIP information duties for qualifying articles.
- 6 Reddit packaging documentation discussion. Attributed community observation about supplier declarations; not REACH legal guidance.
Conclusion
We keep REACH information useful by mapping every cosmetic-pack article, retaining component-specific supplier evidence, and reviewing the file whenever the released system changes.