APQR (Annual Product Quality Review) in Pharma: What It Must Cover
2026-06-09
What an Annual Product Quality Review (APQR / PQR) must cover in pharma — batches, deviations, OOS, complaints, change controls, stability, CAPA — the regulations (21 CFR 211.180, EU GMP Ch.1, Schedule M, ICH Q7), and how to make it continuous instead of a year-end fire-drill.
Once a year, a pharma quality team disappears into a spreadsheet marathon. Pull every batch record for the product. Every deviation. Every OOS. Every complaint, change control, and stability result. Stitch it into one document, find the trends, and certify that the process stayed in control. That document is the Annual Product Quality Review (APQR) — and for most companies it's weeks of manual compilation that's out of date the moment it's finished.
This guide covers what an APQR (also called a Product Quality Review, PQR) must contain, the regulations behind it, and how to stop it being an annual fire-drill.
What an APQR is
An APQR is a periodic (usually annual) review of all quality data for a product, done to verify that the manufacturing process and its specifications remain consistent and in control, to spot trends before they become problems, and to drive improvements. It's not a box-ticking summary — it's the evidence that your quality system actually worked over the year.
The regulations behind it
The APQR/PQR is a hard requirement, not best practice:
- US FDA — 21 CFR 211.180(e) requires an annual review of records to evaluate quality standards and determine the need for changes.
- EU GMP — Chapter 1 (Product Quality Review) sets out, in detail, the elements a PQR must cover.
- India — Schedule M (Revised) requires periodic quality reviews of products.
- ICH Q7 carries the equivalent requirement for active pharmaceutical ingredients.
- WHO GMP mirrors these expectations for emerging-market inspections.
What an APQR must cover
This is where the work is. A complete APQR pulls together a full year of data from across the quality system:
- Starting and packaging materials — suppliers used, any changes, incoming results.
- In-process and finished-product results — critical parameters and specification results, with trends.
- Out-of-specification / out-of-trend results — every OOS investigation and its outcome.
- Deviations — all deviations for the product, their root causes and recurrence.
- Change controls — every change control affecting the product, material, or process.
- Market complaints and recalls — all complaints and any recalls, with patterns.
- Stability results — outcomes of stability studies and any adverse trends.
- Returns and rejections — rejected batches and the reasons.
- CAPA status — effectiveness of corrective actions raised during the year.
- Equipment and utility qualification status, and the status of technical/quality agreements and regulatory commitments.
The review ends with a conclusion — is the process in control? — and a set of recommendations and CAPAs for the year ahead.
The APQR is your quality system, summed up
A YEAR OF QUALITY EVENTS THE APQR
------------------------ --------
Deviations ────────────┐
OOS / OOT ─────────────┤
Change controls ───────┤ aggregate + Is the process
Complaints / recalls ──┼────── trend ────────► in control?
Stability results ─────┤ per product + CAPAs / actions
Batch + spec results ──┤ for next year
CAPA effectiveness ────┘
Look at that list and the truth becomes obvious: the APQR isn't a separate task — it's the sum of everything your quality system did all year. If those events are captured as connected, structured records, the APQR is a query. If they live in paper files, shared drives, and a dozen registers, it's a three-week archaeology project.
Why the annual fire-drill happens
For most companies APQR is painful for one reason: the data is scattered and disconnected. Deviations are in one register, OOS in another, complaints in email, stability in a lab notebook, change controls in a binder. So once a year someone manually hunts down a year's worth of records per product, re-keys them into a template, and tries to trend numbers that were never stored in a trendable form. By the time it's compiled, it's already stale — and it can't tell you anything during the year, when it would actually be useful.
How to make APQR continuous, not annual
The fix isn't a better template — it's capturing the underlying events as structured, connected data in the first place:
- Every quality event is a record, not a document — each deviation, OOS, complaint, change control, and stability result is captured in structured fields, tagged to the product and batch.
- They're linked — a complaint ties to its deviation and CAPA; an OOS ties to its batch. The relationships the APQR needs already exist.
- The review becomes a query — pulling the year's deviations, OOS, complaints, and trends for a product is a filter, not a file hunt.
- And it's live — the same data that builds the APQR can be watched through the year, so trends surface in month three, not at year-end.
How Flobri does it
Flobri runs each quality process — deviation, OOS, change control, complaints, recall, CAPA, stability, batch release — as connected, audit-ready workflows, each event tagged to its product and batch. So an APQR isn't a year-end project:
- The year's deviations, OOS, complaints, change controls, and stability results for a product are already captured and linked — the compilation is a filter, not a hunt.
- Trends are continuous — you see them as they build, with a complete audit trail behind every number.
- The reviewer spends their time on the conclusion and the CAPAs, not on assembling the data.
Frequently asked questions
What is APQR in pharma?
The Annual (or periodic) Product Quality Review — a yearly review of all quality data for a product (batches, deviations, OOS, complaints, change controls, stability, CAPA) to confirm the process and specifications stayed consistent and in control, and to drive improvements.
What's the difference between APQR and PQR?
They're the same thing — "Product Quality Review" (PQR) is the EU GMP term, "Annual Product Quality Review" (APQR) is the common US/India term. Both describe the same periodic review.
What regulations require it?
US FDA 21 CFR 211.180(e), EU GMP Chapter 1, India's Schedule M, ICH Q7 (for APIs), and WHO GMP all require a periodic product quality review.
How often must an APQR be done?
Typically once a year per product, though the exact period is whatever your procedure commits to and your regulators expect.
What should an APQR conclude?
Whether the manufacturing process and specifications remained in a state of control, what trends or recurring issues were found, and what corrective/preventive actions and improvements are needed for the coming year.
Flobri runs deviation, OOS, change control, complaints, recall, CAPA, stability, and batch release as connected, audit-ready workflows — so the data your APQR needs is captured, linked, and trendable all year, not reconstructed at year-end. See how Flobri handles pharma quality workflows.