GPSR: assignments and inheritance

An assignment says which products get which data. One assignment can apply to all products, a category (with its subcategories) or a brand (a value of the brand attribute, by default manufacturer or brand).

1. Add an assignment

Catalog › GPSR › Assignments

Click Add assignment, choose All products, Category or Brand (attribute value) under Scope, then the category or brand.
For Manufacturer and EU responsible person choose Inherit (the value comes from a higher level), Set (you pick a record) or None (not needed) (for example a manufacturer in the EU needs no responsible person).
Optionally tick pictograms, enter warnings and instructions for safe use (one paragraph per line, per store view) and add documents (PDF, PNG, JPG or a link).
If the products of this assignment must have warnings, switch on Products must have warnings: the report will mark products without warnings.

2. How a product inherits the data

Each role (manufacturer, responsible person) is decided on its own, in this order:

the product (fields in the GPSR group on the product),
the brand,
the category (the deepest wins; at equal depth the lower Priority),
all products.

Warnings, instructions, pictograms and documents add up over all levels by default. If you want the narrowest level only, switch off Merge warnings and pictograms in the settings.

When a product is in two categories with different assignments, the module picks one by the rule above and marks the product as a category conflict in the report.

3. On the product: overview and override

Catalog › Products

The product has a GPSR group. Its title shows the status (complete, manufacturer missing, not required), and above the fields is an overview: what the customer sees and where each value comes from.

The inheritance overview on a product: manufacturer and responsible person inherited from the category, warnings, pictograms and documents — The inheritance overview. The Source column says whether a value comes from the product, the brand, the category or all products.

Manufacturer and EU responsible person: empty means inherit, a chosen record overrides the inheritance, None hides the block.
Model (identification) and Batch or serial number: the product identification (an empty model shows the SKU). The EAN is read from the attribute you choose in the settings.
Additional warnings of the product and instructions: per store view, added to the warnings of the category and the brand.
GPSR not required: for example services or gift cards. The section is not shown and the product does not count as missing data.

If you save a product without a manufacturer, Magento warns you but does not block the save.

4. What the customer sees

The Safety information section on the product page with pictograms, manufacturer, responsible person, identification, warnings and documents — The section under the add to cart button. Without a manufacturer the section is not shown.

The product fields also work with the standard product import and the Update attributes mass action in the product grid. For an import by SKU with checks, see GPSR: CSV import.

Was this article helpful?

Badges and labels on productsExtensions Product questions and answersExtensions Product enquiry formExtensions Product attachments (data sheets, manuals)Extensions Back in stock notificationExtensions

Cookie name	Cookie purpose
PHPSESSID	Preserves the visitor's session state across page requests.
magelan_geo	Remembers that the visitor closed the suggestion of the other language version of the store, so it is not shown again.
form_key	Protects visitor's data from Cross-Site Request Forgery Attacks.
guest-view	Stores the Order ID that guest shoppers use to retrieve their order status. Used in “Orders and Returns” widgets.
login_redirect	Preserves the destination page the customer was loading before being directed to log in.
mage-banners-cache-storage	Stores banner content locally to improve performance.
mage-cache-sessid	The value of this cookie triggers the cleanup of local cache storage.
mage-cache-storage	Local storage of visitor-specific content that enables ecommerce functions.
mage-cache-storage-section-invalidation	Forces local storage of specific content sections that should be invalidated.
mage-messages	Tracks error messages and other notifications that are shown to the user, such as the cookie consent message, and various error messages. The message is deleted from the cookie after it is shown to the shopper.
private_content_version	Appends a random, unique number and time to pages with customer content to prevent them from being cached on the server.
section_data_ids	Stores customer-specific information related to shopper-initiated actions such as display wish list, checkout information, etc.
user_allowed_save_cookie, cookie_consent	Stores the user's cookie consent state for the current domain.
X-Magento-Vary	Configuration setting that improves performance when using Varnish static content caching.

Cookie name	Cookie purpose
product_data_storage	Stores configuration for product data related to Recently Viewed / Compared Products.
recently_compared_product	Stores product IDs of recently compared products.
recently_compared_product_previous	Stores product IDs of previously compared products for easy navigation.
recently_viewed_product	Stores product IDs of recently viewed products for easy navigation.
recently_viewed_product_previous	Stores product IDs of recently previously viewed products for easy navigation.
_fbp	This cookie is installed by Facebook to store and track visits across websites.

Cookie name	Cookie purpose
dc_gtm_*	Throttles request rate when Google Analytics is deployed with Google Tag Manager.
_ga, _gat, _gid, _ga_, _gat_	This cookie is installed by Google Analytics. They are used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in a way that does not directly identify anyone.