You need to keep clear, retrievable product safety documentation that shows your product was designed, made, and supplied with the information needed to be safe under normal and reasonably foreseeable use. Keep the evidence that supports your safety assessment, traceability, warnings, and any tests or checks you relied on, and be ready to provide it quickly if authorities ask.
This proof matters most for EU GPSR compliance records under the General Product Safety Regulation (EU) 2023/988 (GPSR), especially for non-EU brands and online sellers that ship directly to EU consumers and may be asked for market surveillance evidence at any time.
Below are the specific types of proof to keep, what belongs in a technical file, how long to retain it, and who should store it.
What proof shows a product is safe under EU product safety rules?
Proof that a product is safe under EU product safety rules is a set of EU GPSR compliance records that demonstrates you identified foreseeable hazards, reduced risks through design and controls, and provided clear consumer information such as instructions and warnings. It also includes traceability and quality evidence that supports consistent production and safe supply.
Under the GPSR, authorities typically look for a coherent safety story: what the product is, how it can be used, what could go wrong under reasonably foreseeable conditions, and what you did to prevent harm. Your market surveillance evidence should be consistent across product labeling, listings, packaging, and internal records.
- Product identification and traceability: model or type, batch or serial where applicable, manufacturer details, and supply chain information.
- Safety assessment: a documented risk assessment covering intended use and reasonably foreseeable misuse, including vulnerable users when relevant.
- Design and manufacturing controls: specifications, critical safety requirements, and checks that show the product matches the assessed design.
- Testing and verification: test reports or evaluations you relied on, plus a rationale for why they are relevant to your product and risks.
- Consumer information: instructions, warnings, and safety information in the required languages for the markets where you sell.
- Post-market inputs: complaint handling records and analysis of accidents and safety-related feedback, with corrective actions where needed.
Keep the proof practical. If a document does not help explain why the product is safe, it usually does not belong in your core safety evidence set.
Which documents should I keep in my product safety technical file?
A product safety technical file should contain the product safety documentation that lets an authority understand the product, evaluate its risks, and verify the controls you used to keep it safe. For GPSR purposes, focus on documents that support your safety assessment, traceability, labeling, and your ability to respond quickly to information requests.
While the exact contents vary by product, a strong technical file usually includes:
- Product description: intended purpose, variants, accessories, and key safety-relevant features.
- Bill of materials or critical components list: especially parts that affect safety, such as batteries, chargers, heating elements, blades, or load-bearing parts.
- Risk assessment and safety rationale: hazards, risk evaluation, and risk reduction measures tied to design and information for use.
- Applicable requirements mapping: the EU rules and standards you used as references, and how you meet them.
- Test reports and evaluations: internal or third-party testing, plus any calculations or engineering checks relevant to safety.
- Quality and production checks: incoming inspection criteria, in-process checks, final inspection, and change control records for safety-critical changes.
- Labeling and packaging: artwork files, label content, symbols used, and placement requirements.
- Instructions and warnings: the exact versions supplied to consumers, with language versions and revision history.
- Traceability records: batch records where used, supplier identification, and distribution channels.
- Complaint and accident log: what was reported, how you assessed it, and what corrective actions you took.
Do not treat the technical file as a dumping ground. Organize it so you can answer typical authority questions fast: what the product is, what risks you identified, what evidence supports your controls, and how you can trace affected units if a safety problem appears.
How long do I need to keep product safety records, and who must store them?
You should keep technical documentation retention long enough to support enforcement and traceability after the last unit is placed on the EU market, and you should be able to provide it promptly upon request. In practice, retention is often set to at least ten years for many EU product compliance regimes, but the right period depends on the product and the specific EU rules that apply.
For GPSR-focused EU Responsible Person documentation, the key is that an economic operator established in the EU can make required information available to authorities. The Market Surveillance Regulation (EU) 2019/1020 (MSR) sets the framework for how authorities request and assess compliance information, and it is a useful reference point for how quickly and reliably you need to respond.
To set a defensible retention policy in 2026, use these practical rules:
- Start the clock from the last date the product was placed on the EU market, not the first sale.
- Align to the strictest applicable rule if your product also falls under sector legislation beyond GPSR.
- Keep version control so you can show what instructions, warnings, and design version applied to each batch or period.
- Store records in a retrievable format with clear indexing, so you can respond quickly to market surveillance evidence requests.
- Define responsibilities between the manufacturer and the EU-based economic operator that holds the documentation access obligation.
Who must store the records depends on your supply chain. If you sell directly into the EU without an importer or distributor that can take the role, you still need an EU-based economic operator to hold and provide the required documentation access. Under the MSR, the Responsible Person role is held by an economic operator, and that role must be able to notify risks to the manufacturer in line with Article 4 of the MSR.
How [COMPANY] helps with product safety documentation and retention for EU market access?
We help you build, organize, and maintain the product safety documentation and technical documentation retention process you need for EU market access under the GPSR, including the practical ability to provide market surveillance evidence when requested. Our focus is independent regulatory compliance support for non-EU manufacturers and online sellers that need reliable EU Responsible Person documentation handling.
- Documentation readiness checks to confirm you have the required safety records, instructions, warnings, and traceability information in place
- Structured technical file organization so documents are complete, consistent, and easy to retrieve under time pressure
- Secure documentation storage and controlled access to support retention and fast authority responses when information is requested
- Clear roles and workflows aligned with GPSR and the MSR so your team knows what to maintain and when to update it
To see how this works for your product range, review our EU compliance services and then contact our team to set up the right documentation and retention approach for your EU listings.
Related Articles
- Is there any EU equivalent of the US Consumer Product Safety Commission that I need to know about?
- Can EU customs stop my products at the border for GPSR violations?
- Is there a checklist I can follow to make sure my product label is EU ready?
- What safety information must appear on clothing product pages in EU?
- Do plush toy eyes and buttons need to pass EN 71 small parts tests?
