[Home](/)/[Resources](/resources)/CE DoC Deep Dive EUDocumentationDeep dive # CE Declaration of Conformity Deep Dive: Multi-Directive Structure and Audit-Proofing The base guide lists the five headline DoC mistakes. This deep dive goes deeper into the structural decisions that determine whether a DoC actually holds up under scrutiny: how to structure a declaration across multiple directives and product variants, why standard references quietly go stale, translation obligations, the DoC-versus-DoP distinction, and what market surveillance authorities actually flag when they open a file. Copy Link[Share on WhatsApp](https://wa.me/?text=https%3A%2F%2Fkrono-labs.com%2Fguides%2Fce-doc-common-mistakes-deep-dive) At a glance Structural scenarios covered 4 Common surveillance findings 6 Related deep dive DoC vs DoP FAQs 6 On this page * [1\. One DoC per product, even across multiple directives](#single-vs-multi) * [2\. Standard drift: the silent way a valid DoC becomes invalid](#standard-drift) * [3\. Version control across product revisions and variants](#version-control) * [4\. Translation obligations most manufacturers underestimate](#translation-obligations) * [5\. DoC versus DoP: a distinction that matters for construction products](#doc-vs-dop) * [6\. Who can actually sign, and what happens when they leave](#signatory-authority) * [7\. What market surveillance authorities actually flag in practice](#surveillance-findings) * [8\. Digital DoCs, QR-code links, and eIDAS-compliant signatures](#digital-doc) ## 1\. One DoC per product, even across multiple directives The [base guide on CE DoC common mistakes](/guides/ce-doc-common-mistakes) lists missing or incorrect directive references as a top error. What that single line item understates is how much structural judgment goes into correctly scoping a DoC once a product is subject to more than one directive, or comes in multiple variants. The default rule is one Declaration of Conformity per product, listing every applicable directive within that single document — not a separate DoC per directive. A Wi-Fi enabled smart plug, for example, typically needs one DoC that references RED (covering the radio and, for RED-scoped products, EMC and electrical safety aspects that RED's essential requirements absorb) and RoHS, rather than three separate documents. The most common failure mode is not producing multiple documents where one would do — it is omitting a directive that applies less obviously, such as forgetting to reference RoHS on a product the team primarily thinks of as "the RED product." For product families sharing a platform across multiple SKUs, the scoping question gets harder still — see the comparison below for how the right structure changes with product complexity. ## 2\. Standard drift: the silent way a valid DoC becomes invalid A DoC that was entirely correct on the day it was signed can become defective months or years later without anyone touching it, because the harmonised standards it cites are periodically updated, withdrawn, or superseded in the Official Journal. When that happens, the presumption-of-conformity basis for that specific standard reference lapses — even though the physical product hasn't changed at all. This is a fundamentally different kind of error than the ones a one-time DoC review catches. A DoC can be perfectly correct at signing and still be sitting on stale references two years into continuous production, if nobody is monitoring standard status on an ongoing basis. Products with long production runs — industrial equipment, infrastructure components, anything not iterated on a fast consumer-electronics cycle — are especially exposed to this, precisely because nobody revisits a DoC that seems to be working. The practical mitigation is treating standard-status monitoring as a recurring compliance task tied to the product's production lifecycle, not a one-time step completed at launch and then forgotten. ## 3\. Version control across product revisions and variants How a DoC should be structured changes meaningfully with product complexity. The table below compares four common scenarios and where the structural risk concentrates in each. Scenario Recommended approach Where the risk concentrates Single-directive product (e.g., a simple LED lamp under RoHS + a safety directive) One DoC listing both applicable directives, both sets of standards, one declaration statement Low — straightforward as long as both directive references are current. Multi-directive product (e.g., a Wi-Fi enabled smart plug: RED, RoHS, and potentially EMC coverage folded into RED) One DoC covering all applicable directives for that product, each listed with its own standards Medium — easy to omit a directive that applies less obviously, like forgetting RoHS on a product primarily thought of as an RED product. Product family with shared platform, multiple SKUs One DoC per distinct technical file scope — variants sharing the same design and compliance basis can share a DoC if the scope statement is explicit about which model numbers are covered High — the most common structural error is a DoC that implies family-wide coverage when only the flagship model was actually tested. Product requiring both DoC and a separate mark-specific declaration (e.g., MID's M mark, or a Notified Body certificate reference) One DoC referencing the relevant Notified Body certificate number and any supplementary mark basis, alongside standard CE elements Medium — omitting the NB certificate reference or supplementary mark basis is a common gap in multi-mark products. A revised DoC issued after a correction should carry a new version number or date and be retained alongside the prior version with a documented explanation of what changed — never silently overwritten. ## 4\. Translation obligations most manufacturers underestimate Many manufacturers treat an English-language DoC as sufficient across the entire EU market, and in practice a single English DoC often goes unquestioned for a long time. But the underlying expectation across many member states is that the DoC — or at minimum the safety-relevant accompanying documentation — is available in the national language of the country where the product is actually placed on the market. Because this expectation is implemented at the national level rather than uniformly across the whole directive framework, the practical exposure only becomes visible during a market surveillance interaction in a specific member state — which is precisely why it is easy to underestimate until it becomes a live issue. A manufacturer selling into more than a handful of EU markets should treat translated documentation as a standing operational requirement, not a one-off task handled only if a customer or authority specifically asks. ## 5\. DoC versus DoP: a distinction that matters for construction products Declaration of Conformity and Declaration of Performance are not interchangeable terms, even though they sound similar and both accompany CE-marked products. A DoC, used across most CE marking directives, is a binary compliance statement: the product meets the essential requirements of the listed directives. A DoP, specific to the Construction Products Regulation, instead declares a construction product's performance against a set of declared characteristics — it does not make a single pass/fail claim the way a DoC does, because construction products are assessed against performance levels that a specifier chooses to accept or reject for a given use. A product spanning both worlds — a smart building-management sensor embedded in construction hardware, for example — can genuinely need both documents: a DoC covering the electronic component's directives (RED, RoHS, and so on) and a DoP covering the construction-product performance characteristics of the housing or structural element it's built into. Treating these as one document, or assuming a DoP satisfies a DoC requirement or vice versa, is a structural error that surfaces most often in hybrid electronic-and-construction product categories. ## 6\. Who can actually sign, and what happens when they leave The base guide correctly notes that the DoC must be signed by the manufacturer, an EU Authorised Representative, or an authorized company signatory. What that leaves unaddressed is what happens operationally when the person who signed a still-current DoC leaves the company, or when signing authority was never formally delegated in the first place. A DoC does not become invalid simply because its original signatory has since left — the declaration was valid at the moment it was signed. But an organisation that cannot clearly demonstrate the departed signatory had actual authority to bind the company at the time of signing creates unnecessary friction if a market surveillance authority ever asks the question. Maintaining an internal record of who held signing authority for CE documentation, and when that authority was assigned or transferred, closes a gap that is invisible until exactly the moment it becomes a problem. ## 7\. What market surveillance authorities actually flag in practice Beyond the categorical mistakes the base guide lists, patterns emerge in what actually draws scrutiny during a market surveillance review. The table below reflects the kinds of findings that recur most often. Standard reference cites a withdrawn or superseded EN number Very common Harmonised standards are periodically updated, and their Official Journal listing can lapse or be replaced. A DoC that cites a standard no longer current at the time of market placement does not provide presumption of conformity, even if the product was actually tested to a still-valid predecessor. DoC scope does not match the physical product on shelf Common A product revision — new firmware, a changed antenna, a different power supply — that is not reflected in an updated DoC and technical file is a frequent finding, particularly for fast-iterating connected products. Manufacturer address on the DoC does not match the address on the product label or packaging Common A mismatch here raises immediate questions about which legal entity actually stands behind the compliance claim, and is one of the fastest things a market surveillance inspector checks. No EU Authorised Representative listed for a non-EU manufacturer Common for importers/first-time exporters A non-EU manufacturer cannot sign a valid DoC without either an EU-based operation or a properly appointed Authorised Representative — this is one of the more frequent reasons a DoC is rejected outright rather than merely flagged for correction. Declaration statement is generic boilerplate not tied to the specific product's tested configuration Occasional A DoC that reads as though it was copied from another product line, with only the product name swapped, tends to draw closer scrutiny of the underlying technical file to confirm the testing actually matches this specific product. Signature present but signatory's authority to bind the company is unclear or undocumented Occasional While the DoC itself doesn't need to prove signatory authority on its face, an authority failing to establish this during an investigation adds friction and delay to resolving a compliance question. ## 8\. Digital DoCs, QR-code links, and eIDAS-compliant signatures A growing share of manufacturers provide the DoC digitally — as a downloadable document linked from a QR code on the product or packaging, rather than a printed insert. This is generally acceptable under current digital labelling provisions, but it introduces failure modes a paper DoC does not have: a broken link, a webpage taken down during a site redesign, or a document quietly moved without updating the referencing QR code all functionally recreate the exact same problem as never having issued a DoC at all, from the perspective of anyone trying to access it. Any electronic signature used on a digital DoC needs to meet eIDAS requirements — uniquely linked to the signatory, capable of identifying them, and created in a way that lets any subsequent change to the document be detected. A scanned image of a handwritten signature pasted into a PDF does not meet this bar on its own; a proper qualified or advanced electronic signature does. Manufacturers moving to digital-only DoCs should treat link stability and retrieval testing as an ongoing operational check, not a one-time verification at the point of publishing. ## Frequently asked questions ### Can one DoC cover an entire product family, or does every SKU need its own? One DoC can cover multiple SKUs only when they genuinely share the same technical file and compliance basis — same design, same test results applicable, no material differences affecting the assessed requirements. The DoC's scope statement must explicitly list which model numbers or variants are covered. A common and costly mistake is writing a DoC broadly enough to imply coverage of an entire product family when only the flagship model was actually tested, leaving other variants technically uncovered. ### What happens to standard references when a harmonised standard is updated? When a standard the DoC cites is withdrawn or superseded, the DoC's presumption-of-conformity basis for that reference lapses — even though the underlying product may still perform identically. The practical fix is to re-verify against the current standard (which may involve re-testing if the new version changed test methods or limits) and issue a revised DoC citing the current reference. This is why periodic Official Journal monitoring, not a one-time check at launch, is part of maintaining a valid DoC over a product's market life. ### Does a DoC need to be provided in every language of the countries where the product is sold? Requirements vary, but many member states expect the DoC — or at minimum the safety-relevant parts of the accompanying documentation — to be available in the national language of the country where the product is placed on the market. Providing only an English DoC across the entire EU is a common shortcut that some national market surveillance authorities will flag, even though the directive-level DoC content requirements themselves are largely EU-wide. ### Is a Declaration of Conformity the same as a Declaration of Performance? No — they cover different legislation and are not interchangeable. A Declaration of Conformity (DoC) is the standard document under most CE marking directives (RED, LVD, EMC, Machinery, and others). A Declaration of Performance (DoP) is specific to the Construction Products Regulation and declares a construction product's performance against declared characteristics rather than a binary conformity statement. A product spanning both regimes — construction hardware with an integrated electronic control unit, for instance — may need both a DoC for the electronic component's directives and a DoP for the construction-product characteristics. ### Who is legally allowed to sign a DoC on behalf of a company? The DoC must be signed by the manufacturer or their EU Authorised Representative, and in practice by an individual with actual authority to bind the company to the declaration — commonly a director, a designated compliance officer, or another authorized signatory. The DoC itself does not need to document that authority on its face, but an organisation should be able to demonstrate the signatory's authorization if a market surveillance authority asks, and should have a clear internal process for reassigning signing authority when a designated signatory leaves the company. ### Are digital or QR-code-linked Declarations of Conformity legally valid? Yes, with conditions. A DoC provided digitally — including as a document accessible via a QR code or URL printed on the product or packaging — is generally acceptable under current EU digital labelling provisions, provided the link remains stable and accessible for the required retention period, the document itself is complete and unaltered, and any electronic signature used meets eIDAS requirements for being uniquely linked to the signatory and tamper-evident. A broken link or a webpage that has since been taken down defeats the purpose and creates the same practical problem as never having produced the DoC at all. **Disclaimer:** This page is an educational resource only and does not constitute legal or regulatory advice. DoC content requirements, translation expectations, and digital documentation acceptability vary by member state and directive — always verify current requirements and consult qualified counsel before finalising a Declaration of Conformity. 🇪🇺 CE Marking roadmap for your product Every standard, document, and test that applies — free, no account required. See your free roadmap[ Want an expert to take your product through 🇪🇺 CE Marking compliance for you? One consultant from Krono's compliance team takes your product from requirements to legal sale, with a fixed quote before any work starts. See compliance services](/services) Learn this properly In-depth course that teaches the full process, not just this one answer. [Start the course — $149](/courses/01-ce-marking-for-electronics-engineers)[Prefer to read? Get the book — $24.99](/books/01-ce-marking-for-electronics-engineers) Related guides * [CE DoC Common MistakesComplete guide to avoiding common DoC mistakes.](/guides/ce-doc-common-mistakes) * [CE Conformity Assessment Modules Deep DiveA deep dive into all sixteen CE conformity assessment module variants — A1/A2, C1/C2, D1, E/E1, F1, G, H1 — how they chain together across design and production phases, and worked module-selection walkthroughs for RED, Machinery, and PED products.](/guides/ce-conformity-assessment-modules-deep-dive) * [MID Deep DiveA deep dive into the Measuring Instruments Directive: how MI-001 to MI-010 categories map to conformity modules, why the CE + M mark combination exists, national metrology legislation, and the sub-metering edge cases manufacturers miss.](/guides/measuring-instruments-directive-deep-dive) * [FCC SDoC Deep DiveA deep dive into FCC SDoC: mixed-mode devices combining unintentional and intentional radiators, responsible-party succession, the 72-hour record production standard in practice, and how SDoC compares to CE self-declaration under Module A.](/guides/fcc-sdoc-supplier-declaration-deep-dive)