FDA Warning Letter

Regulatory Event

Dabur India Limited, the New Delhi-headquartered consumer health and pharmaceutical group, received FDA Warning Letter 320-26-105 on July 24, 2026, following a January 12–16, 2026 inspection of its over-the-counter drug manufacturing facility at Survey No. 225/4/1, Village Saily, Silvassa, in Dadra and Nagar Haveli and Daman and Diu, India. The letter’s lead finding is not a missed specification or an equipment malfunction. It is a falsified logbook. FDA’s investigator requested the equipment usage logbook for a manufacturing unit and line that Dabur’s own management stated was dedicated exclusively to one product. The firm delayed producing the record for several days, and when it finally appeared, the investigator subsequently discovered the original logbook still sitting in the document room. The two documents did not match. The version handed to FDA listed entries only for the single product management had described, deliberately omitting multiple U.S.-marketed OTC drug products that were documented in the original.

That observation, cited under 21 CFR 211.22(a) as a failure of the quality unit’s authority and responsibility to review production records for errors, is why this letter reads as data integrity rather than a documentation lapse. Fabrication is not a training gap; it is evidence that someone at the facility understood the exposure created by the real record and manufactured a substitute to conceal it. FDA’s letter goes further: investigators also found discrepancies between the source data in Dabur’s analytical data books and the final values reported in batch manufacturing records and certificates of analysis, for residue on ignition, melting range, pH, and viscosity across multiple batches. None of the discrepant values were themselves out-of-specification results, which makes the finding more troubling rather than less. A quality unit that signs off on records without reconciling source data to reported values has abandoned the basic ALCOA+ discipline — Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, Available — regardless of whether the underlying product happened to pass.

What the Record Documents

Dabur’s February 2026 response attributed the falsified logbook to “inadequate documentation controls, insufficient oversight, and lack of robust governance,” and proposed retraining personnel, revising procedures, and sending a limited sample of affected product to a contract laboratory for retesting. FDA rejected this as inadequate for a reason every Chemistry, Manufacturing, and Controls (CMC) and quality practitioner should internalize: the response treated fabrication and data discrepancy as isolated procedural gaps rather than as evidence of a systemic breakdown in quality unit oversight and quality culture. It did not address whether the individuals responsible for the falsified record retain the ability to influence Current Good Manufacturing Practice (CGMP)-related or drug application data going forward. It did not include a comprehensive retrospective risk assessment of the potential impact on drug products already distributed to the U.S. market. And it did not evaluate whether the quality unit is capable of performing its required functions at all.

This is the same enforcement logic FDA applied to Ranbaxy Laboratories’ Paonta Sahib facility in India, placed under Import Alert 66-40 in 2008 after investigators documented that analysts were selectively reporting passing chromatographic results while discarding failing runs — a violation of 21 CFR 211.194(a)(8)’s requirement that laboratory records be complete, accurate, and attributable to the individuals performing the work. It is also the reasoning behind Sun Pharmaceutical Industries’ 2014 Warning Letter for its Halol facility, where backdated laboratory records and shared analyst login credentials under 21 CFR 211.68(b) and 211.194(a) triggered an 18-month FDA reinspection cycle and a re-evaluation of more than 40 stability studies. Dabur’s failure mechanism is different — this is paper-based logbook fabrication and manual transcription discrepancy, not electronic chromatography data manipulation — but the regulatory conclusion FDA draws is identical: once an investigator finds one falsified or unreconciled record, the agency’s default assumption is that the quality system itself, not a single employee, is the point of failure.

Technical and Quality Context

The letter’s second citation, under 21 CFR 211.194(a), compounds the picture. Dabur’s analytical notebooks documented microbiology plates for finished drug products and media plates for process water testing as incubated, but the plates themselves were physically absent from the incubators, with no documented explanation of their disposition. Separately, the firm could not produce test procedures, analytical workbooks, or test data sheets supporting the certificate of analysis results for a defined set of U.S.-marketed batches, and had not made the required entries in equipment logbooks reflecting which instruments were used for specific release tests. FDA’s assessment of this pattern is direct: “reliability of data is fundamentally compromised when there is a failure to record data or to maintain complete and accurate records of test results.” A quality unit cannot exercise its disposition authority under 21 CFR 211.22 if it cannot first verify that the underlying test data actually exists.

Two further citations round out the letter and explain the drug recall that followed. Under 21 CFR 211.67(b), Dabur’s cleaning validation program for a non-dedicated manufacturing line relied exclusively on visual inspection, with no scientifically derived maximum allowable carryover limits, no quantitative residue testing, and no direct surface sampling of difficult-to-clean areas; a second shared line used to manufacture multiple OTC drug products had no cleaning validation performed at all. Under 21 CFR 211.100(a), the firm confirmed during the inspection that it had not performed process validation for a defined subset of the drug products it manufactures across two separate unit lines — FDA’s published letter redacts the exact count, but the admission covers products on both named lines. FDA held a teleconference with Dabur on May 13, 2026 recommending removal of affected batches from the U.S. market. Dabur issued a voluntary recall on June 2, 2026 covering several product lines, but as of the letter date had not recalled others. FDA placed all Dabur drug products offered for import into the United States under Import Alert 66-40 on June 5, 2026 — a supply chain consequence that follows directly from a data integrity finding, not from a failed product quality test.

Decision Relevance

For quality and regulatory leaders reading this letter, the lesson is not “improve logbook discipline.” It is that FDA’s remediation expectations for a falsification finding are categorically different from its expectations for a documentation-gap finding, and a response built around retraining and a contract-lab retest of a narrow sample set will be rejected, as Dabur’s was. FDA explicitly recommended engagement of a qualified independent consultant to conduct a comprehensive six-system audit of the entire operation, and asked Dabur to state whether it will appoint a Chief Integrity Officer empowered to receive anonymous employee complaints and ensure any potential breach is investigated independently. Companies facing a comparable finding need a data integrity remediation program built to that standard from the outset — a scoped investigation methodology, third-party-led personnel interviews, a retrospective risk assessment of distributed product, and a root-cause analysis that identifies whether individuals involved in the falsification still influence CGMP data — not one assembled only after a first response has already been rejected and the Import Alert exposure has extended by months. That is the specific gap XGene Consulting’s data integrity and quality system remediation practice is built to close: designing the investigation protocol, ALCOA+ implementation plan, and CAPA effectiveness framework FDA expects to see before a facility can credibly pursue resolution of its compliance status. If your quality system carries any of the same exposure — shared or non-dedicated logbooks, unreconciled analytical transcription, or cleaning validation resting on visual inspection alone — the time to find out is before an investigator does. Reach out to discuss a confidential CGMP and data integrity gap assessment.