Common GPSR mistakes online sellers make
After a year of GPSR enforcement, the same gaps appear over and over in marketplace suppressions and national-authority findings. Here are the seven most common — and what a clean fix looks like.
A year of enforcement under Regulation (EU) 2023/988 has produced a clear pattern. The 2025 enforcement summaries from BAuA (Germany), DGCCRF (France), AGCM (Italy) and the Dutch NVWA, combined with marketplace listing-suppression data, all point at the same recurring gaps. None of them are exotic — most are structural problems with how online sellers organised their data before GPSR landed.
This guide walks through the seven most common GPSR mistakes online sellers make, with the underlying cause and the clean fix for each.
1. Responsible Person on the website but not on the listing
The most common Article 19 finding by a wide margin. Non-EU sellers add the EU Responsible Person details to the website's "Legal" or "Imprint" page — which is correct — and then assume that satisfies the obligation. It does not. Article 19(1)(c) requires the Responsible Person's identity and contact to be visible to the consumer before the conclusion of the contract, which means on the product page, on every channel.
Fix. Render the Responsible Person block from a single data source on every product page, in every channel, in every destination language. Most Shopify themes need a custom metafield and a section binding; most marketplaces have a dedicated field that just needs to be populated.
2. Warnings translated for one EU market only
The product page shows the EN 71-1 small-parts warning in English. The seller ships to Germany, France, Poland and Spain. Article 9(7) and Article 19 require the warning to be in a language "easily understood by consumers in the country of sale" — for every destination, not just one.
Fix. Maintain a warnings dictionary keyed by SKU and destination market language. Push translations through your localisation pipeline alongside the rest of the listing copy. For marketplaces with per-locale listings (Amazon DE vs Amazon FR), the dictionary populates the right locale automatically.
3. Manufacturer identified as a marketing name
The listing says "Made by Aurora Co." A market-surveillance officer searches the EU and national company registries — and finds no Aurora Co. Aurora is a trading name; the underlying legal entity is "LumenCorp SAS". Article 9(5) and Article 19(1)(a) require the legal manufacturer name (or registered trade mark, but only if it is registered).
Fix. Use the format "BrandX, a trading name of LegalEntityCo SAS" or list the legal entity explicitly. If your trade mark is registered, you can list the trade mark with the registration number.
4. Generic technical file shared across SKUs
A common mistake for sellers with many variants: a single "general risk assessment" copy-pasted across every SKU. Authorities reject this. Article 9(2) is explicit that the risk assessment must reflect the actual product as placed on the market — including the foreseeable misuse risks specific to its category and target audience.
Fix. A short (2–4 page) per-SKU risk assessment is sufficient for most categories. Reuse boilerplate sections (e.g. category-level hazards) but require a per-SKU exposure-and-mitigation table that names the variant, the target user, and the residual risk after mitigations.
5. Incident-response SOP that points at an unmonitored inbox
The SOP exists. It says "report incidents to compliance@brand.com." That inbox is a shared mailbox that nobody monitors at weekends. The product safety officer who tries to reach you with a Safety Gate alert on a Friday afternoon gets no response by Tuesday. The authority concludes — correctly — that there is no functioning corrective-action capability.
Fix. Name a specific human owner (with a deputy), commit to a published decision window (24h to acknowledge, 48h to notify the Safety Business Gateway if confirmed unsafe), and put the SOP in the same place as the rest of your operational playbooks. Test it quarterly with a tabletop exercise.
6. Responsible Person on file but not registered in the EU economic-operator database
eBay validates Responsible Person appointments against the European Commission's economic-operator database. A few EU RP service providers are not in the database — usually because they are new entrants or have an irregular legal structure. The listing passes initial validation, then gets suppressed weeks later when the eBay system completes the registry check.
Fix. Before appointing a Responsible Person, confirm they are registered as an economic operator in the EU. Ask the provider for their EORI number and their registration in at least one Member State's product-safety registry.
7. Recall communications that do not follow the Implementing Regulation template
Implementing Regulation (EU) 2024/1435 prescribes the exact format of recall and safety-warning notices to consumers under GPSR. National authorities no longer accept free-form recall press releases. The notice must include specific elements (product identification, hazard description, action required, remedy choice between repair/replacement/refund, contact for queries) and use the visual template the implementing regulation specifies.
Fix. Pre-stage the recall notice template before you need it. Most authorities provide a downloadable template per Member State; Regonance bundles them into the incident response kit.
How Regonance helps
Regonance scans your existing product files and listings, identifies which of these seven gaps apply per SKU per channel, and outputs a prioritised remediation list — high-impact fixes first. Most sellers close the top three gaps inside a working week using the structured output. Run a free scan on a single SKU to see your current exposure.
What to do this week
- Audit the Article 19 fields on your top 20 EU-selling listings against the seven gaps above.
- Confirm your Responsible Person is in the European Commission's economic-operator database.
- Localise warnings for every destination market.
- Run one tabletop exercise on your incident SOP — find the failure modes before an authority does.
Glossary
Safety Gate Portal. The EU's rapid alert system for non-food dangerous products, accessible to authorities and the public.
Safety Business Gateway. The EU portal where economic operators notify authorities of unsafe products and corrective actions.
Implementing Regulation (EU) 2024/1435. The rule that prescribes the template and procedure for recall and safety-warning notices under GPSR.
EORI number. Economic Operators Registration and Identification number — the EU identifier used for customs but also relied on for product-safety registry checks.
Educational information, not legal advice. Consult the consolidated text of Regulation (EU) 2023/988 and the relevant implementing acts on EUR-Lex for the authoritative legal sources.
Frequently asked questions
What is the single most common GPSR mistake?+
Listing the Responsible Person on the brand's legal page but not on the product listing itself. Article 19 is product-specific and channel-specific — the information must render on every product page, in every destination market language. The 2025 BAuA and DGCCRF enforcement summaries both rank this first.
How aggressive is GPSR enforcement so far?+
Less aggressive on first-time gaps than on repeated failures. Most national authorities issue a written request first; non-response within the deadline (typically 10 working days) triggers escalation. Marketplace suppression happens faster — Amazon EU and Zalando suppress automatically when key fields are missing.
Will fixing the listing also fix marketplace suppression?+
Usually yes, but with a lag. Most marketplaces re-evaluate suppressed listings within 24–72 hours of the seller updating the compliance dataset. Some require manual reactivation via seller support.
Can I fix GPSR gaps retroactively for products already sold?+
Yes for the listing-side fixes (Article 19 information). No for the technical file — if you placed a product on the market without a risk assessment, that placement is non-conformant and an authority finding will reach back to it. Going forward you can clean up.
Run a free compliance readiness scan
Upload product files or a listing URL and see exactly which fields are missing.
Start free scanAI-assisted informational guidance. Not legal advice. Consult qualified counsel for your specific situation.