Chemical supplier approval document checklist: what to submit

Who uses a chemical supplier approval document checklist, and when?

A chemical supplier approval document checklist is used by the supplier's quality, regulatory or technical service person who assembles the documents a customer asked for before a new product, grade or source is approved. It is filled once per customer request and per product, in the days between receiving the request and sending the package.

The customer side of the same process is well covered. A buyer-side approval checklist for chemical procurement teams scores eight areas, from certifications to technical support, and asks for a current safety data sheet (SDS), lot-specific certificates of analysis (CoA) and certificates that name the producing site (Elchemy, 2025). That list tells the buyer what to demand. It does not tell the supplier how to check that each document it sends is the right revision, still valid and consistent with the others.

The supplier's checklist exists for that second job. Its four sections follow the order in which the work is done: fix what the customer requires, check the state and identifiers of each document in hand, list what is missing or inconsistent, then plan the fixes and the submission date. A request from an automotive, electronics or food packaging customer adds documents, but the four sections stay the same. The editable Word checklist and an Excel register with a CSV copy are at the end of this page.

Which documents does a customer supplier approval request usually ask a chemical supplier for?

A customer supplier approval request usually asks a chemical supplier for an SDS, a technical data sheet (TDS), a CoA for a named lot, a quality management certificate, substance statements such as REACH SVHC and RoHS, and the customer's own questionnaire. Which of these are required, and in what form, is set by the customer's request, so the checklist records the requirement each document meets.

The table below decides which basis to write next to each document in the first section of the checklist.

The SDS row is the one most often misread: neither the US nor the EU rule gives an SDS a fixed expiry, so its state turns on whether it is the latest revision.

Some rows are conditional. A RoHS statement matters only when the product goes into electrical or electronic equipment, the scope of Directive 2011/65/EU. REACH Article 33 applies to articles, so a request for an SVHC statement on a chemical mixture most likely comes from a customer that makes articles and needs the content for its own duty. Mark such rows conditional, with the condition, rather than leaving them out.

What goes in each section of the supplier approval document checklist?

Each section of the supplier approval document checklist holds one kind of entry: section 1 the required documents and their basis, section 2 the state of each document and the identifier comparison, section 3 every missing or unapproved document and every mismatch, and section 4 the fixes with owner and date. The same columns appear in the Excel register, one row per document.

Fill section 1 from the customer's request before opening any file in hand. A list written after looking at the folder tends to match the folder, and a document the customer asked for but the supplier never had drops out unnoticed. Once section 1 is fixed, every later section is checked against it, and a requirement found later is added to section 1 as a gap, with the date it was found.

The table below previews every part of the checklist, with the format each entry takes and an example value.

Validity remaining is the key column: a certificate that is valid today but expires before the customer finishes its review will come back as expired.

How do you record the issuer, issue date and validity of each supplier approval document?

You record the issuer, issue date and validity of each supplier approval document by copying them from the document itself, not from a file name or a cover email, and by computing the days of validity left on the planned submission date. A file called "SDS_current" may hold an old revision.

Write the issuer as the legal entity and site printed on the document. Distributors often hold documents issued by the maker, and a certificate that names a parent company rather than the producing site is a warning sign on the buyer side (Elchemy, 2025).

Write every date as YYYY-MM-DD. Where the document has no expiry, write "none" and record the revision date instead. An SDS falls in this group: the US rule requires significant new hazard information to be added within three months (29 CFR 1910.1200(g)(5), accessed 2026), and the EU rule requires an update without delay and a dated revision marked "Revision: (date)" (REACH Article 31(9), 2026 consolidation). Enter any maximum age the customer's request sets.

Choose one of four states. Present means the right document is in hand and valid. Missing means it is not in hand. Expired means its expiry date has passed or falls before the planned submission. Unapproved means it is unsigned, a draft, or not released by the issuer. For a quality certificate, check validity in a register such as IAF CertSearch, which returns certificate validity details for certificates from accredited certification bodies (IAF CertSearch, 2026).

How do you find mismatched product names, grades and lots across supplier approval documents?

You find mismatched product names, grades and lots across supplier approval documents by choosing one reference document, usually the customer's request or the TDS, and comparing five identifiers on every other document against it: product name, grade, part number, lot and revision. A mismatch is any identifier whose printed value differs from the reference, even when everyone knows it is the same product.

