What is a technical file and is it actually required for every product?

A technical file is the set of product safety and compliance documents that show a consumer product is safe and meets the EU rules that apply to it. In practice, it is required whenever EU law requires you to be able to demonstrate compliance, and under the General Product Safety Regulation (EU) 2023/988 (GPSR) you must be able to provide relevant technical documentation on request.

Not every product needs the same depth of EU technical documentation, but virtually every consumer product sold into the EU needs some form of documented evidence of safety, traceability, and controls. The exact contents depend on the product, its risks, and whether any CE marking legislation applies.

The questions below break down what a technical file is, when it is required, what to include, and how long to keep it.

What is a technical file in product compliance?

A technical file is a structured collection of EU technical documentation that demonstrates how a product was designed, assessed, and controlled to meet applicable EU safety requirements. It typically includes product identification, risk assessment, test evidence, labeling and instructions, and supply chain traceability so authorities can verify compliance quickly when requested.

Think of the technical file as your proof pack. It should let a competent reviewer understand what the product is, how it is made, what hazards were considered, what safeguards exist, and what evidence supports your safety claims.

In EU compliance, the term is used in two common ways:

GPSR technical documentation for general consumer product safety, focused on risk assessment, safe use information, and traceability.
CE marking technical file under specific harmonized legislation (for example, toys, machinery, EMC, radio equipment), which can require more formal conformity assessment evidence.

Even when a product is not CE marked, you still need organized documentation that supports safety and enables fast responses to market surveillance questions.

Is a technical file required for every product sold in the EU?

A technical file is not a single universal checklist required in the same way for every product, but some form of EU technical documentation is effectively required for virtually all consumer products sold in the EU. Under GPSR, products must be safe, and you must be able to provide documentation that demonstrates safety and traceability when authorities ask.

Whether you need a full CE marking technical file depends on whether your product falls under CE marking legislation. If it does, the technical file requirements come from that specific law and related standards, not from GPSR.

For most sellers, the practical rule is simple: if you cannot show how you assessed and controlled product risks, you are not ready for an authority request or a marketplace compliance check.

Also note the role requirements: for many non EU businesses selling to EU consumers, an EU Responsible Person must be designated within the EU supply chain. That role is taken by an economic operator, not an individual, and it supports documentation availability and cooperation with authorities.

What should a technical file include?

A technical file should include enough GPSR technical documentation to identify the product, show how you evaluated safety risks, and prove that labeling, instructions, and controls match those risks. If CE marking applies, the CE marking technical file must also include the specific evidence required by the relevant EU legislation and conformity assessment route.

To keep it practical, build your file around what an authority or marketplace reviewer will ask first: what is it, what can go wrong, what did you do about it, and where is the evidence.

Product identification: model or SKU, batch or serial logic, product description, photos, variants, and intended use.
Manufacturer details: legal entity name and address, plus key production sites where relevant.
Risk assessment: hazards, foreseeable misuse, vulnerable users (for example, children), and risk controls.
Test reports and evidence: relevant safety testing, material declarations where needed, and quality checks tied to identified risks.
Design and manufacturing information: bill of materials or critical components, drawings, and process controls for safety-critical steps.
Labeling and traceability: product markings, warnings, batch identifiers, and any required contact details on the product or packaging.
Instructions for use and safety information: clear user guidance, maintenance, disposal, and warning statements aligned to the risk assessment.
Change control: records of design changes, supplier changes, and how you reassessed risk after changes.
Complaint and accident monitoring: how you capture feedback, investigate accidents, and decide on corrective actions.

A common mistake is collecting documents without linking them back to the risk assessment. A strong technical file tells a coherent story from hazards to controls to evidence.

How long must technical documentation be kept and who can request it?

Technical documentation should be kept long enough to support enforcement and traceability, which in many EU product regimes is commonly at least ten years after the last product is placed on the market, although exact retention rules depend on the applicable legislation. Market surveillance authorities can request EU technical documentation, and you must be able to provide it promptly.

Under the Market Surveillance Regulation (EU) 2019/1020 (MSR), authorities have strong powers to request information and documentation to verify compliance. Marketplaces may also ask for documentation to keep listings active, even though they are not the authority.

Retention is not only about storage. It is about being able to retrieve the right version fast, including:

the exact documentation for the specific model and batch or production period
the language versions of instructions and warnings used in the EU
the latest risk assessment reflecting any design or supplier changes

Role clarity matters. The Responsible Person role supports cooperation and documentation availability. Separately, where an Authorized Representative is appointed for applicable legislation, that role has specific regulatory tasks. Under MSR Article 4, the Responsible Person must inform the manufacturer if there are risks, but the Authorized Representative is responsible for notifying serious risks to the authorities.

How EARP helps with technical files and EU technical documentation

We help non EU manufacturers and sellers get their technical file and EU technical documentation into a review-ready state for GPSR and, where applicable, CE marking technical file expectations, while also providing the required EU Responsible Person coverage so documentation can be made available to authorities when requested. Our support is practical and process-driven:

Document completeness checks against product type, risk profile, and applicable EU requirements
Structured technical documentation storage with fast retrieval for authority requests
Verification workflows to confirm required safety documents are present and consistent across variants
Regulatory liaison support to help you respond clearly and on time if market surveillance contacts you

If you want to keep selling in the EU with confidence, review our EU compliance services and then reach out through our contact page to discuss your products and documentation setup.