Retaining a Perfume PIF for Ten Years: What Belongs in the File
Ten years is longer than most brand partnerships, longer than most product lifecycles, and longer than the average tenure of whoever signed the artwork. A product information file assembled at launch is usually complete and almost never mai
Ten years is longer than most brand partnerships, longer than most product lifecycles, and longer than the average tenure of whoever signed the artwork. A product information file assembled at launch is usually complete and almost never maintained, and the gap surfaces only when a distributor asks about a batch you shipped four years ago.
The retention rule is simple to state and hard to satisfy: the file must exist, describe the product as it was actually made, and be producible on demand long after everyone involved has moved on. This article sets out what belongs in a perfume product information file, when its clock starts, and how to structure one so that a colleague who has never seen the product can answer within a day.
Table of Contents
- When the clock starts, and what it is measuring
- What belongs in the file
- Version drift, the quiet failure
- Retention in practice: format and custody
- Practical guide: building a file that survives a decade
- Frequently asked questions
- Conclusion
When the clock starts, and what it is measuring
Retention periods for cosmetic product files are generally tied to the last batch placed on the market, not the launch date and not the date the formula was signed. A fragrance launched in one year and discontinued six years later starts its clock twice: once for the first batch and again for the final one. If your records key on launch, every product you retire becomes a compliance debt with an unknown due date.
The practical consequence is that a product information file needs two anchors — a product identity and a production event. Whether the obligation runs ten years or another period depends on the market, and the wording should be read in the current official text for each destination. What does not vary is the logic: the clock follows the goods, so goods must be traceable to a batch, and the batch to a version of the file.
What belongs in the file
The product information file is not one document but an envelope around several, and its value is that a reader can move from a claim on the label to the evidence behind it without leaving the folder.
1. Product description and intended use
What the product is, how it is used, the pack formats and the markets. This block looks trivial and most often fails on retrieval: a file describing "Eau de Parfum 50 ml" cannot be matched to a shipment labelled with an internal SKU.
2. The safety report
The finished-product cosmetic product safety report, with its conclusion, label warnings and assessor signature. Our perfume formats are each documented under a single report; here the point is that the version in the file governed a specific batch.
3. Manufacturing and quality evidence
A manufacturing description specific enough to be auditable, a statement of good manufacturing practice, the batch record, and the raw material documentation for that batch — certificates of analysis for the alcohol and the compound, plus the allergen declaration it was bought against.
Why the batch record carries more weight than the certificate
A certificate of analysis describes a drum. A batch record describes what happened in the room: which drum, weighed by whom, at what temperature, adjusted how. If a complaint later alleges that a batch smells different, the certificate will look identical to every other delivery, while the batch record shows whether the fragrance was weighed at the stated percentage or adjusted after a shortfall.
4. Claims substantiation
Whatever the pack promises — longevity, concentration, "free from" statements, dermatologically tested — needs a document behind it. Claims without substantiation are the fastest route from a marketplace query to a suspended listing.
5. Label and artwork versions
The final artwork, the approved text, and a record of when each version was in production. This block is most often missing entirely, and it answers the commonest question after a complaint: what did the customer read?
| Block | Typical evidence | Most common gap |
|---|---|---|
| Product description | Specification sheet, pack formats, market list | No link between internal SKU and customer-facing name |
| Safety report | Parts A and B, signed and dated | Formula version cited is not the version produced |
| Manufacturing | Method description, GMP statement, batch record | Generic GMP certificate with no method detail |
| Claims | Test reports, supplier statements, literature | Copy written before any test was run |
| Labels | Artwork files with dates and approval | No record of which version was on shelf when |
Version drift, the quiet failure
A file is complete on the day it is assembled. Failures happen afterwards, without anyone deciding to break a rule.
The fragrance is reformulated. Compounds are revised for regulatory, sourcing or cost reasons, sometimes under the same product code, with a customer notice that arrives as an email attachment nobody files. The safety report then references a composition that no longer exists.
A material is substituted. A dye is dropped over supply, or an alcohol grade changes to meet a freight constraint. The product is fine; the file now describes something else.
Artwork is amended at the printer. A warning is reflowed, a symbol resized, a claim tightened. Approved text and printed carton diverge by one sentence — exactly the sentence a complaint will quote.
The supplier changes. A new filler or bottle vendor arrives with documentation in a different format and different identifiers, and nobody reconciles it to the file structure.
Each is a small event that produces a large retrieval problem. The control is not vigilance but a rule: any change to formula, component, supplier or artwork creates a new version, dated, with the reason recorded. A one-page amendment log at the front of the file does more for a decade of integrity than any amount of filing discipline.
Retention in practice: format and custody
Where the file lives determines whether it can be produced. Three arrangements are common; one survives.
Factory-held or email-bound. The documents sit in the manufacturer's quality system, or the file exists as a mail thread. Both are convenient while the relationship and the thread last, and both fail when they end: a factory-held file leaves with the factory, and a thread is retrievable only by whoever remembers it.
Controlled folder with an index. One folder per SKU, one subfolder per version, a single index listing each document with its date and scope, searchable PDFs for signed documents, native files for artwork, and an offline copy. This is the only arrangement that answers a request from someone who has never seen the product. A folder only its author can navigate is a memory, not a record.
| Event | What the clock attaches to | What must still exist |
|---|---|---|
| First commercial batch | The batch placed on the market | File version 1, batch record, artwork version |
| Formula or supplier change | Batches made after the change | New version, amendment note, superseded copy retained |
| Product discontinued | The final batch produced | Complete file set, plus destruction or sell-through evidence |
| Responsible operator changes | Unchanged, but custody moves | Written handover of the full set, with an index |
Practical guide: building a file that survives a decade
Step 1 — Fix the identifier before the first batch
Give every SKU an internal code that never changes, and map it to the customer-facing name, pack size and market. Everything else is filed against that code.
Step 2 — Assemble the five blocks at approval, not at shipment
Collect the safety report, method description and artwork approval while they are being discussed. Chasing them a year later costs weeks.
Step 3 — Attach a batch record to every production
Not a summary: the record with weights, yields and adjustments, plus the certificates for the materials actually consumed. Our supplier ingredient checks describe what those certificates should contain.
Step 4 — Open a version for every change
Formula, component, supplier, artwork, market. Date it, note the reason in one line, and keep the superseded version rather than overwriting it.
Step 5 — Write the index, and make it the only way in
One page per SKU listing every document, its date and the batch range it covers. If a document is not in the index, it is not in the file, whatever the folder contains.
Step 6 — Rehearse retrieval once a year
Pick a batch at random and ask someone uninvolved to produce its complete file within one working day. The exercise finds naming failures and orphaned versions before an authority does.
Frequently asked questions
What is private label perfume manufacturing?
Production of fragrance under a buyer's brand, with formula, bottle and carton agreed with the manufacturer. The factory compounds and fills; the brand owns the identity, the claims and the compliance record.
Who owns the formula in a private label arrangement?
It depends on the contract. Exclusive development usually transfers rights to the brand; stock fragrance selection typically does not. Settle it before sampling.
How long does a first production run take?
Usually eight to twelve weeks from approved sample, dominated by component lead times rather than filling. Printed cartons carry the longest minimum.
Does the ten-year period apply to every market?
No. Retention periods and the responsible party differ by jurisdiction, and the period should be confirmed in the current official text for each market rather than borrowed from a supplier.
Do I need to keep documents for a discontinued product?
Yes, for the period running from the last batch placed on the market. Discontinuation changes when the clock starts, not whether it runs.
Can the factory hold the file on my behalf?
It can hold a copy but cannot carry the obligation, which attaches to the party placing the product on the market. A factory-held file leaves with the factory.
What if the fragrance house reformulates without telling us?
Assume it will and make notification a contractual term. Without it the file drifts silently, and the first sign may be a complaint rather than a document.
How should the file be stored?
Searchable PDFs for signed documents, native files for artwork, one index per SKU, and an offline copy that does not depend on one cloud account or one employee's access.
Conclusion
A product information file is a durability problem disguised as a paperwork problem. The content is knowable at launch; what fails is the ability to prove, years later and under pressure, which version of the product a batch was, what it was made from, and what the customer was told.
Build the product information file around identifiers and versions rather than around documents, attach a batch record to every run, and rehearse retrieval before anyone asks. That structure also pays commercially: when a retailer asks a technical question, the answer is a link rather than an investigation. Our customization process hands over the documentation set at each stage, so the file is built as the product is built.
Discuss your fragrance programme with our team:
WhatsApp: +86 17324762943
Email: adon@customperfumeoem.com
Website: customperfumeoem.com
