Product Recalls: The Operational Playbook Every Merchant Needs

The recall scenario no one wants to face

You receive a notification from your supplier: a batch of products may have a safety defect. Batch numbers X through Y. You have 72 hours before you're required to notify the relevant regulator.

The clock is running. What do you do?

Most merchants discover in that moment that they don't have a process. They have:

• A spreadsheet of orders that may or may not be complete
• An email list that hasn't been cleaned in 18 months
• Products still listed and actively selling on 12 channels
• No idea which customers bought the affected batch

This is avoidable. Here's the correct playbook.

Step 1: Identify and freeze affected inventory (within 1 hour)

The first action is to prevent any further sales of the affected product. This means:

1. Identify affected SKUs by batch number, date range, or supplier lot
2. Mark all affected products as recalled so they can't be purchased
3. Remove from storefront listings and POS availability
4. Flag any open orders containing affected products for review

In BestWebby, creating the recall records it. The freeze is then a single action on that record: Freeze inventory marks every affected SKU as recalled, which pulls those products out of your storefront listings and the POS product search in one step, rather than a channel-by-channel hunt. Reviewing open orders is still yours to do. If you also list on external channels, pull those listings in the same first hour.

Step 2: Cross-reference your customer database (within 2 hours)

Now you need to know who has the affected product. This requires querying your order history by SKU and batch number.

The query you need: Which customers ordered SKU X between date Y and date Z?

This should produce a list of order IDs, customer names, email addresses, shipping addresses, and quantities purchased.

In BestWebby this is the Cross-reference action on the recall. It scans your order history for the affected SKUs and opens one case per customer, carrying the order IDs, contact details, and unit counts you need to notify them. Customers who already have a case are skipped, so you can run it again as later orders surface.

Step 3: Notify affected customers (within 4 hours)

Customer notification is legally required in most jurisdictions and needs to include:

• The specific product affected (name, model, batch number)
• The nature of the safety concern
• Whether the customer should stop using it immediately
• What they should do next (return for refund, dispose of, wait for collection)
• Your contact information for questions

Tone matters. Customers who receive a clear, proactive, empathetic notification from a brand they trust are far more forgiving than customers who learn about a recall from the news.

In BestWebby, Notify customers emails every affected customer who has an email on file, personalized per case, with a private link to a page on your own storefront where they can confirm they have seen the notice. Additional channels such as WhatsApp are planned on the roadmap to extend reach further.

Step 4: Manage the return process

Once notified, you need to track who has acknowledged, who has returned the product, and who hasn't responded.

Maintain per-case status: Notified → Acknowledged → Returned → Closed.

Issue refunds as returns are received. If a customer doesn't respond within a reasonable window, follow up. Document everything — regulators may ask for completion statistics.

Step 5: File the regulatory report

Within 24-72 hours (varies by jurisdiction), you may be required to file a formal recall notice with the relevant regulator:

• US: CPSC (Consumer Product Safety Commission)
• UK: Trading Standards
• EU: RAPEX system via the relevant national authority
• CA: Health Canada (for food/health) or CCCR (Consumer Product Safety Act)

The report requires: product description, hazard identification, affected units, distribution history, and corrective action plan.

BestWebby generates a PDF in the standard CPSC format — ready to attach to the filing. This is the document that would otherwise require a legal team to prepare.

Step 6: Notify your supplier

Your supplier needs to know about the recall, both so they can stop shipping affected stock and because you may have grounds for a claims conversation depending on the root cause.

Send formal written notification (email with delivery confirmation is sufficient) as soon as the recall is created.

Step 7: Close the loop

When a sufficient percentage of affected units have been returned, you can close individual cases and eventually the overall recall. Document completion statistics: units sold, units returned, outstanding.

Regulators look favorably on recalls with high completion rates and clear documentation.

The takeaway

A well-executed recall is operationally intense but manageable. A poorly executed one — with delayed customer notification, ongoing sales of affected product, and incomplete documentation — creates regulatory, legal, and reputational risk that far exceeds the cost of the recall itself.

The playbook is the same every time. Automate it.