How do I create a compliant technical file when I sourced the product from a supplier who provides no documentation?

If your supplier provides no documentation, you can still create a compliant EU technical file by rebuilding the evidence yourself: identify the applicable EU safety rules, document the product design and intended use, run a risk assessment, obtain or commission test reports where needed, and compile traceability and labeling records. The goal is complete, retrievable EU technical documentation.

This approach matters even more under the General Product Safety Regulation (EU) 2023/988 (GPSR), because authorities and online marketplaces can ask for product compliance documentation quickly and expect you to produce it without delay. The steps below show how to reconstruct a GPSR technical file from scratch and keep it ready for market surveillance requests.

The sections answer the most common questions sellers ask when documentation is missing, including what to include, how to rebuild it, and what risks you face if you sell without it.

What is a technical file and when is it legally required in the EU?

An EU technical file is a structured set of EU technical documentation that demonstrates a consumer product is safe and that you can substantiate safety-related claims, labeling, and traceability. It is legally required whenever EU product safety rules expect you to be able to show evidence of compliance, especially when authorities make market surveillance requests.

In practice, a technical file is your proof pack. It should let a regulator understand what the product is, how it is made, what hazards you considered, and what controls you put in place to reduce risk. Under GPSR, the expectation is not a single fixed template but a complete, coherent record that supports safe market access for consumer products sold in the EU.

Even if a product is sourced from a factory that refuses to share internal records, the obligation to hold adequate product compliance documentation does not disappear. If you place products on the EU market, you need to be able to produce documentation when requested and keep it up to date as the product, suppliers, or standards change.

How can you rebuild missing documentation if the supplier provides none?

You can rebuild missing product compliance documentation by treating the product as if you are documenting it for the first time: define the product and intended use, map applicable EU requirements, perform a safety risk assessment, gather objective evidence through testing and inspections, and record traceability and labeling. The result is a defensible GPSR technical file you control.

Identify the exact product variant by SKU, model, batch, materials, and key components so your EU technical documentation matches what you sell.
Define intended use and reasonably foreseeable misuse including user groups such as children, and environments such as indoor, outdoor, wet areas, or charging scenarios.
Map applicable EU rules and standards based on product type and features. GPSR applies broadly, and other sector rules may also apply depending on the product.
Run a documented risk assessment listing hazards, who could be harmed, severity, likelihood, and the risk reduction measures you implement.
Obtain objective evidence such as third-party test reports, material declarations, or inspection records. If you cannot obtain them, commission testing for the risks you identified.
Verify labeling and instructions including warnings, language requirements, and traceability information so the product can be identified and used safely.
Create a change control log so any supplier change, material change, or design update triggers a review of the technical file.

A practical tip is to start with the highest-risk areas first. For many consumer products, that means mechanical hazards, choking risks, sharp edges, overheating, chemical exposure, and battery-related hazards. Your documentation should show how you checked these risks and what you did to reduce them.

Which documents are typically included in an EU technical file?

An EU technical file typically includes product identification, design and manufacturing information, a safety risk assessment, evidence supporting safety such as test reports, and the labeling and instructions supplied to users. For a GPSR technical file, the emphasis is on demonstrating product safety and traceability rather than following a single rigid checklist.

Product description and identification including model numbers, photos, variants, and bill of materials where available.
Manufacturer and supply chain details including factory identity, addresses, and any intermediaries involved in fulfillment.
Risk assessment and risk controls documenting hazards, mitigations, and residual risk.
Test reports and assessments relevant to the product’s hazards and claims, such as mechanical safety, chemical safety, electrical safety, or flammability where applicable.
Label artwork and packaging files showing warnings, symbols, batch or serial identifiers, and any required contact details.
Instructions for use and safety information in appropriate EU languages for the markets you target.
Quality and consistency records such as incoming inspection checks, production checks, or supplier specifications if you can obtain them.
Traceability records including batch tracking, shipment records, and how you can identify affected units if a safety problem is found.

Keep the file internally consistent. If your listing says a product is suitable for a certain age group or has a specific performance claim, your technical documentation should support that. If you change packaging, warnings, or materials, update the file and record the change.

What are the risks of selling in the EU without a complete technical file?

Selling in the EU without complete EU technical documentation creates immediate operational and legal risk: you may not be able to answer market surveillance requests on time, marketplaces can block listings, and authorities can require corrective actions or remove products from sale. A weak GPSR technical file also makes it harder to manage accidents and safety complaints.

Under the Market Surveillance Regulation (EU) 2019/1020 (MSR), authorities can request documentation and expect it to be made available. If you cannot produce coherent product compliance documentation, you may face escalations such as increased scrutiny, requests for additional evidence, or measures that restrict market access.

Marketplace disruption when platforms ask for proof of an EU Responsible Person and supporting documentation.
Regulatory action if authorities conclude you cannot substantiate product safety.
Slow response to safety issues because you cannot quickly identify batches, affected units, or root causes.
Higher recall complexity since traceability gaps make targeted corrective action difficult.

Also note the role split: the EU Responsible Person is an economic operator that supports compliance and documentation availability, while an Authorized Representative may have different obligations depending on the applicable legislation. Under MSR Article 4, the Responsible Person must inform the manufacturer if it has reason to believe a product presents a risk, but the Responsible Person is not the economic operator responsible for notifying serious risks to authorities.

How EARP helps with building and maintaining compliant EU technical documentation?

We help you turn missing supplier paperwork into a controlled, audit-ready documentation set by building a practical GPSR technical file framework, checking completeness against your product’s risk profile, and maintaining EU technical documentation so it is ready for market surveillance requests. We also act as your EU Responsible Person where required, with an independent compliance focus.

Technical file rebuild support to structure your product compliance documentation, identify gaps, and prioritize evidence that regulators typically expect.
Documentation verification processes to confirm required safety documents are present, consistent, and retrievable when requested.
Secure documentation storage and availability so files can be provided to authorities without delay.
Ongoing maintenance with change tracking so updates to suppliers, materials, or labeling trigger a documentation review.

If you need help rebuilding a compliant technical file fast, review our EU compliance services and then contact us through our contact page to discuss your product, your current documentation gaps, and the quickest path to compliant EU market access.