Como Solicitar uma FDS em Conformidade com o REACH para Magic Fire Powder e Verificar SVHCs?

Getting a REACH-compliant SDS for Magic Fire Powder sounds simple — until a shipment sits in EU customs waiting for it GHS hazard identification ¹. In our export files at Sunrich, that document decides everything.

To get a REACH-compliant SDS for Magic Fire Powder, request the latest 16-section SDS from the manufacturer, verify it cites Regulation (EC) No 1907/2006, check Section 3 CAS numbers against the ECHA Candidate List, and confirm no SVHC exceeds the 0.1% w/w threshold.

That answer covers the essentials. But the details matter, because "Magic Fire Powder" is a trade name used by many vendors for very different formulations. Let me walk you through the full process, step by step, from the factory side.

What documents should I request from my supplier to confirm REACH compliance for Magic Fire Powder?

A German distributor once asked us for "the REACH certificate" for our color-flame packets. I had to explain gently: REACH doesn't issue a single certificate. It requires a document set.

Request the current 16-section SDS citing REACH Annex II requirements, a written SVHC declaration referencing the ECHA Candidate List, third-party test reports, the full ingredient composition with CAS registration numbers, and Annex XIV and Annex XVII status confirmations — all matched to the exact product code.

The single biggest mistake I see buyers make is accepting a generic PDF labeled "SDS" without checking what is actually inside it. In our seventeen-plus years exporting color-flame products to Germany, France, the Netherlands, and Poland, we have learned that EU importers who ask for the full document package upfront almost never face customs delays. Buyers who accept a one-page "safety statement" often do.

Here is the document set I recommend you request in writing, before you place any order:

Match every document to the exact product

Do not accept an SDS for "colored flame powder" in general. The document must carry the same trade name, article number, and revision date as the product you are buying. At our factory, every Magic Fire batch links back to a specific SDS version and SGS test report. If a supplier cannot make that link, treat it as a warning sign.

Check the revision date

An SDS from 2019 may miss substances added to the Lista de Candidatos da ECHA ³ since then. The list is updated roughly twice a year. Ask when the SDS was last reviewed, and ask whether the supplier monitors Candidate List updates as part of their downstream user obligations ⁴.

How do I check if Magic Fire Powder contains any SVHCs above the safe threshold?

During a factory audit last year, a UK buyer's compliance officer sat down with our SDS and the ECHA database side by side. Watching her work taught me exactly how a professional SVHC check should run.

Open SDS Section 3, list every substance and its CAS number, then search each one on the ECHA Candidate List. If any listed SVHC appears at or above the 0.1% w/w threshold, the supplier must disclose it and provide safe-use information under Article 33.

The check itself is not complicated. But it must be done against the actual formulation, not the product name. Different "Magic Fire" powders on the market use different chemistry — some are metal-salt crystals, others are coated mineral pigments like silicon dioxide laminated with titanium oxide ⁵. Our own color-flame formulations use eco-friendly ingredients precisely because we know EU buyers will run this exact screening.

The five-step screening process

1. Verify identity first. Confirm the trade name, article number, and revision date on the SDS match your product.
2. Extract Section 3 data. The SDS Section 3 composition must list hazardous ingredients with CAS registration numbers and concentration ranges.
3. Cross-reference ECHA. Search each CAS number on the ECHA Candidate List, which is updated bi-annually. This takes minutes per substance.
4. Apply the threshold. Look for explicit wording such as "does not contain a substance in the candidate list of substances of very high concern above 0.1% (w/w)." That sentence is what you want to see.
5. Read Section 15. Regulatory information here should state Candidate List status, Annex XIV authorisation status, and Annex XVII restrictions.

Watch for language that dodges the question

Some SDSs simply say "not classified as hazardous" under Regulamento CLP ⁶ compliance rules. That is a GHS hazard identification statement — it is not an SVHC declaration. A mixture can be non-hazardous under CLP and still contain a Candidate List substance. Also note that some compliant SDSs state a full chemical safety assessment has not been carried out for the product. That is legal, but it tells you the supplier's data has limits, so a written SVHC declaration becomes even more important.

