A Naming Scheme for Supplier PDFs That Actually Works

Open your downloads folder right now. If it looks anything like most makers' folders, you've got a dozen files called "SDS.pdf," "SDS(1).pdf," and "SDS_final_v2.pdf," and not one of them tells you what's actually inside without opening it. That's fine when you have six ingredients. It stops being fine around ingredient thirty, and it becomes a real problem the day a regulator, an insurer, or your own future self needs to find the exact document behind a specific formula decision.

The fix isn't a fancy piece of software. It's a naming convention you apply by hand, every time, without exception.

Why generic filenames cost you time later

A supplier's default filename tells you almost nothing useful. It's built for their filing system, not yours. When you're assembling a Cosmetic Notification Form submission or answering a question from Health Canada about a specific ingredient's concentration, you need to move fast between the formula, the INCI list, and the source document that backs each entry. If finding the right SDS means opening four PDFs to check which one is current, you're burning time you don't have, usually at the worst moment.

There's also a compliance angle. Safety data sheets get updated. A supplier reformulates a blend, changes a CAS number, or revises a hazard classification, and suddenly the SDS you filed against is out of date. Without a naming system that surfaces the version and date at a glance, outdated documents quietly sit in rotation next to current ones, and nothing flags the difference until it matters.

A convention that scales

Here's a structure that works whether you have ten ingredients or two hundred:

SUPPLIER_INGREDIENT_DOCTYPE_YYYYMMDD.pdf

Broken down:

• Supplier: short, consistent code for the vendor (not the brand name of the product, the actual supplier). Pick one spelling and stick to it: MakingCosmetics becomes MKGCOS, not sometimes MC and sometimes MakingCos.
• Ingredient: the INCI name, or a recognizable shorthand for a blend (trade name plus a note that it's a blend, since trade names never appear on your actual filing).
• DocType: SDS, COA (certificate of analysis), TDS (technical data sheet), or IFRA for fragrance compliance documents.
• Date: the document's own issue date, in YYYYMMDD so files sort chronologically without any extra effort.

So a safety data sheet for a rosehip oil from a supplier you code as BIOAROMA, issued in March 2025, becomes:

BIOAROMA_RosaCaninaFruitOil_SDS_20250312.pdf

Anyone on your team, or you in eighteen months, can read that filename and know exactly what it is without opening it.

Handling supplier blends

Blends deserve their own naming note because they're where most filing errors start. A supplier blend expands into multiple INCI components once it's in your formula, and each component's real concentration is the blend's use level multiplied by its percentage inside the blend. If you name the file only after the trade name, you lose the thread back to which components you already mapped out.

Add a short suffix noting it's a blend and roughly what's inside:

CRODA_NatureGuardECT_SDS_blend-preservative_20241108.pdf

That single suffix saves you from re-opening the PDF every time you need to remember whether this was the preservative blend or the emulsifier blend.

A simple version-control habit

When a supplier sends an updated SDS, don't overwrite the old one. Keep both, with their real dates in the filename, and note in your formula record which version you notified against. If Health Canada or a customer ever asks why your filing shows one concentration and the current SDS shows another, you want the historical document sitting right there, not lost to an overwrite.

A quick table helps some makers standardize their document-type codes across a whole team:

Code	Document	Typical use
SDS	Safety Data Sheet	Hazard info, composition (section 3), handling
COA	Certificate of Analysis	Batch-specific purity or assay results
TDS	Technical Data Sheet	Usage rates, solubility, recommended dosing
IFRA	IFRA Certificate	Fragrance compliance and restriction limits
SPEC	Specification Sheet	Physical and chemical properties

Where this pays off

The real payoff shows up at notification time. When you're mapping a formula's INCI names and CAS numbers for a Cosmetic Notification Form, having every source document named consistently means you can move through fifteen ingredients in the time it used to take for five. It also means that if a reviewer asks you to substantiate a single ingredient's concentration, you pull one file instead of searching your whole drive.

This is part of why Cosmetic Comply's ingredient matching works off your actual supplier documentation rather than guesswork. Clean, consistently named source files make the INCI and CAS mapping faster and the concentration math easier to check. It's a small habit, but it's the kind that quietly saves you hours across a product line's lifetime.