GPSR for Amazon FBA: Bulk Compliance for Large Catalogs

If you run a large FBA catalog in the EU, you have probably already met the wall. Amazon's automated blocks demand manufacturer and EU Responsible Person data for every active ASIN. The manual form approves your data fine when you do it one listing at a time. Then you try to do it for the rest of your thousands of SKUs and the bulk upload throws Error 5995, the Submit button greys out, and Seller Support sends back a copy-pasted tutorial on doing it manually.

One seller put the problem plainly: "We have thousands of SKUs! Doing this manually, one by one, will take months, if not a year. It is physically and mathematically impossible." That is the real bottleneck. The compliance data is correct. The platform is what is blocking you.

This guide covers the workflow that goes through: SKU-level submission, localized TSV templates, and direct-download document hosting. If you are new to the regulation itself, start with what GPSR is and come back. For the general marketplace picture, see GPSR on Amazon.

Why the bulk upload breaks for resellers

Amazon's catalog is built around Brand Registry. The brand owner controls the master ASIN content, and the parser treats safety attributes as brand-owned fields. When a high-volume reseller who is not the registered brand owner tries to push compliance data through a standard category file, the system flags it as an unauthorized content modification.

That is where Error 5995 and Error 8541 come from. Error 5995 fires when a non-brand owner tries to modify listing content reserved for the registry owner. Error 8541 is an attribute conflict, triggered when the value you submit differs from what is already in the catalog. Neither error means your data is wrong. They mean the parser is protecting brand-owned fields from an account it does not recognise as the owner.

As one seller described it: "When we try to use the bulk upload Excel files, it is a complete mess. There are hundreds of complicated columns, and it constantly throws errors (like Error 5995 and 8541) because we are not the Brand Owner, even though we are legally authorized to sell these products."

The frustrating part is that your legal duty does not change. You still have to provide manufacturer and Responsible Person data. The fix is not getting brand approval. It is submitting the data at a different level.

The fix: submit at SKU level, not ASIN level

Brand owners can apply compliance details across an entire brand. Resellers cannot, and that is fine, because you can upload safety information at the SKU level instead. SKU-level data maps to your specific inventory offering rather than the master catalog ASIN. That bypass is the whole game.

A widely-shared seller answer says it directly: "You don't need Brand Registry to submit Responsible Person and Manufacturer information at the SKU level. Use the Manage Your Compliance dashboard (separate from Account Health) to access submission options."

So the first correction is the tool you use. The Account Health page is where the Submit button freezes and greys out. The Manage Your Compliance dashboard is the regulatory portal built for processing safety files and manufacturer details outside the Account Health framework. Use that one.

The second correction is the file format and scope, which is where most of the remaining errors live.

Building TSV templates that don't error

Three rules turn the "Excel flat-file nightmare" into something that uploads cleanly.

One product type, one store, per file. You cannot use a master file to cover everything. As Amazon's own guidance puts it: "In order to upload product documents to your SKU, you must generate a spreadsheet for a single product type and a single store in the official language of that store (for example, German for Germany)." The template will let you tick more than one product type. Don't. Select exactly one.

Save as .TSV, not Excel. This single change resolves a lot of upload failures. "Save your completed file as Tab-Separated Values (.TSV) rather than Excel format. This often resolves upload errors. The system can handle large batches (up to 10,000 ASINs per file)." Tab-Separated Values is a plain-text format the parser handles more reliably than a binary Excel workbook.

Find the hidden columns. The fields you need sit at the far right of the purple-coded Safety and compliance section, and they are often hidden by default. Click the plus sign in the Excel header to unhide them. If a message above the Generate spreadsheet button offers the beta version of the product information template, opt in, because that version carries the GPSR attributes you need.

For a fuller walk-through of what belongs in each safety field across platforms, our technical documentation template guide breaks down the document set behind these columns.

The safety attestation shortcut

Not every product needs a full uploaded manual. For products that do not require explicit safety warnings, you can satisfy the requirement with the attestation flag: "If you want to provide a safety attestation, enter Yes in the gpsr_safety_attestation column."

That is a real time-saver across a large catalog. You reserve PDF manuals for products that genuinely need warnings or instructions, and use the attestation column for the rest. For where attestations fit in the wider GPSR picture, see our note on the safety attestation.

Hosting manuals: the direct-download URL trap

When a product does need a manual, the document column wants a URL, and this is where a lot of otherwise-correct files get rejected. Amazon's parser requires a direct public download link, one that immediately downloads the PDF. A browser-viewable share link will not pass.

The guidance is specific: "Use the URL where your image or product document is stored, which must be a direct download link (e.g. https://s3.amazonaws.com/my-store-public-files/installational_manual.pdf) rather than a sharable link that opens the PDF in a browser."

In practice that means a host like Amazon S3 that serves the file directly. Standard Google Drive and Dropbox share links open a viewer page first, so the validation engine rejects them. Set up a public S3 bucket (storage runs roughly €5 to €50 per month for a large catalog) and link to the raw object.

What this costs, and where the money leaks

The platform mechanics have a price tag. The numbers below are typical ranges, not Amazon fees:

• A bulk-compliance tool like ComplyGPSR runs around €99 to €499 per month as a fixed subscription, a low-to-moderate operational cost.
• S3 storage for your manuals sits at €5 to €50 per month, basically negligible.
• Virtual-assistant labour to prepare and submit a bulk batch can run €500 to €2,000 per batch, the heaviest line item if you outsource the file work.
• Listing deactivation is the one that actually hurts: every day a non-compliant ASIN is suppressed is a day of lost buy-box revenue and stock stagnation.

The math favours getting the file workflow right once over paying for repeated manual batches. The deactivation risk is what makes this urgent rather than optional.

Three misconceptions that waste weeks

"Brand Registry is required for bulk submissions." It is not. Resellers submit at the SKU level through Manage Your Compliance using category-specific templates. The block you are hitting is a level problem, not a permissions problem.

"Google Drive links are fine for manuals." They are not. The validation engine rejects any link that does not start an immediate file download. Host on S3 or an equivalent direct-download URL.

"I can update everything from one master file." No. One product type, one store, one language, per file. eBay lets sellers update compliance attributes directly on active listings through basic updates, but Amazon runs every safety submission through its brand validation parser, which is exactly why the per-type discipline matters. If you also sell there, our GPSR on eBay guide covers that lighter flow.

Don't forget the physical inventory

The catalog fix solves the listing block. It does not solve the boxes already sitting in EU fulfilment centres. If that physical inventory lacks the required manufacturer and EU Responsible Person details on or with the product, it can be suppressed or disposed of. You may need to apply compliant stickers, which for FBA stock usually means a removal order or a prep-service relabel before it goes back in.

The Responsible Person is a separate obligation from the data upload. Every product you place on the EU market needs a Responsible Person established in the EU, named on the product and traceable. EUProof generates the GPSR documents you need to fill these fields and stickers, including the data that goes into your TSV. We do not act as your Responsible Person; if you need that service, read how the Responsible Person role works and arrange one separately.

Get the documents ready before you touch the template

The TSV workflow is only as good as the data you put in it. Before you open a single template, you want a clean set of manufacturer details, Responsible Person information, and any required manuals or attestations per product type. That is the part EUProof handles: generate the GPSR document set for your catalog, then map it into the SKU-level fields.

Check whether your products are in scope with the am-I-affected tool, see what document the generator produces in our generate GPSR documents in 5 minutes walk-through, and start at the templates page when your data is in order.

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