An online listing is one of the places where the customer should receive the required information before purchase. The GPSR sets out the minimum scope of data for distance sales. A marketplace or shop may have its own field layout, but responsibility for the accuracy of the data for a specific product does not disappear once it has been entered into a form.
What information to prepare for a distance listing
The listing should contain data that makes it possible to identify the manufacturer and, where the manufacturer is not established in the Union, the relevant responsible person in the EU as well. Identification of the product is needed, including an image and information that allows it to be recognised, along with any warnings or safety information required for the product.
The scope should not be created at the level of the whole brand without checking the variant. Colour may not matter, but a different capacity, material, power supply or age group may change the information. Listing data must therefore be linked to the SKU being sold and to the current revision of the documentation.
Manufacturer and responsible person data
The trade name should lead to a real entity, and the postal and electronic addresses must be usable for contact. If the manufacturer is outside the EU, the responsible person's details cannot be an arbitrary European warehouse address. You need to know the basis on which they hold the role and the scope of products covered.
In the catalogue it is worth separating the manufacturer, importer, responsible person and commercial supplier. Merging these fields into one causes errors with products from different supply chains. Each relationship should have a source and a date of confirmation.
Identifying the correct product
A marketing title is not always enough. A model, type, batch number or other identifier is needed where applicable, along with an image that matches the product being offered. The internal SKU should lead to the data used in the listing and to the correct documentation.
If a seller merges listings from several suppliers, they must take care not to assign one set of data to products that are only apparently identical. Different factories, materials or designs may mean separate evidence and different safety information.
Warnings in a readable form before purchase
Safety information should be easily accessible in the listing itself. Placing it only in a low-resolution image or in a file that has to be downloaded may limit readability. The content should be consistent with the information supplied with the product.
It is worth keeping a separate source field for the approved content and a mapping to the sales channel field. This makes it possible to detect that a listing still contains an older version. If a marketplace shortens or formats the content, the company should check the final view, not just the result of sending the data.
Preparing data for Allegro
Allegro provides sellers with mechanisms for presenting information related to the GPSR. Field names and the process may be updated, so the platform's current documentation should be used before publication. The internal catalogue should remain the source from which the required data can be prepared without retyping it from emails.
At the current stage, GPSR / PPWR can be used for importing and processing data and for checking completeness. If the Allegro module is marked as in preparation, it should not be presented to the customer as a working export. An honest separation of the functions that are available from those that are planned prevents operational and marketing errors.
Online shop and structured data
Your own shop gives you more control over the layout, but it requires a place to be designed for the safety data. The information should work on desktop and mobile, for variants and language versions. You also need to make sure that the cache system does not retain old content after an update.
It is worth testing the page as the customer sees it: before adding to the basket, without logging in and on a small screen. Checking the admin panel alone does not confirm that the information is readable in the public listing.
Pre-publication check process
- confirm the company's role and the responsible person,
- identify the exact SKU and variant,
- check the manufacturer's data and contact addresses,
- link the warnings to the current risk assessment,
- choose the correct market language,
- compare the listing content with the instructions and label,
- record the date and the approving person,
- view the final listing as a logged-out customer,
- save the result and fix all gaps before selling.
Updating multiple channels
A change to the source information should point to all the listings it affects. With multiple channels, a status is useful: to update, prepared, published, checked. Marking the data as sent is not enough if the final view has not been confirmed.
A controlled system reduces repeated retyping and preserves a record of decisions. It does not, however, release the seller from verifying the channel's requirements and the accuracy of the public listing.