One more technicality worth knowing: when fire powder is sold in sealed packets treated as "articles," the 0.1% w/w calculation basis can shift. Some suppliers calculate concentration against the whole article weight, including packaging, which can mathematically dilute the reported percentage. Ask your supplier to confirm the calculation basis in writing.

Can I get a valid SDS that meets EU import requirements before placing my order?

Trial-order buyers often assume documentation comes after payment. In our sales process, we flip that: the SDS, SGS reports, and SVHC declaration go out with the very first quotation to any EU prospect.

Yes. A reputable manufacturer will provide the current SDS, SVHC declaration, and test reports before you order — free of charge. Under REACH, the SDS must also be supplied in the official language of the EU member state where the product is placed on the market.

A supplier who hesitates to share documentos de conformidade pre-order is telling you something. Producing a compliant SDS costs a serious manufacturer nothing extra — the document already exists if the product has been legally sold in the EU. When we onboard a new distributor in France or the Netherlands, we send the full document pack within one working day of the inquiry, because our buyers treat certification as a hard requirement, not a nice-to-have.

What "valid for EU import" actually means

Validity has several layers. Check each one against this table:

Use the pre-order window wisely

Before money changes hands, you hold maximum leverage. This is the moment to request the SCIP notification number ⁷ if the product qualifies as an article containing an SVHC, since that digital identifier confirms registration in the ECHA database for waste-management transparency. It is also the moment to ask whether the supplier monitors the ECHA Registry of Intentions, so substances heading toward future SVHC listing can be substituted early rather than after a regulatory deadline hits your inventory.

In our experience, first samples should reliably reflect mass-production quality — and the same principle applies to paperwork. The SDS you review pre-order must be the same document that accompanies the container. Ask the supplier to confirm this in writing, and file both together.

What should I do if my supplier can't provide an up-to-date REACH-compliant SDS?

Years ago, we lost a bid to a cheaper competitor — then won the account back six months later when that competitor's missing SVHC declaration stalled the buyer's goods at Rotterdam. That episode shaped how I advise buyers today.

Do not import the product. First, send a formal written request citing REACH Article 31 and the Article 33 communication duty. If the supplier still cannot deliver a current, product-specific SDS within a reasonable deadline, switch to a certified manufacturer that can.

A missing or outdated SDS is not a paperwork inconvenience. It shifts legal exposure onto you. As the EU importer, you inherit downstream user obligations, and your customers gain a "right to know" under Article 33 — any consumer can request SVHC information from you, and you must respond within 45 days, free of charge. If your supplier cannot answer that question, neither can you.

Escalate in a structured way

1. Send a formal written request. Cite REACH Article 31, name the exact product and article number, and set a clear deadline. Keep the email trail.
2. Offer alternatives. If the supplier claims trade-secret protection, remind them that proprietary labels in Section 3 do not exempt disclosure of any SVHC present above the 0.1% w/w threshold. A confidentiality agreement can cover the rest of the formula.
3. Request a bridging declaration. A signed statement confirming no Candidate List, Annex XIV, or Annex XVII substances can hold you over while a full SDS is updated — but only as a temporary measure.
4. Set a hard cutoff. If nothing arrives by your deadline, stop the purchase. No price advantage offsets a customs seizure or a product recall.

Evaluate replacement suppliers on documentation first

When you re-source, invert the usual order: check documents before samples. Here is the comparison framework I suggest:

We built our own export program around that right-hand column, because buyers in the US and Europe told us plainly: consistent documentation is worth more than a few cents saved per packet.

Conclusão

An outdated or missing SDS can freeze your shipment, expose you legally, and damage customer trust. Verify the document set, screen Section 3 against the ECHA Candidate List, and partner only with manufacturers who prove compliance before you pay.

Notas de rodapé

1. Explains the classification system referenced as separate from SVHC disclosure requirements. ↩︎

2. Official EU regulation text establishing the legal SDS supply obligation cited throughout. ↩︎

3. Official ECHA database buyers must search to verify SVHC status by CAS number. ↩︎

4. Official EU business portal detailing REACH compliance duties for downstream users. ↩︎

5. Background reference for the mineral pigment compound mentioned as a coating ingredient. ↩︎

6. ECHA's official explainer on the classification rules distinguished from SVHC declarations here. ↩︎

7. ECHA's official database page for the article-based SVHC notification system mentioned. ↩︎