What Is a Declaration of Conformity? (And Why You Can’t Use Your Supplier’s)

If you are new to selling into Europe, the term declaration of conformity EU can sound more complicated than it really is. It is not a secret certificate. It is not something Brussels mails to you. And it is definitely not just a random PDF your supplier sends over at 11:48 pm.

A Declaration of Conformity, usually shortened to DoC, is a legal statement saying: this product meets the EU rules that apply to it, and the company signing this document takes responsibility for that claim.

That last part is what people miss. A DoC is not just about the product. It is about who is standing behind it. If you are the one placing the product on the EU market under your own company or brand, your supplier’s paperwork usually does not cover your legal role.

This article explains what a declaration of conformity is, what it must contain, when self-declaration is enough, when you need a Notified Body, and why using your supplier’s document can leave you exposed.

What is a declaration of conformity, in plain English?

A DoC is the formal document that connects your product, the rules that apply to it, and the legal entity taking responsibility.

Think of it as the final written statement that says: we checked the product against the right EU laws, we have the evidence, and we are prepared to stand behind it if anyone asks questions.

It exists because the CE marking system is mostly based on manufacturer responsibility. For many product categories, there is no central EU office issuing you a “CE certificate.” You identify the applicable rules, gather the evidence, complete the conformity assessment, and then issue and sign the declaration yourself.

That is why a DoC matters so much. It shows which laws, which company, and which evidence trail.

Who must issue the DoC?

This is where most confusion starts.

In simple terms, the DoC must be issued by the party legally responsible for the product’s compliance. In many cases that is the manufacturer. But for ecommerce sellers and importers, the important question is: who counts as the manufacturer in EU law for this product?

If a Chinese factory makes a product and sells it under its own brand into Europe, that factory is normally the manufacturer and should issue the DoC.

If the factory makes the product for you and you sell it under your own name or brand, then for CE purposes you are usually treated as the manufacturer. That means the declaration needs to be in your company’s name, not your supplier’s.

If you are an EU importer bringing in a third-country product for EU sale, you also have obligations to verify that the product complies and that the right documentation exists.

So the short version is this:

• If you sell under the factory’s brand, the factory’s DoC may be the main declaration.
• If you sell under your brand, the factory’s DoC usually does not cover you.
• If you are the EU importer, you cannot just shrug and say “my supplier handled compliance.”

That is why “my supplier sent me a CE certificate” is one of the most common and most expensive mistakes sellers make.

Why your supplier’s DoC usually doesn’t protect you

A DoC is tied to a legal entity. That is the whole point.

If your supplier’s declaration says the manufacturer is Shenzhen XYZ Trading Co., Ltd., and your Amazon store, packaging, invoice, and listing all show YourBrand GmbH or YourBrand Ltd, those are not the same legal person. The document does not magically transfer responsibility to you.

Here is the practical example. A factory makes a desk lamp and has EMC and safety test reports. Then you put your own brand on the lamp, import it into Germany, and sell it across Amazon EU. The factory’s declaration may show that their version of the lamp was assessed under their name. But the product being placed on the EU market under your brand needs a DoC that points back to your legal entity.

The supplier’s paperwork is still useful. Their test reports, product specs, bill of materials, and existing compliance documents can help you build your own file.

But using their DoC as if it were yours is like driving around with someone else’s insurance document and hoping nobody notices the name mismatch.

What a DoC must contain: the 9 required parts

If you are searching for an EU declaration of conformity template, this is the part that matters. The exact layout can vary a little by directive, but for most CE-marked products the standard model comes down to nine required parts.