Work identifier by identifier rather than document by document. Write the reference value first, then read the same field on every other document. Product names drift when a product is renamed and older documents keep the former name. Grades drift when a suffix marks a pack size or plant. Lots drift when a CoA from a stock sample is sent in place of the lot that will ship. A buyer-side checklist treats a CoA without a lot number or test method as a warning sign (Elchemy, 2025).

Check two more fields that are not identifiers but cause the same rejection. The EU rule requires the SDS to be dated and supplied in an official language of the Member State where the product is placed on the market, unless that state provides otherwise (REACH Article 31(5) and 31(6), 2026 consolidation). A substance statement checked against an older Candidate List no longer covers the list in force, since ECHA adds entries; on 4 February 2026 it added two (SGS, 2026). Check the current entry count on ECHA's Candidate List page before signing the statement.

Record each mismatch with the documents involved, both values, the corrected value and whether it blocks submission.

How do you plan the fixes before submitting a supplier approval package?

You plan the fixes before submitting a supplier approval package by turning every missing, expired or unapproved document and every blocking mismatch into one dated action with a single owner and a condition that closes it. The earliest submission date is then the latest due date among the blocking fixes, not the date the customer asked for.

Write each fix as what, who and by when. "Reissue SDS with product name Grade 40, regulatory affairs, 2026-11-06, closed when the revised SDS is in the package" can be checked; "update documents" cannot. The owner is the person who can change the document, which for a distributor is often the maker, so the due date has to allow for that request.

Separate blocking fixes from improvements. A missing CoA for the lot that will ship blocks submission. A TDS with an older layout but correct values may not. Keep the two lists apart so that the improvements do not delay the package.

Then set the final state. The package is ready to submit only when no required document is missing, expired, unapproved or in conflict with another; otherwise it needs remediation, and the checklist shows the earliest date it can go. Where a customer accepts a partial package, record which documents go first and which follow, with their dates.

Before sending, read the package once more against the frozen list in section 1, not against memory of what was fixed.

What does an illustrative filled supplier approval checklist look like?

An illustrative filled supplier approval checklist for one customer request shows most documents present, one expired, one unapproved and one identifier mismatch, with three fixes and an earliest submission date. All values below are illustrative and describe no real product, supplier or customer.

The table below is the illustrative state of the package for a corrosion inhibitor, Grade 40, lot 2610-014, with a planned submission date of 2026-11-10.

The key row is the SDS: the document is valid, but its product name differs from the TDS and the request, so it blocks the package as surely as a missing document would.

Read across the example and the final state follows. Three fixes block submission, the latest due on 2026-11-06, so the package needs remediation and the earliest submission date is 2026-11-06, four days ahead of the planned 2026-11-10 (illustrative). If any of the three slipped past 2026-11-10, the checklist would show it before the customer did. The ISO 9001 row shows why validity is counted at submission: 202 days left covers a review lasting a few months, while 20 days would not (illustrative).

When does a standard supplier approval document checklist not fit?

A standard supplier approval document checklist does not fit when the approval rests on more than documents: an on-site audit, a sample qualification, or a sector process with its own forms and portals. In those cases the checklist still covers the documents, but the decision depends on evidence it does not hold.

Automotive, aerospace, medical device and pharmaceutical customers often run their own approval routes, and their forms decide the documents, formats and signatures. Food contact and drinking water uses add declarations tied to the jurisdiction of use. A customer that scores suppliers across quality, supply, finance and sustainability, as a buyer-side checklist does (Elchemy, 2025), will judge areas this checklist leaves out.

The checklist also does not judge content. It confirms that the CoA is for the right lot and that the SDS is the latest revision; it does not say whether the test values meet the customer's specification or whether the hazard classification is correct. Those are technical reviews in their own right.

A single-document request, such as a customer asking for one updated SDS, needs no checklist; a line in the request log is enough. Multi-site suppliers should fill one checklist per producing site, since certificates and CoAs differ by site.

Lubinpla keeps the documents produced for each customer by document type and shows them in a data room view, so the same checklist can be kept with that customer's other records. Edit the Word or Excel version to add the documents a sector route requires.