Does a Detergent Digital Product Passport Replace a Safety Data Sheet?

No. Learn how the EU Detergent DPP differs from a REACH Safety Data Sheet, when an SDS is required and how the Annex VI exception works.

Status: Adopted Detergents Regulation; REACH SDS duties remain separate
Detergent DPP general application date: 23 September 2029
Last verified: 2 September 2026

LinkedIn X Email

Navigate this page

Direct answer
Does every detergent need a Safety Data Sheet?
What is the Detergent DPP for?
What is an SDS for?
What exactly is the Annex VI SDS exception?
When is an SDS still required?
Can the DPP be used as the SDS?
Can the SDS replace the whole Detergent DPP?
What information can overlap?
What about the Detergents ingredients data sheet?
What should manufacturers avoid when structuring product dat
Common mistakes
Practical conclusion
Evidence / legal basis
What we're watching
Sources

Direct answer

No. A Detergent Digital Product Passport does not replace a Safety Data Sheet.

They are different legal information systems serving different jobs.

The Detergents Regulation requires a DPP for a detergent or end-user surfactant before it is placed on the market once the new regime applies. REACH Article 31 separately determines when a Safety Data Sheet, or SDS, must be supplied or provided on request. ¹ ²

There is one important connection between them. Annex VI Part A(h) of Regulation (EU) 2026/405 normally requires the DPP to contain a full list of substances intentionally added in the detergent or surfactant, with the specified treatment of qualifying carry-over preservatives. But that point does not apply to industrial and institutional detergents, or to surfactants, where equivalent information is provided through an SDS under REACH Article 31. ¹

That is a narrow alternative route for one DPP information requirement. It is not a rule saying the SDS replaces the DPP, or the DPP replaces the SDS.

Does every detergent need a Safety Data Sheet?

No.

Whether an SDS is required is determined under REACH, not by the fact that a product happens to be a detergent.

At a high level, REACH Article 31 requires an SDS to be supplied for a substance or mixture in specified circumstances, including where it meets the criteria for classification as hazardous under the CLP Regulation. Article 31 also covers certain other substance cases and creates request-based SDS rights for some mixtures that are not themselves classified as hazardous but contain specified substances above the relevant thresholds. ²

REACH also contains an important general-public rule. Where a hazardous substance or mixture is offered or sold to the general public with sufficient information to allow users to take the necessary protection measures, the SDS need not be supplied to the public unless requested by a downstream user or distributor. ²

ECHA's current SDS guidance summarises the same boundary: hazardous substances or mixtures and certain PBT/vPvB or Candidate List substances are within the SDS regime, while certain non-hazardous mixtures can require an SDS on request. ³

So avoid the shortcut:

"Detergent = SDS"

The correct test is the applicable REACH/CLP SDS rule for that substance or mixture and supply context.

What is the Detergent DPP for?

Regulation (EU) 2026/405 creates a product-model DPP for detergents and end-user surfactants. Article 21 requires the passport to contain at least the data in Annex VI Part A, be accurate, complete and up to date and be made accessible according to the DPP access architecture. ¹

The mandatory Part A dataset includes, among other things:

trade name, unique product identifier and a colour image of the packaging or label
manufacturer and applicable importer/authorised-representative information
manufacturer unique operator identifier
reference to the DPP service provider hosting the backup copy
product traceability identification
a statement that the passport is issued under the manufacturer's sole responsibility
commodity code where applicable
compliance and relevant Union-law references
the intentionally-added-substances information in point (h), subject to its exception
intentionally added micro-organism information where applicable

That is not the structure or purpose of an SDS.

What is an SDS for?

An SDS is a chemical hazard and safe-use communication document governed by REACH.

REACH Annex II describes the SDS as a document that enables users to take necessary measures for protection of human health and workplace safety and protection of the environment. Its standard structure includes 16 sections covering areas such as:

identification
hazards
composition/information on ingredients
first aid
fire-fighting
accidental release
handling and storage
exposure controls and personal protection
physical and chemical properties
stability and reactivity
toxicology
ecology
disposal
transport
regulation
other information

