Product specification, safety data sheet and certificate of analysis: what each tells a buyer, and what to check before using them.
Start with the right question
A product specification describes agreed product requirements. A safety data sheet, usually shortened to SDS, provides chemical hazard and safe-handling information. A certificate of analysis, or CoA, reports information for an identified batch. They serve different purposes. Asking for “the certificate” can leave everyone talking about a different document.
For a buying or technical review, first explain the decision you need to make. Are you assessing product suitability, preparing workplace handling procedures or checking a delivered batch? Give the supplier the product code, intended use and, where relevant, batch number. Clear identification is the least glamorous part of the request and often the most useful.
The specification sets the product requirements
Look for the product identity, version or issue date, characteristics and acceptance criteria relevant to your application. The exact content varies by material and agreement. Clarify what is measured, what is assessed by another method and what information is descriptive. Ask about any requirement your team needs that the document does not address.
Use the specification as part of an agreed technical conversation. It cannot communicate every assumption in a project by itself. If your manufacturing process, packaging or sales market creates a particular requirement, discuss it explicitly. Make sure the approved version is the one purchasing and quality teams are working from.
The SDS supports safe handling
HSE explains that safety data sheets provide information used to assess chemical risks at work. They include hazard and handling information and support the employer’s assessment. The SDS itself is not a workplace risk assessment. Receiving the document does not complete that task.
Check the material identity, supplier details, issue date and the information relevant to your work. Ask for clarification when handling, storage or emergency instructions are unclear. Share the document with the people responsible for workplace controls. Do not use it as proof that a flavour or fragrance is suitable for an unrelated finished-product application.
The CoA belongs to a batch
When requesting a CoA, provide the batch or lot number from the supplied material. Check that the document identifies the material you received and the relevant batch. Review the tests and results or statements reported against the applicable requirements. CoA formats and reporting practices vary, so ask what any unfamiliar field means.
A specimen CoA can help with supplier qualification, but it should be identified as a specimen. It does not report the results of the batch sitting in your stores. Keep the batch-specific document connected to the delivery and your own receipt records so later questions can be traced back to the correct material.
Keep the whole file connected
Build a document register around product codes, batch references where relevant, issue dates and responsible owners. Record which version your team reviewed and what further information is outstanding. If the material or intended use changes, ask whether the documents need updating. Avoid quietly inheriting an old approval into a different project.
These three documents are important pieces of a technical file, with different scopes. Other information may be needed for your product, market or claims. This guide explains the distinction; it is not a complete compliance checklist or legal advice. Bring your technical requirements into the conversation early. Good paperwork should make the next decision clearer.
Sources & further reading
General guidance for project planning. Technical requirements depend on the actual formulation, intended use and market.
