Corrective action requires more than removing a listing. This material focuses on the withdrawal notice: its recipients, versions, channels and proof of dispatch. A separate article on controls and the evidence trail covers the wider preparation of case documentation.

Corrective action has a defined scope

Possible actions include, among others, correcting information, suspending sales, removing a listing, withdrawing from distribution, recovering the product from consumers or other measures that limit risk. Not every incident requires the same solution.

Before starting the process, the product, variants, batches, sales period, markets and channels must be identified. The scope should follow from the data, not just from the catalogue name. If batches cannot yet be separated precisely, the assumption made and the risk of it changing should be recorded explicitly.

A single action record

The central record should contain:

The record does not replace any required notifications or documents, but it brings them together into a single trail. People in the company then work from the same decision and the same scope.

Map of recipients and channels

A notice may be needed for consumers, distributors, marketplaces, the supplier, the warehouse, the service centre, an authority and internal teams. Each group needs a different form, but the key facts should not differ.

It is worth preparing a table: recipient, purpose of the notice, channel, deadline, owner, version of the content and proof of completion. A lack of response from a recipient does not automatically mean the task has been completed. For important contacts, the method of reminder and escalation must be defined.

Content for the consumer

The notice should make it possible to recognise the product and understand what needs to be done. Clear photographs, the model, the batch marking, a description of the risk and an unambiguous action for the user are needed. The language should not play down the problem or shift responsibility onto the customer.

Instructions for return, repair, replacement or ceasing use must correspond to the approved action. If more than one route is provided for, it must be explained which situation each one applies to. Contact details should remain active throughout the handling period.

Language versions and consistency

When selling in several markets, language versions are needed. Each should indicate the source text and the person verifying it. A change to the batch scope or to the customer instructions must trigger an update of all active versions.

Files sent earlier remain in the history. They should not be replaced by a new document under the same name without a revision number. This makes it possible to establish which notice reached a given recipient.

Marketplaces and your own shop

Deactivating a listing is an operational task that has to be confirmed in every channel. It is worth recording the listing identifier, the link, the time of deactivation and a screenshot or confirmation. If the channel allows buyers to be contacted, the set of recipients should follow from the list of orders relating to the relevant variant and period.

At the same time, re-publication of the product through an automatic import or by an operator must be blocked. A status of "inactive" in one system alone may not stop synchronisation with another channel.

Warehouse and supply chain

Goods in the warehouse should be separated physically and in the system. The block must cover receipts, transfers and order fulfilment. The supplier should receive the batch identification, a description of the problem and the scope of the information needed for analysis.

If the product is in transit, it must be established whether the delivery can be stopped or directed for inspection. Logistics decisions must be linked to the action record so that they do not later return to normal circulation without a deliberate release.

Measuring performance

A list of messages sent does not show the full outcome. Depending on the action, it is worth monitoring the number of products identified, notices delivered, responses, returns, repairs, products remaining with customers and cases requiring a reminder.

Indicators cannot replace an assessment of effectiveness. A low response rate may mean outdated data, unclear content or the wrong channel. Every correction to the approach should be recorded.

Working with authorities

The scope and form of contact depend on the incident and on the competence of the authority. The company should retain the information sent, confirmations, questions and answers. If an authority indicates additional actions, they should enter the same task list and decision history.

External communication should not be conducted from multiple independent mailboxes without a central record. An agreed contact owner reduces the risk of contradictory answers.

Closing the action

Before closure, the completion of tasks, the reconciliation of products, the durability of the blocks and the updating of documentation should be checked. The root cause analysis should lead to changes in the design, supplier control, risk analysis, instructions or the product intake process.

The period of further monitoring should also be defined. A new report after formal closure may require the case to be reopened. The history should retain the original closure and the later decision.

Most common mistakes

GPSR / PPWR supports the list of products, tasks, communication versions and proof of completion. The choice of action and the approval of content are decided by a person on the basis of an assessment of the specific risk. The system is there to ensure consistency and a trail, not to replace that decision automatically.