Annual Product Review (Supplements)
An annual product review for a dietary supplement is a structured periodic evaluation of manufacturing and quality information for a product or product family. It can expose trends and improvement needs, but its exact scope should follow the firm's quality system and applicable requirements rather than borrowed pharmaceutical claims.

On this page · 16 sections
- 1What a periodic product review can achieve
- 2Define product and period
- 3Build a balanced evidence set
- 4Turn the data into decisions
- 5Review and approve transparently
- 6Inside V5: assembling product history
- 7Explain it for your operation
- 8Reconcile the complete batch population
- 9Analyse trends with denominators and context
- 10Include contract-manufacturing evidence
- 11Make conclusions specific and testable
- 12A practical review structure
- 13A proportionate implementation plan
- 14Internal review questions
- 15Records and evidence to retain
- 16Questions to ask when evaluating software
How does Annual Product Review (Supplements) apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a periodic product review can achieve
A review gathers dispersed evidence into one product-level assessment: batches made, yields, specification results, deviations, material and supplier issues, complaints, returns, investigations, changes, stability information and open actions.
Part 111 does not simply create the same named annual-product-review provision used in drug GMP. A supplement firm should describe the review honestly as part of its quality oversight and avoid claiming a frequency or format that the applicable rule does not prescribe.
02Define product and period
State the products, strengths, flavours, package forms, sites, contract partners and dates included. If products are grouped, document why their formulation, process and risk permit a meaningful combined review.
Account for every planned, completed, rejected, reprocessed, reworked or cancelled batch so favourable results are not reviewed in isolation.
03Build a balanced evidence set
Review master and batch record changes, component and supplier performance, in-process and finished specifications, yield and reconciliation, deviations, investigations, complaints, returned product, reserve or stability information where applicable, label changes, sanitation or environmental signals relevant to the product, and action status.
Use rates and denominators, not counts alone. Explain missing data and distinguish confirmed causes from open hypotheses.
04Turn the data into decisions
Look for recurring failure modes, gradual shifts, differences by line or supplier, repeat temporary corrections and controls that generate frequent exceptions. Compare against prior periods using consistent definitions.
Conclude whether specifications, process controls, supplier controls, training, monitoring or the master record need review. Assign owners, due dates and the formal change or CAPA path where needed.
05Review and approve transparently
Quality personnel should review the source, calculations, exclusions, conclusions and open actions. Contract manufacturing responsibilities should be explicit so the brand owner and manufacturer understand what information each provides and who makes decisions.
Retain the review as a controlled record and preserve the underlying evidence. A dashboard snapshot without interpretation is not a product review.
06Inside V5: assembling product history
V5 can connect production records, material lots, quality records, document versions, training, equipment and traceability. This can reduce manual searching when authorised reviewers assemble a product-level view.
V5 does not determine the review's regulatory scope or approve its conclusions. People assess trends, decide significance and authorise actions.
07Explain it for your operation
Choose one high-volume or high-risk product and map where each review input lives. Agree definitions and denominators, reconcile the batch list, and create a short conclusion for every significant signal rather than attaching unexplained charts.
Track resulting actions outside the report with owners and dates, then use the next review to check whether decisions were completed and effective.
08Reconcile the complete batch population
Start from independently controlled production and disposition records, not a manually selected success list. Reconcile manufactured, packaged, released, rejected, reworked and destroyed quantities and explain cancelled or incomplete records.
Group by relevant formulation, strength, package and site. Preserve enough detail to see whether a favourable total hides a weak subgroup.
09Analyse trends with denominators and context
Plot key attributes and exceptions against batches or time, with limits and significant changes visible. Compare complaint rate to units distributed, deviations to batches produced and supplier failures to lots received.
Do not treat every fluctuation as deterioration. Consider method, specification, material, equipment and volume changes before concluding.
10Include contract-manufacturing evidence
Define data exchange, cut-off dates, investigation ownership, review and approval in the quality or commercial arrangements. Address missing or late information rather than silently omitting it.
The product owner and manufacturer may hold different evidence. The review should show how those views were reconciled and who owns each resulting action.
11Make conclusions specific and testable
State whether controls remain suitable, identify every unresolved signal and name the formal path for action. Avoid a generic ‘acceptable’ conclusion unsupported by individual evaluations.
Carry actions into the controlled action system and review their completion and effectiveness. The report is a decision record, not the end of the work.
12A practical review structure
Begin with an executive scope and reconciled batch table, then evaluate materials and suppliers, manufacturing performance, specification results, deviations, complaints, returns, stability or reserve information where relevant, changes and action status. Every section should state what the data show and what decision follows.
End with named conclusions: controls remain suitable, a trend needs further investigation, a master record needs change, or supplier oversight needs strengthening. Assign each action to a controlled record rather than leaving it only in meeting minutes.
13A proportionate implementation plan
- Confirm the applicable requirement, product scope and decision owner.
- Map the current method and the records already available.
- Define terms, responsibilities, evidence and exception handling in the approved procedure.
- Pilot the method on one representative process and challenge a difficult exception.
- Train affected roles, approve the change and monitor whether the method works as intended.
- Review after significant change and retain a transparent history of decisions.
Scale the formality to risk and complexity. A small operation still needs clear responsibilities and reconstructable evidence, while a multi-site operation also needs harmonised definitions, governance and comparison rules.
14Internal review questions
- Can a reviewer identify the source, owner, method and current approved version?
- Do summaries reconcile to original records and include unfavourable or missing evidence?
- Are exceptions visible, assessed and linked to the affected material, product or process?
- Are actions assigned, overdue items escalated and effectiveness reviewed?
- Have changes in product, supplier, equipment, method or regulation triggered reassessment?
- Does the record distinguish system support from the decision an authorised person made?
15Records and evidence to retain
- Approved scope, definitions and responsibilities for annual product review supplement.
- Source records and identifiers that let a reviewer reconstruct the work.
- Methods, assumptions, calculations, exclusions and any data-quality limitations.
- Exceptions, investigations, decisions, approvals and resulting actions.
- Version history showing when the approach changed and why.
Records should be proportionate to the decision and usable by someone who was not present. Preserve original evidence and corrections rather than replacing it with an unexplained summary.
16Questions to ask when evaluating software
- Can users trace every summary value back to its source record and version?
- How are roles, permissions, signatures and corrections recorded?
- Can the workflow reflect our approved procedure without inventing a universal rule?
- What happens during an outage, and how are later entries distinguished?
- Can we test the highest-risk exception with realistic data before committing?
- Which decisions remain explicitly assigned to an authorised person?
Frequently asked questions
Q.What is annual product review supplement?+
An annual product review for a dietary supplement is a structured periodic evaluation of manufacturing and quality information for a product or product family. It can expose trends and improvement needs, but its exact scope should follow the firm's quality system and applicable requirements rather than borrowed pharmaceutical claims.
Q.Is annual product review supplement required in every operation?+
The applicable product rules, market, risk and approved quality system determine what is required. The method should be justified for the operation rather than copied without context.
Q.Can software make the final quality decision?+
No. Software can organise records, calculations and workflow, but authorised people remain responsible for scientific, quality and disposition decisions.
Q.How should a site start?+
Choose one bounded process, define the decision and evidence, test the method with real records, correct gaps, then expand under change control.
Q.What evidence should be retained?+
Keep the approved method, source records, assumptions, exceptions, review, decision, approval and any resulting action with enough context to reconstruct the work.
Q.How often should it be reviewed?+
Use the applicable requirement and a risk-based cycle, with earlier review after significant change, failure, complaint, deviation or new knowledge.
Primary sources
Want to see how Annual Product Review (Supplements) could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
