QUALITY · CERTIFICATE OF ANALYSIS

The Certificate of Analysis, Explained

The per-batch document that turns a specification into evidence — what it must show, how receiving teams use it, and why we publish no invented results, signatures or certificate numbers.

Illustrative image — Close-up of a batch certificate document beside labelled sample bags and a clipboard on a laboratory bench Illustrative image

What is a Certificate of Analysis?

A Certificate of Analysis (COA) is the per-batch document in which a supplier reports a specific batch's test results against the agreed specification. If the specification is the contract, the COA is the evidence of performance against it — the document your receiving team uses to decide whether a delivery goes into stock or into quarantine. Every batch of egg ingredient you buy should arrive with one, and every COA should trace unambiguously to the physical packs it covers.

This page explains what a COA must show and how buyers use it. Two commitments up front, per our documentation policy: we do not display a sample COA filled with invented results, signatures or certificate numbers — our sample format is [SAMPLE COA FORMAT TO BE PROVIDED] — and we do not publish laboratory names or accreditations we cannot evidence.

Quick answer: a COA verifies one batch: it names the product and batch, lists the parameters tested, shows actual results next to the acceptance criteria from the specification, and carries a date and release authorisation. Buyers use it at receiving to accept or hold a delivery, and file it as the batch's quality record for traceability and any later investigation.

What a COA must show, field by field

Batch identification

The batch or lot number — identical to the code on your packs and shipment documents. This is the COA's reason to exist: without matching batch identity, a certificate is a brochure. The date/lot relationship matters too: production date, test date and shelf-life reference should reconcile with the batch code and the specification's stated shelf life.

Test parameters

The characteristics analysed for this batch — which should mirror the specification: physical (appearance, colour), chemical (moisture, protein, fat where relevant) and microbiological criteria. A COA testing different parameters than the specification defines is a mismatch worth querying.

Test results

Actual measured values per parameter — not "conforms" alone. Real numbers let your QA team judge margin against limits and trend consistency across batches; bare pass/fail statements hide both. Where a result can only be qualitative (e.g., appearance), it should still be reported against its reference.

Acceptance criteria

The specification limits each result is judged against, stated alongside the result. Result-without-criterion is unverifiable; criterion-without-result is unproven. Both columns must be present for the document to do its job.

Supplier documentation & release

Identification of the issuing party, a release authorisation (name/role of the person releasing the batch), and issue date. Electronic signatures or authorised sign-off are normal; what matters is that release authority is defined. Methods referenced per parameter complete a rigorous document.

How buyers use a COA in practice

At receiving: match the COA batch code to the delivered packs; review results against criteria; confirm nothing is missing. Discrepancy means hold-and-query, not shelve-and-forget. In the quality file: COAs accumulate into the batch history that demonstrates ingredient control for your own audits and regulatory inspections — your supplier's COAs become part of your due-diligence evidence. In trend review: a sequence of COAs across batches reveals consistency — drift, tightening, sporadic outliers — that no single certificate shows. Serious buyers ask for history, not snapshots.

In verification: initial batches from a new supplier warrant independent laboratory verification against COA claims; as reliability demonstrates itself, verification frequency scales down. Our samples exist precisely for that first step. In investigations: when something goes wrong in your production, the batch COA — linked through traceability to production and testing records — is where the answer starts.

What a Sahya Agro COA covers

  • Product identity and batch number matching the shipped packs.
  • Parameters tested per the product's specification.
  • Results reported per parameter for the batch.
  • Issue identification for receiving verification.

Batch COAs are provided with shipped product and during qualification for evaluated batches.

What we deliberately do not show online

  • No sample COA with invented results — [SAMPLE COA FORMAT TO BE PROVIDED] during qualification.
  • No signatures, certificate numbers or laboratory names displayed for show.
  • No accreditation claims — status [CERTIFICATION STATUS TO BE CONFIRMED].

A COA's credibility comes from what it documents per batch, not from how it looks on a website. Ask for the real format with real batch documentation when we qualify — that is the version that matters.

[FSSAI LICENCE NO. — TBC] [CERTIFICATION TO BE CONFIRMED]
FAQ

COA questions

A per-batch quality document in which the supplier reports a specific batch's test results against the agreed specification — product and batch identification, parameters tested, actual results, acceptance criteria, dates and release authorisation. It is the batch-level evidence that a delivery meets what you agreed to buy.

Batch identification matching the packs, the parameters tested (mirroring the specification), actual results per parameter, the acceptance criteria they were judged against, production/test/issue dates, and release authorisation from the supplier. Result without criterion, or criterion without result, makes the document unverifiable.

Match the COA's batch code to the delivered packs, review each result against its acceptance criterion, and confirm the document is complete before the stock is accepted. Any mismatch — wrong batch, missing parameter, out-of-limit value — means hold and query, not shelf.

No. The specification is the standing definition of what the product must be; the COA reports one batch's actual results against it. You qualify a supplier on the specification and accept each delivery on the COA — the two documents work as a pair, and their parameter lists should match.

Actual results wherever the parameter is quantitative. Numbers let your QA team judge margin against limits and trend consistency across batches; 'conforms' alone hides both. Qualitative parameters like appearance should still report against their reference standard.

The batch code on the COA is the same code on your packs, your shipment documents and the supplier's production and testing records — the thread that lets a delivery be verified, a complaint investigated and any corrective action scoped. A COA without matching batch identity breaks that thread.

The sample format is [SAMPLE COA FORMAT TO BE PROVIDED] — shared during qualification with real batch documentation. We do not display a certificate with invented results, signatures or numbers on the website: a COA's credibility comes from what it documents per batch, not from how a sample looks online.

For the ingredient's shelf life plus your own product's traceability horizon — your supplier's COAs form part of your due-diligence evidence in audits and investigations. Retention periods belong in your quality procedures; retain at least as long as any product made with the batch remains in the market.

Yes for new suppliers: independent laboratory verification of initial batches establishes whether COA claims match reality. As reliability demonstrates itself over time, verification frequency typically scales down — a risk decision your QC plan owns. We provide samples for exactly this purpose.

REQUEST A QUOTE

Want our COA format?

Request it during qualification — with real batch documentation, not a showroom sample.