Notifying an authority: when a product problem stops being an internal matter

Telling the regulator is a different obligation from fixing the fault

The corrective action, the containment, the analysis and the customer communication all belong to the operational response. Sitting alongside them, most consumer product regimes place a separate duty on businesses that know or have reason to believe something they placed on the market presents a risk: inform the relevant authority. That duty does not wait for the investigation to conclude, and it is not discharged by dealing with the problem competently in private. Treating the two as one activity is why notification frequently happens late, after the company has spent weeks establishing exactly what went wrong.

The trigger is a judgement made on incomplete information

Nobody gets a clean signal. What arrives is a cluster of warranty returns, an injury report of uncertain cause, a component test result that looks wrong, or a distributor mentioning something in passing. The threshold in these regimes is generally framed around knowledge or reasonable belief that a risk exists, not around proof, which means waiting for certainty is itself a decision with consequences. Companies that handle this well define in advance who convenes, what evidence gets assembled, and what kinds of signal automatically escalate, so the judgement is made by prepared people rather than by whoever is available.

The duty moves along the chain, and it does not stop at the maker

Importers, own-brand sellers and distributors typically carry obligations of their own, including passing on what they learn and cooperating with the authorities. A distributor who receives complaints and forwards none of them is a common weak point, and one worth addressing in supply agreements with an explicit reporting expectation. Conversely, a manufacturer whose customer notifies an authority first loses control of the narrative entirely. Agreeing in advance who notifies, in which markets, and how the parties inform each other is a contractual discussion best held while nothing is going wrong.

What the authority expects to receive

Notification formats differ, but the underlying questions are consistent: what the product is and how to identify affected units, what the risk is and how it was identified, how many units went where, what the business is doing about it, and who to contact. Answering those requires traceability data and a distribution list that already exists. Where they do not exist, the notification either goes in vague, which invites a wider intervention, or goes in late while somebody reconstructs shipment records. The information demand is why traceability discipline is really a preparedness measure.

Deciding not to notify is a decision that needs a record

Where a business concludes that a problem does not meet the threshold, the reasoning behind that conclusion, the evidence considered, who took part and when should be written down at the time. If the issue escalates later, the existence of a considered assessment is the difference between a defensible judgement and an apparent failure to engage. What triggers notification, to whom, in what timeframe and in what form is set by national law and by product-specific regimes that vary and change; this is orientation only, and the relevant authority and a qualified adviser should be consulted on any live matter.

Frequently asked questions

Do we still have to report if we have already corrected the problem and nobody was hurt?

Possibly, because the duty in many regimes attaches to the existence of a risk in products already on the market rather than to whether harm occurred or whether you have since acted. Having a corrective plan underway usually strengthens the position rather than removing the obligation. Absence of injury reports is also weak evidence, since minor incidents frequently go unreported. Take advice on the specific facts instead of assuming a fix closes the question.

Who decides whether a recall happens, us or the authority?

In most cases a business can act voluntarily and often should, but authorities generally hold powers to require action where they consider the response inadequate. That means the practical dynamic is negotiation: the company proposes a scope and a method, the authority tests whether it is proportionate. Arriving with a well-reasoned risk assessment, a defined affected population and a plan tends to produce a narrower outcome than arriving with an incomplete picture.

We sell across several countries. Is a single notification sufficient?

Usually not. Duties are set nationally, and although authorities share information about dangerous products, sharing is not the same as being notified. Where goods went to several markets the normal expectation is engagement with each relevant authority, sometimes through the local importer. Consistency of message across those notifications matters, because discrepancies between what different regulators were told become a separate problem on top of the original defect.