Declaration of Conformity Examples: What a Valid DoC Actually Looks Like

Declaration of Conformity examples are worked samples of the signed legal statement a manufacturer issues to declare that a product meets every applicable EU requirement. In plain terms, a Declaration of Conformity (DoC) is a one-page undertaking but the examples below show why the fields on that page are only the visible tip of the obligation.

A Declaration of Conformity example is a short document usually one page that follows the Annex III model of Decision No 768/2008/EC (for CE-marked products) or a sector-specific model such as Annex VIII of the PPWR (for packaging). Every valid example contains the same core fields: a unique product identification, the manufacturer’s name and address, the exact “sole responsibility” statement, the object of the declaration, a conformity statement listing each Union act, the dated harmonised standards used, any notified body, additional sector information, and a signature with place and date. The example teaches you the format; the technical file behind each line is what makes the declaration true.

Key takeaways

• Most Declaration of Conformity examples share the same nine-field skeleton the Annex III model because every sectoral act incorporates it.
• PPWR packaging DoCs use the Annex VIII model and become mandatory for packaging placed on the EU market from 12 August 2026.
• A DoC is issued per product type, not per shipment and it is only as valid as the technical file that evidences every claim on it.
• Copying a template gets the fields right and the evidence wrong the fastest route to a formally non-compliant declaration.

Declaration of Conformity examples start with the Annex III model

Most teams searching for Declaration of Conformity examples are not missing the concept they are trying to confirm that their own document has the right fields in the right order. The pain is that a DoC looks deceptively simple: one page, a signature, done. The reality is that Annex III of Decision No 768/2008/EC prescribes nine mandatory elements, and market surveillance authorities treat a missing or vague field as a non-compliance in its own right independent of whether the product is physically safe.

Every CE-marked product from a router to an EV charger draws on the same skeleton, because each sectoral directive or regulation incorporates the Annex III model. Here is a worked CE example for a consumer wireless router:

The benefit of anchoring to this model is presumption of correctness: a single declaration can cover all applicable acts, so one document not four carries the product to market. The proof that it is done right is traceability: field 1 must identify the exact unit or production run, and field 6 must cite the dated edition (“EN 60204-1:2018”, not “EN 60204-1”). Undated standards and pre-signed declarations are the two errors that turn a tidy-looking example into an invalid one.

Understand the Declaration of Conformity (DoC) Under PPWR
Read our complete guide to the PPWR Declaration of Conformity.

Declaration of Conformity examples under PPWR follow the Annex VIII model

For packaging, Declaration of Conformity examples change shape. From 12 August 2026, Regulation (EU) 2025/40 (PPWR) requires an EU declaration of conformity drawn up under Article 39 to the Annex VIII model for every packaging type placed on the EU market. The pain here is scale: importers and brand owners are not authoring one DoC, they are collecting and verifying them across hundreds of SKUs and suppliers, each backed by an Annex VII technical file.

Master Product SKU Mapping for PPWR Compliance
Read our guide to Product SKU Mapping for PPWR Compliance.

A worked PPWR example for a corrugated transport box:

Missing any Annex VIII field renders the DoC invalid treated under PPWR as if no declaration existed at all. That is the benefit of a structured platform view over a copied template: the capability to hold the recyclability grade, recycled-content percentage and substances-of-concern evidence [as connected records, and to regenerate the Annex VIII DoC automatically when any input changes] means the declaration and the technical file never drift apart.

Declaration of Conformity examples for machinery add a technical-file signatory

Machinery shows how sector-specific Declaration of Conformity examples extend the baseline. Under Regulation (EU) 2023/1230 (applicable 20 January 2027), the Annex V model keeps every Annex III field and adds: the name, address and function of the person authorised to compile the technical file (who must be established in the EU), the conformity assessment procedure followed, and where applicable the reference of the EU type-examination certificate. Partly completed machinery uses a separate Declaration of Incorporation with its own Annex V Part B model, a distinction that trips up many first-time examples.

The pattern repeats across the framework: toys in scope must carry the unique identifier of their Digital Product Passport in the DoC from 1 January 2026 under Regulation (EU) 2025/2509, and the Ecodesign Regulation (EU) 2024/1781 lets the declaration and supporting documentation live inside the DPP itself. The direction of travel is unmistakable: the DoC is becoming a live, linked record rather than a static PDF which is exactly where connected traceability data earns its place.

Build Audit-Ready Technical Documentation
Read our complete guide to Technical Documentation and Compliance.

Why most Declaration of Conformity examples get copied wrong

1. The declaration is the easy page; the technical file is the iceberg

The DoC that authorities and customers rely on is one page. The Annex VII technical file behind it construction drawings, material specifications, test evidence, supplier documentation can run to dozens of pages per SKU. Teams that copy an example nail the visible 10% and under-build the 90% that survives an audit. A declaration without its evidence file will not withstand market surveillance scrutiny; it is a claim with nothing underneath it.

2. Declaration in excess is a false statement, not a safe hedge

A common instinct is to list every plausible act “to be safe.” But a DoC declares conformity with every act it names. Listing the Low Voltage Directive on a battery-powered product outside its voltage range creates a false declaration the opposite of caution. Over-declaration is a substantive error; under-declaration (omitting the Radio Equipment Directive for a machine with a wireless module) is equally fatal. The example must match the product exactly, not aspirationally.

3. A DoC is issued per product type, not per shipment

Plenty of examples online imply a fresh declaration per delivery. Wrong: the DoC covers a product type or family and is updated when that type changes not re-issued per shipment. Get this backwards and you drown in redundant paperwork while missing the one update that actually mattered when the design changed.

4. The example only scales if your evidence does

One perfect DoC example is a formatting exercise. Ten thousand of them kept current as standards, suppliers and materials change is a data problem. This is where a copied Word template quietly fails and connected traceability data wins: the declaration should be a generated view of verified records, not a document someone remembers to update.

How TraceX Helps

Creating a Declaration of Conformity is only as reliable as the data behind it. TraceX PPWR solutions centralize packaging specifications, material composition, supplier declarations, conformity evidence, and technical documentation into a single audit-ready platform. By connecting every packaging SKU with its compliance records, TraceX enables manufacturers to generate accurate, compliant Declarations of Conformity and maintain the supporting documentation required throughout the product lifecycle.

Declaration of Conformity examples: copied template vs. platform-generated

A buyer’s checklist for judging any Declaration of Conformity example

Before you trust a Declaration of Conformity example your own or a supplier’s run it against this list. Every unchecked box is a potential formal non-compliance.

• Does field 1 identify the exact product type, model or serial range (not a generic category)?
• Is the manufacturer (and, if non-EU, the authorised representative) named with a full address?
• Does it list every applicable act and only the applicable acts?
• Are harmonised standards cited by dated edition, published in the OJEU?
• Is a notified body named only where one was actually involved (never for Module A)?
• Is there a place, date and signature from an authorised natural person (no pre-signed, undated DoCs)?
• For packaging: does it follow the Annex VIII model and reference Regulation (EU) 2025/40, Articles 5–12?
• Is there a complete technical file behind every claim, retrievable on request?

Frequently Asked Questions (FAQ’s)