For two years, the industry debated whether FDA would ever cite a firm for how it used AI. On 2 April 2026, it did.
The FDA AI warning letter to Purolea Cosmetics Lab is the first to call out AI misuse in drug manufacturing by name. The firm had used AI agents to write its drug product specifications, procedures and master production and control records. Nobody in the quality unit checked them properly.
FDA did not ban AI. It said something more useful: the tool changes nothing about who is accountable. If your teams, or your contract manufacturers, are drafting SOPs or batch records with ChatGPT, Copilot or an AI agent, this letter tells you what an investigator will ask for.
FDA’s position is simple: AI can help write a GMP document, but the quality unit still owns it.
Purolea is a small homeopathic drug maker in Livonia, Michigan. FDA inspected the site from 28 to 30 October 2025 and issued Warning Letter 320-26-58 on 2 April 2026. Most of the letter covers familiar failures: insanitary conditions, no microbial release testing, and components accepted on supplier certificates alone.
The new part sits under the quality unit citation. The firm told investigators it used AI agents to create:
FDA wrote that if you use AI as an aid in document creation, you must review the AI-generated documents to make sure they are accurate and actually compliant with cGMP. Failing to do that was cited as a violation of 21 CFR 211.22(c), which requires the quality unit to approve or reject procedures and specifications.
FDA inspects Purolea’s Livonia, Michigan site and documents AI use.
FDA issues Warning Letter 320-26-58 citing 21 CFR 211.22(c) and AI overreliance.
Investigators also found the firm had not performed process validation before distributing product, as 21 CFR 211.100 requires. Asked why, the firm said it did not know about the requirement because the AI agent never told it.
FDA rejected that answer. If the firm resumes manufacturing, the letter says any output or recommendation from an AI agent must be reviewed and cleared by an authorised human representative. FDA also asked the firm to bring in a qualified consultant for a full six-system audit before resuming.
FDA is not saying AI is off-limits. As one regulatory attorney told RAPS, the problem was that “no one reviewed it” — not that AI was used.
AI-generated SOPs and batch records fail in a specific way: they look finished. That is exactly what makes them risky.
Three failure modes show up in the Purolea case and in the commentary that followed:
The fix is not a new rule. FDA applied the existing one: the quality unit must approve procedures and specifications, and review batch records before release. What changes is how much scrutiny an AI draft needs.
| Document | Where AI can help | What the quality unit must still verify | Rule in play |
|---|---|---|---|
| SOPs | First draft, structure, plain-language rewrite | Matches the real process, cites current regulations, nothing missing | 21 CFR 211.22(c), 211.100 |
| Specifications | Formatting, pulling compendial references | Every limit, method and reference is correct and justified | 21 CFR 211.22(c), 211.160 |
| Master production and control records | Template build, step sequencing | Each step, quantity and in-process control matches the validated process | 21 CFR 211.186 |
| Executed batch records | Completeness checks, error flagging | Full QU review before release; no AI approval | 21 CFR 211.192, 211.22(a) |
| Deviations and CAPA | Summaries, trend search | Root cause logic, impact assessment, approval | 21 CFR 211.192 |
| Inspection responses | Drafting support | Every citation and commitment is real and accurate | Firm accountability |
For electronic records, the same logic extends to 21 CFR Part 11 and ALCOA+: you should be able to show how a final record was created, who edited it and who approved it.
Purolea was the first letter, not the last. One industry analysis counted 11 AI-adjacent warning letters and 3 that named AI explicitly in Q2 2026 (April to June).
The same analysis says most of the AI-adjacent letters went to overseas sites, particularly in India. Its explanation is inspection frequency, not AI adoption: Indian sites are inspected more often, so gaps surface there first. Treat these counts as indicative; the analysis reconstructed them from FDA’s letter index and trade press.
For sponsors, the message is direct. If you rely on a contract manufacturer, assume your partner will be asked to show AI controls on the same terms you would be. Your accountability for product quality does not move to the CMO.
Which AI or ML tools touch GMP activities, including those built into validated platforms?
What decision does each tool support, how risky is it, and where are its limits?
Show the SOP, reviewer qualification and audit trail that turns AI output into a GMP record.
How are model updates, retraining and prompt changes assessed by QA?
Practical step: add AI clauses to your quality agreements. Cover permitted AI uses, human review, records of AI use, change control for models and prompts, and your audit rights.
Yes, but only inside a controlled process. The model itself cannot be validated the traditional way; the way you use it can.
A reasonable expectation is that an auditor will treat a general-purpose chatbot like any other unqualified software. If it drafts SOPs, you should be able to show that the activity was assessed, controlled and verified. Europe is heading the same way: draft EU GMP Annex 22 would keep generative AI and large language models out of critical GMP uses, allowing them in non-critical tasks with documented human oversight. The draft is not yet in force.
An AI that does not know what it does not know will not tell you what it missed. Your reviewer has to.
RxCloud helps life sciences teams adopt AI in a way that stands up to inspection, at your sites and at your partners’.
RxQCAgent is built for exactly the gap Purolea exposed: it helps reviewers catch problems earlier, while the approval decision stays with your quality unit.
Related reading: EU GMP Annex 22 explained · How to validate AI in pharma · GxP-compliant AI systems
Warning Letter 320-26-58, issued on 2 April 2026 to Purolea Cosmetics Lab in Livonia, Michigan. It is the first cGMP warning letter to cite overreliance on AI in drug manufacturing.
21 CFR 211.22(c). The quality unit failed to review AI-generated specifications, procedures and master production or control records for accuracy and cGMP compliance. The letter also cites missing process validation under 21 CFR 211.100.
No. FDA said AI output must be reviewed and cleared by an authorised human before use. The issue was unreviewed AI output, not AI itself.
Yes, inside a controlled process: an approved tool, a defined use, a validated workflow, qualified human review, quality unit approval and records of each step.
You validate the process of using it, not the underlying model. Define intended use, test with known answers, set acceptance criteria and scale the effort to the GMP risk.
Yes. Sponsors stay accountable for product quality. Expect CMOs, especially frequently inspected overseas sites, to be asked about AI controls, and cover AI in your quality agreements.
Draft EU GMP Annex 22 covers AI in GMP. It would keep generative AI out of critical uses. It is still a draft; the EMA’s target for final text is Q4 2026.
Talk to our quality team about an AI-readiness review of your sites, your SOPs and your contract manufacturers.
Talk to our quality team