Content updated
A specification identifies proposed or agreed material limits. A Technical Data Sheet (TDS) explains context. A Certificate of Analysis (COA) reports an identified sample or batch. Reading them together is more useful than asking for an unspecified certificate.
Use each document for its actual question
If columns extend beyond the frame, scroll the table horizontally.
| Record | Use it to check | Does not establish |
|---|---|---|
| Specification | Identity/grade, limits, units, methods, revision and agreement status | That every value was tested on every batch. |
| TDS (Technical Data Sheet) | Description, typical properties and technical context | That typical values are guaranteed limits. |
| COA (Certificate of Analysis) | Sample/lot, tests, methods and reported results | Future batches or finished-food performance. |
| SDS (Safety Data Sheet) | Material-specific hazards and handling information | Food-grade status or order conformity. |
Technical basis: OSHA — Hazard Communication: Safety Data Sheets
Resolve identity and scope before values
Match the offer, specification and COA: exact material, form/blend, producer/packing source and grade. A shared abbreviation can conceal another form or method. Confirm whether a specification is a reference example, proposed source record or agreed order version.
Keep a cross-reference between source, document title/revision, sample/lot and material. An older stored document does not necessarily describe the current offer.
Investigate a numerical disagreement
- Check analyte and basis: compound assay is not automatically a phosphorus expression.
- Match units, dry/as-is basis if relevant, solution concentration, preparation and temperature.
- For viscosity/gel results compare instrument/settings and the method’s recipe or ionic conditions.
- Distinguish typical value, limit and individual result; ask what “conforms” means if no result is listed.
- Clarify scope and method before deciding equivalent or nonconforming.
Certificates are separate evidence
A management-system certificate needs a named holder, site, scope, issuing body and validity review. ISO explains that external bodies perform certification; an ISO name nearby does not make every product certified.
Source/product declarations need their own identity and conditions. Ask about Halal, Kosher, allergens, GMO, origin or other records for the specific source; do not assume a complete package exists.
Technical basis: ISO — Certification
Connect sample review to receiving checks
A representative COA supports early review. For an order, agree source/grade/specification version, expected batch records and deviation handling. Separate document review from sampling/testing required by the buyer’s acceptance plan.
These are matters to agree for a purchase, not evidence of an audited IngredientCore receiving, traceability or change-control system.
Request version and sharing permission
- Give product/grade, food application, market and review purpose.
- Name relevant records and methods; ask if current applicable versions can be shared.
- Resolve issuer/site/grade differences and missing units or methods.
- Agree a suitable sharing route for restricted files; a hidden public link is not protection.
Sources and scope
Use identity references, technical explanations and food-system studies for their stated purposes. Match each reference to its stated material, food system and test conditions.
- OSHA — Hazard Communication: Safety Data Sheets
US hazard-communication context; an SDS is not a food-grade certificate or batch acceptance report.
- ISO — Certification
Certification and independent issuing bodies; not verification of any company’s certificate or its coverage.