10 Common PIF Mistakes That Make Products Look Non-Compliant

10 Common PIF Mistakes That Make Products Look Non-Compliant

Quick Answer

A product can be perfectly safe and still look non-compliant, because an inspector judges what the file lets them verify. The usual culprits are not dramatic failures but inconsistencies: the label says one thing, the formula another, the safety report a third. Most can be prevented with a short cross-check before launch. This article walks through ten mistakes that make good products look bad, and what to do about each.

Why Appearance Matters as Much as Substance

Under Article 22, enforcement authorities check compliance through the product information file as well as through samples and laboratory tests. They cannot see what you meant; they can only see what you documented. When documents contradict each other, an inspector has to ask which one is true, and that question alone can start a longer investigation. If you want to know what happens next, our guide to PIF inspection readiness walks through a request step by step.

The Ten Mistakes

1. The formula in the file is not the formula on sale

How it looks: the file describes an earlier version; the batch records describe a newer one.
Fix: give every formula a version number and date, and cite it in the description, the safety report and the batch records. See our guide to keeping a PIF up to date.

2. The safety report is unsigned, undated or not for this pack

How it looks: a report that does not clearly belong to the product on sale. Article 10 requires an assessment by a person with formal qualifications in pharmacy, toxicology, medicine or a similar discipline, so the assessor's name and credentials should be visible.
Fix: confirm the report is signed, dated, covers both Part A and Part B of Annex I, and names the product exactly as sold.

3. Claims on the website that the file never saw

How it looks: the label is modest, the product page promises more.
Fix: list every claim used anywhere, and match each to evidence. Our guide to claims substantiation explains the standard to meet.

4. The notified address is not where the file is

How it looks: Article 13 requires notification of the address where the file is kept, and updates without delay when notified information changes. An out-of-date address suggests the file is not under control.
Fix: review notified details whenever you move premises, change provider or change Responsible Person.

5. Documents in the wrong language

How it looks: supplier statements and test reports in a language the authority cannot readily read. In Great Britain the file must be in English.
Fix: obtain or commission English versions early, and keep the originals alongside. Our comparison of UK and EU PIF requirements covers the language rules.

6. A GMP "statement" with no evidence behind it

How it looks: one sentence saying the product is made to GMP, nothing more.
Fix: ask the manufacturer for a certificate, audit summary or signed statement tied to the site, and include a process description. Our guide to GMP and ISO 22716 shows what supports it.

7. Stability and microbiology data from another formula or pack

How it looks: test reports that refer to a different code, pack or version. Annex I expects stability under reasonably foreseeable storage conditions and challenge test results to be part of the safety report.
Fix: make sure each study names the tested formula and pack. Read our article on stability and challenge testing for what each study should show.

8. Blank or vague animal testing information

How it looks: a section left empty, or a single "no animal testing" line with no source.
Fix: record supplier statements and your own declaration, as the file's fifth section requires. See our guide to the animal testing ban.

9. Undesirable effects handled in an inbox, not in the file

How it looks: customer complaints exist, but nothing in the file shows they were reviewed. The safety report must be kept up to date with additional information generated after launch, and serious undesirable effects must be reported.
Fix: keep a complaints log, review it regularly with your assessor, and know your reporting steps. Our article on SUE reporting sets them out.

10. No index, no owner, no version history

How it looks: a pile of documents that nobody can navigate quickly. Article 11 requires the file to be readily accessible and kept for ten years.
Fix: add a one-page index, name an owner and keep dated versions. Our guide to PIF retention shows how.

The 15-Minute Cross-Check

Before you launch or after any change, compare the same six items across every document. If any one differs, find out why before anyone else does.

Check this item Against these documents
Product name and code Label, file description, CPSR, notification
Formula version File, CPSR, batch records, test reports
Ingredient list Label, formula, SDS list
Claims Label, website, adverts, evidence file
Responsible Person and address Label, notification, file location
Pack and PAO / durability Artwork, stability data, CPSR

Practical Checklist

  • Give each formula a version number and use it in every document.
  • Check the safety report is signed, dated, complete and for the final pack.
  • Compare label, website and advert claims to your evidence list.
  • Make sure notified details and file location match.
  • Keep English versions of every document for Great Britain.
  • Hold evidence, not just statements, for GMP and animal testing.
  • Keep a complaints log and an index, and review both regularly.

Frequently Asked Questions

Can a safe product still fail an inspection?

It can fail to demonstrate compliance. Authorities check the file as well as the product, so inconsistent or missing documents can lead to requests for corrective action even where nothing is unsafe.

What is the most common PIF inconsistency?

A mismatch between the formula or claims on sale and what the file documents, usually after an unrecorded change. A short cross-check after each change prevents most of these.

Who should review my PIF before an inspection?

The Responsible Person is accountable, ideally supported by the safety assessor. A fresh pair of eyes, such as a compliance consultant, often spots gaps that the team who built the file no longer sees.

Should I fix a gap quietly if I find one?

Fix it properly and record it. Add new, dated documents rather than altering old ones, and if the gap suggests the product may not comply, take corrective measures as the Regulation requires.

Final Word

None of these ten mistakes needs a bigger budget; they need a habit. A product that is safe, honestly labelled and consistently documented is easy to defend. A product with the same safety record but contradictory paperwork is a gift to anyone looking for a problem.

Want a second pair of eyes on your PIF? NestQual reviews and builds complete Product Information Files so what you sell and what you document always match.

Get a CPSR for your product See the Complete Compliance Pack

Sources

  1. Regulation (EC) No 1223/2009, Article 10 — Safety assessment (as it applies in the UK) — legislation.gov.uk
  2. Regulation (EC) No 1223/2009, Article 11 — Product information file — legislation.gov.uk
  3. Regulation (EC) No 1223/2009, Article 13 — Notification — legislation.gov.uk
  4. Regulation (EC) No 1223/2009, Article 22 — In-market control — legislation.gov.uk
  5. Regulation (EC) No 1223/2009, Annex I — Cosmetic product safety report — legislation.gov.uk
  6. Related guides on this site: PIF inspection readiness, Keeping a PIF up to date, PIF retention

This article is for general information and does not constitute legal advice. Always confirm current requirements for your specific product and market with a qualified safety assessor or Responsible Person.

Back to blog