The overlap in words such as "ingredients" or "composition" does not make the documents interchangeable.

What exactly is the Annex VI SDS exception?

The key wording is in Annex VI Part A(h) of the Detergents Regulation.

Point (h) requires a full list of substances intentionally added to the detergent or surfactant, identified as specified by the law, plus qualifying carry-over preservatives.

The Annex then says that the obligation in point (h) does not apply to industrial and institutional detergents, or to surfactants, for which equivalent information is provided by means of an SDS under REACH Article 31. ¹

The logic is:

the DPP still exists
Annex VI Part A still applies
point (h) is the field with the defined exception
an SDS can provide the equivalent substance information for the specified product contexts
the other mandatory DPP information does not disappear
any independent REACH SDS duty also remains a REACH duty

A useful way to say it is:

The SDS exception can remove duplication of one substance-list field. It does not merge the two legal instruments.

When is an SDS still required?

The answer depends on REACH Article 31 and the product's hazard/composition/supply facts.

Situation	SDS position at a high level	DPP consequence
Detergent mixture meets CLP hazardous-classification criteria	SDS supply obligation applies under REACH Article 31, subject to the Article 31 rules including the general-public provision	The Detergent DPP remains a separate obligation when Regulation 2026/405 applies.
Non-hazardous mixture contains specified substances above Article 31(3) thresholds	Recipient may have an SDS right on request	Do not assume an SDS exists automatically. Test the actual Article 31 conditions.
Hazardous detergent sold to the general public with sufficient safe-use information	SDS need not be supplied to the public unless requested by a downstream user or distributor	Consumer-facing DPP duties are not replaced by that rule.
Industrial/institutional detergent with an SDS that provides the equivalent Annex VI(h) information	The SDS can satisfy the narrow Part A(h) alternative route	Do not repeat the Part A(h) substance list solely because it is normally mandatory, but keep all other applicable DPP data.
Surfactant with an SDS that provides the equivalent Annex VI(h) information	Same narrow exception can apply	Again, this does not replace the complete DPP.
Consumer/non-hazardous detergent with no Article 31 SDS trigger	An SDS may not be required	The DPP still applies from the Detergents Regulation's application date if the product is in DPP scope.

This table is deliberately high level. SDS applicability should be assessed against the current REACH and CLP rules for the actual formulation and supply chain.

Can the DPP be used as the SDS?

Not merely because it contains some overlapping information.

An SDS has a prescribed REACH function and structure. A Detergent DPP has a different statutory dataset, identity model, persistence architecture and access model.

If a company chooses to expose an SDS through or alongside the same digital product experience, that is an information-architecture choice. It should not be described as legal substitution unless the relevant law expressly provides for it.

For the Annex VI(h) exception, the legal direction actually runs the other way: a qualifying SDS can prevent the need to repeat a particular DPP substance list.

Can the SDS replace the whole Detergent DPP?

No.

Even where the Annex VI(h) exception applies, the DPP still has mandatory data that an SDS is not designed to replace, including product identity, operator identifiers, DPP service-provider reference, traceability, DPP responsibility statement and the other Annex VI fields. ¹

An SDS is therefore not a fallback version of the passport.

What information can overlap?

There can be overlap, especially around chemical identity and product information.

Information territory	DPP	SDS	Boundary
Product identity	Yes	Yes, in SDS identification	Similar fact can exist in both for different legal jobs.
Manufacturer/supplier identity	Yes	Yes	Keep the governed source consistent, but publish according to each instrument's rules.
Ingredient/substance information	Yes, Annex VI(h) subject to exception	Yes, SDS composition section where applicable	This is the main overlap, but the legal selection rules are different.
Hazard classification	Not a universal Annex VI Part A field as a complete SDS-style hazard section	Core SDS function	Do not copy the SDS hazard section into the mandatory DPP schema by default.
First aid / fire / accidental release / exposure controls	Not part of the minimum Annex VI Part A dataset	Standard SDS sections	Keep in the SDS/safety-document layer unless another rule requires separate publication.
DPP identifiers, backup provider and registry-linked product architecture	Core DPP architecture	Not an SDS function	SDS cannot replace these passport requirements.
Intentionally added micro-organisms	Mandatory DPP data where relevant	Could appear in safety information depending on SDS rules, but not because Annex VI requires it	Treat the DPP rule on its own terms.

