How Do You Stop Sending an Outdated SDS or the Wrong Lot's CoA?

This method covers the outbound package a supplier or distributor sends with a chemical shipment: safety data sheet (SDS), Certificate of Analysis (CoA) and technical data sheet (TDS). It does not replace a customer's incoming inspection, transport documents or a regulated batch release.

Why do outdated SDS and wrong-lot CoA errors slip through more often than missing files?

Outdated SDS and wrong-lot CoA errors slip through more often than missing files because a missing file stops the package, while an old revision or another lot's certificate looks complete. Neither OSHA nor REACH publishes error rates for outbound packages, so this is an inference from how the checks work, not a measured share.

A missing file fails the first question anyone asks: is there an SDS and a CoA in the folder? An outdated SDS passes that question. It has the right product name, all 16 sections and a revision date in section 16, which OSHA describes as "when the SDS was prepared or when the last known revision was made" (OSHA 3514, 2012). Nothing on the page says a newer revision exists.

A wrong-lot CoA passes for the same reason. The product name, grade and test list match. Only the batch number differs, and it differs from a number on the order or the container label, not from anything inside the certificate.

Why does checking each SDS or CoA on its own miss a mismatch with the shipment?

Checking each SDS or CoA on its own misses a mismatch with the shipment because currency and target are properties of the pairing, not of the file. A file can be right for one shipment and wrong for the next.

Three questions matter for an SDS. Is it the supplier's latest revision? That needs the supplier's current revision date, held outside the file. Is it for the grade on the order? That needs the order line. Is it in the language of the market? In the EU, the sheet "shall be supplied in an official language of the Member State(s)" where the product is placed on the market (REACH, Regulation 1907/2006, Article 31). That needs the destination.

A CoA has the same structure. ICH Q7 recommends that a certificate carry the batch number and that each test is listed "in accordance with compendial or customer requirements" (ICH Q7, 2000). Whether those are the right lot and the right test list depends on the shipped lot and the recipient's specification.

So a file-by-file review answers "is this a valid document?" The question that stops errors is "is this the document this shipment needs?", and it can be answered only with the shipment details beside the file.

Which details decide the SDS and CoA documents a shipment needs?

Five details decide the SDS, CoA and other documents a shipment needs: product, grade, lot, market and recipient. Fix them from the order and the dispatch record before looking at any file, because each one changes which version of a document is correct.

• Product: the identifier exactly as printed on the SDS and the label, so the sheet and the container name the same thing.

• Grade: the variant, viscosity class or concentration on the order line. Two grades can share a trade name and still have different SDS and CoA files.

• Lot: the batch number or numbers being shipped, taken from the dispatch record or container label, not from the last CoA on file.

• Market: the destination jurisdiction, which sets the SDS format and language. The EU language rule applies to the Member State where the product is placed on the market (REACH, Regulation 1907/2006, Article 31).

• Recipient: the customer's own requirements, such as a named test list on the CoA, an approval reference or a required certificate type.

Write the five details at the top of the check sheet. Every later step compares a file against this list, so an error in the list repeats in every check.

How do you check an SDS and CoA package step by step?

You check an SDS and CoA package step by step by running five steps in a fixed order, each with one action and one result. The order matters: a file that fails presence is not worth testing for currency.

1. Fix the required list. From the five shipment details, list every document the shipment needs: SDS per product and market, CoA per shipped lot, TDS, and any certificate the recipient names.

2. Check presence. Tick each required document as present or missing. A missing document stops the package until it is supplied.

3. Check currency. Compare the SDS revision date in section 16 with the supplier's latest revision. OSHA expects significant new hazard information to reach the sheet within three months (OSHA, 29 CFR 1910.1200, 2026), so an older date is a question to ask, not proof of a fault.

4. Check target match. Confirm the CoA batch number equals each shipped lot, and that grade, market version and language match the order and destination.

5. Check conflicts. Compare values that appear in more than one document, such as grade name, flash point or density, and, before release, resolve any difference that a typical value set against a measured lot result does not explain.

How do you match an SDS revision and a CoA lot number to the order?

You match an SDS revision and a CoA lot number to the order by comparing each against an outside record: the supplier's latest SDS revision date, and the lot numbers in the dispatch record. Neither match can be confirmed from the document alone.

For the SDS, read the revision date in section 16 and compare it with the latest revision the supplier has issued. Under REACH, a revised sheet is identified as "Revision: (date)" and must show where changes were made to the previous version (REACH, Regulation 1907/2006, Article 31 and Annex II). In the US, the updated sheet has to travel "with the first shipment after a safety data sheet is updated" (OSHA, 29 CFR 1910.1200, 2026).

For the CoA, list every lot in the shipment and pair each with one certificate. A split shipment from two lots needs two certificates. When a distributor or repacker reissues a certificate, ICH Q7 recommends that it refer to the original manufacturer and the original batch certificate, with a copy attached (ICH Q7, 2000).

How do you confirm the SDS and CoA package is ready to send?

You confirm the SDS and CoA package is ready to send when it passes five checks against the fixed list: presence, SDS currency, CoA lot, grade and market, and agreement across documents. A failure on any one holds the package.

The table below decides whether an outbound SDS and CoA package can be released, and what to do when a check fails.

The CoA row is the easiest to wave through: a certificate for another lot reads as complete, so compare the batch number against the dispatch record, digit by digit.

Record the result of each check on the sheet with the date and the person who ran it, so a later question about the shipment can be answered from the record. Such records are documented information, which ISO 9001:2026, published on 16 September 2026, addresses under support (ISO, 2026).

What do you do when two documents in the SDS and CoA package conflict?

When two documents in the SDS and CoA package conflict, hold the package, decide which document is the authority for the value in question, and get the other one corrected by its issuer. A conflict means at least one document is wrong for this shipment, so sending both passes the problem to the customer.

Each document answers a different question. The SDS is the regulated hazard record, so a hazard value such as flash point is settled by the current SDS revision, not by a brochure. The CoA reports measured results for one lot against its specification. The TDS usually gives typical values, which describe the product in general and are not limits for a lot.

A grade name that differs between files is an identity question: confirm which grade was shipped, then replace the wrong file. An SDS value that differs from the TDS is a currency question: check whether one predates a revision. A CoA result outside the acceptance limits on the certificate or the specification agreed with the customer is a quality question for the quality unit, not a paperwork fix.

In Lubinpla, a submission document check fixes the required document list before looking at the files you have, sorts what it finds into missing, expired, wrong-target and conflicting documents, and decides whether the package can be sent, with the lot and order details supplied by you because the platform keeps no lot or shipment fields.

Common mistakes when sending an SDS or CoA

The common mistakes when sending an SDS or CoA come from skipping the fixed list or trusting a file because it looks complete. Each mistake below has passed a file-by-file review.

• Sending the SDS that was on file at the last shipment. The supplier may have revised it since, and US rules attach the updated sheet to the first shipment after the update (OSHA, 29 CFR 1910.1200, 2026).

• Taking the most recent CoA in the folder instead of the certificate for the shipped lot.

• Sending one CoA for a shipment drawn from two lots.

• Editing a batch number or date on a certificate. A certificate issued by the quality unit should be dated and signed by authorized personnel (ICH Q7, 2000); a corrected copy has to come from the issuer.

• Using the SDS for one market in another, where format or language differs.

• Treating TDS typical values as the specification when comparing them with CoA results.

• Checking documents against the customer's last order rather than this one.