When Safety Gate names your product: the first days of response

Read the product identification, the risk description, the measures taken, and the notifying country, in that order. Identification tells you whether the alert truly covers your product or a lookalike: model, batch, brand, and any photograph or barcode detail. Risk tells you the fault mechanism and who could be harmed. Measures tell you what has already been ordered or agreed, which frames what you must now do.

Do not react to the headline alone. Headlines compress, and a compressed headline can suggest a wider scope than the alert's detail supports, or a narrower one. The detail is the document, and every later message you write should be traceable to a line in that detail, not to a summary you read in a hurry.

Verification is a records exercise. Compare the alert's identification against your batch records, sales records, and supplier records: which batches match, which markets received them, which channels sold them, and how many units remain with buyers versus in warehouses. Where the alert's identification is ambiguous, ask the notifying authority or your responsible person for clarification promptly, and act on the cautious reading while awaiting it.

Scope verification also covers lookalikes. If the alert names a product you sell under a different brand, or a component you share with the named product, the alert may still affect you indirectly, because authorities and buyers will ask. Illustration: a seller of camping lanterns finds an alert naming a lantern with the same battery pack it uses, and checks its own lanterns for the same charging fault before anyone asks.

The first messages go to the authority contact and the responsible person, to trade partners with a hold where needed, and then to buyers where the measure requires it. Each message should carry the same core facts: the alert reference, the product and batch scope as verified, the fault, the remedy, and the contact route. Consistency across those messages prevents the confusion that arises when partners and buyers receive different versions.

Speed matters, but accuracy matters more in the first hours. A message sent before scope is verified will need correction, and corrections to a public alert response are costly in trust. A short holding message, stating that the alert is being verified and that sales are paused in the meantime, can buy the hours needed for verification without leaving partners in silence.

Gather the batch and traceability records, the test evidence for the affected and nearby batches, the complaint history, the supplier records for the relevant component, and the listing and labelling as sold. That set lets you answer the authority's questions, test whether the alert's fault applies to your units, and decide whether the remedy should match the alert's measure or go further.

Preserve the physical evidence too. Retain samples from the affected batch, and do not scrap or repair them before the authority has had a chance to inspect or test, unless the authority agrees. A sample destroyed in haste cannot support a later argument that the fault did not apply, and its absence will be noticed.

The alert is public, so buyers, journalists and trade partners may ask about it before you have contacted them. Prepare a short factual statement: the product and scope, what buyers should do, and where to get help, without speculating about cause or blaming a supplier before the evidence supports it. That statement should match the authority messages word for word on scope and action, because discrepancies will be found and quoted.

Staff answering messages need the same statement and the same answers for gift recipients and second hand buyers, who will appear. A single briefing sheet for the contact team, updated as scope verification progresses, keeps every reply consistent during a period when inconsistency is most damaging.

An alert case closes when the measure is completed, the outcomes are tracked, and the authority is satisfied with the result, which may involve a final report or a follow up check. The seller should keep the full file: the alert, the verification, the messages, the tally, and the preventive change, because the alert remains searchable online and future partners or authorities may ask about it.

The preventive change deserves its own attention. An alert case that ends without a design, supplier, or check change is likely to recur, and a recurrence after a public alert is judged harshly. The closing record should therefore state the change and its evidence, so the alert becomes a turning point in the product's history rather than a recurring headline.