How should a distributor organize TDS, SDS and CoA files?
Summary
Organizing supplier TDS, SDS and CoA files takes 4 steps: pool the files; tag each by product type, brand and document type; merge brand spellings; check gaps. The method holds when every file carries all three tags in any folder, and when each certificate of analysis is filed under its own lot number instead of replacing the last one.
US OSHA requires distributors to pass safety data sheets and updated information to other distributors and employers with the initial shipment and with the first shipment after an SDS is updated (OSHA 29 CFR 1910.1200(g)(7)(i), 2024).
EU REACH requires each distributor to keep the information it needs for its REACH duties for at least 10 years after it last supplied the substance or mixture (REACH Article 36, consolidated 2026).
Under EU REACH, a revised SDS is identified as "Revision: (date)" and goes to all recipients supplied within the preceding 12 months (REACH Article 31 paragraph 9, consolidated 2026).
ICH Q7 recommends a certificate of analysis, issued on request, for each batch of an active pharmaceutical ingredient, showing the batch number, the date of release and each test with its acceptance limits (ICH Q7, 2000).
This method covers the document library of a chemical distributor that resells products from several manufacturers. How to write your own SDS as a formulator or importer, and how to read the content of a TDS or CoA, are separate questions.
What do you need before organizing supplier TDS, SDS and CoA files?
Before organizing supplier TDS, SDS and CoA files, a distributor needs three things: a list of the products it sells, a fixed list of product types, and one place where every document will live. Without the fixed type list, every person invents a new label.
The product list comes from the sales or purchasing system: every item sold, its brand and its supplier. Mark which items are hazardous chemicals, because those need a safety data sheet (SDS) under US OSHA and EU REACH, while a technical data sheet (TDS) is the maker's own product description.
The product type list should be short enough to choose from without searching, such as 20 to 40 terms for a lubricants and adhesives range (illustrative). Write each type the way customers ask for it, such as "hydraulic oil".
The single place can be a shared drive, a document system or a data room, as long as it allows tags on each file, so one SDS is found by product type, brand and document type without three copies. ISO 15489-1:2016 lists metadata for records among the concepts and principles of records management, and these tags are that metadata (ISO 15489-1:2016).
Why can't you find supplier TDS, SDS and CoA files when each maker names them differently?
Supplier TDS, SDS and CoA files go missing because each maker names files and folders its own way, and a library sorted by supplier folder inherits all of those systems at once. One maker sends "SDS_EN_US_4471.pdf", another sends "Product Safety Sheet - Grade 46 (rev 3).pdf", and a third sends a ZIP file from its portal with numbered names (illustrative).
The same brand also arrives under several spellings. A brand written with a hyphen on the TDS, without it on the SDS and in capitals on the CoA is three brands to a folder search (illustrative). Staff search by the name they remember and conclude the document does not exist.
A folder tree by supplier also breaks when one brand is bought from two suppliers: the same SDS sits in two folders, and nobody knows which revision is current. US OSHA requires a distributor to pass on the updated SDS with the first shipment after an update (OSHA 29 CFR 1910.1200(g)(7)(i), 2024), so a superseded copy that wins the search is a compliance problem. The fix is to describe each file with the same three tags, whatever its name or folder.
How do you organize supplier documents step by step?
You organize supplier TDS, SDS and CoA documents in four steps, done in order, each finished for all files before the next begins.
Pool them. Copy every TDS, SDS and CoA from email, drives and supplier portals into one library, keeping each original file and the date received.
Tag each file with product type, brand and document type. Choose the product type from your fixed list, write the brand as the preferred spelling, and set the document type to TDS, SDS or CoA. Rename the file to one pattern, such as Brand_Product_SDS_2026-03-14 for an SDS revision date or Brand_Product_CoA_Lot24117 for a certificate (illustrative).
Merge brand spellings. Pick one preferred name per brand and record every variant you found under it, so a search for any variant reaches the same tag.
Check gaps. Run the check table below against the product list: every hazardous product sold needs a current SDS, every product a TDS, and every lot shipped a CoA.
Do step 2 in batches by supplier, because one supplier's files usually share a naming habit. Repeat step 4 whenever a revised SDS or a new lot arrives.
Which three tags should every supplier TDS, SDS and CoA carry?
Every supplier TDS, SDS and CoA should carry three tags: product type, brand and document type. Each tag answers one question staff ask: which product class, which brand, which document.
Product type comes from your fixed list, not the supplier's wording. Brand is the preferred spelling from your alias list. Document type has three values only, TDS, SDS and CoA, so a file the supplier called "MSDS" or "datasheet" is not missed.
Revision date and lot number identify which copy you have, not what it is, so put them in the file name. An SDS shows its date of preparation or last revision in section 16 (OSHA, 2012), and under EU REACH a revised SDS shows "Revision: (date)" on its first page with an indication of which version it replaces (REACH Annex II, section 0.2.5, consolidated 2026).
Language and country also belong in the file name. EU REACH requires the SDS in an official language of the Member State where the product is placed on the market (REACH Article 31 paragraph 5, consolidated 2026), so one product can have several valid SDS files.
How do you merge brand name variants in supplier TDS, SDS and CoA files?
You merge brand name variants by choosing one preferred spelling for each brand and listing every other spelling as an alias that points to it. Library science calls this a controlled vocabulary: ANSI/NISO Z39.19 covers synonym rings, taxonomies and thesauri (NISO, 2010), and ISO 25964-1:2011 gives recommendations for thesauri used for information retrieval (ISO 25964-1:2011).
A practical alias list for a supplier document library has one row per variant:
Preferred brand: the spelling on the maker's own website or trademark, used as the tag.
Variant: the spelling as it appeared on a file, such as with or without a hyphen, a space, capitals or the maker's company name in front (illustrative).
Where seen: the document and supplier where the variant appeared.
Collect variants during step 2, not from memory: add a row each time a file shows a new spelling. A sub-brand that is a different product line keeps its own tag; a spelling difference does not.
Keep brand and maker separate: a maker can own several brands, and one brand can come through several suppliers. Record the maker or supplier as a file property, not a second brand tag.
How do you file a CoA that changes with every lot?
You file a CoA that changes with every lot by keeping every certificate as its own file, named with the lot or batch number, under the same three tags as the product. A certificate of analysis belongs to one lot; a TDS and an SDS belong to a product and a revision. Filing a new CoA over the old one loses the record for lots already delivered.
ICH Q7, written for active pharmaceutical ingredients, recommends that a certificate of analysis be issued for each batch on request, give the batch number and the date of release, and list each test with its acceptance limits and numerical results (ICH Q7, 2000, section 11.4). For industrial chemicals outside that guideline, treat the CoA the same way: one file per lot.
When an agent or broker issues a new certificate, ICH Q7 recommends that it refer to the original manufacturer and the original batch certificate, "a copy of which should be attached" (ICH Q7, 2000, section 11.44). Keep the maker's original CoA next to your reissued one, with the same lot number in both file names.
Customers ask for a CoA by the lot number on the label, so put the lot right after brand and product in the file name.
How do you check that a supplier TDS, SDS and CoA library is complete?
You check a supplier TDS, SDS and CoA library by comparing it against the product list and against the shipments: every product sold must be findable by its three tags, every hazardous product must have a current SDS, and every lot shipped must have its CoA. Run it after every supplier update and before a customer audit.
The table below decides whether each supplier document can be found and whether any SDS or CoA is missing or superseded.
Check | Pass | Fail and what to do |
|---|---|---|
Three tags | Every file has product type, brand and document type | Untagged file: tag it from the list, never leave it in an "other" folder |
Brand spelling | One tag per brand, variants listed as aliases | Two tags for one brand: merge them and add the variant to the alias list |
SDS present | Every hazardous product sold has an SDS (OSHA 29 CFR 1910.1200(g)(7)(i), 2024) | No SDS: request it from the maker or supplier before the next shipment |
SDS current | Revision date in the file name matches the maker's latest | Older revision: replace, keep the old one marked superseded |
CoA per lot | Each lot shipped has its own CoA file with the lot number | Missing lot: request the CoA from the supplier for that lot |
TDS present | Every product sold has a TDS | No TDS: request it, and mark the product so sales knows |
The SDS current row matters most: a file with an old revision date has to be replaced and marked superseded, because the updated SDS must reach the customer with the first shipment after the update. Lubinpla files documents under the same three tags, suggests tags from the file path and name without reading the content, and groups brand spelling aliases; it has no revision date or lot field, so those still belong in the file name.
Common mistakes when organizing supplier TDS, SDS and CoA files
The most common mistakes when organizing supplier TDS, SDS and CoA files are sorting by supplier folder only, overwriting old revisions, free tags and trusting file names.
Folder by supplier only. The same brand bought from two suppliers ends up in two places with two revisions. Tag by brand and keep the supplier as a property.
Overwriting the old SDS. Deleting a superseded SDS removes the record of what you passed on with earlier shipments. EU REACH requires distributors to keep the information they need for REACH duties for at least 10 years after last supply (REACH Article 36, consolidated 2026). Mark old revisions superseded instead.
Free tags. When anyone can type a product type, "hydraulic oil", "hyd. oil" and "HM oil" soon coexist (illustrative). Keep the list fixed.
Trusting the file name. A file called "SDS" may be a TDS. Open each file once during step 2 and tag it from what the document says.
Frequently asked questions
How long should a distributor keep old SDS revisions?
Under EU REACH, a distributor keeps the information needed for its REACH duties for at least 10 years after it last supplied the substance or mixture (REACH Article 36, consolidated 2026). In the US, where an SDS serves as an employee exposure record, an employer may drop it if a record of the chemical's identity, where and when it was used is kept for at least 30 years (OSHA 29 CFR 1910.1020(d)(1)(ii)(B), 2011).
Should we rename the supplier's files?
Rename a copy, not the original. Keep the supplier's file as received with the date received, and give the working copy your naming pattern with brand, product, document type and revision date or lot. The original proves what the supplier sent if a question comes up later.
Where does the supplier name go if it is not a tag?
Record the supplier as a property of each file or in the product list, not as a fourth tag. Staff look for documents by product, brand and document type; the supplier matters when you request a missing SDS or CoA, so it belongs in the record you use for that request.
Do employees need the SDS library at their work area?
US OSHA requires employers to keep SDSs readily accessible to employees in their work areas during each work shift, and permits electronic access when it creates no barrier to immediate access (OSHA 29 CFR 1910.1200(g)(8), 2024). A tagged library meets the search part only if staff on site can open it.