Guide hub

Documentation and Quality Guide

A practical overview of product documentation, batch-specific document requests, traceability questions, and how different document types support technical and commercial review.

Direct answer

COA, TDS, SDS, declarations, allergen information, and traceability records answer different questions. Batch-specific or customer-specific documents may need a direct request and should not automatically be publicly indexed.

Key takeaways

  • A COA is batch-focused; a TDS is product-focused; an SDS is safety-focused.
  • Declarations and allergen information should be reviewed for the specific product and market.
  • Batch-specific documents belong in controlled communication, not broad public pages.

Purpose of each document

Documentation requests should identify the exact product family, category context, product code where available, intended market, and whether the request is batch-specific or general.

DocumentPrimary purposeImportant note
Certificate of AnalysisBatch-related analytical or conformity informationMay depend on a specific lot or production batch
Technical Data SheetProduct properties, handling, and application informationUsually product-focused rather than batch-specific
Safety Data SheetSafety, handling, transport, and hazard communicationMust be reviewed for the relevant product and jurisdiction
Declarations and allergen informationCustomer, market, or compliance review supportMay require a direct request and current review

Batch traceability

Traceability relies on accurate product identification, category context, batch or lot number, date information, and customer/order reference. Product codes in catalogue data should not be treated as globally unique until collisions are validated.

Document request process

Send the product family, product code if known, category name, destination market, requested document type, and whether the document must refer to a specific batch. Avoid publishing batch documents publicly unless there is a deliberate business and compliance reason.

  1. Identify the product with category context plus code or canonical product ID.
  2. State the document needed: COA, TDS, SDS, declaration, allergen information, or traceability support.
  3. Include destination market and customer use case.
  4. Wait for the reviewed document rather than copying claims from a catalogue page.

Responsible use of documents

Public educational pages should not invent certifications, regulatory statements, allergen claims, or universal suitability statements. When in doubt, request current product documentation.

Related guides

Sources and references

  1. Sly Commerce catalogue category data Sly Commerce 2026-06-26URL: https://slycommerce.com/productsLive product-family and category-routing context only; not product-specific suitability claims.

Request a product document

Tell us the product, category, batch if available, destination market, and document type needed.