TDS vs SDS: technical and safety data sheet differences
Understand the difference between a technical data sheet (TDS) and a safety data sheet (SDS), with a cleaning product example and supplier request template.
View guide and template →QuiMatrix
Document Management for Personal Care Product Manufacturers
Manufacturers of shampoos, shower gels and skin care products need ingredient information from different suppliers. QuiMatrix brings technical data sheets, SDS and other documents together so R&D, quality, regulatory and purchasing teams can find originals, review updates and follow up missing information. For teams in Spain and Latin America, including contract manufacturers.
Request a demoIngredient information is spread across development, quality and purchasing
R&D retains a data sheet from development, quality receives a later specification and purchasing has an open supplier enquiry. When someone asks about the ingredient, it may be unclear which file was used, which is newer or whether the supplier response resolves the question. A shared record distinguishes received documents, outstanding reviews and earlier versions.
An ingredient document record that supports the team’s work
Connect each ingredient to its documents
Retain commercial reference, supplier, language and date for available files. Bring together technical data sheets, SDS, specifications, declarations and test documents used by the team, within the agreed scope.
Prepare development enquiries
Locate extracted information and check it against the original document. If an ingredient question has no documented answer, record the gap so that a specific clarification can be requested.
Keep the context of updates
When another version arrives, review changes before using it as a reference. Retain the connection to the earlier document to identify the information available during a previous review.
Coordinate requests and internal review
Purchasing can follow up with the supplier while quality or regulatory colleagues check the response. Separating “received” from “reviewed” helps prevent a record being closed simply because a PDF has arrived.
Example: completing an ingredient document record for a shampoo
Illustrative example: a contract manufacturer prepares an ingredient document review. It has a technical data sheet and a specification, but a question about test conditions remains open. The team connects the enquiry to the source document and requests the missing information. When a response includes a new version, both sources are reviewed and their relationship retained. The supplier report remains documentary evidence within its specific scope; the team assesses its applicability to the product under development.
Frequently asked questions
Is this intended for shampoo, shower gel and skin care manufacturers?
The workflow addresses ingredient and supplier documents used by these manufacturers. A demonstration reviews your document types, references and responsibilities to define the scope.
How does this differ from the cosmetics and fragrances page?
Both describe the same application. This page focuses on a manufacturer’s ingredient records, specifications, test documentation and reviews across teams. The cosmetics and fragrances page also explores fragrance documentation, IFRA documents and allergen declarations.
Can it support manufacturing for other brands?
It can support internal organisation of raw material and supplier documents. Permissions, information separation and any client exchange need to be defined during implementation; this page does not imply a client portal or automatic sharing of document records.
Does an ingredient document automatically substantiate a finished product claim?
The application helps teams find and review documents; it does not decide whether a test applies or approve product claims. A competent team needs to assess the information’s scope and the needs of the product and market.
See the workflow with your team’s needs in mind
Tell us which documents you manage and we will review how QuiMatrix fits your workflow.