FDA Recall

Regulatory Event

The FDA has classified a nationwide recall of eight Rohto Cooling Eye Drops products as Class II, covering 11,960,623 cartons — roughly 12.46 million bottles — sold at Walmart, CVS, Amazon, Kroger, and directly through the manufacturer’s own online store. Rohto-Mentholatum (Vietnam) Co., Ltd. initiated the voluntary recall on July 14, 2026; FDA assigned the Class II classification on July 23. The stated reason is “lack of assurance of sterility” — notably, FDA’s public record does not cite a specific identified contaminant, degradation product, or confirmed non-sterile test result. The recall spans the full Rohto Cooling Eye Drops line: ALL-IN-ONE, Max Strength (single and twin-pack), Optic Glow, Digi Eye, Dry Aid (single and twin-pack), and Cool Relief, each a distinct multi-ingredient formulation. The Mentholatum Company, the US distributor based in Orchard Park, New York, told trade press the action followed “a manufacturing review at the production facility in Vietnam involving manufacturing process and controls,” adding that “there has been no evidence indicating that product does not meet specifications” and that the recall is a precautionary measure. No adverse events have been reported.

That framing is worth sitting with, because it is easy to read a Class II classification — and a company statement emphasizing no confirmed nonconformance — as evidence this is a low-stakes, almost administrative event. It is not. FDA’s Class II designation reflects the probability of serious harm given the product’s use pattern: an OTC topical eye drop carries lower acute risk than an injectable, which is part of why an equivalent “lack of assurance of sterility” finding in a parenteral product would likely be evaluated as Class I. The classification describes consequence, not root cause severity. A recall phrase like “lack of assurance of sterility,” issued in the absence of a specific confirmed contamination event, typically means something more structurally significant than a single failed lot: it means the firm’s own review could not demonstrate, with adequate data, that its sterility assurance program was operating as designed across the affected production run. That is a program-level finding, not a batch-level one, and it is the kind of finding that shows up during self-initiated manufacturing reviews precisely because it is the kind of gap that routine batch release testing is not designed to catch on its own.

What the Record Documents

For a multi-dose, non-sterile-manufactured OTC ophthalmic product line like this one, sterility assurance rests on a combination of controls: environmental monitoring trending in the filling and packaging areas, preservative effectiveness testing (PET) validated against the specific formulation and container-closure system, container-closure integrity for the dropper-tip delivery format, and bioburden control at critical process points before and after fill. Ophthalmic drops are formulated with antimicrobial preservatives specifically because they are used repeatedly from an open, multi-use container after purchase — but PET validation is only meaningful if it is re-verified whenever formulation, packaging component, or process parameters change, and if ongoing environmental monitoring data continues to support the original validation over time. A “manufacturing review” that surfaces a sterility assurance gap without a specific failed lot is the profile of a firm discovering that one of these supporting pillars — most plausibly environmental monitoring trend data, PET revalidation currency, or bioburden control documentation — no longer demonstrated the assurance the original validation claimed, prompting a recall of everything within the affected timeframe rather than a narrower, contaminant-specific action.

This is exactly the scenario 21 CFR 211.192 exists to prevent. The production and process control review requirement obligates a quality unit to review and evaluate any unexplained discrepancy or failure of a batch to meet its specifications before that batch is released — and, critically, to extend that investigation to other batches that may have been associated with the specific failure or discrepancy. When a firm’s internal review later identifies a gap of this kind across a broad production window spanning eight product lines and configurations, it raises the direct question of whether the original batch release review had sufficient visibility into the underlying sterility assurance data trends to flag the issue before, not after, product reached the shelf. A batch record review that confirms specification compliance on a per-lot basis without cross-referencing ongoing environmental monitoring and PET trend data across the review period is structurally unable to catch a program-level assurance gap like this one, even when every individual lot passes its own point-in-time release tests.

Technical and Quality Context

Whether this is an isolated finding at this one facility or part of a broader pattern is not yet answerable from the public record, and this article should not overreach on that point. What is fair to note is that this is the second Class II recall in recent weeks tied to a sterility assurance issue in a topical ophthalmic product, following FDA’s Class II classification of Lupin Limited’s prednisoLONE Acetate Ophthalmic Suspension for a separate foreign-substance finding. The two events involve different companies, different manufacturing sites, and different specific mechanisms, and should not be conflated into a single root cause — but together they are a reminder that ophthalmic products, despite their outward simplicity as OTC or prescription drops, carry sterility assurance and container-closure obligations that are easy to under-resource relative to injectables, precisely because the acute risk profile is lower.

Quality directors overseeing topical ophthalmic or other multi-dose preserved products should treat this recall as a prompt to verify three things directly, with data rather than assumption: that PET validation for every marketed formulation and container-closure combination remains current against the actual production process in use today, not the process in place when the original validation study was executed; that environmental monitoring trend data from filling and packaging areas is being reviewed on a rolling basis for excursions or drift, not only checked against action limits lot by lot; and that batch record review under 211.192 explicitly incorporates a check against current sterility assurance trend data before release, rather than treating batch release and program-level quality trending as two separate, disconnected review streams. A program that only fails when a specific lot fails point-in-time testing will, by design, miss exactly this kind of assurance gap until a recall of this scale becomes the only remaining corrective option.

Decision Relevance

XGene Consulting works with OTC and prescription topical drug manufacturers on sterility assurance program design and remediation — PET validation strategy, environmental monitoring program review, and building batch release review processes that connect point-in-time lot testing to ongoing program-level trend data rather than treating them as separate systems. If your quality unit could not answer, with current data, whether your own preservative effectiveness and environmental monitoring validation still reflects your actual production process today, that is a gap worth closing before it becomes a recall notice of your own.