Skip to content
Compliance

GPSR Marketplace Data: Automate Kaufland and Amazon

Which GPSR product safety fields Kaufland and Amazon require, how to send them via Seller API and SP-API, and how to keep them in your PIM or ERP.

Written by
Md AshikSenior Software Engineer, Artisan Dojo
Published
Reading time
8 min read
Quick summary30-second read
  • GPSR applies from 13 December 2024 and requires manufacturer details, an EU responsible person where needed, product identification and safety information on listings.
  • Kaufland now accepts GPSR contacts through Contacts endpoints in Seller API v2 and is discontinuing the older product_safety_contact attribute.
  • Kaufland contacts can be set per manufacturer name or per EAN, and product-level contacts override the manufacturer level.
  • Amazon takes GPSR attributes through the Listings Items API or JSON_LISTINGS_FEED, but contacts must exist in Seller Central first.
  • Model manufacturers and responsible persons as their own records in your PIM or ERP and push changes to every marketplace automatically.

GPSR marketplace data is the product safety information that Kaufland, Amazon and other marketplaces now require on every non-food listing in the EU: who the manufacturer is, who the EU responsible person is, how to reach them, and which warnings and safety documents apply. Both marketplaces accept it through their APIs, so you can send it automatically instead of typing it into seller portals. The data should live once, in your PIM or ERP, and flow from there to every channel.

This guide covers what the regulation asks for, which fields Kaufland and Amazon use, and how to automate it. It is written from the integration side and is not legal advice.

What does GPSR require from marketplace sellers?

The General Product Safety Regulation, Regulation (EU) 2023/988, applies from 13 December 2024. For distance sales, including marketplace listings, Article 19 says an offer must clearly show at least:

  • Manufacturer details. The manufacturer's name, registered trade name or trademark, plus a postal and electronic address.
  • The responsible person, if the manufacturer is outside the EU. Their name, postal address and electronic address. Article 16 says a product may not be placed on the EU market unless an economic operator established in the Union is responsible for it.
  • Product identification. Information that identifies the product, including a picture of it, its type and any other identifier.
  • Warnings and safety information. Anything that must be on the product or packaging, in a language consumers can easily understand, as decided by the member state where the product is sold.

For a seller with thousands of SKUs, that is a data problem, not a one-off form: every product needs these values, and each marketplace models them differently.

Which GPSR fields do Kaufland and Amazon use?

Here is how the required data maps to each marketplace, and where it should live on your side. Field names come from Kaufland's Seller API documentation and Amazon's SP-API changelog; always check the current docs before you build.

Required dataKauflandAmazonWhere it lives in your PIM/ERP
Manufacturer name and addressContacts API, contact type manufacturer, set per manufacturer name or per EANEntered in Seller Central, then referenced via gpsr_manufacturer_reference.gpsr_manufacturer_email_address (ASIN level)Manufacturer or brand master record, linked to each product
Manufacturer email or websitecontact_info.email_address or website_url (at least one)The manufacturer email, which must match what is in Seller CentralSame manufacturer record
EU responsible personContacts API, contact type eu-responsible-person, country must be an EU member stateEntered in Seller Central; dsa_responsible_party_address at SKU levelSeparate "responsible person" record, linked per manufacturer or product
Product identification and pictureEAN, model number, category and product images in product dataStandard listing attributes and imagesProduct master: GTIN, model, images
Warnings and safety informationsafety_guidelines attribute, in the marketplace's national languagecompliance_media with content_type safety_information or user_manual, plus content_languageLocalized text fields or documents per product and language
Safety documents and certificatessafety_data_sheet and ce_certificate attributes (image or PDF URL)compliance_media documents, linked by URL (source_location)Digital asset management or PIM document fields
Safety attestationNot applicablegpsr_safety_attestation (boolean)A flag on the product

How the Kaufland product safety contact works

Kaufland originally took GPSR contacts as a product attribute, product_safety_contact. It now has dedicated Contacts endpoints in Seller API v2 under /v2/contacts, and its Seller University says the old attribute is being discontinued. If your integration still writes product_safety_contact, plan the move now.

The Contacts API has two levels:

  • Manufacturer level, addressed by manufacturer name. A contact set here applies to all of that manufacturer's products. Kaufland resolves the name against its catalog, including capitalization variants and synonyms.
  • Product level, addressed by EAN. A contact set here overrides the manufacturer-level contact for that product.

Each contact has a name, a postal_address (street, house_number, postal_code, city, country_code) and contact_info with an email address, a website or both, plus an optional phone number. The PUT calls fully replace the contact and are idempotent, which makes them safe to retry.

One detail matters for expectations: for the manufacturer type, Kaufland picks one contact from all sellers' submissions to show on the product page, so yours may not be the one displayed. Your EU responsible person is always shown if you set it.

Safety information, safety data sheets and CE certificates are still regular product attributes (safety_guidelines, safety_data_sheet, ce_certificate) sent through product data upload. For more on Kaufland's product and offer model, see how to connect Kaufland to your ERP.

How Amazon GPSR attributes work in SP-API

