FDA's annual review asks less than the PQR does

211.180(e) sets a floor: batches, complaints, recalls, investigations

21 CFR 211.180(e) requires written records to be kept so that data can be used to evaluate, at least annually, the quality standards of each drug product, specifically to decide whether specifications or manufacturing and control procedures need to change. The written procedures the subsection requires have to cover, at minimum, a review of a representative number of batches, whether approved or rejected, together with a review of complaints, recalls, returned or salvaged product, and any investigation conducted under 211.192 for that product over the period. The regulation names a floor, not a format — it doesn't require a single consolidated report, a fixed template, or a review completed within any stated number of days of the period's close.

ICH Q7 names the same review and widens it

FDA adopted ICH's Q7 guidance for active pharmaceutical ingredients in August 2001, and Q7's own section 2.5 calls for a periodic, documented product quality review covering a wider list than 211.180(e) names on its own: critical in-process control and test results, failed batches, deviations, changes, stability-program results, returns, complaints, recalls, and the adequacy of the corrective actions already taken. A firm manufacturing only drug products under 211.180(e), with no API operation Q7 would reach, can run a narrower review than one that also has to answer Q7's own broader list.

EU GMP's PQR reaches further still

EU GMP Part I, Chapter 1, requires a product quality review under its own name and extends the list again: starting and packaging materials, the qualification status of relevant equipment and utilities, and any regulatory variations tied to the marketing authorization all sit inside the EU's version of the same annual document, alongside the elements Q7 and 211.180(e) already share. A review built strictly to FDA's own minimum, covering only batches, complaints, recalls, returns, and 211.192 investigations, hasn't addressed equipment qualification or a marketing-authorization variation at all — not because the firm did anything wrong, but because FDA's own regulation never asked it to.

One document, built to the broadest scope, covers the rest

None of the three frameworks conflicts with the others; they overlap on a shared core and diverge only in how far past that core each one reaches. A firm selling only into the US market can run the review 211.180(e) describes and nothing more. A firm that also manufactures an API, or sells into the EU, is already required to meet the wider list somewhere — and the practical version of this document that most multinational manufacturers actually run is a single annual review built to the EU's broader scope, which happens to satisfy FDA's narrower one inside it rather than running three separate reviews against three separate lists.

Where this meets the file

An annual product review template built around the union of these three lists — FDA's own minimum nested inside the broader ICH and EU elements, each section citing which framework actually requires it — is previewed in the launch catalog alongside this blog's other validation and release templates. If your site runs this review differently, the shelf takes that correction directly.