Withdrawing a recalled product from every sales channel
Head office can block a SKU in the ERP while a franchise, marketplace listing or third-party warehouse continues to sell or dispatch it. A listing marked inactive does not tell the recall lead what happened to orders already picked.
- Source recordsAffected product notice
- ProcessingExpand to offers and bundles
- Decision ownerRecall lead
- Operational outputVerified channel withdrawal
Implementation approach
Build a crosswalk from the supplier’s affected model or batch to retail SKUs, bundles, marketplace listings and fulfilment locations. Issue channel-specific holds and collect acknowledgements separately for listings, open orders and stock on hand.
Exceptions and operating controls
Leave unknown batch identity on hold for the recall lead. Take unavailable marketplace APIs through a documented manual route. Keep customer contact attempts separate from confirmed remedies.
Illustrative operating scenario
A recalled charger is sold individually and bundled under a different SKU. The store listing comes down, but the bundle remains in the warehouse pick queue until its separate hold is accepted.
Acceptance test and handover
Run a simulated withdrawal with an unreachable channel. Trace one affected unit from the supplier notice to each offer, location and customer remedy, and report the remaining unexplained units.
Industry evidence
The ACCC asks suppliers to monitor recall effectiveness, review progress and adjust their approach. ACCC Product Safety on tracking a recall