On Amazon, GPSR data travels with the listing through the Listings Items API (v2021-08-01) or the JSON_LISTINGS_FEED feed type. Amazon's changelog names these attributes:

  • gpsr_manufacturer_reference.gpsr_manufacturer_email_address, at ASIN level.
  • dsa_responsible_party_address, at SKU level, for the responsible party.
  • gpsr_safety_attestation, a boolean.
  • compliance_media, for documents such as safety information, user manuals and instructions for use, each with a language code and a URL. Google Drive and Dropbox links are not accepted.

There is a prerequisite: the manufacturer and EU responsible person contact details must already exist in Seller Central or Vendor Central. The attributes reference those records rather than carrying the full address, so the email you send must match exactly.

Not every product type has these attributes. Call getDefinitionsProductType for each product type you sell and read the GPSR attributes from the returned JSON schema. Validate against that schema before you submit. Our Amazon SP-API integration guide covers the Listings Items API and feeds in more detail.

Top tip

Model the manufacturer and the EU responsible person as their own records in your PIM or ERP, not as text fields on each product. Then one correction to an address updates every product that uses it, and you can push it to Kaufland once at manufacturer level instead of thousands of times per EAN.

How to automate GPSR data for marketplaces, step by step

1. Make your PIM or ERP the single source

Decide where GPSR data is owned. Usually that is the PIM if you have one, otherwise the ERP. Add:

  • A manufacturer entity with legal name, postal address, email and website.
  • A responsible person entity with the same fields, and an EU country.
  • A link from each product to its manufacturer and, where needed, its responsible person.
  • Localized safety text per language you sell in, and document fields for manuals, safety data sheets and certificates, stored as stable public URLs.

2. Fill the gaps from suppliers

Much of this data comes from suppliers and brands. If you already receive product data by feed, extend the mapping to include manufacturer contacts and safety documents, and flag products where the supplier sends nothing. Our post on supplier feed automation covers how to normalize feeds before they reach your catalog.

3. Map to each marketplace

Write one mapping per channel:

  • Kaufland: push manufacturer contacts and EU responsible persons through the Contacts API at manufacturer level, use product-level contacts only for exceptions, and send safety_guidelines and document attributes with product data in each storefront's language.
  • Amazon: make sure the contacts exist in Seller Central, then send the GPSR attributes and compliance_media with your listings, validated against the product type schema.

4. Sync changes, not everything

Send updates when a manufacturer address, responsible person or safety document changes, plus a scheduled full reconciliation. Because Kaufland's contact PUT calls are idempotent and Amazon's listing patches are partial updates, retries are safe if you design for them.

5. Check what the marketplace actually has

Kaufland offers a GPSR report in the seller portal under product data reports, with an is_compliant flag and a reason per item. On Amazon, read back listing issues through the Listings Items API. Feed both into one list of non-compliant SKUs that someone actually works through.

6. Monitor and alert

Alert when non-compliant items rise, when a contact push fails, or when a marketplace retires a field, as Kaufland did with product_safety_contact.

Common mistakes

  1. Typing GPSR data into seller portals by hand. It works for the first hundred SKUs and drifts from your catalog after that.
  2. Storing contacts as free text on every product. Every address change becomes a bulk-edit project.
  3. Mixing up manufacturer and responsible person. They are different roles with different fields on both marketplaces.
  4. Sending an Amazon manufacturer email that does not match Seller Central. The reference only works if the contact already exists there.
  5. One language for all storefronts. Safety information must be in a language consumers in each country can understand.
  6. Building on a deprecated field such as Kaufland's product_safety_contact without a migration plan.

Frequently asked questions

Does GPSR apply to sellers outside the EU?

It applies to products sold to consumers in the EU, wherever the seller is based. If the manufacturer is outside the EU, there must be an economic operator established in the EU responsible for the product, and its details must appear in the listing.

What is the Kaufland API product safety contact?

It is the GPSR contact data Kaufland needs for the manufacturer and the EU responsible person. It was first a product attribute, product_safety_contact. Kaufland now provides Contacts endpoints in Seller API v2, set per manufacturer name or per EAN.

Can I bulk upload GPSR data to Amazon?

Yes. Through SP-API you can send GPSR attributes with the Listings Items API or in bulk with JSON_LISTINGS_FEED. Amazon also offers inventory file templates in Seller Central for manual bulk uploads.

Does my ERP connector handle GPSR already?

Many multichannel tools and ERP connectors, including those for systems like JTL or plentymarkets, have added GPSR mappings. Check that yours uses the current Kaufland Contacts endpoints and supports the Amazon attributes for your product types. A custom integration makes sense when your data model or channel mix goes beyond what the connector maps.

What happens if GPSR data is missing?

Kaufland says offers without the required manufacturer or responsible person information are excluded from sale. Amazon requires sellers of non-food products in its EU stores to provide GPSR information, so check listing issues in Seller Central or through the Listings Items API for affected SKUs.

Need help automating GPSR data?

We build and maintain marketplace integrations that send product safety data from your PIM or ERP to Kaufland, Amazon and other channels, alongside orders, stock and prices. See our Kaufland API integration, Amazon SP-API integration and supplier feed integration services, or book a free 30-minute call below to talk through your setup with the engineer who would build it.

Need help with this?

Describe your project. Get a reply from an engineer.

Which marketplaces or platforms are involved?
What do you need?
How should we get back to you?

We use your details only to reply to this inquiry. See our privacy policy.

Keep reading

Related guides

All guides
MessageFree 30-min call