Start by identifying the sample
Before reading numbers, confirm what was tested. The report should connect to a recognisable product or sample description. A generic peanut report is not automatically evidence for a masala peanut pack, and a Shengdana Chutney report should not be silently reused for Jawas Chutney.
ZANZAN links separate reports for Shengdana Chutney, Jawas Chutney, Masala Peanuts and Salted Peanuts. Product-specific linking reduces the chance that a customer applies one result to the wrong recipe.
Find the laboratory and dates
Look for the laboratory identity, sample receipt or testing dates, report date and any accreditation or scope information shown. Dates provide context; they do not by themselves tell you whether a current pouch is within its best-before period. For that, use the batch and date declaration on the physical pouch.
Read the parameter, method and unit together
A number without its unit can be meaningless. Protein reported as grams per 100 g is different from milligrams per serving. Sodium may be expressed in milligrams, while energy may appear in kilocalories. The test method explains how the parameter was determined and may affect how results can be compared.
Never compare two numbers until the parameter, basis and units match. If one value is per 100 g and another is per serving, convert them carefully or use the label's own serving information.
Why per-100 g results are useful
Per-100 g reporting provides a common reference that makes products easier to compare. It is not a serving recommendation. A chutney portion may be one or two teaspoons, while a peanut snack portion may be larger. Translate the reference value to the amount you actually eat.
Understand detection limits and result language
Reports may use terms such as not detected, below the limit of quantification or less than a stated value. These phrases do not all mean absolute zero. They describe what the method could detect or quantify under its stated conditions. Keep the qualifier attached to the number.
What one laboratory report can establish
A report can provide evidence about the tested sample for the listed parameters. Depending on its scope, it may help describe nutrition, composition or other measured properties. It can support label preparation and internal quality checks when used appropriately.
What it cannot establish
- It cannot prove a food will prevent, treat or cure a medical condition.
- It cannot replace the ingredient and allergen declaration.
- It cannot prove an unnamed competitor's product is unsafe.
- It cannot guarantee every batch will have perfectly identical values; agricultural ingredients naturally vary.
- It cannot tell you how much you personally should eat.
Better proof versus louder marketing
An evidence-led product page puts the relevant report beside the exact product, keeps the ingredient list visible and explains the limits of the data. Poor documentation may show impressive-looking numbers without naming the sample, unit or method, or may turn a nutrient measurement into a sweeping health promise.
ZANZAN's product pages let customers move from taste and ingredients to the linked report before checkout. The aim is not to overwhelm people with a PDF. It is to make the path from claim to evidence short and inspectable.
A seven-question report checklist
1. Is this the exact product I am considering? 2. Who performed the test and when? 3. Which parameter was tested? 4. Which method and unit were used? 5. Is the basis per 100 g, per serving or something else? 6. Does the result include a qualifier or detection limit? 7. Does the product page avoid claiming more than the report actually shows?
Use the report with the physical pack
The strongest consumer check combines three layers: the product page for convenient pre-purchase information, the report for measured sample data, and the physical pouch for current ingredients, allergens, batch, dates and storage. If those layers appear inconsistent, contact the brand rather than guessing.