REACH compliance declaration age: when it is too old to rely on
Summary
No fixed age applies: EU REACH sets no expiry, and a compliance declaration is too old once ECHA updates the Candidate List after its stated list date. The Article 33 duty follows that list and what the product contains, so a formulation or supply chain change also calls for a new declaration.
REACH Article 33 requires suppliers of an article containing a Candidate List substance above 0.1% w/w to give the recipient enough information for safe use, at least the substance name (REACH Article 33, 2006).
A consumer who asks must receive that information free of charge within 45 days (REACH Article 33, paragraph 2, 2006).
On 4 February 2026, ECHA added two entries, taking the Candidate List from 251 to 253 entries (SGS, 2026).
The 0.1% w/w threshold applies to each component article of an assembled product, not to the whole product (CJEU C-106/14, 2015).
When is a REACH compliance declaration still valid, and when not?
A REACH compliance declaration stays valid only while two things hold: the Candidate List date it states matches the latest ECHA update, and the product it describes has not changed.
The European Chemicals Agency (ECHA) must "publish and update the list referred to in paragraph 1 on its website without delay after a decision on inclusion of a substance has been taken" (REACH Article 59, paragraph 10, 2006). That list, the Candidate List of substances of very high concern, moves on decision dates, not on a fixed calendar, so a declaration has no shelf life in months. You measure its age against the updates ECHA has published since its list date, the Candidate List update the declaration says it was checked against.
Use the table below to judge a declaration you hold or are about to send. It also marks the cases where this verdict does not apply.
Condition | Verdict | Why |
|---|---|---|
States a Candidate List date equal to the latest ECHA update; product unchanged | Valid | Article 33 duty refers to the Article 59(1) list |
States a list date before the latest ECHA update | Reconfirm against the new entries, then reissue | New entries can create new Article 33 duties |
States no list date, only a signature date | Reissue | Cannot be checked against later updates |
Formulation, raw material source or component supplier changed | Reissue | SVHC content can change; 0.1% w/w applies per component article (CJEU C-106/14, 2015) |
Product is a substance or mixture, not an article | Use the SDS route instead | REACH Article 31 covers substances and mixtures; a non-classified mixture gets an SDS on request |
Product placed on the market under UK REACH | Not judged here | Separate UK REACH Candidate List (HSE) |
The second row is the one that decides: a declaration signed after the latest update can still be out of date if the list date it names is older.
Which Candidate List date should a REACH compliance declaration state?
A REACH compliance declaration should state two things: the date of the ECHA Candidate List update it was checked against, and the number of entries the list held on that date.
On 4 February 2026, ECHA added two substances, taking the list from 251 to 253 entries (SGS, 2026). A published supplier declaration signed on 14 April 2026 states that "The Candidate List, as of February 2026, now comprises 253 substances." (Remora Electrical, 2026). A customer can check that wording against later updates. A signature date alone cannot be checked that way, because it does not show which list the supplier checked.
The same declaration commits to "monitoring updates to the Candidate List" but gives no rule for when it stops being valid (Remora Electrical, 2026). What makes the document checkable, then, appears to be the list date in its body, not a stated validity period.
Keep only the newest version of each declaration in one place, as with a single source of truth for product datasheets, so you do not send a customer a superseded copy.
When does a formulation or supply chain change make a REACH declaration invalid?
A formulation or supply chain change makes a REACH declaration invalid when it could bring a Candidate List substance into the product above 0.1% w/w. For articles, the Court of Justice of the European Union ruled that Article 33 applies where "one or more constituent articles" contain a substance of very high concern (SVHC) "in a concentration above 0.1% weight by weight of that article" (CJEU C-106/14, 2015). The threshold is measured against each component, not against the assembled product. A new component supplier, a new coating or new packaging can therefore change the answer even when the finished product looks the same.
Article 33 information is limited to what is "available to the supplier" (REACH Article 33, 2006). Your declaration therefore rests on the declarations your own suppliers give you, and when an upstream supplier changes, the chain behind your declaration changes too.
Substances and mixtures follow a different route. For them the safety data sheet (SDS) carries this duty: suppliers must update it "without delay" when new hazard information becomes available (REACH Article 31, paragraph 9, 2006).
When must you send customers a new REACH declaration?
Send customers a new REACH declaration in three cases: after each Candidate List update they rely on, after any product or supply chain change, and whenever a customer asks for a current statement.
If an article you supply contains a newly listed substance above 0.1% w/w, Article 33(1) requires you to give the recipient enough information for safe use, at least the substance name (REACH Article 33, 2006). A consumer who asks must receive it free of charge within 45 days (REACH Article 33, paragraph 2, 2006).
Producers and importers carry a separate duty as well: they must notify ECHA when a listed substance is in their articles above 0.1% w/w and over one tonne per year (REACH Article 7, paragraph 2, 2006), and that duty applies six months after the substance is listed (REACH Article 7, paragraph 7, 2006).
If a newly listed substance may be present and only testing can settle it, ask a regulatory specialist. In Lubinpla, you can keep each declaration in the data room under the certificate tag and share it with customers; the data room has no revision date field, so put the Candidate List date in the file name.
Frequently asked questions
Does a REACH declaration need reissuing after every Candidate List update?
REACH does not require it, but every update needs a check against the new entries. If none of the new substances is present above the 0.1% w/w threshold of REACH Article 33 (REACH Article 33, 2006), reissuing with the new list date shows the customer that the check was made.
What happens if you send customers an outdated REACH declaration?
An outdated declaration does not change the legal duty. Article 33 applies when the article contains a listed substance above 0.1% w/w, whatever an older declaration says (REACH Article 33, 2006).
Does a REACH compliance declaration cover mixtures?
No. Article 33 covers articles only. For substances and mixtures, the SDS carries the information: a hazardous substance or mixture needs one, and a non-classified mixture containing a Candidate List substance at 0.1% or more by weight needs one when the recipient asks (REACH Article 31, paragraphs 1 and 3, 2006).