CE, Declaration of Conformity and Technical File Check

The CE mark is the smallest and most misread statement on a product: not a quality seal but a legal undertaking in which the manufacturer declares the product's conformity with the applicable regulations. The written price of that undertaking is the declaration of conformity; the pile of evidence behind it is the technical file. For the importer, CE is the beginning of the chain asked about at customs and in market surveillance: which regulations the mark rests on, whether the declaration matches the product, and whether the technical file exists and stays current. At physical inspection the examiner checks not the product but this chain; when a link is found broken, the product stays on the bench. The most common mistake is treating CE as decoration rather than document; never requesting the declaration, or filing whatever arrives unread. This article explains the control language of the declaration of conformity, the components of the technical file, and the importer-side verification practice.

Who is this for?

This guide is for every party that meets a CE-marked product. Importers are obliged to read and archive the arriving product's declaration set; an unread document counts as no document at inspection. Distributors must be able to procure the declaration of the products they market; market surveillance can ask the distributor too. Procurement teams write the declaration and technical file requirements into the supplier contract at order; a post-order request holds the shipment. Regulatory units derive which regulations the product is subject to and audit whether the declaration covers that list. Quality units physically check at acceptance that the marks and identifiers on the product match the declaration. Customs brokers carry the declaration set into the file for positions in control scope. Manufacturer representatives keep the declarations of the product family accessible on the Türkiye side. Service and spare-part units ask whether a changed component breaks the conformity chain. At inspection the question produces a chain: where does the mark come from, to which product does the declaration belong, where is the file?

Which products does it cover?

The scope is all product families carrying, or required to carry, CE marking. Electrical and electronic products: the scope of the low-voltage and electromagnetic compatibility regulations. Machinery and mechanical equipment: the machinery safety regulation and the partly completed machinery construct. Radio and connected devices: the radio equipment regime. Personal protective equipment and non-toy safety products: their own regulation sets. Medical devices and in vitro diagnostic products: carry CE in the conformity language of medical device legislation; the declaration and file structure is shaped by the sector regulation. Special regulatory areas such as pressure equipment, measuring instruments and construction products are also members of the CE family. Those at the border: products not requiring CE carrying it is itself a nonconformity; the mark, even if wrong, is a conformity claim. The scope screening is done product by product; two models of the same family can enter different regulation sets. For every product the same question applies: on which regulations does this mark rest, and where is the evidence?

When does it apply?

Document control is applied at the critical moments of the product's life cycle. At first import the full check runs: the regulation set is derived, the declaration is read, the file is requested, model matching is verified. On model revisions a new declaration is requested; the old declaration does not cover the new revision, even the serial number range may have changed. On supplier change, the new manufacturer's declaration is taken for the same product; one manufacturer's declaration does not cover another's product. In market surveillance and complaint flows, the file becomes the first evidence called upon. For positions entering control scope at customs, the declaration set is submitted in the pre-declaration process; at physical inspection the marks and identifiers on the product are compared with the file. In internal audits, the currency of the declaration archive is screened; stale standard references are a risk signal. When the product is withdrawn from the market or recalled, the declaration and file scope determine the event's product span. In every case the common tool is the same: a checklist and the written verification of the three matches.

Legal framework and authority

The frame is the common conformity architecture of the technical regulation family. Each product family's own regulation defines the route of conformity assessment, the module structure, and when a notified body enters. The declaration of conformity is the visible output of that architecture: the manufacturer's name and address, the product description, the applied regulations, the referenced standards, and the signature-date elements are the declaration's minimum content. The technical file is the pile of evidence behind the declaration: design information, risk assessment, test reports, instructions for use and the serial production control structure are the file's classic components; while the file need not be submitted, it must be kept presentable when requested. In the import layer, the annual Product Safety and Inspection communiqués list the control scope of CE-requiring products by GTİP in their annexes; positions in scope pass TAREKS control before declaration. The authority distribution: the Ministry of Trade for customs control and communiqué application, and the ministry responsible for the product's technical regulation in market surveillance. Communiqués renew annually; the control list changes while the conformity architecture stays fixed.

Step-by-step process

1. Derive the product's regulation set: which regulations, which essential requirements.
2. Read the declaration: manufacturer, product description, model, applied regulations, standard references, signature-date.
3. Physically verify the declaration-product match: the label and serial identifier must overlap the declaration.
4. Check the currency of the standard references; compare the declaration's date with the standard versions.
5. Where a notified body is required, verify the body number exists in both the mark and the document.
6. Request the technical file or its summary; look for each claim in the declaration to have a counterpart in the file.
7. Check that the test reports are model-based and the reporting laboratory is competent.
8. For a position in control scope, attach the document set completely to the pre-declaration application.
9. Archive the documents by product family; with revision and date tracking.
10. Record the label, mark and identifier verification at acceptance.

Document checklist

• Regulation set table: product family, regulations, essential requirements.
• Declaration of conformity, with model and serial identifiers.
• Manufacturer identity information and signature-date verification.
• Standard reference list and version control.
• Notified body certificate and number, where required.
• Test reports, model by model, with reporting laboratory information.
• Risk assessment and design documentation summary.
• Instructions and information documents.
• Pre-declaration application and outcome document, if in scope.
• Archive record: product family, model, document date, next review.

Parties and responsibilities

The chain's fragile link is the declaration going unread: if the document entering the file does not match the product by model and date, a thick file is thin evidence. Reading is part of acceptance.

Exceptions and edge cases

The edge of CE practice produces real questions. Where the product falls under more than one regulation, the declaration must name them all together; a missing regulation is partial conformity and raises a question at physical inspection. On a product whose own regulation does not foresee CE, carrying CE can count as an unfair claim; the mark is not a label but a legal statement. A partly completed machine arrives without CE but with a declaration-like technical document; when assembly completes, integral conformity is rebuilt. In system and plant deliveries, the components' declarations and the whole's conformity are separate layers; a component declaration does not cover the assembled product. In second-hand products the declaration chain belongs to the old manufacturer; the current importer separately assesses its ability to take over the file. In products sold as sets, each component's declaration is requested separately; a set heading hides no declaration. In medical devices, CE is embedded in the sector legislation's conformity structure; the general CE control language is applied translated into the sector's language. In every edge case the tool is the same: reading the triple of regulation set, declaration and file together.

Common mistakes

The most common mistake is never requesting the declaration; the mark has been seen, the document never archived. The second is filing the declaration unread; model mismatches and stale standard references go unnoticed. The third is assuming test reports by product family rather than by model; the report must carry the declaration's model by name. The fourth is skipping the notified body requirement; a high-risk product arriving without the body number has an incomplete file. The fifth is never requesting the technical file; the file goes assumed, and when market surveillance requests it there is no time to prepare. The sixth is not renewing the declaration on revision; the new version is imported with the old document. The seventh is treating CE as a quality seal and misusing it in marketing language; the mark's meaning can be neither narrowed nor widened.

Important notice

This article is general information, not legal or customs advice; for CE conformity processes, the product's current technical regulations and the communiqué texts must govern, and a licensed customs broker should be consulted. The regulation and standard examples here are not binding; conformity assessment must be made for each product with its own regulation set. Communiqué numbers and scope lists change annually; official sources must be checked before any transaction.