What belongs in a cosmetic PIF?

A PIF is a connected product record

A product information file connects the product to the evidence supporting its safety and other regulatory questions. It is not another name for a single safety report. HPRA's PIF guidance describes the file's main components and its retention requirement.

For day-to-day work, start with a product-specific index. The index should identify the current record, where supporting material lives and which questions remain unresolved. It helps a specialist review the file without treating document presence as a conclusion about the contents.

Organise the main evidence areas

Keep the product description, CPSR, manufacturing information and GMP context, claims support and relevant animal-testing information distinguishable. The specialist should check the exact requirements and applicability for the product and market. Do not invent a document to fill a category that has not been properly scoped.

For each area, record the product or variant covered, the document version, its location, the owner and the review state. If the file supports only part of the question, say so. If a record is missing or its status is uncertain, preserve that uncertainty in the index.

Keep the safety report inside the wider picture

The CPSR is one component of the PIF. A safety report does not, by itself, establish that the manufacturing record, claims evidence or other product-file material is complete. Conversely, a neatly indexed folder does not replace the specialist safety assessment.

Give a report an exact product and revision link. Check that the material being reviewed relates to the same specification, use and packaging as the product you intend to supply. A shared product name is not enough to establish that relationship.

A synthetic index with useful gaps

For Sample Product A, the index contains a current product description, an artwork draft and several supplier documents. The CPSR field says not recorded, the manufacturing evidence has an open question and the proposed claim has no linked substantiation.

This is a useful starting index because it exposes what needs attention. It is not a complete PIF. Assign specific actions, such as confirming the assessor handover requirements or locating the evidence supporting a particular claim. Keep each task with the relevant record rather than marking the entire file complete.

Maintain the file as the product changes

Record new information and material changes with dates and version links. Ask the specialist which parts of the file need to be updated and which earlier decisions no longer describe the current product. Keep the retention basis and the event from which it runs explicit; do not substitute the upload date for the legal trigger.

For the EEA context, HPRA describes a ten-year retention period running from placing the final batch on the market. Keep the actual trigger and supporting history identifiable, and have the specialist verify the current provision and any case-specific implications. Do not silently substitute a differently worded GB trigger or a spreadsheet creation date.

CosmeBeacon can organise evidence and a review of the current product revision. Its file count is an organisational measure, not a PIF completeness or compliance score. Keep the source, jurisdiction and review date beside any retention or completeness decision.

Sources and legal dates