What about the Detergents ingredients data sheet?

There is a third information layer that should also remain separate.

Regulation (EU) 2026/405 requires an ingredients data sheet for emergency-health-response purposes in specified cases, including an Article 8(6) route for detergents and end-user surfactants that are mixtures for which there is no obligation to provide information under CLP Article 45. That information is provided to the Member State appointed bodies and is governed separately from the DPP. ¹

So a detergent data architecture may need to support at least:

DPP data
SDS data where REACH requires or provides it
Detergents Regulation ingredients-data-sheet information
physical/digital labelling information
technical documentation and evidence

Those are connected, but they are not the same document.

What should manufacturers avoid when structuring product data?

Avoid `has_sds = true` as a universal detergent default

SDS applicability is conditional. Record why the SDS exists and which legal trigger or request route applies.

Avoid copying every SDS field into the DPP

The DPP minimum dataset comes from Annex VI Part A. Extra information should have a reason and an access decision.

Avoid deleting the Annex VI(h) field from the schema entirely

The exception is conditional. A product outside the industrial/institutional or surfactant exception can still require the point (h) substance list.

Avoid using one "ingredients" object for every legal audience

The DPP substance list, SDS composition section, ingredients data sheet and label can have different inclusion rules, levels of detail, audiences and access conditions.

Keep one governed fact source, but preserve legal views

A strong product-data model can reuse the same verified chemical identity and supplier evidence while generating different legally appropriate outputs. That is better than maintaining contradictory copies or forcing every source field into every publication channel.

Common mistakes

"Every detergent needs an SDS"

No. REACH determines SDS applicability. Hazardous classification is a central trigger, some non-hazardous mixtures create request-based duties and the general-public rule affects when an SDS needs to be supplied.

"The DPP replaces the SDS"

No. The Detergents Regulation preserves a narrow SDS-based alternative for Annex VI(h), which confirms that the two systems can coexist.

"If there is an SDS, the detergent does not need a DPP"

No. The Annex VI(h) exception affects one information requirement, not the passport obligation as a whole.

"The DPP should contain the complete SDS because both are digital"

Not established. Digital delivery does not collapse different legal instruments into one dataset.

Practical conclusion

Design the Detergent DPP and SDS as connected but distinct outputs.

For each product:

determine whether the Detergents Regulation DPP applies
determine separately whether REACH Article 31 requires or enables an SDS
determine whether the narrow Annex VI Part A(h) SDS exception is available
preserve the other mandatory DPP fields even when that exception applies
keep SDS hazard/safe-use information in its own governed legal layer
maintain the ingredients data sheet, labelling and technical evidence as separate layers where applicable

Evidence / legal basis

The Detergent DPP boundary comes primarily from Regulation (EU) 2026/405, especially Articles 8 and 21 and Annexes IV and VI. ¹

SDS scope comes from REACH Regulation (EC) No 1907/2006, especially Article 31 and Annex II. ²

ECHA guidance was used as authoritative explanatory support, not as a substitute for REACH. ³

What we're watching

The future Article 21(10) Detergent DPP implementing act, including detailed carrier, access and update arrangements.
Any amendment to Annex VI before the 23 September 2029 application date.
Any REACH or CLP change that materially alters SDS triggers or composition communication before this resource is integrated.

None of those open implementation points currently changes the answer that the DPP and SDS are separate legal instruments.

Keep exploring

The questions this page usually raises next.

Does this reach your products?

Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.

Check a product How a value is decided

Help someone else make sense of product passports.