REACH Compliance Wholesale Catalogue Guide

EU retailers buying beauty, home goods or electronics rarely want a lecture on chemical law. They want the right REACH file next to the SKU before they raise a PO. A REACH compliance wholesale catalogue is how wholesale brands deliver that: SVHC statements, Safety Data Sheet (SDS) links, article communication notes and, where relevant, SCIP references living beside price, MOQ and stock in the B2B storefront.

This guide explains what buyers typically request, which products draw extra scrutiny, and how to attach documents so distributors stop chasing email. It is operational guidance for founders, sales, ops and compliance owners—not legal advice. Confirm duties with your counsel or national REACH helpdesk.

What is REACH compliance in a wholesale catalogue?

REACH compliance in a wholesale catalogue is the practice of publishing the chemical-safety and article-communication documents your EU customers need—linked or attached per product—so ordering and due diligence happen in one place. REACH (Regulation (EC) No 1907/2006) is the EU framework governing registration, evaluation, authorisation and restriction of chemicals; in B2B wholesale the day-to-day work is supply-chain communication, not running a registration dossier yourself.^[1]

Supply chain documents flowing toward a product shelf

In catalogue terms that usually means:

• A short REACH / SVHC declaration or statement per article or product family
• SDS access for substances and mixtures you place on the market, where SDS duties apply^[5]
• Clear notes when a product is an article (finished goods) versus a substance or mixture
• Links or identifiers related to the SCIP database when your process requires them for articles containing substances of very high concern (SVHCs)^[4]
• Version dates and a named internal owner so files stay current

ECHA (the European Chemicals Agency) publishes the SVHC Candidate List and guidance on supply-chain communication duties.^[2][3] Article 33 of REACH sets a communication duty along the supply chain when an article contains a Candidate List SVHC above 0.1% weight by weight (w/w).^[3] Your catalogue is simply the channel retailers already use to order—so it is a practical place to fulfil “please send REACH docs” without a separate portal or shared drive.

What REACH data do beauty, home and electronics retailers typically request?

Requests vary by category, retailer size and their own customer audits. Patterns repeat across beauty and cosmetics, home and design, and electronics.

Beauty and cosmetics

Buyers often ask for:

• SDS for professional or bulk chemical products and some intermediates
• Declarations covering restricted substances relevant to cosmetics law and REACH overlap
• Confirmation that listed SVHCs are not present above applicable thresholds in packaging components (pumps, caps, secondary packs) treated as articles
• Batch or version identity so quality teams can match paperwork to goods received

Finished cosmetic products sit under sector rules as well as chemical frameworks; still, packaging, solvents and ancillary chemicals drive many wholesale REACH questions. Brands in wholesale for health & beauty see the same pattern: retailers want files before the first order, then updates when formulations or packs change.

Home and design goods

Furniture, textiles, candles, cleaning-related goods and décor often trigger:

• Article 33-style SVHC communication for components (metals, plastics, coatings, adhesives)
• SDS where you supply mixtures (finishes, cleaners, fragranced refills)
• Material declarations for high-touch parts (handles, laminates, foam)

Electronics and components

Electronics buyers commonly request:

• SVHC statements for articles and complex objects
• Evidence aligned with their SCIP or article-tracking process when SVHCs are present in scope^[4]
• SDS for chemical consumables, pastes or kits sold alongside hardware
• Clarity on spare parts versus full devices (each may need its own statement)

Across all three, the catalogue should answer: What is this SKU under REACH (substance, mixture, article)? Which file applies? When was it last reviewed?

Which products and materials trigger extra REACH scrutiny?

Extra scrutiny tends to follow materials and use context, not marketing category alone.

Higher attention often falls on:

• Plastics, rubbers, foams and recycled polymers
• Coatings, inks, adhesives and surface treatments
• Metal alloys and plated parts
• Textiles with complex finishes
• Electrical and electronic articles with many sub-components
• Professional chemical products sold as mixtures

Complex objects (many components) need a disciplined bill-of-materials approach: one weak supplier declaration can block a whole SKU. Spare parts, refill packs and “kit” SKUs should not inherit a parent declaration blindly—link the file that matches what the retailer actually receives.

