Blog

GPSR complaints: the register, accident reports and recalls

Under the GPSR you must let customers report safety problems, investigate each report, log it in a complaints register and report serious accidents to the EU.

By Andreas Du Rietz, founder of Replyful ·

Does this apply to you?

Yes, if you sell products to consumers in the EU under your own brand. The GPSR treats you as the manufacturer, even if a factory makes the product for you. It has applied since 13 December 2024.

Enforcement is rising. Safety Gate, the EU's alert system for dangerous products, logged a record 4,671 alerts in 2025, 13% more than in 2024. Cosmetics made up 36% and toys 16%.

What a complaint must go through

  1. The customer reports it

    Through a channel you publish: email, phone or a page on your site. It must be accessible to people with disabilities.

  2. You investigate

    Which product and batch, what happened, and whether anyone was hurt.

  3. You log it in the register

    Together with any recalls and fixes for that product. Only the personal data the investigation needs.

  4. Someone was seriously hurt: report it

    Through the EU's Safety Business Gateway, without undue delay.

Every safety complaint ends up in the register. Only an accident that seriously hurt someone also goes to the EU.

The complaint arrives as a normal ticket

Customers don't write "I'd like to file a safety complaint". They write "the charger got really hot" or "my daughter got a rash", often inside a return request. If support handles it as a return, the register stays empty and the accident goes unreported.

So treat safety words as a trigger: hot, burn, smoke, rash, swelling, a small part that came off. When one shows up, ask the same three things every time:

  • The product and batch number. The register is per product, and a batch tells you how far a problem reaches.
  • A photo. Of the product and the batch label.
  • Was anyone hurt? If yes, how badly. This decides whether you report to the EU.

What goes in the register

One line per complaint: the date, the product and batch, what happened, any injury, and what you did about it. Your recalls and corrective actions go in the same register. Read it per product. Three "got hot" complaints on one charger in a month is a pattern to act on, before an authority spots it for you.

If you have to recall

Contact every buyer you can identify directly, using your order data. Title the notice "Product safety recall". Offer at least two of repair, replacement or a refund of at least the price paid, at no cost to the customer.

How Replyful handles it

In Replyful, you write a process in plain language, and the AI agent follows it whenever a customer describes a safety problem in chat or email. This is the whole setup:

Name

Product safety

When to use it

The customer says a product got hot, caused a rash or injury, or lost a small part.

Steps

  1. Ask which product it is and for the @batch_number on the label.
  2. Ask for a photo of the product and the batch label.
  3. Ask whether anyone was hurt, and save the answer as @injury.
  4. Tell the customer our team will look into it, then hand over with @transferToHuman.
@batch_number and @injury are data fields: the agent asks for them and saves the answers on the ticket, where your team sees them.

A "Product safety" topic labels those tickets automatically, so filtering the inbox by it gives you the register. Automatic topics are on the Pro and Enterprise plans.

See how your support is really doing.

Not better in 90 days? Your subscription back.