How do I map Responsible Person and manufacturer fields through a feed tool or inventory system?

Default hero background
Uncategorized
Jason van de Zande

Map the Responsible Person and manufacturer fields by treating them as two separate, persistent product attributes in your feed tool or inventory system: the manufacturer identifies who made the product, while the GPSR Responsible Person identifies the EU-based economic operator responsible for specific compliance tasks. Then push both sets of details consistently to every marketplace and label where required.

This approach matters most for non-EU brands and cross-border e-commerce sellers because marketplaces increasingly validate these attributes before allowing EU listings. Clean field mapping also helps you respond quickly if EU authorities request EU market surveillance documentation.

The sections below define each role under the General Product Safety Regulation (EU) 2023/988 (GPSR), show practical GPSR Responsible Person field mapping steps, and explain what records to store.

What do “Responsible Person” and “manufacturer” mean under EU GPSR, and why do marketplaces ask for both?

Under GPSR, the manufacturer is the business that manufactures a product or has it designed or manufactured and markets it under its name or trademark, while the Responsible Person is an EU-based economic operator designated to perform specific compliance support tasks for products placed on the EU market. Marketplaces ask for both because they need clear accountability and a reachable EU contact for enforcement and safety checks.

These two fields are not interchangeable. The manufacturer remains the origin of the product and its safety responsibilities, while the Responsible Person provides an EU point of contact and helps ensure required information and documentation can be made available to authorities on request.

Marketplaces request both fields because they must reduce the risk of non-compliant listings and because enforcement has become more systematic. If a listing lacks a valid EU Responsible Person, platforms may block, suppress, or flag the offer even if the manufacturer data is present.

One more nuance that affects how you store and route data: under the Market Surveillance Regulation (EU) 2019/1020 (MSR), the Responsible Person must inform the manufacturer about risks according to Article 4, but the Responsible Person role is not the same as an Authorized Representative role. An Authorized Representative is not mandatory, but a Responsible Person is required for many non-EU selling models where no other qualifying EU economic operator exists.

How do you map Responsible Person and manufacturer fields in a feed tool or inventory system?

Map GPSR Responsible Person field mapping by creating two distinct attribute groups in your system: one for manufacturer identity and one for EU Responsible Person identity, then linking both to each SKU and each EU marketplace channel. The key is consistency: the same legal entity names and addresses must flow from your source of truth into every feed export and listing template.

A practical, low-friction way to do this is to treat your inventory system as the master record and your feed tool as a transformation layer.

  1. Define your source of truth: choose one system where manufacturer and Responsible Person data is maintained and approved, then lock down editing rights.
  2. Create separate fields for each role, rather than overloading one field with combined text.
  3. Map at the right level: manufacturer is often brand-wide, while Responsible Person can be brand-wide or product line-specific depending on how you set up representation. Avoid mapping only at account level if you sell multiple brands.
  4. Normalize formatting: use the full legal entity name, complete postal address, and a monitored email address. Keep punctuation and line breaks consistent so marketplaces do not treat variants as mismatches.
  5. Set channel rules: each marketplace has its own attribute names and validation. Build channel-specific mappings that pull from the same internal fields.
  6. Validate before publishing: run a feed preview and spot-check multiple SKUs, including variations, bundles, and multipacks.

For sellers managing multiple catalogs, it helps to store manufacturer mapping as a reusable entity record and then reference it by ID in each SKU. Do the same for the Responsible Person record. This reduces errors when you update an address or contact email and need the change to propagate everywhere.

If your feed tool supports conditional logic, add rules such as: apply the EU Responsible Person fields only to EU destinations, and keep other regions untouched. That keeps your global catalog clean while meeting product feed compliance attributes required for EU listings.

What data format and supporting documentation should you store for Responsible Person and manufacturer attributes?

Store manufacturer and EU Responsible Person vs. manufacturer data as structured, version-controlled records: legal entity name, full address, and reliable contact details, linked to each SKU and to the technical documentation set for that product. Keep the data exportable in common formats such as CSV or JSON so you can respond quickly to EU market surveillance documentation requests.

For the attributes themselves, aim for structured fields rather than a single free-text blob.

  • Manufacturer fields: legal entity name, registered address, country, contact email, and where relevant the brand name used on the product.
  • Responsible Person fields: legal entity name, EU address, contact email, and internal reference ID that ties the RP record to the correct SKUs.
  • SKU linkage: SKU, model, batch or lot identifier where you use one, and the marketplaces where the product is listed.

For supporting records, GPSR focuses on being able to demonstrate product safety and provide information to authorities when requested. What you store depends on the product, but your system should at least support storing and retrieving:

  • Technical documentation that demonstrates how you assessed and managed product safety risks for the consumer product.
  • Product identification and traceability information such as model identifiers and supplier references.
  • Labeling and instructions files, including language versions used for EU consumers where applicable.
  • Accident and complaint handling records that help you track safety signals and corrective actions.

Operationally, treat documentation like a controlled library: keep a clear folder structure per SKU, record document versions and dates, and log who approved changes. This makes it much easier to answer authority questions quickly and consistently, especially when a marketplace escalates a compliance check.

How EARP helps with mapping Responsible Person and manufacturer fields for EU GPSR compliance?

We help you implement GPSR Responsible Person field mapping by giving you a clear, EU-based Responsible Person setup and a practical data model you can plug into your feed tool or inventory system without guesswork. We focus on accuracy, continuity, and fast response readiness so your listings can stay compliant across EU marketplaces.

  • Define the correct role split between manufacturer data and Responsible Person data so your listings match GPSR expectations.
  • Provide the EU Responsible Person details in a consistent format that is easy to map into product feed compliance attributes.
  • Set up documentation handling so required product safety materials are organized, stored, and available to authorities on request.
  • Support channel readiness by aligning your internal records with common marketplace attribute requirements.

If you want help validating your fields and getting your EU listings unblocked, contact EARP through our contact page or review our compliance services to see the fastest path to a clean, scalable setup.

Related Articles