Product Recall and Field Safety Notice Template
When a product has to be recalled, the notice is the document that gets read, so it has to be plain, specific and complete. This template structures the notice around what a reader needs: what is wrong, which units, what to do and how to get help.
Fill in
Product Recall and Field Safety Notice Template
Safety Notice: PowerBank Pro 20000, model PB-20K
From: Northfield Electronics Inc. Date: 2026-10-20 Units affected: 4200
What is the problem
A fault in the battery protection circuit may allow the unit to overheat while charging, which presents a burn and fire hazard.
Which products are affected
PowerBank Pro 20000, model PB-20K Lot codes 2506A through 2508C, manufactured June to August 2026
The lot code is printed on the label on the back of the unit.
Known incidents
Eleven reports of overheating, three reports of minor property damage, no injuries reported to date.
What you should do
Stop using the product. We will provide the following remedy at no cost to you: Free replacement.
To arrange the remedy, contact recall@example.com or 1-800-555-0100.
Acknowledgement of receipt
| Recipient | Date received | Units held | Action taken |
|---|---|---|---|
Approvals
This is a starting point, not legal advice. Recall and reporting duties vary by country and product type. For example, in the United States, firms may have to report certain hazards to the CPSC within 24 hours of becoming aware. Have legal counsel and your regulator contact review the notice before it goes out.
Test your lot traceability
Optional: we can walk through a mock recall query on your ERP data and show where traceability breaks.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill in the product, affected lots and the hazard in plain language. Choose the action the user must take and the remedy you offer, and give a working contact. The preview updates as you type; export to PDF or Word when it reads correctly. Keep the notice short, because a long notice delays the part that matters, which is what to do. Attach the acknowledgement table for distributors, who are often asked to confirm receipt and report their stock.
What a good notice says
Regulators and consumer agencies generally expect a notice to identify the product, describe the defect and the hazard, state the number of units, say whether there have been incidents, and give a clear instruction and remedy. Write the hazard in terms of what could happen to a person, not an internal failure code. Avoid minimising language and avoid blame. Include enough identification, such as model, lot code and where to find it, that a non-technical user can tell if they are affected.
- Product name, model and lot or serial range
- The hazard, in plain words
- Incidents known to date, factually stated
- What the user should do right now
- The remedy and how to claim it
- Contact details that are staffed
Before you send
Confirm the affected population from your traceability data, not from memory. In an ERP this means a lot or serial where-used query from the finished item back to components and forward to customer shipments. Check the notice with legal and with the regulator contact for each market, since reporting deadlines and wording rules differ. Record who approved the notice and when, and keep proof of how and when each recipient was informed.
Common mistakes
Notices that bury the instruction under company background, that use jargon, or that list the wrong lot range cause the most trouble. Another is forgetting distributors and service partners, who hold stock and field the calls. Plan the support line before the notice is published, and set a way to track return rates so you can report progress to the authority.
Frequently Asked Questions
Is this the same as a field safety corrective action notice?
It is similar in structure. Medical device field safety notices follow specific regional rules on content and recipients, so use this as a general layout and follow the requirements of the relevant medical device regulation where they apply.
Who must approve a recall notice?
Normally quality or compliance, legal and a senior executive. Many companies also require sign-off from the regulator liaison. The signature block here records the approvals so the decision trail is clear.
How do I identify affected units?
Use lot and serial traceability. Query which lots of the faulty component went into which finished lots, then which customers received those lots. Test this query before you need it, because a recall is the wrong time to find gaps.
Should the notice mention incidents?
Yes, if there are known incidents, state them factually and briefly. Authorities expect transparency, and leaving them out can damage trust and worsen enforcement outcomes. Do not speculate beyond what is known.
If traceability from lot to customer shipment is slow in your ERP, we can help build the query so you can size a recall in minutes rather than days.
Related Tools
Product Safety Test Report Summary Template
A one-page summary of a product safety test campaign: standards applied, tests run, results, deviations and the overall conclusion.
Compliance & ContractsProduct Compliance Technical File Index Worksheet
An editable index of the documents in a product technical file, with owner, revision, location and next review date.
Compliance & ContractsSVHC Candidate List Article Screening Worksheet
Log each SVHC found in a component, compute its concentration in the article and flag when the 0.1% w/w threshold is exceeded.
Compliance & ContractsProduct Marking and Labeling Compliance Checklist
A checklist to audit the markings and labels on a product and its packaging before release.
More Compliance & Contracts tools
See all- SAP SoD Residual Risk Score Calculator
- SAP Firefighter ID Usage Review Log
- IBM i (AS/400) User Profile Access Review Worksheet
- SyteLine Security and User Access Audit Checklist
- Infor XA (MAPICS) User Access Review Worksheet
- China ERP Data Security and Compliance Assessment
- ERP Vendor Data Processing Agreement Outline
- GDPR ERP Data Migration Checklist
- EU Machinery Regulation 2023/1230 Readiness Checklist
Keep exploring
Free tools
- Medical Device Recall Cost EstimatorEstimates the cost of a field action from units affected, retrieval and replacement costs, notifications and fixed overhead.
- Field Action and Recall Support Plan TemplateA supplier-side plan for supporting a customer field action: suspect lots, traceability boundaries, sort actions, communications and approvals.
- Engineering Change Shop Floor Notice TemplateA one page notice that tells production what changed, from which work order, and what to do with old-revision parts.
ERP fixes and how-tos
- How to Link a CAPA to ERP Lots and Serial Numbers for Containment and EffectivenessUse ERP lot and serial genealogy to scope containment for a CAPA, record affected jobs and shipments, and verify effectiveness with real data instead of opinion.
- How to Add a Custom Field to an IFS Cloud PageStep-by-step guide to adding a custom field in IFS Cloud with configuration mode, plus data types, permission needs, upgrade safety and why a field may not show.
- Date Code and Lot Traceability in Cetec ERPHow to keep date code and lot traceability in Cetec ERP for electronics: capture at receiving, preserve through builds, and answer a recall trace quickly.
Runs with your ERP
- 1 EDI Source EDI Integration with Infor VISUALHow 1 EDI Source connects Infor VISUAL to trading partners for EDI orders, invoices and ship notices via ION or direct API: setup, pitfalls and private AI.
- Infor Service Mobile with Infor SyteLine Field ServiceInfor Service Mobile is a field technician app listed as a CloudSuite Industrial add-on. What it connects to in SyteLine service, setup steps, pitfalls, FAQ.
Guides
- Infor M3 Lot Traceability and Recall Management ConfigurationConfigure Infor M3 lot traceability with forward and backward tracking, recall management, lot status workflows, and serialization for regulated industries.
- BRCGS Packaging Materials Audit Prep for Label and Packaging ConvertersPreparing a label or packaging converter for a BRCGS Packaging Materials audit: hazard analysis, traceability tests, document control and customer specs.
- How to Configure Safety Stock Parameters in Infor SyteLineStep-by-step guide to configuring safety stock parameters in Infor SyteLine. Learn how to set reorder points, buffer quantities, and demand-driven safety stock calculations.
AI on your ERP
- AI for Food Manufacturing ERP: FSMA Traceability and Recall ReadinessAI on the ERP of a food manufacturer: FSMA 204 trace-back, lot and allergen checks, supplier verification and recall drills. Private, read-only deployment.
- NetSuite AI for Food and Beverage: Lot Genealogy, Shelf Life and Recall ReadinessAI on NetSuite for food and beverage: lot genealogy, FSMA 204 traceability, shelf-life and FEFO questions answered from live data, on-prem or private cloud.
Software
- IFS Field Service ManagementIFS Field Service Management covers service orders, scheduling optimisation and mobile work within IFS Cloud. Modules, integrations, AI uses and alternatives.
- Oracle Field ServiceOracle Field Service schedules, routes and equips mobile workers within Oracle cloud applications. Modules, integrations, AI uses and alternatives.