Skip to main content

GPSR in online stores: organise product information correctly

Manufacturer details, responsible persons and safety information: how retailers can structure GPSR information in stores and product data.

E-commerce strategy Published: Updated:
AI-generated article graphic: GPSR in online stores — manufacturers, data and safety.

Quick answer

The EU General Product Safety Regulation (GPSR) has applied since 13 December 2024. Online offers for products within its scope must visibly include information such as manufacturer details, product identification and required safety warnings. The information needed also depends on your role and the product. A module can help maintain data but does not replace checking its accuracy.

For retailers, implementation often starts with a practical question: where are manufacturer details stored, and who keeps them current? Copying this information into individual descriptions means repeating every update. A reliable data process reduces that work.

What information does the GPSR require in an online offer?

Article 19 of Regulation (EU) 2023/988 specifies the manufacturer’s name, postal address and electronic address. Where the manufacturer is based outside the EU, corresponding details of the responsible person in the EU are also needed. The product must be identifiable, and required warnings or safety information must be visible in the appropriate language. Scope and product-specific legislation need to be assessed separately: the regulation does not apply indiscriminately to every type of goods.

How does the information reach your store?

Choose an authoritative source for each piece of information. For a small catalogue, this may be the store itself; with several sales channels, a PIM or inventory system may be more appropriate. The key is to avoid independent updates in several places. Assign each product to its manufacturer and keep a clear record of any separate responsible person.

  • Contact suppliers: request the information and documents needed for each product.
  • Map the data: maintain manufacturer details, responsible persons and product identifiers separately.
  • Check languages: provide information for the markets you actually serve.
  • Test the display: check product pages, mobile views and variants.
  • Coordinate channels: supply the store, marketplaces and exports from the same source.
  • Track changes: assign responsibilities and schedule further checks.

What should a PrestaShop, Shopify or Shopware extension do?

Use a small test catalogue to check whether the chosen module or app handles the required data properly. Important points include imports, variant mapping, multilingual content and visible output in your theme. Also ask how data can be exported if you switch extensions.

An extension can provide fields and display options. That does not establish whether entered contacts are correct or warnings fit a particular product. Nor should you assume a marketplace feed automatically transfers every store field.

What issues can acceptance testing reveal?

For example, compare a product from an EU manufacturer with an imported product. Then check a variant and a second language. Is the information displayed there too? On mobile, is it clear which product a safety warning concerns? Does a correction in the authoritative data source reach the store display?

These sample checks are a practical starting point. Larger catalogues also need systematic checks for missing or contradictory entries. A missing required value should be flagged in the data process before the product is approved.

What does this mean for Swiss retailers?

Swiss retailers selling into the EU need to assess how their offers target the EU market. The specific circumstances matter, not just the company’s registered office. Clarify product responsibility and legal obligations with qualified advisers. At sjmedia, we support the technical implementation, data flows and store display.

Our guide to optimised product pages explains how to combine required information with a clear product presentation.

Sources & further reading

Author & technical review

Written by

Jochen Schmid
Managing director

Initial consultation · Presta · SEO · GEO · Ads · Klaviyo · Live Shopping · CRO · Migration

Technically reviewed by

Damian Rutkowski
Project manager / developer

Presta · Shopware · API · Support