How to respond when a product in your catalogue is recalled

A recall is an operations event, not a legal one

A recall in your category is not primarily a legal problem. It is a timed operations problem, and almost everything that determines the outcome is decided in the first few hours by whoever happens to be working.

Regulators classify recalls by how much harm the product can do. In the United States the FDA uses three classes, where Class I means a reasonable probability that use will cause serious harm or death, Class II covers temporary or medically reversible consequences, and Class III covers products unlikely to cause harm but still in violation. The Consumer Product Safety Commission runs the equivalent process for most non-food consumer goods. Sellers tend to encounter these as a headline rather than as a notice, which is the root of the problem.

Why sellers find out last

The notification chain runs from regulator to manufacturer to distributor, and a marketplace seller is frequently not on it. A seller buying through a distributor, or reselling, may have no contractual right to be told at all. The practical result is that the first signal is a customer message, a marketplace policy notice, or a news story — all of which arrive after the public does. Any plan that assumes you will be told in advance is a plan for a situation you are not in.

The four moves, in order

Pull, notify, document, then reconcile — in that order, and without waiting for certainty on the later steps.

Pull means delisting rather than marking out of stock, because an out-of-stock listing stays indexed, stays reviewable and in some cases stays purchasable through saved links. Notify means contacting the buyers who received affected units, which requires knowing which units were affected. Document means recording the timeline as it happens rather than reconstructing it later. Reconcile means working out returns, refunds and supplier recovery, and it is deliberately last because it is the only step with no clock on it.

What the record has to show

The only thing that matters afterwards is whether your record shows what you knew and when you acted on it.

Keep a timestamped log from the first signal: when you learned, from where, what you pulled and at what time, who you contacted, and what you told them. Two numbers come out of it — time from first signal to delisting, and time from delisting to customer notification — and those two are what a marketplace, an insurer or a regulator will look at. A seller who acted within the hour and can show it is in a different position from one who acted within the hour and cannot.

Where sellers make it worse

The most common way sellers deepen a recall is by narrowing it too early.

Faced with a recall covering specific lots, the instinct is to pull only the lots named and keep selling the rest. That is correct if and only if you can prove which units you shipped came from which lot. Most small sellers cannot, because incoming stock was never recorded by batch, and a claim that your units were unaffected then rests on nothing. The other frequent error is a customer notice written to minimise alarm to the point where it fails to tell the recipient to stop using the product, which converts a supply problem into a credibility one.

What the first hour looks like

In practice the first hour is unglamorous. Someone delists across every channel, including the ones nobody remembers — a secondary marketplace account, a social shop, a feed pushed to a comparison site. Someone else pulls the order history for the affected period and separates buyers who received units in scope. Somebody starts the log. Nobody spends that hour deciding who pays, because that question keeps and the other three do not.

The case that this is over-preparation

The argument against building this in advance is that recalls are rare, most sellers will never face one, and the effort is better spent on things that happen weekly. A small operation running on thin margins can reasonably conclude that it will improvise if the day comes, and it will usually be right.

It is a fair calculation with one asymmetry worth naming: the preparation is cheap and the improvisation is expensive at exactly the moment you have least capacity. Two of the four moves — knowing every channel where your listings appear, and recording incoming stock by batch — cost almost nothing to maintain and are the two that cannot be done retroactively. Deciding not to write a full plan is defensible. Not knowing where your listings are is not.

Traceability is the whole game

Nearly every hard decision in a recall reduces to one question: can you tell which units you shipped came from the affected batch. With that record you pull a defined set, notify a defined list, and keep selling the rest with a defensible basis. Without it you are choosing between over-recalling at your own cost and under-recalling with no evidence behind the claim.

The record needed is small — supplier, batch or lot identifier, quantity, and the date range those units shipped. It does not require a system; a spreadsheet updated at goods-in is enough for most catalogue sizes, and the discipline matters more than the tooling.

It has to exist before the event, because the one thing you cannot do during a recall is reconstruct which physical units went to which customer three months ago. Sellers who try end up notifying everyone who ever bought the product, which is expensive, and which tells regulators and customers exactly how much you knew about your own supply chain.

Writing the customer notice

The notice has one job: get the recipient to stop using the product. Everything else — apology, explanation, remedy — is secondary and should not be allowed to bury the instruction. Notices that lead with reassurance routinely fail this, because a reader who is reassured in the first line does not read the second.

State what the product is, how to identify it, what to do with it now, and what you will do about the money. In that order, in plain sentences, in the subject line as well as the body. If a batch identifier is the way to tell affected units apart, say where on the packaging to find it.

Resist the temptation to characterise the risk yourself. Where a regulator has classified the recall, cite that classification and link the official notice rather than paraphrasing it — your paraphrase is a claim about safety that you are not qualified to make and will be held to.

The contract clause worth adding now

Most sellers have no contractual right to recall notification from the people they buy from. Adding one is a single clause: the supplier notifies you within a defined period of becoming aware of a safety issue or regulatory action affecting supplied goods, and provides the batch identifiers involved.

The same clause is the natural place to settle who bears the cost of pulled stock and customer refunds. That question is far cheaper to answer in a supply agreement than in a dispute during the week you are both under pressure.

For sellers who buy through distributors or on open terms, this may not be negotiable — in which case the honest conclusion is that you are relying on public notices, and your monitoring should reflect that rather than assume a call that is never going to come.

Build the response before you need it

Spend an afternoon on the two things that cannot be done retroactively: a list of every channel your listings appear on, and a record of incoming stock by batch.

Week one, write down every surface where your catalogue appears, including dormant accounts, social shops and any feed pushed to a third party, and confirm who can delist on each. Week two, start recording incoming stock by supplier, batch and date range at goods-in. Week three, draft the customer notice template and the internal log format, so neither is being written under pressure. Week four, add the notification clause to your supplier terms and subscribe to the official recall feeds for the categories you actually sell in.

Rehearse the pull, not the paperwork

Once a year, take one live product and time how long it takes to delist it everywhere and to produce the list of buyers who received it in a given month. That single rehearsal surfaces the two failures that matter — a channel nobody can access and an order history nobody can filter by batch — and it does so on a day when neither is urgent. Record the two times; they are the numbers that would be quoted back to you.

Repeat after adding a sales channel, changing supplier, or expanding into a category with its own regulator. Each of those changes the shape of the response, and the plan that fitted a single-marketplace catalogue does not fit four channels and two jurisdictions.

Editorial conclusion

A recall is survivable and frequently routine. What separates a contained one from a damaging one is not the seriousness of the defect but whether the seller could pull fast, tell the right people, and show afterwards what they knew and when. Two of those depend entirely on records kept before anything went wrong, which is why the preparation is cheap and the improvisation is not.