What this is
What counts as a product change under this record?
What counts as a product change under this record?
A product change is any alteration to what the finished product is, contains or is labelled as — a different recipe, ingredient, supplier, pack format, label or declared shelf life. It does not cover how the product is made; that's a process change (QUA-070). The two route to different reviewers and trigger different downstream checks.
How is a product change different from a Management of Change (MOC) record?
Management of Change (FDN-020) is the umbrella record for any change that isn't a like-for-like replacement, across any function on site. A product change request is the specialised version, carrying label, allergen and shelf-life questions an MOC would not ask. Where the change also needs the wider MOC process, the PCR links to it.
Why does a product change sometimes need the customer's approval and sometimes not?
Customer approval is usually contractual, not regulatory — private-label agreements often reserve the right to reject a recipe, supplier or pack change before it reaches their shelf. It depends on the specific contract, which is why the record asks the question rather than assuming an answer.
Scope
When is a product change request required?
This record covers what changes about the product, not how it's produced and not a short-term deviation. Raising it for the wrong change sends it to reviewers who can't approve what's being asked.
Use this template when
- A recipe, ingredient, supplier, pack format, label or declared shelf life is about to change, or has just been proposed
- The change reaches the ingredient list, allergen declaration, nutrition panel or a label claim, and needs sign-off before print
- A new supplier is replacing an existing one for the same ingredient, and the swap needs a formal approval trail
- The customer's contract requires them to see and approve product changes before they take effect
- A linked specification record needs updating to match what's now being made
Do not use it for
- Process Change Request (QUA-070), which covers a change to equipment, settings or sequence rather than the product itself
- Validation Record (QUA-071), which records the evidence a change works, once the PCR has approved making it
- Temporary Change Authorization (QUA-072), which authorises a short-term deviation with an end date, not a permanent change
- Management of Change (FDN-020), the broader record for changes that don't fit a specialised template
- Anything outside KnowQuality, such as a supplier onboarding that belongs to procurement rather than product specification
Compliance mapping
Which ISO 9001 cl.8.5.6 requirements does this satisfy?
ISO 9001 cl.8.5.6 requires organizations to control changes for production or service provision, reviewing the extent needed. The clause is short; the form makes that review concrete for a food manufacturer.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.5.6(a) | Review the consequences of change | Food safety and legal review |
| ISO 9001 cl.8.5.6(b) | Verify conformity before the change proceeds | Customer and supply |
| ISO 9001 cl.8.5.6 | Control the change, including formal authorisation | Decision |
| ISO 9001 cl.7.5.3 | Control of documented information, including spec and label | Downstream requirements |
| ISO 9001 cl.8.5.1 | Traceable identification and target implementation date | Header |
| ISO 9001 cl.8.3.6 | Control of design and development changes to the recipe | The change |
| ISO 9001 cl.9.1.3 | Evaluation of the change's effect after implementation | Decision |
What it does not cover
- An allergen profile change with 'New Allergen Introduced' left blank, which leaves the highest-risk question in the form unanswered.
- A 'Yes' on Claims Affected with no note on which claim changes, which gives quality nothing to check the artwork against.
- Customer Approval Required marked Yes with no Customer Notified entry, which breaks the approval chain before it starts.
- A Decision of Approved recorded before the HACCP reassessment it triggered is closed, which authorises a change the safety case hasn't caught up with.
- An Effective From date earlier than the Artwork Approved date, which means the change went live under the old label.
Global
Product Change Request requirements by country
A product change touches labelling and allergen law before anything else, and that law differs sharply by market. These are the three regimes most manufacturers running this template have to satisfy.
FALCPA, given effect through 21 CFR 101.9 and 101.22 (nutrition and allergen labelling)
Any of the nine major allergens introduced by an ingredient or supplier change must appear in the 'Contains' statement before the product ships
New Allergen Introduced and Nutrition Panel Changes are effectively a pre-check against a labelling recall, not an internal formality
Regulation (EU) No 1169/2011 on the provision of food information to consumers
The ingredient list, allergen emphasis and nutrition declaration must be updated in step with any recipe change
A recipe or supplier change without a matching label review is a labelling non-conformance the moment it reaches an EU or Northern Ireland shelf
Food Information Regulations 2014 (retained EU law) and the 2019 amendment known as Natasha's Law
Full ingredient labelling, including allergens, is required even for products packed on-site for direct sale
A pack-format change that moves a product to prepacked-for-direct-sale status changes its labelling obligations entirely — exactly what this record is meant to catch
How to complete it
How to complete a product change request, step by step
Filling in the fields is mechanical. Whether the record stands up to scrutiny later comes down to four judgement calls.
Cost, Regulatory or Supplier driven tells an auditor almost nothing on its own. The detail field either shows the working — the specific driver, the alternative considered, why this option won — or leaves a justification that won't survive a second look.
Every field in that section is a gate, not a formality. If the recipe or supplier is effectively locked in before the allergen, nutrition and HACCP questions are asked, the review becomes a record of a decision already made rather than a check on it.
Skipping customer sign-off speeds the change up. Whether it's defensible depends on the contract, not how the requester answered — and the record carries no evidence field to show the contract was checked.
A plan to exhaust old-label stock before the new label goes live is only as good as the stock control behind it. The field records intent; whether mixed old and new labels turned up on the line is a fact the record doesn't ask for.
What auditors find
Most common product change request findings
What an auditor tends to flag when reviewing a completed PCR.
| Finding | Clause | What fixes it |
|---|---|---|
| Allergen Profile Changes is 'Yes' but New Allergen Introduced is unanswered | ISO 9001 cl.8.5.6(a) | Make New Allergen Introduced mandatory whenever Allergen Profile Changes is Yes, not merely conditionally visible |
| Specification Update Required is 'Yes' with no linked specification reference anywhere on the form | ISO 9001 cl.7.5.3 | Add a specification ID field, conditional on Specification Update Required, mirroring HACCP Plan ID and Validation ID |
| Decision is Approved while Shelf Life Validation Required is Yes and Validation ID is blank | ISO 9001 cl.8.5.6(b) | Block Decision, or require Conditions text, until every 'Yes' in the food safety review carries its evidence reference |
| Target Implementation Date precedes the date artwork was actually approved | ISO 9001 cl.7.5.3 | Validate Effective From against Artwork Approved so the change can't be dated ahead of the label it depends on |
| Action Required is Yes but CAPA ID is never populated | ISO 9001 cl.10.2 | Require CAPA ID before the record can close whenever Action Required is Yes |
| Post Change Review Date is left blank on records marked Approved with conditions | ISO 9001 cl.9.1.3 | Make Post Change Review Date mandatory whenever the decision carries conditions |
Case in point
Case in point: a supplier swap that skipped the allergen check
A site swapped its dried-fruit supplier for cost reasons — same product, cheaper price, no recipe change on paper. Quality signed off the recipe as unchanged and the PCR closed in two days. Nobody re-ran the allergen check, because the recorded change type was 'Supplier', and the form doesn't force one just because the ingredient looks the same.
The new supplier's dried fruit was processed on shared lines with tree nuts; the old one wasn't. The nutrition panel and recipe didn't need to change — but the allergen statement did, and it went to print unchanged. The fix wasn't a new field; it was making Allergen Profile Changes ask about the ingredient's source, not just its declared content.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
6 sections
- Reference
- QUA-069
- Archetype
- Record
- Record ID
- PCR-2026-000
- Scoring
- Risk band
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 9001 cl.8.5.6
- Links
- Links MOC, Spec
- Tags
- Change, Quality
- Sections
- 6
- Fields
- 52
- Follow up fields
- 11
- Repeating sections
- 0
- Links out
- 6
Header
9 fieldsRequest ID*
Auto sequence. Format PCR-2026-0000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Requested By*
Requesting Function*
Target Implementation Date*
The change
6 fieldsProduct Affected*
Change Type*
Recipe, ingredient, supplier, pack format, label, shelf life or specification.
Current State*
Proposed State*
Reason For Change*
Cost, availability, customer request, improvement, regulatory or supplier driven.
Reason Detail*
Food safety and legal review
10 fieldsRecipe Changes Reach The Label
Almost every product change touches the ingredient list, the allergen declaration or the nutrition panel. Confirm all three before anything is approved.
Allergen Profile Changes*
- No3 pts
- Yes0 pts
New Allergen Introduced
- No3 pts
- Yes0 pts
Allergen Plan Update Required
Ingredient List Changes*
- No3 pts
- Yes1 pt
Nutrition Panel Changes*
- No3 pts
- Yes1 pt
Claims Affected*
- No3 pts
- Yes0 pts
HACCP Reassessment Required*
- No3 pts
- Yes1 pt
HACCP Plan ID
Links to QUA-046 HACCP ID
Shelf Life Validation Required*
- No3 pts
- Yes1 pt
Customer and supply
6 fieldsCustomer Approval Required*
Customer Notified
Customer Approval Received
New Supplier Required*
- No3 pts
- Yes1 pt
Supplier Approval ID
Links to QUA-038 Approval ID
Specification Update Required*
Downstream requirements
8 fieldsLabel Artwork Change Required*
- No3 pts
- Yes1 pt
Artwork Approved
Old Stock Run Down Plan
Mixed old and new labels on the line is a common labelling incident.
Validation Required*
Validation ID
Links to QUA-071 Validation ID
Training Required*
Change Involved
Anything that is not a like for like replacement needs change control.
MOC ID
Format MOC-2026-00000.
Links to FDN-020 MOC ID
Decision
13 fieldsDecision*
Conditions
Effective From
First Batch Reference
So the change can be traced to the exact batch it started on.
Post Change Review Date
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Quality Manager*
Signature*
Site Manager*
Second Signature*
QUA-069 · record IDs look like PCR-2026-000 · Links MOC, Spec
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures the decision. Keeping the allergen, label and validation trail in step with it is where it gets away from a spreadsheet.
Holds the product change library against your specification and allergen registers, and won't let a record reach Approved while a HACCP reassessment or shelf-life validation it triggered is still open.
Tracks which product changes touch a regulated claim or a customer contract term, and keeps label sign-off evidence in one place for the next audit.
Turns 'Training Required: Yes' into an actual assignment against the people on the affected line, rather than a box ticked and forgotten.
Coordinates the crew across quality, production and label sign-off, rolls open changes into one view, and holds every write for your approval before it touches a record.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Product Change Request definitions and key terms
- PCR
- Product Change Request — the mint code this record uses for its own ID, in the format PCR-2026-0000.
- CCP
- Critical Control Point — a step where control is essential to prevent or eliminate a food safety hazard. A recipe change can shift where a CCP sits, even though the CCP question itself lives on the process-change side.
- Allergen declaration
- The label statement identifying allergenic ingredients, usually a 'Contains' statement or bolded ingredient-list emphasis. It has to be re-derived, not assumed, every time the recipe or a supplier's ingredient specification changes.
- MOC
- Management of Change — the broader record (FDN-020) for changes that aren't a like-for-like replacement, across any function on site. A product change links to it when it also needs the wider MOC process.
- Waiver and concession
- A separate record (FDN-030) for a one-off departure from specification on a specific batch, as distinct from a permanent product change that updates the specification itself going forward.
FAQ
Frequently asked questions about product change request
Does every ingredient substitution need a PCR?+
Yes, if it changes what the label has to say — the ingredient list, allergen statement, nutrition panel or a claim. A genuinely like-for-like replacement from the same supplier is the one case the record isn't built for; the moment the source or specification differs, it's back in scope.
Who has to sign off a product change?+
Quality and production always; the customer only where the contract requires it. The record separates Customer Approval Required, Customer Notified and Customer Approval Received because those happen at different times and shouldn't be one tick-box.
What happens if the change also needs equipment or process changes?+
Then it needs a Process Change Request (QUA-070) alongside this one — a product change can be approved with no process implications at all, and vice versa, and conflating the two makes both harder to route.
Why does the form ask about old stock run-down separately from the label change itself?+
Because the two happen on different timelines. Approving a new label doesn't retire the old one from the warehouse, and mixed old and new labels on one line is a common labelling incident traced back to change control.
Can a product change be approved with conditions?+
Yes — Approved with conditions exists for exactly that, and the Conditions field is free text. The gap most records leave is that nothing on the form checks the condition was actually met before the change went live.
Does a declined product change need to be retained?+
Yes. A declined request is evidence the change was considered and rejected, which matters if it's proposed again later, or if an auditor wants to see the review process has teeth, not just a rubber stamp.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Change Control
Management of Change
Makes sure a change to equipment, materials, people or process is assessed before it happens rather than after
Waiver and Concession Record
Records a documented decision to proceed outside the normal requirement, with the risk accepted and by whom
Interim Control Record
Records the temporary control holding a risk while the permanent fix is built, with the date it must be replaced
Equipment Specification Record
Holds the specification a new machine must meet, covering performance, safety, hygiene, energy and maintenance access
Process Change Request
Requests a change to how a product is made, including equipment, settings or sequence
Validation Record
Records the evidence that a change works as intended before it becomes standard
More in Change Control
Process Change Request
Requests a change to how a product is made, including equipment, settings or sequence
Validation Record
Records the evidence that a change works as intended before it becomes standard
Temporary Change Authorization
Authorises a short term deviation from standard process, with an end date
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 cl.8.5.6 — Control of changes
- 21 CFR 101.9 and 101.22 — US food labelling and allergen declaration
- Regulation (EU) No 1169/2011 — Food information to consumers
- Food Information Regulations 2014 (UK) and the 2019 amendment known as Natasha's Law
- Codex Alimentarius CXC 1-1969 — General Principles of Food Hygiene
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.