How to Read Sugar Specifications and a Certificate of Analysis

Start with a document review sheet

Open the agreed specification and the complete report side by side. Create a review sheet with one row for each required test and separate columns for the specification reference, acceptance criterion, reported result, unit, method and outstanding question. Keep the original wording and value when entering the data.

This makes an omission visible. A blank result should remain an unresolved item until the issuer explains it; it should not disappear because the other rows look satisfactory. The worksheet is a practical reading aid, not a replacement certificate or a new set of product limits.

Check the identity and version of the report

Read the first and final pages before studying the analytical values. Note the report identifier, laboratory or issuer, issue date, sample description and any amendment or replacement notice. Where a report is supplied as screenshots, request the complete issued document so that footnotes, qualifications and the authorization section can be reviewed.

A revision needs an explanation. If two files have the same report number but different values, ask the issuer which version is authoritative, what changed and whether the earlier version has been withdrawn. Preserve both files and the clarification in the purchasing record; do not edit the certificate yourself.

• Check that page numbering and report identifiers agree throughout the file.
• Distinguish the date of sampling, receipt, testing and report issue where they are provided.
• Ask whether an attachment, appendix or subcontracted test report forms part of the result.
• Record an unreadable field as a question instead of guessing its meaning.

Read what was actually sampled

A sugar test report describes the material submitted for examination. Ask who collected the sample, where and when it was collected, how it was identified and which sampling record supports its connection to the goods being assessed. A laboratory receiving a customer-supplied sample may not have observed the collection or the consignment.

If the sample is described only as 'white sugar', request the missing identification before treating the result as evidence for a particular batch. If several lots are represented, ask how the sampling plan covers them. A favourable result from one unidentified sample is not enough to establish the condition of every bag or every lot.

Match the method, not just the parameter name

Sugar quality parameters become comparable when their definitions, methods and reporting basis align. If a specification requests conductivity ash and the report states only 'ash', ask the issuer to identify the measurement. Likewise, a polarization result and another measure of sucrose content should not be treated as interchangeable merely because both concern sugar composition.

For ICUMSA 45 sugar specifications or other refined white sugar specifications, capture the full method reference and its publication year. ICUMSA explains that the year is an important part of a method citation, and that its shortened numbering system removed secondary subject numbers. A differently formatted reference may therefore need a documented cross-check rather than an immediate rejection.

Ask the laboratory to confirm the method's scope and applicability to the material. Resolve an outdated or substituted method with the buyer's technical reviewer and the issuer; do not silently assume equivalence or change the agreed requirement after seeing the result.

Reference: ICUMSA: method numbering and publication years · ICUMSA: methods and their application

Keep units, basis and qualifiers attached to the value

Copying only the number into a spreadsheet can remove the information needed to interpret it. Preserve symbols such as '<' and '>', the unit and any statement about dry basis or as-received basis. Confirm decimal separators when documents move between languages.

For mass fractions, 100 mg/kg equals 0.010% by mass. This is only a unit-conversion example, not a recommended sugar limit. A correct conversion does not resolve a different analytical method or a different reporting basis.

A result reported below a stated reporting or quantification limit does not mean that the measured substance is exactly zero. If the specification limit is lower than the laboratory's stated reporting capability, ask whether the test can support the required comparison. Keep the laboratory's explanation with the review.

Ask how a pass or fail statement was reached

A number near a limit needs careful interpretation. Where a laboratory issues a statement of conformity, ask which specification and decision rule it used, and how measurement uncertainty is handled where relevant. ILAC G8 discusses these decision rules; it does not provide one universal rule for every test or purchasing situation.

Do not create an extra tolerance after receiving an inconvenient result. If the decision basis is unclear, ask the laboratory and the buyer's qualified reviewer to explain it against the applicable requirement. Record their conclusion and the supporting report version before closing the review.

Reference: ILAC G8: decision rules and statements of conformity

Verify the issuer and the relevant accreditation scope

COA verification should distinguish report authenticity from laboratory accreditation. For an authenticity question, contact the issuing organization through independently obtained contact details and quote the report number. A logo or a QR code on a forwarded file is a starting point for a check, not its conclusion.

Where accredited testing is required, verify the laboratory's current status and relevant scope with its accreditation body. Check the applicable testing activities rather than assuming that an accreditation symbol covers every result on the page. ILAC provides a route to accreditation-body directories and explains how status and scope can be checked.

A manufacturer-issued COA and an independent sugar laboratory report identify different issuers. Record who performed the work and what evidence your agreed review requires; do not describe a document as independent without checking that fact.

Reference: ILAC: checking accredited bodies, certificates and reports

A worked example: satisfactory figures, unresolved evidence

Imagine a purchasing file in which the approved specification is revision C, the report refers to revision B, and the sample code does not appear in the accompanying identification record. The numerical results look acceptable against the values the reviewer expected. This example is fictional and describes a document-review situation, not a Zenith Eclipse shipment.

The first action is to record two questions: which specification was used, and how does the sample code connect to the material? Ask for an issuer-confirmed explanation or an appropriately amended report. The figures alone cannot answer either question.

Close each question with a dated response and the responsible reviewer's decision. This preserves the distinction between 'the reported numbers look acceptable' and 'the evidence has been checked against the correct requirement'.

A sugar specification checklist for your next review

Use the following questions as a concise request for clarification. Select the items that are actually missing from the file, identify the report reference and give the issuer enough context to respond precisely.

• Please confirm the current report version and whether it replaces an earlier issue.
• Which specification reference and revision were used for this assessment?
• What record connects the sample identifier to the material under review?
• Please confirm the complete method reference, including its year, for the unclear result.
• What unit, reporting basis or qualifier applies to this value?
• Does a missing entry mean not requested, not tested or not reported?
• If conformity is stated, which decision rule and applicable uncertainty treatment were used?
• Where accreditation is required, which relevant activities are covered by the laboratory's current scope?

Keep a clear record of the final review

Save the original specification, issued report, sampling evidence, questions, responses and final review record together. Identify who reviewed the documents and when, and keep superseded versions distinguishable from the current file.

This guide helps organize a document review. Product acceptance remains a decision against the agreed requirements and applicable technical assessment; reading a certificate does not replace testing or establish facts that the report does not cover. For a supply enquiry, use the separate Zenith Eclipse sugar page and share any unresolved document questions with your requirements.

Reference: Zenith Eclipse sugar supplier page