How to Translate a U.S. Recall Notice for FDA, CPSC, and NHTSA
A translated U.S. recall notice must carry the same hazard, product identifiers, remedy and recalling firm as the English original, under the same urgent label. Translators change wording, never facts. The recalling firm owns the content. A subject-matter reviewer, a compliance reviewer and the agency contact approve it before release. Each language version is then tracked under version control.
Table of Contents
What is a translated recall notice and what does it cover?
A recall notice is a written communication that tells consumers, consignees or owners that a product is being removed or corrected because of a safety risk or a regulatory violation. A translated recall notice is the same communication in another language, prepared for people who read that language better than English.
The scope in this article is the United States. Three agencies set most of the rules:
The Consumer Product Safety Commission (CPSC) covers consumer products.
The Food and Drug Administration (FDA) covers food, drugs, devices and other regulated products.
The National Highway Traffic Safety Administration (NHTSA) covers vehicles and motor vehicle equipment.
The notice types in scope are public press releases, direct notices to consumers, letters to consignees such as distributors and clinics, web pages, social posts, posters and owner letters.
The data category matters. A recall notice itself is public safety content. The mailing list behind a direct notice is different. It can hold names, addresses, purchase records and, for medical products, patient or device-linked information. Those records need access control, encryption and a documented processing agreement with any language vendor.
What must stay unchanged in translation?
The CPSC rule on recall notice content lists what a notice must contain. The list includes the word “recall” in the heading and text, the date, product-identifying information, the action being taken, the approximate number of units, a hazard description and the identity of the recalling firm. The full list is in 16 CFR 1115.27.
The translator keeps these elements exact:
Model names, model numbers, lot numbers, serial ranges and UPC codes.
Dates, including manufacture, sale and recall dates, in a format the reader cannot misread.
Unit counts and measurements, with units of measure converted only when the source states both.
The hazard statement and any injury or incident counts.
The remedy: repair, replace, refund or stop use, and how to obtain it.
Telephone numbers, web addresses and the firm’s legal name.
The translator adapts sentence structure, register and idiom. Product identifiers and the firm’s name stay in their original form, because a consumer matches them against a label on the product.
How should “recall notice” and related terms be translated?
The CPSC handbook for product safety planning and recall reporting supports a consistent rule. Use the plain-language equivalent of each recall term, and keep the English word “recall” in the title or right beside the translation on first use. Translate “recall notice” as the natural equivalent of a notice that requires action. Use the same approved term in the notice and in every related channel. Do not replace it with a softer word such as “update” or “advisory.” See the CPSC Recall Handbook.
The same handbook recommends “Recall Notice” or “Safety Recall” at the top of targeted email and postal notices. Translate that label once, approve it, and place it in the term base as a locked entry.
Agency labels differ:
Agency | Label or wording in agency text | Translation control |
CPSC | “Safety Recall” or “Recall Notice” on direct notices | Locked term, plus English “recall” on first use |
FDA | “URGENT: [product type] RECALL [or CORRECTION]” in large, bold print on written communications to direct account consignees | Locked template, product type variable only |
NHTSA | “SAFETY RECALL NOTICE” on the owner letter envelope | Envelope text reviewed against the regulation |
The CPSC and FDA wording comes from the sources above and the FDA guidance on product recalls. The NHTSA envelope wording comes from 49 CFR 577.5, which requires the phrase in all capital letters in a type larger than the address and distinguishable in another way. That guidance also says the terms “market withdrawal” and “stock recovery” should not be used in these communications. Do not introduce target-language equivalents of those terms.
Which agency rules affect translated notices?
Requirements differ by product and agency. No single U.S. rule requires every recall notice in every language.
CPSC
Under 16 CFR 1115.26, a notice may be required in languages in addition to English when the Commission or a court decides this is necessary or appropriate to adequately inform and protect the public. The regulation lists the marketing and geographic circumstances that apply. The same section asks for simple language designed for the targeted consumers, with highly technical or legal terminology avoided or minimized.
The CPSC’s focus group research also recommends that awareness campaign communications, and forms or instructions for reporting defective products, be available in Spanish. See the CPSC focus group report.
FDA
The FDA recall procedures chapter tells firms to discuss recall communications with their Division Recall Coordinator before issuance. The coordinator should offer to review consignee communications. Whether bilingual or multilingual communications are needed should be explored in that discussion. See FDA Chapter 7, Recall Procedures.
The regulation on recall communications, 21 CFR 7.49, requires the communication to state that the product is subject to a recall and that further distribution or use should cease immediately. Those two statements must survive translation without softening.
NHTSA
Part 577 sets the format and content of owner notification letters and the envelope notation. The regulation text is 49 CFR Part 577. Check it for any language requirement before drafting a non-English letter. If the text is silent on a point, ask the NHTSA Recall Management Division before mailing. Mark any such assumption [VERIFY] in the project file.
What are the steps, owners and controls?
The steps below assume a manufacturer or distributor that has already decided to recall.
Freeze the source text. Owner: recall lead. Control: a signed-off English master with a version number. The agency has reviewed or cleared it where required.
Decide languages and channels. Owner: regulatory affairs. Control: a written rationale based on the affected market, the agency contact’s advice and the data on who bought the product.
Load the term base. Owner: localization manager. Control: locked entries for “recall,” the label, the hazard terms and the remedy verbs. Existing translation memories are checked for outdated recall wording.
Produce the draft. Owner: language provider. Control: AI+HUMAN hybrid translation by a linguist with subject-matter expertise, working in a secured environment with access control and a logged audit trail.
Run quality assurance. Owner: language provider. Control: automated checks for numbers, model codes, dates and URLs against the source, plus a documented QA pass against the standard the contract names, such as ISO 17100.
Review for equivalence. Owner: a second linguist, or a bilingual employee at the firm. Control: comparison of hazard, remedy and contact details against the English master.
Test for comprehension. Owner: marketing or communications. Control: a read-through by a native speaker who is not a specialist. This checks plain language and a clear call to action.
Approve. Owner: regulatory affairs and legal. Control: written sign-off per language, recorded against the version number.
Publish and sync. Owner: communications. Control: all language versions go live in the same window, and the English page links to each translation.
Monitor and update. Owner: recall lead. Control: change log, described below.
How do you write for clarity, urgency and culture without changing meaning?
The CPSC focus groups found that English and Spanish communications should be culturally relevant, use true-to-life imagery to show hazards and create urgency. Posters should use few words and a clear call to action. The participants usually learned about recalls from retailers, manufacturers or news reports. The route to Spanish content should be clear and supported by search engine optimization. Source: CPSC focus group report.
In practice, the translator:
Puts the action first: stop using the product, then the reason.
Uses the verb forms and politeness level that fit the audience, applied the same way in every sentence.
Replaces idioms with literal statements.
Avoids dialect-specific words when the audience spans several regions.
Keeps the hazard severity unchanged. A word that means “may be a problem” does not translate “can cause serious injury.”
Warnings that readers do not understand can leave people exposed to harm. Readers who want background on what happens after a dangerous imported product injures someone can see this overview of product injury claims in Pennsylvania. That is one more reason to test the translation for comprehension before release.
What are the decision criteria for choosing a language provider?
Use these criteria in the request for proposal. Each can be checked with a document or a test.
Criterion | What to ask for |
Subject-matter expertise | Named linguists with credentials in the product field, such as medical devices or consumer goods |
Process standard | Certification to ISO 17100, and ISO 18587 if post-editing of machine output is used |
Information security | ISO 27001 certificate, data location, subcontractor list, access control model |
AI governance | Written policy on AI use, human review of every segment, ISO 42001 if claimed |
Turnaround | Written hours for a rush recall, with weekend coverage |
Terminology | Import of the firm’s term bases and translation memories, with locked entries |
Traceability | Audit trail per segment, version history, delivery of QA reports |
Regulatory fit | Experience with the relevant sector, such as MDR or HIPAA for medical products |
Data handling | Processing agreement covering mailing lists and any personal data |
A certificate is evidence of a process, not of a given translation. Ask for the certificate scope and the issuing body, and check that the certificate is current.
What do examples look like?
Example 1: consumer product, Spanish. A CPSC-regulated toy has a choking hazard. The English notice has a heading with “Recall,” the product name, model numbers, the hazard and a refund remedy. The Spanish version keeps “Recall” beside the Spanish term on first use, repeats the model numbers character for character and puts “stop using the toy and keep it away from children” in the first sentence. A native reviewer checks the call to action.
Example 2: medical device, multilingual consignee letter. A firm recalls a device lot. The English letter opens with the FDA-style urgent heading. The firm raises the need for translations with its Division Recall Coordinator before issuance. Language versions are produced from a locked template. Only the device type, lot range and contact fields vary. Distributors confirm receipt through a reply form.
Example 3: vehicle owner letter. A manufacturer mails an owner letter for a defect. The envelope carries the phrase required by Part 577. A translated insert accompanies the letter. The VIN list and the dealer instructions are checked automatically against the source.
What are the failure modes and mitigations?
Failure mode | Effect | Mitigation |
Softened label such as “update” | Reader does not treat the notice as urgent | Locked label in term base, regulatory review |
Altered model or lot number | Reader wrongly believes the product is unaffected | Automated number check against source, second review |
Old translation memory match | Outdated remedy or phone number appears | Remove stale segments before the project, review all matches |
Technical or legal wording | Consumer does not understand the action | Plain-language rules, comprehension test |
Translations published late | Part of the audience is warned after the rest | Simultaneous release, same approval workflow |
Personal data in a vendor tool | Privacy exposure | Processing agreement, access control, data location stated in contract |
Unlogged machine step | No evidence of how text was produced | Audit trail, AI+HUMAN hybrid process with named reviewer |
English changes, translations do not | Conflicting instructions | Change log tied to version numbers |
How do you manage updates and versions when recall information changes?
Recall facts change. The affected range expands, the remedy becomes available, or the firm closes the recall. Each change must reach every language at the same time.
The U.S. Department of Labor recommends mapping content workflows for planning, publication, review, updates and retirement. Publication workflows should address how to update content for accuracy and timeliness. Retirement workflows should say whether content is removed or archived. See the Department of Labor content governance guide.
Apply that to translated recalls:
Give every notice a version number shared by all languages.
Mark the changed segments in the English source so the translator updates only those and reviews context.
Store each approved version, with date, approver and language.
Archive closed recalls with a visible status line instead of deleting them, unless the agency or counsel directs otherwise.
Keep the translation memory current. Add the approved final text, not the draft.
We treat recall notices as the highest-stakes short text a localization team handles. The text is brief, the reader may be at risk, and one wrong digit in a lot number defeats the whole notice. Our position is that speed and control belong together. The LangOps System, our proprietary AI platform on EU servers, produces the first draft. Linguists with subject-matter expertise review it as part of an AI+HUMAN hybrid process. Terminology comes from the client’s own term bases, so “recall” and the hazard terms never drift between channels. We also argue for planning translations before the recall is announced. A firm that has approved terms, templates and reviewers in place can release every language together when the time comes. Eric Brown
Our perspective
Where AD VERBUM fits
AD VERBUM is a language service provider with 25+ years of experience, 3,500+ subject-matter expert linguists and support for 150+ languages. It operates a proprietary LangOps System hosted on EU servers. Its certifications include ISO 17100, ISO 18587, ISO 13485, ISO 27001 and ISO 42001, audited by Bureau Veritas. It states a turnaround of 3x to 5x faster than traditional workflows. It imports client translation memories and term bases. See the translation and localization services for regulated documentation.
Key points
A translated recall notice keeps hazard, identifiers, remedy and firm identity identical to the English source.
Keep the word “recall” in the heading, or beside the translation on first use, and never replace it with “update” or “advisory.”
Translation requirements differ by agency. CPSC may require additional languages, FDA asks firms to discuss translations with the Division Recall Coordinator, and NHTSA sets envelope and letter format in Part 577.
Use plain language and put the action first.
Lock labels and hazard terms in a term base.
Check numbers, dates and codes automatically, then review them by a second linguist.
Treat mailing lists as personal data with access control and a processing agreement.
Version every language together and keep a change log.
FAQ
Does a U.S. recall notice have to be translated?
Not always. The CPSC can require additional languages when it decides this is needed to inform and protect the public, under 16 CFR 1115.26. FDA guidance tells firms to discuss multilingual communications with the Division Recall Coordinator. Confirm the current requirement with the agency handling the recall.
Should the word “recall” be translated?
Yes, with the English word kept in view. Use the natural target-language term, and keep “recall” in the title or alongside the translation on first use. Use the same approved term in every channel.
Who should approve a translated recall notice?
The recalling firm approves it. Regulatory affairs and legal sign off on each language against the English master. For FDA-regulated products, the Division Recall Coordinator can review communications before issuance.
Can machine output be used for recall notices?
Only inside a controlled process. Every segment needs human review by a subject-matter linguist, QA checks on numbers and codes, and an audit trail. Final approval stays with the recalling firm.
Sources