EU GPSR online listing release workflow

Start the release by identifying the exact product version that will appear online: model, variant, bundle contents, software or firmware state, age or user limitations, EU countries of sale, seller role, and whether another Union product regime adds more specific rules. For GPSR purposes, the listing still needs a responsible economic operator established in the Union when the product is placed on the Union market.

Do not treat a listing refresh as copy-only work when a new supplier, component, software function, private-label brand, bundle, or safety-relevant modification changes the product facts. GPSR treats a person that places a product under its own name or trademark, or substantially modifies a product in a safety-relevant way, as taking on manufacturer obligations for that product.

For each product page, the release owner should compare the live preview against the GPSR distance-sales fields before the listing is approved. The same core fields also need to be accepted by marketplace listing tools, because marketplace providers must design interfaces that enable traders to provide and display this product-safety information.

The listing should make safety information visible or easily accessible before purchase. Do not hide warnings, age restrictions, use limitations, or required languages inside images, expandable marketing modules, or files that are hard to reach from mobile product pages.

The listing can pass only when the safety file is complete enough for a product-safety reviewer or market surveillance authority to understand why the product is considered safe. The evidence should sit behind the listing approval, not inside the marketing copy, and should be versioned to the exact online product offer.

Manufacturers must carry out an internal risk analysis and draw up technical documentation before placing products on the market. The evidence pack should therefore connect the product page to the risk analysis, applied standards or other safety criteria, test reports where relevant, warnings, instructions, traceability identifiers, and supplier or downstream records.

Before publication, confirm that the selling channel can actually display the GPSR fields and that the marketplace account has product-safety processes for notices, authority orders, dangerous-product alerts, and consumer notifications. If the product is sold through a marketplace, the trader should test the listing preview exactly as a consumer will see it.

Marketplace providers have product-safety duties of their own, including Safety Gate Portal registration, single points of contact, internal product-safety processes, notice processing, cooperation with authorities and economic operators, and action on dangerous-product offers. A trader release checklist should therefore capture both the trader's submitted fields and evidence that the marketplace page displays them correctly.

Publication is not the end of the GPSR workflow. The listing owner should monitor consumer complaints, support tickets, marketplace notices, supplier updates, Safety Gate alerts, test failures, and accident reports, then route safety issues to the manufacturer, importer, responsible person, marketplace provider, and market surveillance authority path as applicable.

If the product is dangerous or an accident has occurred, the team should use the Safety Business Gateway route required for economic operators and marketplace providers, prepare consumer-facing safety warnings or recall notices where needed, and keep the live listing aligned with the corrective action.