How to Build a Product File for Every SKU You Sell
A product file is the difference between answering a question in an hour and spending a week reconstructing records. Every SKU needs one, built as you launch rather than assembled during a problem. Here is the structure and what goes in each section.
Why This Matters More Than It Sounds
This guide is for supplement, Ayurvedic and herbal brand owners in India.
Record keeping sounds like an administrative preference until the moment someone asks a specific question: a consumer complaint about a batch, a marketplace query, a regulatory enquiry, a distributor dispute, a prospective retail partner’s due diligence.
At that point, a brand with an organised product file answers in an hour. A brand without one spends days emailing the manufacturer, searching inboxes and reconstructing what was agreed. The second position is weaker in every one of those conversations.
The work is front-loaded: build the file during launch when the documents are arriving anyway, and maintain it per batch.
The Four Sections
Use the same structure for every SKU.
| Section | Contents |
|---|---|
| Regulatory | Your registration or licence, manufacturer’s licence with scope visible, GMP certificate where applicable, all with validity dates |
| Product | Approved specification, full formulation including excipients, extract markers and standardisation, approved physical sample reference, approved artwork with compliance review record |
| Evidence | Stability data in the actual pack, certificates of analysis by batch, independent test reports, transit test results |
| Commercial | Signed manufacturing agreement, change control correspondence, pricing and MOQ terms, complaint log entries referencing batch numbers |
Keeping the same four sections across every SKU means anyone can find anything, which matters when the person who set it up is not available.
What People Most Often Omit
Five items that are routinely missing.
- The approved physical sample, and a note of which batch it came from. Without it, no comparison is possible later.
- The artwork compliance review record, as opposed to the artwork itself. The record is what demonstrates the review happened.
- Change control correspondence, which is often scattered across email rather than filed.
- Transit test results, which are usually treated as a one-off exercise rather than evidence.
- The manufacturer’s licence scope page, as distinct from the first page of the licence.
Maintaining It
The file is only useful if it stays current.
Per Batch
Add the certificate of analysis, checked against the specification, and log key values. This is the only recurring task.
On Any Change
File the change control correspondence and update the specification. Never let a change exist only in email.
At Renewal
Replace licence and certificate copies when they renew, and note the new validity dates.
Annually
Review the whole file, refresh the physical reference sample, and confirm nothing has drifted out of date.
Keep it somewhere more than one person can access. A product file on one laptop is a single point of failure.
Build Checklist
Work through for each SKU.
- Create the four sections with consistent names.
- File your registration or licence and the manufacturer’s, with scope pages.
- File GMP certification where applicable, with validity dates.
- File the approved specification and full formulation.
- Record the approved physical sample and the batch it came from.
- File approved artwork and the compliance review record.
- File stability data for the actual pack.
- Start a certificate of analysis folder organised by batch.
- Start a batch log of key values.
- File the signed agreement and all change control correspondence.
- Link complaint log entries to batch numbers.
- Store it where more than one person can access it.
- Test it by attempting to reconstruct one batch’s history.
Need Documentation Worth Filing?
Share your product and our team will provide licences, specification, stability and per-batch certificates in a consistent format.
Frequently Asked Questions
What belongs in a product file?
Four sections: regulatory documents with validity dates, product documents including specification, formulation, physical sample reference and approved artwork, evidence including stability data and certificates of analysis by batch, and commercial documents including the agreement and change control correspondence.
Why does it need to be per SKU?
Because specifications, stability data, artwork and batch records are product-specific. A combined file makes it impossible to answer a question about one product quickly, which is the entire purpose of having the records organised.
What is most often missing?
The approved physical sample with a note of its batch, the artwork compliance review record as distinct from the artwork, change control correspondence scattered across email, transit test results, and the licence scope page rather than just the first page.
How much maintenance does it need?
One recurring task: filing each batch’s certificate of analysis, checked against the specification, and logging key values. Beyond that, file any change correspondence immediately, refresh licences at renewal, and review the whole file annually.
How do I know the file is adequate?
Try to produce the complete history of a named batch within an hour: specification, certificate of analysis, stability data, artwork approval and any complaints referencing it. The questions you cannot answer show what is missing.