“Not from drug products intended for the U.S. market” — the boundary your quality system does not have
483 response filed 27 February 2026 · Citations 21 CFR 211.194(a), 211.22(d)
A contract testing laboratory in Bengaluru was inspected over three days in February 2026. Investigators asked for the raw data behind a set of microbial test reports and found sheets with blank spaces where plate counts belonged. The firm answered inside the window with a fact FDA never disputed: the samples in question were not from drug products intended for the United States.
FDA accepted the fact and rejected the argument. A 483 response cannot be bounded by a line that does not exist inside the quality system it is defending.
Earlier issues asked how large a retrospective review must be. This one asks which population you may draw it from.
What FDA found
Auriga Research Pvt. Ltd. tests drug products for the U.S. market under contract. The first finding is documentary, not analytical. Summary reports carried final plate counts; the raw data sheets beneath them, for some of the same samples, did not. FDA’s description is plain: “the test sheets had blank spaces where entries should have been recorded.”
The second finding is what the quality unit did with results it could see. Three out-of-specification investigations, each closed on a passing repeat: an assay that passed once the autotitrator was swapped; a second whose initial test and five repeats were all invalidated on a weighing error; a stability impurity resolved by retesting retains in triplicate. In two of three, the preventive action was that somebody was told. FDA names the pattern: “testing into compliance.”
- 4 – 6 Feb 2026
- FDA inspects the Bengaluru laboratory and requests raw data behind microbial test reports.
- 27 Feb 2026
- 483 response filed. Documentation gaps acknowledged; the affected samples identified as non-U.S. product.
- 12 Aug 2026
- Warning letter. Both responses inadequate; consultant recommended; three-year retrospective OOS review requested.
What the firm said
This is the response most firms write, and the instinct is defensible. FDA’s authority runs to drugs for the U.S. market; if the records at issue sit outside that, saying so is not evasion but ordinary scoping. The firm paired it with a second point, offered in good faith and, on its own terms, accurate.
“consistent with an institutional procedural and cultural gap rather than individual misconduct or a coordinated effort to conceal or falsify results” Firm’s 483 response, as quoted by FDA
It is a carefully built sentence. It declines to blame an analyst — the failure mode this series has examined before — and puts on the record what the firm most wanted there: nobody falsified anything. The firm also committed to more quality unit presence at the bench until compliance monitoring showed sustained adherence.
Why FDA rejected it
One quality system, one population
FDA did not contest that the samples were non-U.S. It contested that the distinction was available. The finding was not about those samples; it was about the procedures that produced them, and those procedures carry no market boundary.
“In your response, you stated these samples were not from drug products intended for the U.S. market. However, your firm maintains one quality system and has one set of procedures for testing U.S. and non-U.S. drug products. Thus, the quality unit (QU) failure is applicable to all drug products you test.” FDA, Warning Letter 320-26-113
The exculpatory sentence, read as evidence
The disclaimer of misconduct did more work than intended. FDA quotes it back and draws the opposite inference: “This indicates that these violative practices are used for all drugs you test, including those for the U.S. market.” Individual misconduct is bounded — one analyst, one bench. A procedural and cultural gap is not. In establishing that it was not the first, the firm established the second.
Revising the procedure without reading what the old one produced
FDA is direct: “you are revising procedures without performing a gap analysis of your investigations.” A revised SOP governs the next investigation and says nothing about the closed ones — which sit behind batches already released. The documentation finding draws the same objection: no evidence of “a retrospective review to identify any additional instances of incomplete or non-contemporaneous documentation.”
The function under review is offered as the remedy
The corrective action was more quality unit presence at the bench. But the quality unit is what “reviewed and approved all your out-of-specification investigations,” and FDA notes the response “failed to address the authority, responsibility, and competency” of that unit. More of a function whose judgment is the finding is not a corrective action.
The pattern worth carrying forward
Every 483 response draws a line around the problem — the finding is here, it reaches this far, no further. That line gets drawn where it looks most defensible, and jurisdiction looks strongest of all: it is the boundary FDA is itself bound by.
But FDA does not size a finding by market. It sizes it by system. The question is not which samples were affected; it is which procedures, which analysts, which quality unit. Where those are shared, the affected population is everything they touch. Draw a line your own SOPs do not draw, and you have told FDA you are scoping by exposure rather than by cause.
- Does this boundary exist in our procedures? If U.S. and non-U.S. work run on one SOP set, one system and one quality unit, the market line is a commercial fact, not a quality one. FDA will scope to the shared control; scope there first, and say so yourself.
- What does our own explanation commit us to? “Procedural gap, not misconduct” is written to exculpate and lands as systemic. Read every characterisation you offer as though FDA were sizing the review population from it.
- Are we fixing forward only? A revised procedure governs the next investigation. Name what you have done about the closed ones: the gap analysis, the retrospective review, and the batches those decisions released.
A defensible response would have conceded the shared system in its first paragraph — one procedure set, one quality unit, one review population — then narrowed on evidence rather than jurisdiction: the gap analysis of closed OOS investigations, the retrospective review of documentation practice, and what each one found.
The only boundary you can defend is the one your own procedures already drew. Draw a narrower one, and FDA will replace it with its own.
Veritas Quality Consultants works with pharmaceutical, medical device, and biologics manufacturers on Form 483 responses, root cause analysis, and CAPA development — built to FDA expectations inside the 15-day window.
Request a consultation