Amazon GPSR Bulk Upload: Contacts, Safety Files and ASINs (2026)
2026-09-28
Amazon documents bulk spreadsheet uploads for GPSR warning and safety information, but that does not establish a universal flat-file route for registering full manufacturer and EU Responsible Person contacts. Prepare those contacts first, match your seller SKUs to ASINs, and use the current template for the relevant product type and store. The EUSellKit catalogue helps organise the inputs and per-SKU gaps before submission.
Does the 2026 guide date change the GPSR application date?
No: GPSR has applied since 13 December 2024. The year in this title is the guide year. Article 52 of Regulation (EU) 2023/988 establishes the application date; Article 19 addresses the information in online offers. Updating Amazon fields does not replace product safety work or physical labelling.
How do you add manufacturer and RP information across many ASINs?
First establish the full contact records in Seller Central, then associate the correct records with your offers using the options available in your account. Amazon's GPSR developer announcement directs sellers to enter manufacturer/RP contacts before submitting GPSR attributes. It identifies Account Health as the place to find affected brands and offers.
Group your working data by actual manufacturer and RP coverage. Keep names, postal addresses and emails together, and retain a SKU-to-ASIN mapping. A brand name alone is not a full manufacturer record. For the meaning of each contact, see Amazon EU compliance fields.
Verification limit, 28 September 2026: We could verify Amazon-authored public guidance, but not every signed-in menu or a universal spreadsheet header for uploading full contact records. The linked manufacturer, RP and safety submission help returned a JavaScript shell during verification. Use the current help inside your account; we cannot promise a particular brand-wide selection control or bulk contact-import button.
Which safety-information spreadsheet route is documented?
Amazon's GPSR team documents a catalogue-upload route for safety submissions. Its official bulk-upload instructions describe Catalog → Add products via upload, downloading a spreadsheet for one product type and one store, and completing its compliance section. Submit through the spreadsheet-upload workflow and inspect its processing status. These are published instructions, not a guarantee that your account uses identical menu labels today.
Use the newly downloaded workbook's field definitions and allowed values. Our recommended working sequence is to prepare a small representative batch, save a copy of the file, record the submission identifier, and resolve row-level errors before expanding the batch. Keep unrelated price, quantity and offer changes out of this compliance task unless you intend to update them too.
Which GPSR attribute names can you verify?
Amazon publicly names the following programmatic attributes; they are not guaranteed Excel headers. Its developer documentation identifies:
| Attribute | Documented purpose |
|---|---|
gpsr_manufacturer_reference.gpsr_manufacturer_email_address |
Manufacturer email reference at ASIN level |
dsa_responsible_party_address |
Responsible-party email at SKU level |
compliance_media |
Document details, including type, language and source URL |
gpsr_safety_attestation |
Safety-attestation attribute; read its current definition before using it |
Retrieve the current product-type schema for an API integration, or use the current workbook for a manual upload. A field called “address” should not be assumed to accept a full postal-address block. Do not copy the EUSellKit CSV headers into Amazon and expect an accepted feed.
What should your safety document contain?
It should describe the actual product and the safety information relevant to its intended and foreseeable use. Check that the SKU/model, materials, warnings and language correspond to the item being sold. Reusing a document is sensible only when its content genuinely applies to every mapped product.
Amazon's official safety-document response lists accepted document categories including safety information, instructions for use and user manuals. It also identifies safety-image variants PS01–PS06. Choose the route and document type requested by your current workflow; do not submit an unrelated certificate just to fill a slot.
Never use a safety attestation as a shortcut around necessary warnings. A CSV gap check cannot decide that your product requires no safety information. See our risk assessment guide and Amazon safety-document guide.
How does EUSellKit fit into the bulk-upload process?
Use it to prepare and review data before adapting it to Amazon's format. Save a manufacturer/RP profile, import SKU rows, inspect missing/review items and export marketplace GPSR fields with Seller Pro. Manufacturer/RP row overrides let you handle exceptions without copying the wrong shared contact.
The catalogue allows 5 SKUs free; Seller Pro costs €19/month and supports 2,000 SKUs plus bulk CSV export. The export is a preparation file, not an Amazon-native feed or automatic submission. EUSellKit supports only low-risk, non-electrical categories. Toys, electronics, batteries, cosmetics, food, food-contact items, children's products, PPE, medical products and machinery are outside scope.
What should you check after uploading?
Check both the submission result and the customer-facing offer. Reconcile every submitted SKU with processing errors, outstanding compliance requests and the live listing for each target market. Confirm the displayed contact, product identity and safety information against your source records. Keep the submitted file and correction history so later edits can be traced.
What do sellers ask about Amazon GPSR bulk uploads?
Does one upload cover every EU store?
Do not assume so. Prepare and verify submissions for each target store using its current template and language requirements.
Can I upload the EUSellKit CSV directly to Amazon?
It is not an Amazon-native template. Map its values into the current Amazon workbook or a properly implemented integration.
Does a completed upload prove GPSR compliance?
No. File processing, marketplace review, visible listing information and actual product compliance are separate checks. EUSellKit evaluates entered data, not live listings, and provides no certification.
This guide is general information, not legal advice.
Your next EU order shouldn't be a compliance gamble.
Check my product →EU rules change. Be the first to know.
Get a short email when GPSR or marketplace compliance requirements change — no spam, unsubscribe anytime.