What is the wholesale product recall process in the EU?
The wholesale product recall process EU brands follow is a structured corrective action: identify unsafe or non-compliant stock by batch or lot, stop further supply, notify downstream retailers and distributors, recover or secure product, correct invoices, and report to the relevant market surveillance authority when required.
In B2B wholesale, chaos rarely comes from the safety decision itself. It comes from fragmented order history, missing lot links on invoices, and informal email threads that cannot prove who was told what. A workable process turns those gaps into a short checklist your ops, warehouse, sales, and finance teams can run together.
Corrective action is the umbrella term. Withdrawal means preventing product still in the supply chain from being placed on the market (for example, holding stock at your warehouse or a distributor). Recall means recovering product that has already reached consumers or is available to them via retail.[1] Many wholesale incidents start as a withdrawal and escalate to a recall once sell-through is confirmed.
Product carton linked by a thin thread to a retail shelf
Who is responsible when a brand sells through distributors and retailers?
Responsibility follows economic operator roles under EU product safety rules—not only who owns the brand story. A manufacturer, an importer placing goods on the EU market, and distributors or retailers each have duties scaled to what they control.[2] If you manufacture or import, you typically lead risk assessment, corrective action, and authority contact. If you distribute, you must still cooperate, pass information up and down the chain, and not knowingly supply unsafe goods.
When you sell through multi-tier wholesale—brand to distributor to retailer—write role expectations into trading terms before anything goes wrong. Who issues the public or trade notice? Who pays freight on returns? Who decides quarantine versus destruction? Ambiguity here is what turns a contained lot issue into channel conflict.
The General Product Safety Regulation (GPSR) frames general obligations for non-food consumer products and economic operators.[3] Food and feed follow food-law alert paths (including RASFF).[4] Beauty, food, fashion accessories, electronics, and home goods can sit under different sector rules, but the wholesale mechanics—lot scope, stop-ship, notify, recover, credit—are shared.
How do you identify affected lots and stop further shipments?
Start with the smallest reliable unit of identity: batch/lot number, tied to GTIN (and case GTIN where you sell outer packs). A batch/lot number is the production or packaging identifier that groups units sharing the same risk profile. Without it on pick lists, packing slips, and invoice lines, you are forced to over-recall entire SKUs or date ranges.
Practical stop-ship sequence:
- Freeze pick/pack for the SKU family while you confirm the lot list.
- Query open sales orders, backorders, and reserved stock by lot (or by receipt/production date if lots were weak historically).
- Quarantine on-hand inventory in WMS so it cannot be allocated.
- Block the lot on the B2B catalogue or mark “do not ship” so self-serve reorders cannot pull bad stock.
- Tell 3PLs and multi-warehouse nodes the same freeze in one message, not sequential phone calls.
GTIN setup for units and cases and solid inventory accuracy and order visibility are what make this step hours instead of days. For food and beauty, pairing lots with FEFO inventory for food and beauty also limits how far ageing stock has already travelled.
Branching delivery routes converging back to a central hub
How does batch and lot tracking speed claims and reduce scope?
Traceability one-up one-down means you can name who supplied you (one up) and who you supplied (one down) for each lot, with dates and quantities. Wholesale teams that store lot on the order line—not only in a separate warehouse note—can list affected invoices and retailer accounts directly from the order-to-invoice record.
That list is the difference between a narrow recall and a reputation hit. You contact only buyers of lot L-1042, not every account that ever bought the SKU. Claims after delivery also resolve faster when lot, GTIN, and proof of delivery sit on the same thread; see a structured wholesale claims process after delivery.
How should you alert retailers and document proof of notification?
Retailer product recall notification should be structured, not a casual sales email. Send the same core packet to every affected account:
- Product identity: name, GTIN, batch/lot, and clear photos of marks if helpful
- Risk summary in plain language and the action required (stop sale, remove from shelf, return, or hold for collection)
- Deadlines and logistics contacts
- What consumers should do if sell-through already happened
- Your reference number for the incident
Use channels you can evidence later: portal message, confirmed email to the onboarding contact plus the buyer, and a follow-up call log for high-volume accounts. Proof of retailer notification is a dated record of content sent, recipient identity, and delivery or read confirmation where available. Market surveillance authorities and insurers care about this trail as much as the physical recovery rate.
Keep the tone factual. Retailers need instructions they can forward to store staff, not marketing language. If you operate a branded distributor portal, a single posted bulletin plus account-level flags reduces “I never saw that mail” disputes.
What returns, quarantine, and disposal steps keep the chain clean?
Physical control must match the paperwork. Define whether goods are:
- Held at retailer pending collection
- Returned to your warehouse or a nominated 3PL under a returns authorisation
- Destroyed locally under documented conditions when transport is unsafe or uneconomic
Quarantine means segregated, labelled locations—no mixed pallets with good stock. Count units in and out. Photograph seals or destruction certificates when disposal is required. Align the commercial path with a clear B2B wholesale returns policy so warehouse RMA codes, carriers, and credit triggers are not improvised mid-crisis.
For multi-country EU wholesale, state which entity receives returns in each market. Cross-border reverse logistics without a named ship-to and Incoterm-style clarity create abandoned freight and incomplete recovery counts.
Quarantine barrier around neatly stacked cartons in a warehouse
How do credit notes and invoice corrections work after a recall?
A credit note is the commercial correction that reverses or reduces the amount payable on affected wholesale invoices once goods are confirmed unsaleable or returned under the recall. Issue credits from the original invoice and lot lines where possible so VAT, currency, and retailer statements stay reconcilable.
Good practice:
- Credit only verified quantities (returned, destroyed with certificate, or agreed write-off)
- Separate “recall credit” reasons from ordinary commercial returns for margin reporting
- Do not silently re-ship substitute lots without a new order line—keep audit clarity
- Sync credits to accounting in the same rhythm you sync invoices so open-item chasing does not harass retailers for recalled goods
Brands that already run order-to-invoice in one flow—orders, lots, retailer accounts, and credits together—spend less time rebuilding spreadsheets under pressure. That is an operations design choice you make before the incident, not during it.
When and how do you report to market surveillance authorities?
A market surveillance authority is the national body that enforces product safety rules in each EU country. You report when products present a risk requiring corrective action beyond routine quality complaints, following the timelines and forms that authority publishes. Non-food dangerous products are commonly channelled through the EU Safety Gate system (historically known in trade shorthand via RAPEX).[5] Food and feed safety alerts use RASFF.[4] Your counsel or compliance lead should map which regime applies to the SKU before you need it.
Prepare a single internal fact pack: product ID and lots, risk description, distribution list by country, corrective actions already taken, and copies of retailer notices. Consistency between what you told retailers and what you file with authorities matters. If you are not the manufacturer or importer, escalate upstream immediately and document that escalation—distributors still must cooperate fully.
National pages (for example consumer or food agencies in the markets you ship to) explain local contact points. Do not wait for perfect recovery percentages before first contact when serious risk is plausible; early notice with partial data beats silence.
What should your B2B portal and order data include before a recall hits?
Recall readiness is mostly master data and process hygiene:
| Data / control | Why it matters in a recall |
|---|---|
| GTIN on unit and case | Matches trade notices to what retailers scanned |
| Batch/lot on order, pick, pack, invoice | Scopes who actually received risk stock |
| Retailer contacts and roles | Reaches ops, not only the original buyer |
| Order and shipment history by account | Builds the notification list fast |
| Stop-sell / catalogue flags | Blocks self-serve reorders of bad lots |
| Credit reason codes | Separates recall economics from ordinary returns |
| Portal bulletin or message log | Strengthens proof of notification |
Train sales not to promise “keep selling, we will sort it” when a freeze is active. Give them a one-page script and the incident reference. If your stack still lives in disconnected spreadsheets, the first recall will expose every broken hand-off; upgrading order visibility is preventive maintenance, not a nice-to-have.
Brandgate is built around branded distributor portals and order-to-invoice visibility for Nordic and EU wholesale teams—useful when you need affected invoices, retailer accounts, and credits in one place instead of chasing inboxes. If you want to see how that workflow looks for your catalogue, book a demo.
A compact wholesale recall runbook
Use this sequence as your internal playbook:
- Confirm hazard and classify withdrawal vs recall.
- Lock lots; quarantine warehouse and open orders.
- Export one-up one-down supply and customer lists.
- Notify retailers with identical instructions; store proof.
- Arrange returns, local destruction, or hold-for-collection.
- Issue lot-tied credit notes; sync finance.
- Report to the competent authority / Safety Gate or RASFF path as required.
- Close with a short post-mortem: data gaps, supplier CAPA, and catalogue blocks removed only after clearance.
Run the drill once on a fictional lot. Teams that have rehearsed stop-ship and portal alerts recover trust with retailers far faster than teams inventing the process under load.