Can a single Declaration of Conformity cover multiple product models in the same family?

A single Declaration of Conformity (DoC) can cover multiple product models in the same family when the models share the same applicable EU legislation and standards, and the differences between variants do not affect compliance. The DoC must still clearly identify every model it covers and remain supported by matching technical documentation.

In practice, the deciding factor is not marketing similarity but whether each model variant stays within the same conformity assessment boundaries, including safety-critical design, materials, and intended use. If a change could alter compliance, it usually needs its own evaluation and sometimes a separate DoC.

The questions below explain when a family DoC works, what must match across models, how to list variants correctly, and the most common product family compliance mistakes.

When can one Declaration of Conformity cover multiple models?

One Declaration of Conformity (DoC) can cover multiple models when they are part of a defined product family and each model meets the same applicable EU requirements under the same conformity assessment approach. The models must be sufficiently similar that testing, risk evaluation, and technical documentation remain valid for every listed variant.

This is most common when a manufacturer releases a base product with minor, non-safety-critical variations such as color, cosmetic finish, or packaging changes. It can also work when several model numbers share the same core design and components and differ only in options that do not change the applicable requirements.

Before using one DoC for multiple models, confirm all of the following:

The same EU legislation applies to every model in the family, and no variant triggers additional rules.
The same harmonized standards or other technical specifications were used to demonstrate conformity for all variants.
Any testing or analysis performed is representative of the worst-case configuration, or you have justification showing equivalence across variants.
The technical documentation set can clearly map each model variant to the evidence that supports it.

Also separate DoC logic from GPSR obligations. The General Product Safety Regulation (EU) 2023/988 (GPSR) is about placing safe consumer products on the EU market and maintaining the information and processes that support safety. A DoC is tied to specific EU harmonization legislation where a DoC is required, not to GPSR itself.

What must be identical across models to share a Declaration of Conformity?

To share a Declaration of Conformity, models must match on the compliance-relevant characteristics that determine which EU requirements apply and whether the conformity assessment evidence remains valid. That typically includes intended use, safety-critical design features, key materials, and any components that affect performance, emissions, or protection against hazards.

Think in terms of what could change the risk profile or the applicable legal framework. If a variant changes how the product is used, who uses it, or what hazards it presents, it often breaks the product family compliance logic.

Intended purpose and reasonably foreseeable use must remain the same across variants.
Core design and safety functions should be unchanged, including protective measures and control logic where relevant.
Critical components and materials must be the same or demonstrably equivalent, especially where they affect safety, durability, or chemical exposure.
Ratings and performance limits that influence compliance must stay within the validated range for the family.
Applicable standards and test methods must remain appropriate for every model variant.

If a change introduces a new hazard or increases an existing one, you may need additional testing, an updated risk assessment, and potentially a separate DoC. The same principle applies when a variant adds a feature that triggers additional requirements under EU conformity assessment rules.

Keep in mind that technical documentation should show the family structure clearly. Market surveillance authorities may ask for it, and you should be able to demonstrate why one DoC legitimately covers each model variant.

How should model numbers and variants be listed on a Declaration of Conformity?

Model numbers and variants should be listed on a Declaration of Conformity in a way that uniquely identifies every covered product and prevents ambiguity for authorities, marketplaces, and customers. The DoC should include the base model identifier and a complete, readable list of all included model variants, or a clearly defined coding rule that covers them.

Good listing practices reduce the risk that a platform or authority treats a variant as undocumented. They also make your technical documentation easier to match to the DoC.

List each model number explicitly when the family is small, including suffixes that represent variants.
Use a structured variant matrix in the supporting documentation, and reference it on the DoC only if the reference is unambiguous and controlled.
Define any coding logic if you use ranges or patterns, for example what each character means and which values are included.
Align identifiers across documents so the model name on labels, instructions, test reports, and the DoC all match.
Version control the DoC so updates to model variants or standards are traceable.

Avoid vague phrases such as “all models” or “all variants” without a defined scope. If an authority requests documentation under the Market Surveillance Regulation (EU) 2019/1020 (MSR), unclear identification can slow down your response and create unnecessary scrutiny.

What are common mistakes when using one DoC for a product family?

The most common mistakes with a product family DoC are treating cosmetic similarity as compliance equivalence, failing to list model variants clearly, and relying on technical documentation that does not actually cover every configuration. These errors can lead to marketplace blocks, authority questions, and gaps between what the DoC claims and what evidence supports.

Watch for these frequent issues:

Including variants that trigger different requirements such as changes in intended use, ratings, or added functions that bring in additional standards.
Assuming one test report covers all variants without documenting worst-case selection or equivalence justification.
Mismatched identifiers where the DoC lists one model name but labels, listings, or manuals use another.
Outdated references such as old standards, old manufacturer details, or a DoC that does not reflect current production.
Incomplete technical documentation mapping where it is unclear which drawings, bills of materials, and test evidence apply to which model variants.
Confusing roles and responsibilities in EU market access, especially when an EU Responsible Person is required but an authorized representative is optional depending on the legislation.

Also avoid process gaps after placing products on the market. Under the MSR, the Responsible Person role is held by an economic operator and must be able to provide information and documentation to authorities, and must inform the manufacturer when there is a risk. If a product family DoC is used, the supporting files must stay organized so each variant can be defended quickly if questions arise after an accident report or a marketplace compliance check.

How EARP helps with Declaration of Conformity management for product families

We help non-EU manufacturers and online sellers keep product family compliance defensible by checking whether one Declaration of Conformity (DoC) can legitimately cover multiple model variants and by making sure the supporting technical documentation is complete and retrievable for each model. Our support is practical and documentation-focused, including:

Reviewing your product family structure to confirm which variants can share one DoC and which need separate conformity assessment evidence
Verifying that model variants are identified consistently across labels, listings, manuals, and technical files
Setting up a clear documentation package so you can respond quickly if a marketplace or authority requests information
Providing EU Responsible Person and EU Authorized Representative services designed for ongoing compliance continuity

To discuss your product models and the cleanest way to document them for EU market access, visit our services or send details through our contact form.