Market surveillance across EU countries: same framework, different doors

The shared elements are the safety framework, the alert system, and the principle that a product safe in one market should be safe in all, because buyers face the same risks everywhere. The unshared elements are the practical ones: which authority is responsible for which product type, what language correspondence uses, what deadlines and forms apply, and how inspections are organised locally. A seller who expects identical handling in every country will be surprised; a seller who expects shared principles with local variation will not.

Safety Gate is the bridge between the two. An alert raised in one country becomes visible to others, so a seller may receive parallel contacts about the same product. Those contacts are separate cases, but they concern the same facts, and the seller's answers must be consistent across them, even where the format and language differ.

Language is a practical barrier, not a formality. Authority correspondence arrives in the national language, test reports may be written in it, and deadlines run regardless of translation time. A seller who waits for a perfect translation before acknowledging a message risks missing a deadline, while a seller who replies in the wrong language risks misunderstanding. The workable approach is a prompt acknowledgement in a language the authority accepts, followed by a careful translated response within the deadline.

The seller should also ensure product labelling and warnings match each destination market's language requirements, because a label correct for one country may be incomplete for another. Illustration: a seller of cleaning sprays ships the same label to three markets and learns one market requires an additional warning phrase, a gap found by that country's authority during a routine check.

Parallel cases need a simple case board: country, authority, reference, product and batch scope, deadline, contact person, and status. Without that board, deadlines blur, and a reply meant for one authority may be sent to another, or a narrowing of scope agreed in one country may be forgotten in another. The board does not need software; a single document, updated weekly during active cases, suffices for most small sellers.

Consistency across cases is the discipline that matters most. The fault description, the batch range, and the remedy should be the same everywhere, unless a genuine national difference, such as a different sales period, justifies a difference, in which case the difference should be explained. Inconsistent facts across countries undermine credibility faster than any single unfavourable finding.

The responsible person in the EU is a key contact for authorities, and in a multi country business that role becomes the hub through which many contacts flow. A functioning arrangement means the responsible person actually receives authority messages, understands the product, and can reach the seller quickly. An arrangement that exists only on paper, with messages going to an unmonitored inbox, will fail at the first real case.

The seller should test the arrangement before it is needed: send a test message through the contact route, confirm it reaches a person, and confirm that person knows the product range. That test takes minutes and prevents the classic failure of learning, during an active case, that the contact route never worked.

Working styles vary, in general terms, from highly formal written procedures to more conversational approaches, and from rapid sample testing to longer document reviews. Those differences reflect national organisation and resources, not a difference in the underlying safety goal. A seller should adapt the style of response to the authority in front of them, while keeping the facts and the remedy consistent.

Adapting style means matching formality, respecting deadlines as stated, and using the channel the authority specified, rather than imposing the seller's preferred channel. A seller who insists on phone calls with an authority that works in writing, or vice versa, creates friction that has nothing to do with the product and everything to do with process.

A case in one country is an early warning for the others, because the same product, batch and fault are usually present wherever the product was sold. A seller who waits for each country to act in turn will repeat the same conversation many times, while a seller who proactively reviews other markets after the first case, and corrects or notifies where needed, will often find later contacts shorter or unnecessary.

That proactive review should be recorded: markets checked, scope found, action taken. The record shows authorities in later cases that the seller already acted, and it shows the seller's own team that the product's full footprint was considered. A footprint considered once, thoroughly, beats a footprint discovered country by country under pressure.