Cosmetic COA vs. specification vs. SDS: what each document tells you

Start with the question, then choose the document

A retailer asks for a COA. Your manufacturer sends a file called Product Safety.pdf. Before forwarding it, determine what the retailer is trying to establish. Do they need results for the shipment they will receive, an overview of product hazards, or the quality limits used by the factory? Similar file names do not make these equivalent requests.

This guide is an operational review method for beauty brand teams, not a universal testing protocol or a finding that every cosmetic must carry every document described below. Treat the suggested checks as a way to prepare a clear question for the manufacturer or qualified reviewer. Their scientific assessment and the recipient’s acceptance remain separate decisions.

A specification defines the acceptance criteria

A product specification identifies what will be assessed, its acceptance criteria, and the methods used. FDA’s cosmetic inspection guidance discusses checking materials and products against specifications. It is guidance, not a universal template for this article’s suggested fields. FDA inspection checklist.

For your own record, ask the issuer to identify the specification number, revision, effective date, product code, and applicable manufacturing stage. Keep the approved revision linked to the product you are actually shipping. A new specification may affect how a result is interpreted, so the latest file in a folder should not silently replace the version a historical lot was assessed against.

As a hypothetical example, specification SP-014 revision 2 might state an appearance description and a pH range. Revision 3 might use a different range or method. Your task as an operations coordinator is to notice the difference and route it to the quality reviewer, not decide which revision should apply. Ask for the effective-lot boundary or another written explanation of applicability.

A COA is useful only within its stated scope

A lot-specific COA should make it possible to connect the reported analysis with the correct product and lot. This is reflected in actual supplier practice: Merck’s Sigma-Aldrich COA lookup uses the lot or batch number, with the product number available as an additional search field. That is an example of document retrieval, not a rule that all cosmetic manufacturers use the same format. Certificates of Analysis document search.

When reviewing incoming paperwork, look for the issuer, product identifier, sample or lot identifier, test dates, results, units, methods, applicable limits, and the person or function authorizing the report. Record gaps as questions. Some documents give only a conformance statement for a characteristic; ask the issuer and recipient whether the level of detail meets the particular request.

Distinguish actual lot results from a sample COA, typical values, or an example template. A representative document may help establish what a manufacturer can provide, but it cannot answer a request for an identified shipment merely because the product name matches. Likewise, a raw-material COA does not establish results for the finished cream into which that material was incorporated.

An SDS answers a different safety question

OSHA describes the SDS as a structured hazard communication document covering matters such as identification, hazards, first aid, handling, exposure controls, and physical properties. Its purpose differs from reporting the analytical results of a production lot. Hazard Communication Standard: Safety Data Sheets.

Be precise about applicability. OSHA’s Hazard Communication standard includes an exemption for cosmetics packaged for consumer retail sale and cosmetics intended for employees’ personal consumption at work. Do not turn a commercial request for an SDS into a claim that every retail cosmetic has the same OSHA obligation. Workplace materials and uses need their own applicability assessment. 29 CFR 1910.1200: Hazard Communication.

If an SDS arrives in response to a batch COA request, preserve the file but leave the batch request unresolved. Ask whether a separate analytical report exists. If the recipient really needs hazard information, confirm the formulation and product identifier on the SDS, and ask the issuer whether that revision covers the supplied product. Avoid interpreting the date printed on an SDS as proof of when a particular batch was made.

Match the product, version, and lot before reviewing results

GS1 distinguishes product-level identification from batch-level identification: a GTIN identifies a trade item, while a GTIN together with a batch or lot identifier distinguishes one lot from another. This helps explain why a product barcode alone cannot establish which production lot a document concerns. GS1 Global Traceability Standard.

Use a simple identity check before technical review. Compare the document with the request and with the identifiers your supplier confirms. Do not infer a matching rule merely because two codes share a prefix. Where bulk and finished-pack codes differ, request a written mapping from the party responsible for those records. Record any ambiguity before treating the file as usable.

• Product: match the commercial name with the manufacturer’s internal product or material code.
• Version: identify the formulation and specification revision relevant to the request.
• Stage: distinguish an ingredient, bulk material, filled product, and finished saleable product.
• Lot: match the requested lot exactly, or obtain the issuer’s documented explanation of an equivalent code.
• Scope: confirm the pack size, variant, site, or other detail only where it affects the request.

A hypothetical mismatch: the right serum, the wrong lot

Imagine a brand preparing a retailer response for a 30 mL serum, finished lot F-026. The supplier sends a report for bulk lot B-011 and an SDS with the correct product name. The report may be relevant, but the relationship between B-011 and F-026 is not established by those facts alone. Mark the COA as received with identity clarification needed.

A useful correction request would say: “We need evidence for finished lot F-026 of product SR-030. The attached report identifies bulk lot B-011. Please provide the finished-lot report, or a written mapping that explains how this bulk lot relates to F-026 and identifies what testing and release evidence covers the finished product.” This is a request for clarification, not an invitation to change a lot number on an existing report.

If the manufacturer explains that one bulk lot supplied multiple filling runs, ask your reviewer which additional records are needed for this response. Keep the original report, the explanation, any new report, and the review decision together. The reviewer may accept a combination of records, request more information, or reject the evidence for that purpose.

Do not make the document prove more than it says

A COA does not, by its title alone, establish that every marketing claim is supported, that an ingredient statement matches final artwork, or that a retailer has accepted the product. Treat those as separate questions with their own evidence and decision owners. Even a technically sound report can be irrelevant to a particular claim or product version.

FDA explains that responsible persons must ensure adequate safety substantiation and keep supporting records; it does not prescribe a universal test list for cosmetics. FDA’s small-business cosmetics fact sheet. Treat a COA as evidence within its scope and route broader safety conclusions to an appropriately qualified reviewer.

Keep document review and commercial response status separate. “The correct report arrived” is a coordination milestone. “The qualified reviewer accepted this report for this requirement” is a scoped decision. “The customer accepted the submitted response” is a later external outcome. A single green checkmark should not hide those differences.

Make the next request specific enough to answer

Before sending another reminder, write down the requirement, product and lot, issuer, expected document type, known defect, deadline, and intended recipient. A supplier can respond more usefully to “please confirm which specification revision this report uses” than to “please send the correct compliance documents.”

For repeated requests, use a small set of correction reasons: wrong identity, wrong manufacturing stage, missing result detail, unclear revision, incomplete authorization, or sharing restriction. Allow a written explanation when a field is genuinely not applicable. The goal is a defensible review path, not forcing every supplier into an identical PDF layout.

BeautyAssured helps beauty brands coordinate evidence requests, corrections, and review around the product record. If a COA has arrived but you still cannot explain which product or lot it covers, discuss your workflow with us.