How to Generate GPSR Documents in 5 Minutes (2026)

Under the EU's General Product Safety Regulation, Regulation (EU) 2023/988, having a safe product is no longer enough. You have to prove it on paper. For non-EU sellers, that paper is a technical file and a risk assessment for every product you list. Drafting one by hand takes 20 to 30 minutes. For a 1,000-SKU catalog, that is 300 to 500 hours of admin before you have sold a single extra unit.

This guide covers exactly which documents you need, why the manual route hurts so much, and how sellers in 2026 generate the same files in under five minutes. The frontmatter above walks through the workflow step by step. Here is the reasoning behind each part.

The four documents GPSR actually asks for

The legal foundation for GPSR paperwork is Article 9(2) of Regulation (EU) 2023/988. Whether you build the file by hand or with software, it has to produce four things.

1. Internal risk analysis. A structured assessment of the physical, chemical, and mechanical hazards your product carries, plus the steps you took to reduce them. This is the risk assessment authorities expect to see first.
2. Technical documentation. The dossier itself: a general description of the product, its essential safety characteristics, and a bill of materials. Our technical documentation template shows the full structure.
3. Safety warnings and user instructions. The mandatory product markings, clear usage instructions, and safety warnings, translated into the official language of every Member State where you sell.
4. Declaration of conformity, if it applies. A DoC is not required for general goods covered only by the GPSR. Products that fall under a CE-marking directive, such as toys or electronics, do need a formal self-declared declaration of conformity inside the technical file.

Only the third item ships to the consumer. The risk analysis and technical file are internal. You keep them for 10 years and hand them over only when a market surveillance authority asks.

One point that trips up sellers of intangible goods: where digital products land depends on what they are. Pure digital files, such as ebooks, PDF patterns, and image or print files, are generally outside GPSR scope. The contested case is standalone software and apps, which the European Commission has treated as in scope. If you sell that kind of digital product, you still draw up documentation assessing the risk, even when you conclude the risk is minimal. "Minimal" is a finding you record, not a reason to skip the file.

Why the manual route hurts

Read any seller forum and the complaint is the same. As one creator put it, "The rules seem to require a lot more paperwork, technical documentation like risk assessments, and having an EU Responsible Person." Another was quoted €350 per category just to have an EU company write the risk assessment, and called it "insane."

The frustration is not really about understanding the rules. It is about volume and repetition. Sellers describe the work in plain terms: "it's too much to ask for all this technical documentation for every product I sell," and "you need to provide manufacturer information and a responsible person on every product listing. It can become quite messy managing that by hand."

The manual process means cobbling together supplier PDFs, filling out Word or Excel templates, and translating safety warnings one language at a time. Then comes the upload friction. Amazon sellers report that manual CSV bulk uploads trigger Brand Registry errors, forcing them to fix thousands of ASINs one at a time. The recurring question on those threads is blunt: "How are the massive sellers with 50,000+ listings handling this?"

Do the arithmetic and the scale of the problem is clear. Industry estimates put a single compliant GPSR report at 20 to 30 minutes to source the material data and format it. A seller with 100 SKUs is looking at 30 to 50 hours. At 1,000 SKUs it is 300 to 500 hours, the equivalent of two to three months of full-time work spent typing the same fields into the same templates. And that is the optimistic version, before a single rejected upload or a request to redo a file you can no longer find.

The hidden cost is the rejections. One Amazon seller described the maddening pattern: "When we manually input the Responsible Person and Manufacturer data for a single ASIN, it gets approved. We have the correct data." The bottleneck was not their compliance. It was the bulk system blocking the upload. Manual entry that works for one listing breaks the moment you try to do it across a catalog, which is why sellers keep asking for "a clear, working, step-by-step guide on how to upload GPSR data in bulk without triggering Brand Registry errors."

And there is the problem you only notice months later. As one seller said, "The hardest part usually isn't writing things down once, it's being able to find the right information again when something goes wrong." A folder of loose Word files does not solve that.

The five-minute version

The fix is not a smarter template. It is entering your product data once and letting the tool assemble the documents. The workflow has three real moves: add product, pick category, generate.

Add the product once. You type the product name, a general description, the materials or bill of materials, and upload an image. This is the same data you would otherwise retype into every template by hand. The difference is you do it once.

Pick the category. The category you choose decides which hazards get assessed and which warnings apply. A wooden toy, a phone charger, and a cotton t-shirt carry different risks, and the category is how the generator knows which ones to check. If you are unsure whether your products even fall in scope, our am I affected check sorts that in a minute.

Generate. The tool produces the risk assessment, the technical file, and the safety warnings together, formatted to Article 9(2). A job that ran 20 to 30 minutes by hand finishes in the time it takes to read this paragraph. Because the warnings are generated, not hand-translated, you get them in the official EU languages rather than copy-pasting through a translator.

Then you review. The generator gives you a solid first draft, not a finished legal document you blindly trust. Read it, correct anything specific to your product, and confirm the translations cover the Member States you sell into. The point is not to remove your judgment. The point is to remove the 25 minutes of typing that came before your judgment.

This is what EUProof does. You add a product, pick a category, and get the technical file, risk assessment, and safety warnings back. EUProof generates the documents. It does not act as your EU Responsible Person, so you still need one of those in place.

A note on what software does not replace

Generating documents fast does not remove your other obligations. You still need an EU Responsible Person established in the EU to hold your file and act as the liaison with authorities. Without proper documentation behind them, your Responsible Person cannot represent you to authorities, marketplaces can delist your products, and customs can block shipments at the border.

The documents and the Responsible Person work together. The generator gives you the file. The Responsible Person is who holds it and answers for it. If you sell under your own private label, remember you are legally the manufacturer, so the technical file must carry your brand name and your Responsible Person, even when the lab tests inside it come from your supplier.

Software also does not absolve you of the warnings rule. A QR code that links to safety information does not satisfy the GPSR on its own. The information has to be physically present on the product, the packaging, or an accompanying document, in a language easily understood in the Member State where it is sold. A generator can produce the warning text in 27 languages in seconds. Printing it and putting it in the box is still on you. For the full picture of what goes where, see our guide to GPSR labeling requirements.

There is a findability angle too, and it is the one sellers underrate. The hard part is not writing the file once. It is locating the right version months later when an authority emails you about a specific batch. Loose Word files in a shared drive do not survive that test. Generating documents from a single product record keeps them in one place and tied to the product, which is the version of "organized" the 10-year retention rule quietly demands.

Where this saves the most

The five-minute number matters most when it repeats. One product saved 25 minutes is nice. A 1,000-SKU catalog is the difference between a few hours and several hundred. If you are running a small business or selling handmade goods, the hours you get back are the entire reason to automate at all. For Amazon and bulk sellers, the gain is also dodging the CSV upload errors that come from hand-typing the same manufacturer details thousands of times.

Start with one product. Run the workflow once, see the file it produces, and decide from there. The full pillar guide on GPSR covers the rest of your obligations, and the compliance checklist is a good way to confirm you have not missed anything before you list.

This article is general guidance, not legal advice. Confirm your obligations with a qualified advisor or your Responsible Person.