Layered materials inside a simplified product cross-section

How do you attach REACH statements and SDS links to B2B catalogue products?

Treat compliance assets like any other product attribute in your PIM for wholesale product data: mastered once, published many times.

Practical attachment pattern:

1. Classify the SKU — substance, mixture or article (or a kit that mixes types).
2. Choose the asset type — full SDS (PDF) where required, short SVHC / Article 33 statement, SCIP-related reference or “no SVHC above threshold” declaration where that is your assessed position.
3. Store the master file in controlled storage (DAM, QMS or PIM), with version, language and effective date.
4. Publish a SKU-level link or attachment on the B2B catalogue product page—visible to approved retailers only if the file is sensitive.
5. Add a one-line catalogue note — e.g. “REACH article statement (EN), reviewed [month year]” so buyers see status without opening every PDF.
6. Map variants carefully — same formula, different pack component may need a different article statement.

A branded distributor portal works well here: the orderable product, the declaration and the SDS sit on one screen. Brandgate is one such storefront where those files can live next to wholesale products so approved retailers download what they need during assortment or reordering—not after a week of inbox follow-up.

Keep access control simple. Many brands show “document available” to all logged-in trade customers and reserve heavier technical packs for roles that need them.

Where should brands store master REACH files versus SKU-level links?

Master files belong in a system of record with ownership, version history and retention—PIM, QMS or a controlled document library. That is where you replace a superseding SDS, record the Candidate List review date and archive withdrawn versions.

SKU-level links belong in the wholesale catalogue / distributor portal. The catalogue should not be the only copy of the PDF; it should point at the current approved version. If a retailer downloads a statement with an order confirmation pack, that snapshot may still matter for their audit trail—so prefer immutable URLs or clearly versioned filenames.

Governance tips:

• One internal owner per product family (often quality or regulatory, with ops as publisher)
• Review cadence tied to Candidate List updates and to your own BOM or supplier changes—not only to an annual calendar
• Language strategy for EU trade (at least the languages your key retailers require for SDS where SDS rules apply)
• Same SKU codes in PIM, ERP and catalogue so links do not drift after a renumbering

Central archive connected to many product cards

What is a simple request-to-fulfil workflow for REACH documents?

When a retailer asks for something missing, avoid ad-hoc email threads as the only process.

A lightweight workflow:

1. Capture the request — retailer, SKU, document type (SDS, SVHC statement, SCIP-related info), deadline.
2. Triage — is the master on file? Is the SKU classified? Is a supplier declaration still valid?
3. Fulfil or escalate — attach existing file; or request update from supplier; or mark SKU “documentation pending” so sales does not over-promise.
4. Publish — link on the catalogue product, note version date.
5. Notify — short message to the retailer with deep link to the SKU, not another PDF blob in email.
6. Log — who approved the file and when; useful if you later run a wholesale product recall process in the EU.

Self-serve catalogue links remove most repeat asks. The workflow still matters for new lines, supplier changes and Candidate List updates.

How does REACH data differ from allergens, EUDR and packing documents?

Compliance paperwork multiplies in EU wholesale. Keep types separate so the wrong team is not “owning” the wrong file.

Shared portal, different attributes, different owners. Do not bury SDS inside a packing-slip PDF or mix SVHC text into an allergen field—retailer systems and auditors expect clean separation.

Getting the catalogue ready without boiling the ocean

Prioritise SKUs that are live in the EU assortment, then new launches, then long-tail spares. Start with a consistent statement template, honest classification (substance vs mixture vs article), and working links. Add SCIP-oriented fields only where your process and product scope require them.

Operationally, pair regulatory ownership with catalogue publishing rights. Sales should know where to point buyers; they should not be editing legal wording in a side spreadsheet. When files change, the same PIM-to-catalogue path that updates images and GTINs should refresh compliance links.

If your retailers still collect REACH packs by email, move the files next to the products they already order. A branded B2B catalogue turns a recurring chase into a download. Book a demo to see how that storefront workflow fits Nordic and wider EU wholesale teams.