1. Product model or identification details. This is the type, model, batch, or serial number that ties the declaration to a specific product.
2. Name and address of the manufacturer or authorised representative. This must identify the legal entity taking responsibility.
3. A sole responsibility statement. In plain terms: this declaration is issued under the sole responsibility of the manufacturer.
4. Description or identification of the product. Enough detail to allow traceability. For some products, an image may also be used.
5. The relevant EU legislation. This is where you list the directives or regulations the product complies with.
6. The standards or technical specifications used. Usually the relevant harmonised EN standards, and ideally the version or date where relevant.
7. Notified Body details, if applicable. Only needed when a Notified Body actually took part in the conformity assessment.
8. Any additional information. This can include extra references that help explain the basis of conformity.
9. Signature block. Place and date of issue, name of the signatory, function or job title, and signature.

That is the skeleton. In real life, a good DoC often also includes test report references, especially when you want the document to survive real scrutiny.

Strictly speaking, the legal model often points to the legislation and standards rather than demanding test report numbers on the face of the declaration. But if you leave out all evidence references, you make it much harder to show where your compliance claim came from.

What “self-declaration” actually means

Self-declaration does not mean guessing. It does not mean filling out a template with confidence and moving on.

It means that for many product categories, the law allows the manufacturer to carry out the conformity assessment without hiring a Notified Body. You identify the applicable rules, assess the product, collect the technical documentation, and issue the DoC yourself.

This is normal for a lot of everyday products. Many standard electronics, household items, simple electrical products, and general consumer goods follow this route.

So when people ask, “Do I need an outside lab or an EU consultant to issue my DoC?” the honest answer is: not always. Often you need good evidence, not a middleman.

That evidence may include supplier test reports, product specifications, component details, risk analysis, harmonised standards, labels, instructions, and technical documentation showing the product actually matches the declared version.

Common mistakes that make a DoC weak or useless

Most bad DoCs fail in very boring ways. Not dramatic fraud. Just lazy paperwork.

1. Using the supplier’s declaration as if it were yours

This is the biggest one. Wrong company name, wrong responsible entity, wrong legal effect.

2. Listing the wrong directives

If the product has Bluetooth or Wi-Fi, the Radio Equipment Directive may apply. If it is an electrical product, EMC and possibly Low Voltage may apply. If it is sold for children, toy rules may apply. Get the legislation wrong and the whole declaration becomes shaky.

3. No real product identification

“LED lamp” is not enough. You need model-level traceability. If the declaration cannot clearly link to the actual item being sold, it is weak.

4. No standards or no useful evidence trail

A DoC that says “complies with EU requirements” without naming the standards or technical basis is not helpful. Even when test report references are not written into the legal template as a separate field, including them or aligning them with the technical file makes your documentation much stronger.

5. Copy-paste templates that do not match the product

This is common with supplier packs. You see the wrong product category, outdated directive numbers, or standards that clearly belong to a different item.

6. Forgetting updates

Change the PCB, radio module, power supply, materials, or even the legal entity details, and the declaration may need updating too.

When do you actually need a Notified Body?

For most sellers reading this, probably not. But there are product categories where third-party conformity assessment is required or may be required depending on the route used. This is where a Notified Body comes in.

Common examples include:

• Medical devices
• Personal protective equipment (PPE), especially higher-risk categories
• Pressure equipment

There are also other categories and edge cases where third-party involvement can be required depending on the legislation and the conformity route. The safe rule is simple: do not assume. Check the directive or regulation that applies to your exact product.

If a Notified Body is involved, its details should appear in the declaration where required. If no Notified Body was involved, do not invent one or paste a random lab name.

So what should you actually do?

If you are importing or private-labeling a product for EU sale, the practical workflow is usually:

1. Get the real technical evidence from the supplier, not just a pretty certificate.
2. Work out which EU directives and regulations apply to the actual product you are selling.
3. Match the correct harmonised standards and check that the reports relate to your product version.
4. Issue the declaration in the name of the legal entity responsible for placing that product on the EU market.
5. Keep the file updated and retain it for the required period.

That is what DoC requirements look like in the real world. Just precise.

If you need a faster way to build a clean declaration, you can use getmark.eu. It helps map the relevant EU directives and generate a ready-to-use DoC, especially if you already have the test reports and just need to put the document together properly.